After updating zwavejs2mqtt addon to 0.9.1, binary_sensors not updating

xldy · April 2, 2021, 1:59am

I just updated zwavejs2mqtt addon to 0.9.1, and some binary_sensors are no longer updating. They tend to be the older ones - door windows sensors from gocontrol, a PIR sensor as well. The logs show that they are still updating the status, but the lovelace does not show changes in doors being opened or closed. Newer sensors are working fine.

Eg:
2021-04-01 18:11:55.457 INFO ZWAVE: Node 17: value updated: 32-0-currentValue 255 => 0
2021-04-01 18:11:55.472 INFO ZWAVE: Node 17: value updated: 113-0-Home Security-Sensor status 0 => 2
2021-04-01 18:12:00.706 INFO ZWAVE: Node 17: value updated: 32-0-currentValue 0 => 255
2021-04-01 18:12:00.719 INFO ZWAVE: Node 17: value updated: 113-0-Home Security-Sensor status 2 => 2.

I tried reverting to the old snapshot, but it didn’t help at all. Any one run into similar issues? I also tried a network heal, which seems to have optimized the network, but it didn’t help the old nodes.

Edit: still no clue what’s going on, but I successfully reverted to 0.9.0 after a second try, and everything is normal like before. I guess I’ll be waiting for 0.9.2…

photo64 · April 2, 2021, 3:32pm

I am having a similar issue with door/window sensors and tilt sensor from Vision Security (older Monoprice). How did you revert back to 0.9.0?

LeoGr13 · April 2, 2021, 6:08pm

Similar issue on my system. Got 2 fibaro universal sensors with reed switches and both are not updating anymore. Refresh values works.

@photo64 i think the best way to revert back, is to use your snapshot (in case you created one before the zwavejs2mqtt update)

xldy · April 2, 2021, 6:16pm

Indeed, use your snapshot, and remember to unselect autoupdate if you have it selected. If you can’t start the addon following the restore, just restart homeassistant, and it’ll be ok.

photo64 · April 2, 2021, 6:35pm

I was able to restore from the partial snapshot and I think most everything is working except that when I go to the webui for zwave-js2mqtt nothing shows up. Would I need to restart the add-on?

xldy · April 2, 2021, 6:47pm

Yes try restarting, and if it doesn’t start, just restart homeassistant.

photo64 · April 2, 2021, 6:53pm

Well something is messed up. After restarting the add-on and restarting HA I still have nothing showing in the webui for zwave-js2mqtt.

xldy · April 2, 2021, 7:05pm

Maybe check the supervisor logs and the zwavejs and zwavejs2mqtt logs and see what’s going on?

photo64 · April 2, 2021, 7:08pm

I don’t see any errors in the log and just about everything seems to be working. Unless it didn’t like that I removed some dead nodes after upgrading yesterday.

**Edit -> I did find this error in the supervisor but not sure if it is related. I assume it is

21-04-02 19:06:44 ERROR (MainThread) [supervisor.api.ingress] Ingress error: 400, message=‘Invalid response status’, url=URL(‘http://172.30.33.3:8099/socket.io/?EIO=4&transport=websocket&sid=GuUWqNnZTkE2hvZ7AAAG’)

xldy · April 2, 2021, 7:33pm

Don’t think that’s related. Check your network graph to see if it makes sense. Maybe your network needs to be healed?

photo64 · April 2, 2021, 7:41pm

Graph looks fine. Most everything seems to be working although I am still having an issue with the Vision security door/window sensors. Binary Sensors still not reporting correctly. I wouldn’t expect that to have messed up my Control panel webui.

xldy · April 2, 2021, 8:03pm

What happens if you try to restart (either thru the button itself, or stopping and then starting) the addon? As I said my webui was messed up too before I restarted HA entirely. But looks like you’ve already restarted, so I’m out of ideas ATM.

photo64 · April 2, 2021, 8:13pm

Phew . . . . I asked on HA Discord and was told to clear my cookies for the webui page and it worked. The Control Panel is back. Sensors still don’t work unfortunately.

xldy · April 3, 2021, 5:19am

Great that you were able to sort it out! I usually just refresh the page - even when the instructions said to clear the cache, refreshing worked.

Dave2 · April 12, 2021, 9:35pm

Is there a reported github issue for PIR sensors that are now reporting 0, 255 instead of motion? I’m having the same issues and can’t seem to revert as each time I do it auto-updates back to the latest version before I can stop it.

xldy · April 13, 2021, 6:54am

By “now” do you mean version 0.9.1? The latest 0.11 works fine for me. In any case, I’m not aware of any such issue on github.

Remember to unselect the auto-update to latest version thingy at the addon page, before reverting.

Dave2 · April 13, 2021, 3:48pm

I’m using zwaveJS (not MQTT) V0.1.17 and I have two issues that seem related to the thread above since zwavejs2mqtt’s code base uses zwaveJS as I understand it:

ZP3102 by Vision Security (PIR sold by Monoprice) - Motion is no longer a bool since the update, it is identified as a “basic” sensor and returns the value 0 or 255.
ZD2102 by Vision Security (Door / Window sold by Monoprice) - has not changed from on state since updating to V0.1.17.

xldy · April 14, 2021, 4:46am

Ah, looks like the same problem indeed. 0.1.18 was released earlier today, maybe try that?