Everything (all zwave) mostly working apart from some devices at the end of Aotec zwave extenders. Stange as worked fine before on the Fibaro HCL they replaced. i moved the hub closer to include them, and now waiting for things to settle.
anyway while waiting i thought i would update the zwave type as it seems it defaults to the older/legacy. when i do this it defaults to US so all the devices show pending.
i then set to EU (as im in the UK) and save. It then reverts to US.
after repeating this for some time i am stuck and hoping someone else may know what to do (before abandoning and reverting to legacy)...
Oh its a c8 pro if that helps
ok, partially answered myself. shutdown the hub and powered off for 30 seconds now EU setting seems to have stuck.
now have to work out why all the devices are pending, but they do appear to work
If the "Pending" devices are working then they likely convert to check-marks on their own after a while. You can also try:
- Hit the "Refresh" button for each device on the Z-Wave Details page
- Wake up the "Pending" devices by triggering them - turn switches on/off, open close contacts, motion in front of motion sensors, etc. That worked for me when I had a bunch of devices pending at one point after an update
What hub platform version are you running?
Are you using Z-WaveJS or ZipGateway?
Changing to z-wavejs is what triggered the pending. Pending messages went away but loads of lag and security listed as legacy. Long story short I've had to re-add all the devices (about 5 left to remove &re-add), and things starting to improve . Wish it had been enabled by default as having to open up walls to get at fibaro Dimmer and switches is a right pain for 2 days solid.
The js version seems to work ok once it settles but below is typical workflow for a device
- Patiently remove device. This is very miss or hit (mostly miss). For fibaro devices you basically follow the same process as adding (tap S1 3 times or same with button on device).
- Patiently add
- Previously when device found it would trigger wizard immediately, now it takes about 30 seconds after the message about finding a device
- It finds the device, change the type to the community one (as the default one is missing most feature), save. Then enable "setting" on the preference page and save - this basically reveals all the fibaro settings (brilliant).
- Then repeatedly click configure until the message on the right says update isnt required. This is the same as previous zwave type so in theory good, but...
- At this point the device locks up when you turn it on (turning off does nothing)..
- Settings -> zwave -> find the device and click refresh a few times and the name of the device will randomly change to the device model (e.g. fg-212), but the device now works again
- Rename it again and reset it to the community driver again save and configure
- Now it locks up again, but will probably fix itself over time. However after about 2 devices it all grinds to a halt, so reboot hub (no need to unplug), and then all good.
So some bugs it seems, largely to do with refresh and community "driver" being overwritten by the default "supported" one. It would be really good if the community versions were integrated as they are Fantastic!
Only concern at this point is that maybe there is a memory leak what with the required reboots over time, but I'm hoping not the case if not adding devices.
As a bonus my aotec zwave range extender 6 seem to work properly in the js version!
Ok, reverted. While possible to get things close the following problems:
- Pain to setup with restarts (that only fix things temporarily) and lockups of switches randomly for community dimmer driver
- System driver is responsive, but stays stuck in toggle switch mode despite making changes (I have momentary switches with fibaro so I can control the dimmer). Nothing triggers it to push out the switch change.
- Dashboards = total mess, I think because of the other problems (seems like confirmation messages not sent or received or someone for each action).
Anyway reverted to legacy and things seem ok for now ...
