To fix the vibration sensor, do I need to create a GitHub issue or is it not necessary?
Yeah, that’s better so I don’t forget. Thanks!
How do you proceed if a device is not recognized by Gladys and is not present in the Zigbee list?
Yet it is a Philips hue 9290022168 bulb.
You can contribute to the Zigbee2mqtt project Zigbee2MQTT
You will then need to be patient (as there are two projects to release, one of which we don’t control).
hello @cicoub13,
It’s me again!
Another issue with the XIAOMI cube
On Gladys side, it is still considered as a button click:
While on port 8080 we have:
Problem on Gladys side or integration?
To make it easier to sort, I created a « zigbee2mqtt » label on GitHub that groups all issues related to the services:
I did the same for the Z-Wave integration. Don’t hesitate to create other labels for other integrations to make it easier to navigate 
Hi, I’d like to, but I don’t know anything about GitHub, English doesn’t like me at all, I really don’t know how to word it. I’m stuck 
Hello everyone.
I have finished developing a new feature for Zigbee2Mqtt: bulb color management 
But I don’t have any and I need your help 
If any of you are willing to test my image with Zigbee-compatible bulbs (Philips, Aduro, Ikea, Innr, Osram, …), that would be great.
Same principle as previous tests, this command allows you to launch a container with my image. 
You must delete containers related to Zigbee2Mqtt before or run this command on a Gladys instance where the Zigbee2Mqtt service has never been launched.
docker run -d \
--log-opt max-size=10m \
--restart=always \
--privileged \
--network=host \
--name gladys-zigbee2mqtt \
-e NODE_ENV=production \
-e SERVER_PORT=1080 \
-e TZ=Europe/Paris \
-e SQLITE_FILE_PATH=/var/lib/gladysassistant/gladys-zigbee2mqtt.db \
-v /var/run/docker.sock:/var/run/docker.sock \
-v /var/lib/gladysassistant:/var/lib/gladysassistant \
-v /dev:/dev \
-v /run/udev:/run/udev:ro \
cicoub13/gladys:dev-zigbee2mqtt
The corresponding PR is here: Zigbee2mqtt - Add light color feature by cicoub13 · Pull Request #1203 · GladysAssistant/Gladys · GitHub
Hello everyone!
I’m bumping @cicoub13’s post. It would be really great to get feedback on this development before merging it, since @cicoub13 doesn’t have a lightbulb, they kindly developed the « blind » feature for those who requested it. But if no one provides feedback, it doesn’t really encourage developing features blindly for others ^^
On my side, I have bulbs with brightness and color temperature features… can that help? Or is it specific to bulbs with different colors?
That said, I also have a Xiaomi Smart Color Bulb in my plans… I don’t even remember which protocol it works with (but I don’t think it’s Zigbee…)
I don’t have a Zigbee light bulb device, so I can’t help. Otherwise, it would have been done by now…
Good evening,
I have just acquired Philips lamps with the color-changing feature.
I will test the image and provide feedback as soon as I can
So, I’m answering myself.
@cicoub13 I just finished testing the color management. For my part, I encountered no issues changing the color; it’s instant, and always correct.
However, the bulb temperature management is no longer functional (even though before we could only see the value).
The feature still appears in the device, but on the dashboard, I can neither add it nor control it.
In any case, already thank you for the work done 
Hello @alex. With the Zigbee2Mqtt integration, color management has been developed but is not yet available (it is currently being tested). If the tests are successful, it will be integrated into the next version of Gladys.
Thanks @JeuFore for testing, great news for color management.
I will look into the temperature issue tomorrow (and I will probably need you to retest).
Actually, I enabled the « Lighting Temperature » feature as modifiable (it was previously read_only). But the line in the dashboard didn’t handle it 
I therefore have three possibilities:
- leave the feature in
read_only. In this case, it’s impossible to modify the value from Gladys and it is displayed as a number (as today).
- enable the feature as modifiable with a simple range (like brightness)
- add a bit of color to visually understand that it’s the temperature (ranging from blue to yellow). If you have other style ideas, feel free.
In the background
or in the range
What do you think?
I validate in the range it’s great @cicoub13
Likewise, I validate within the range.
Hello, small question. Is it possible to delete the log when a feature is not configured?
Currently, I have Gladys logs filled with the following messages:
Summary
2021-06-20T21:38:20+0200 handleMqttMessage.js:106 () Zigbee2mqtt device Hue play 3, feature color not configured in Gladys.
2021-06-20T21:38:20+0200 handleMqttMessage.js:106 () Zigbee2mqtt device Hue play 3, feature color_mode not configured in Gladys.
2021-06-20T21:38:20+0200 handleMqttMessage.js:106 () Zigbee2mqtt device Hue play 3, feature color_temp_startup not configured in Gladys.
2021-06-20T21:38:20+0200 handleMqttMessage.js:106 () Zigbee2mqtt device Hue play 3, feature linkquality not configured in Gladys.
2021-06-20T21:38:20+0200 handleMqttMessage.js:106 () Zigbee2mqtt device Hue play 3, feature update not configured in Gladys.
2021-06-20T21:38:20+0200 handleMqttMessage.js:106 () Zigbee2mqtt device Hue play 3, feature update_available not configured in Gladys.
This is a tiny part of the thousands of identical lines…
I noticed another bug, when I make a lot of requests on the zigbee (~400/m), Gladys can no longer keep up and the different pages cannot load.