Yeah I did try that already. The issue persists with HASS offline and the Z-Stick unplugged.
Good idea to do one sensor only! I will try that and get back.
How are Z-Wave assocations created in the first place? I’ve never heard of them, and hadn’t made any changes to my setup when the issue started occuring. Odd…
Usually you have to manually establish the association using software or some sequence with the device itself. Like @aimc mentioned this was the inital idea behind them. A person without a hub can have lightswitch1 trigger lightswitch2 directly. Each manufacturer that supports it, though, can implement the pairing however they want.
How it happened with yours I have no idea…
Small info blurb:
FYI to future readers, what ended up fixing it for me was to exclude all the switches and dimmers being effected and re-including them into the Z Wave network.
Thanks for this post. I have currently the absolut same issue. First I thought is is a Hassio miss configuration.
Butt hassio withouth inserted the USB Z-Wave Controller stick: same issue. Even if the Raspberry with hassio (0.82.1) has no power. -> I will try to remove and add all Z-Wave devices.
You should be able to remove the association from the Zwave configuration menu without removing and adding. If there are battery powered devices, you will need to wake them to make changes.
I did a factory reset on my Zwave (controller, network key, HA) and added my nodes to the ‘new’ network.
Since then, no issue. But a lot of work. I had to open all my wall switches…
@mischoe sorry you had t go through that. Far too much work that didn’t need to be done. Creating and removing associations is a trivial thing through the menu. Hope things are better from now on.
This started happening to me this evening. It’s strange that it’s starting to happen to multiple people. I can’t say I’ve ever setup an association so something must be getting corrupted. I’m don’t think it’s an HA issue, but I’m wondering if it’s something that can be at least identified and maybe fixed programatically.
This just happened to me after restarting HASS! What’s really strange, is that this “effect” seemed to be applied instantly to several multisensors, which should not be possible as they would need to wake up first. Also, HomeID was shown as 0 in the logs and no Z-Wave devices appeared in the config section. After next restart, my devices were back in Home Assistant, but still turned on by the multisensors. I can’t see any strange associations on the multisensors.
I also had the issue after a reboot last week. All 3 of my Fibaro FGMS-001 got associated to broadcast group 255.
There is instruction is the documentation https://www.home-assistant.io/docs/z-wave/control-panel/#broadcast-group that is supposed to fix this issue. That didn’t worked for me, but you should try.
In last resort, I ended up factory resetting the sensors and now I cannot even add them back to HA. I love HA, but I’m very frustrated with Zwave ever since the node renaming feature was removed a few months ago.
Thank you for the link! I got it working by making a small appdaemon app, looping through all nodes and removing node 255 from their association. No idea how it happened, though.
When it happened to me I had to go through each zwave device using the zwave configuration screen and clear any associations to 255. It was a real pain in the backside.
can you post a copy of that code, or put it out on github and provide a link. That would probably be helpful for others if they have this problem.
Sure. It was just a quick and dirty loop trying to remove all associations.
for i in range(1,128):
for j in range(1, 10):
try:
self.log("Removing association {} from {}".format(j, i))
self.call_service("zwave/change_association", association = "remove", node_id = i, target_node_id = 255, group = j)
except:
self.log("error")thanks for sharing but where does this code go? or how do you implement it
In an appdaemon app. If you don’t have this set up, it’s probably easier to remove manually on problematic devices.
I have manually but it keeps coming back…
Any ideas on how to keep that from happening. I have 16 zwave devices setup, spread across light dimmers, lights switch, smart plugs, battery door contacts, motion sensors. It seams like I have to keep remove it from the Leviton dimmers, the Leviton outlet plug along with the Aeotec smart plug and the ZooZ motion sensor
Sorry, no idea. Since it happens with multiple devices, I would guess a bug on the controller side.
This has just happened to me. Out of nowhere a group association to 255 was added to both an Aeotec Multisensor 6 and an Aeotec Microdimmer on my network. I had an existing, trouble free zwave network that had grown over 5 years to 16 nodes:
I had just made a number of changes:
At this point I thought all would be well. But the laggy/unreliable network problem did not go away and I was seeing some callback errors and transmit timeouts in my OZW logs. I think the “all lights on” problem had begun but I hadn’t identified it as such since it seemed like it might just be delayed commands finally getting through. Upgrading to latest home assistant seemed like a good idea, in case my upgrade of python-openzwave had an incompatibility with the older one I was running. Unfortunately I ran into the UI becoming unresponsive and generating error messages that others seem to have reported with 109. I then rolled back to 108.9. I ran another network heal. I also observed that the Nanodimmer that was sitting disconnected on my table was not marked as dead in the zwave network.
And then the pattern of “all lights on” followed by “all lights off” problem became quite apparent as it repeated over time. There was no log of the lights on/off commands in the Logbook, the HA log, or what I could parse out of the OZW log. After this “all lights on” problem continued into the night I started googling and found this thread. Looked and found the two devices with 255 group associations and cleared them. Problem solved for now but concerned about how someone else said the associations kept coming back.
I’m really writing to confirm that this issue has been seen again more recently and provide all of my activities leading up to it in case it causes an “ah ha!” moment for anyone more knowledgeable about zwave and/or home assistant.
My next move is to reconnect that nanodimmer elsewhere in my network and re-run the heal. I did not want to remove it because I knew I would use it again soon and generally avoid remove/re-add cycles since I’ve read others saying the node number always increments and when you hit 255 you have to reset your whole network and re-add it all again, which sounds terrible and I hope never to do.
This is false, it will cycle thru any unused node numbers after 254 (i recall 255 being reserved).
As for your main issue, the way zwave works is if the network controller goes down for whatever reason the mesh network keeps going.