Replies: 6 comments 20 replies
-
This due to the Changes will be available in the dev branch in a few hours from now. (https://www.zigbee2mqtt.io/how_tos/how-to-switch-to-dev-branch.html) |
Beta Was this translation helpful? Give feedback.
-
I also saw this on "update_available" and "update_state" sensors. I am fine if you would like me to open a bug for this. Thank you for the fast response. Regards |
Beta Was this translation helpful? Give feedback.
-
Thanks for release 1.18.3. Should this be fixed now in 1.18.3? Regards |
Beta Was this translation helpful? Give feedback.
-
Is this still on the roadmap for Z2M 2.0.0? Just asking out of curiosity. Regards |
Beta Was this translation helpful? Give feedback.
-
Thank you for release 2.0.0, i am now able to set "homeassistant_legacy_entity_attributes" via GUI. No more unneeded attributes and i hope my database volume is going down now :-) Regards |
Beta Was this translation helpful? Give feedback.
-
I have some troubles with the options here. I am using the Home Assistant addon and i am confused on how to set the config options correctly. If i set "homeassistant_legacy_entity_attributes" in the Home Assistant Supervisor config the following warning is logged:
If i restart the Addon within Home Assistant Supervisor the configuration.yaml does not have "homeassistant_legacy_entity_attributes" set. If i uncheck "Home Assistant legacy entity attributes" within Zigbee2MQTT GUI and restart it via Zigbee2MQTT GUI the configuration.yaml does have "homeassistant_legacy_entity_attributes" set. But this does not persist a Home Assistant host restart. So what is the correct way to set options here? In the Supervisor/Home Assistant GUI or in the Zigbee2MQTT GUI? Sorry if you are not responsible for the addon but i already created an issue here, but it seems that no one feels repsonsible for the Home Assistant addon as there are many open and unanswered issues. Do you know who is responsible for the Home Assistant addon? Regards |
Beta Was this translation helpful? Give feedback.
-
Hi!
I am using Zigbee2MQTT for a few weeks now and my HA database started growing. The cause are many state changes for new entities from Zigbee2MQTT. So i reviewed those a bit and found out that all of those sensors do report multiple attributes, here is an example:
This is a link quality sensor from a light and it has attributes like brightness, color mode and so on. Is this intended or just a configuration issue?
Regards
Richard
Beta Was this translation helpful? Give feedback.
All reactions