Patience… Hah. What I did was have the Zwave2Mqtt page up on that node and select re-interview, but dont hit go yet. Then, on the ZCOMBO, near your Z wave stick, pull the battery, press and hold the test button, reinsert batteries until it beeps once and release. Click enter for re-interview quickly. It should beep again in maybe 5ish seconds. If you’re lucky, itll pick it up the make/model in a minute or so. I had to re-try a few times for each of them, trying re-interview, then heal the next time on that node only. It just picked it up eventually. Dont be too quick at re-trying the re-interview/heal commands either. I think that jams up the network.
I did not exclude and re-add, only re-interview and heal.
For instance, when I updated today, it took the ability to manually put in the device path, which brought down my Z-wave network until I figured out that the device path was not absolute but logical and since that was changed it left it blank. I am usually good at stopping breaking changes and release notes. However, I did not catch this change…please show where this is at.
I just updated to zwavejs2mqtt 1.1.1 which obviously restarted my network. I have a couple battery-powered leak sensors, and i’m surprised that zwavejs2mqtt basically completely forgets everything about those leak sensors until they check in again, which is pretty infrequent. Is there some setting I can use to enable caching of the device info for battery powered devices so that they don’t just show as unavailable in HA until their check-in?
I think the startup process is similar as before, it just takes awhile to populate and shows up differently than were used to. I noticed the same thing the first time I restarted. It seemed like everything was gone. But even sleeping devices populated completely as Asleep and Restartfromcache after a few minutes. It was definitely unnerving when I spent hours getting things set up and it all went away. Just restarted again this morning and saw the same thing, but it all came back within 5 or so minutes.
It would be nice to have some kind of network ready event again. I cant find anything to indicate this with ZWaveJS
For those of you with locks, update your ZWaveJS (or ZWaveJS2MQTT) containers. They made an update that properly updates for manual lock/unlock operations. I have a Schlage BE468 and BE469. Both work great now.
Has anyone had luck with battery powered motion sensors? I get them to show up on the zwavejs2mqtt server and the nodes do habe a binary sensor and multi sensor there, but when I start the Zwave js integration in HA, then the nodes are found but no entities are created. Any help would be highly appreciated, because now I’m stuck with a setup where no motion sensors are working…
Check for disabled entities under that device in Home Assistant. Also, restart Home Assistant again. It seems its required to be restarted when you make some updates to Zwave now. Hopefully that will get fixed soon.
Yes as @gregg098 posted look for those and if needed reinterview the node. Some of my battery powered ones are multi sensors and I had to sit there and press the wake button every few seconds while it interviewed it to pull in all of the properties of the sensor.
Where can I find those? When I go to the node in the integration then there is only a box for “Device info”, “Automations” and “Scripts”. Nothing about disabled entities.
I have hardwired devices that after every restart I have to go in and tell it to interview them. Kinda frustrating especially since a few of them are kinda critical devices. But I’ll ride out the bumps.
I’m trying to configure the Z-Wave-JS addon to connect to a RaZberry running on a separate Pi running ser2net. Looks like @dbrunt was successful in getting the configuration to accept:
For me, this fails validation in the configuration with this error:
Failed to save addon configuration, not a valid value for dictionary value @ data[‘options’]. Got {‘device’: ‘tcp://192.168.1.123:4000’, ‘network_key’: ‘xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx’}
I’ve tried with and without the single quotes and it makes no difference. What else could be different causing validation to fail? (running latest version 0.1.6)
I had to pull and reinsert the battery in all of my motion sensors, leak detectors and door/window sensors before they would show up as entities. I’m sure they would have eventually reported in on their own, but I have easy access to them and didn’t want to wait.
I accomplished this using usbIP where the USB device is mapped across to my server. For the network key I set that in the UI of the zwavejs2mqtt and not in a docker file or anything.
