I’m fairly new to OH… started using 2.5 on RPI3 about a year ago but didn’t get far due to an accident befalling the RPI then not having time. So I just started with OH3 on x86/Debian.
Zigbee2mqtt = working
MQTT.fx confirms that my zigbee devices respond as expected, e.g. I can toggle the relay output by publishing the relevant topic/payload.
Looking from the web UI of OH I can view the E1743 channel state [action/battery/lqi] changing in realtime.
For the (Sonoff) ZBR3 the lqi is displayed however the state always remains OFF. Same with the sitemap view. Using the app or BasicUI the state (as displayed in OH channels) can be toggled but the relay output does not change state.
I’m not convinced that OH is even publishing the ConservHeater topic.
I guess I’m missing something in the OH config; any pointers please?
As you have MQTT.fx you should be able to confirm this - can you?
Also, you may have fallen victim to the annoying bug where openHAB sometimes doesn’t properly register changes made to Things files (certainly an OH2 problem, not sure about OH3). You can restart openHAB, or do this.
How are you doing the toggling? Your Item is a String, not a Switch? Try changing
I stopped OH… I still see the relay announcing its state every 5 minutes. At least I assume this is the relay pushing, and not zigbee2mqtt polling the device.
After restarting OH:
I see OH log messages every 1 min: Starting MQTT broker connection to ‘127.0.0.1’ with clientid
Also looks an item has been corrupted that was previously ok
And I added this last minute - do set your Item to Switch:
Also
Instead of localhost, try using the actual IP address of your device (192.168.1.13, or whatever yours is)- that seemed to work better for me (though I set mine up some time back, so the issue may have been resolved by now).
Had some issues with Z2M… not touched the system since last post so expected it all to be functioning. However, no zigbee comms and Z2M publish failures when trying to send commands. Z2M log shows nothing of interest.
The frustrating part is OH shows MQTT devices as online/green. If there is a problem I’d rather show that in the UI/sitemap.
The OH log message " Try to restore connection to ‘127.0.0.1’. Next attempt in 60000ms" originates from (guess) a duplicate MQTT broker since the ID does not match that of the one defined with my zigbee.things file. This duplicate fails to connect since it is anon - my MQTT requires auth. I need to work out where it is defined… there is only one MQTT broker listed in things UI.
Thanks for the tip on adding state… my button on the sitemap works now.