-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is it possible to update the MQTT topics and message structure? #1075
Comments
Documentation: https://github.com/Koenkk/zigbee2mqtt.io/blob/dev/information/mqtt_topics_and_message_structure.md |
@Koenkk On the first three points everything is fine, thank you very much! |
@Koenkk Are we closing this issue or can something be done on the last post? |
I will look into the last, should be doable. |
Added |
@Koenkk Great, thanks, I figured out where to add this. I think this can be closed Issue. |
@Koenkk Hurried up, changing last_seen via mqtt works correctly with the Ikea switch, but the disable command is not perceived as a dimmer. Feb 23 16:16:48 raspberrypi3 npm[32239]: zigbee2mqtt:info 2/23/2019, 4:16:48 PM Set last_seen to ISO_8601 Feb 23 16:17:01 raspberrypi3 npm[32239]: zigbee2mqtt:info 2/23/2019, 4:17:01 PM Set last_seen to disable |
Can you check with the latest dev branch? |
@Koenkk Thank you very much, now everything works as it should! |
@Koenkk I tried to change the above files for the |
@antti365 please make a PR with the changes you made (doesn't have to be working), we will continue there. |
Something like this ...
Also, if possible, I would like to see in the output of the topic zigbee2mqtt/bridge/log "devices": a list of all devices with a battery value for all devices that transmit this parameter.
And finally, at the start of the bridge, he could report in a certain topic about the state permit_join and log_level.
I would be very grateful for the help in adding these new options.
Update:
4. Another would be to add the setting of the parameters last_seen and elapsed through mqtt.
The text was updated successfully, but these errors were encountered: