Great Idea. I’ve looked through 'em all now. It took a bit of time. You might not be able to answer this but i’ll give it a go and see if you have any clue. A part from The “Aeotec ZW090 Z-Stick Gen5 EU (Node: 1 Complete)” which is the controller itself for z-wave, existed it almost every “lifeline” group association, which I guess is normal as the controller wants to stay informed of any triggered association. I’m only guessing though. The following existed that i didn’t add myself.
Node 40: MuiltiSensor 6.
Group: LifeLine
In this group: Unknown node (255: (0 ? 255.0 : 255))
That last part looks weird. Unknown node…? I wonder how I go about to remove this as the node is not selectable in the list. Any idea?
Other than that nothing else looked weird. Most of my group associations are empty as I usually execute most of my stuff through an automation.
I just checked pastebin, are you sure your spaces are correct in the automation file? It seems like some of your triggers are located under action? YAML can be picky about the spaces sometimes.
I don’t have the Multisensor so I don’t have any reference. Since this is a device that could easily be a trigger device for other lights or switches that could easily be in other rooms or odd locations, you might look at this as a suspect. I would spend times with the logs and see what happens at the same time as an odd light change before declaring it the problem. I don’t know how disruptive it might be in your situation, but you could cover it up, take it down, remove power etc. to see if the problem goes away. If it is the problem, remove node, add node and rename it to the old name should correct things.
Thanks for taking your time to have a look. I am not certain about anything really. When I do a “check config” everything checks out. Also, the last time when I experience these weird on/off problems I check all of the automations on the start page of Home Assistant to see if any of them were triggered. There is a field that says “Last triggered: x hours ago” or something like that. None of the listed automations on the start page of home assistant had been triggered. I’m not sure if you can really trust that simply by checking though.
The reason why stuff is organized a bit weird and not structured the same way in every automation is because some of them I made by using the automation guide. I didn’t like it though so I edited the ones after the first couple of entries by hand.
I would also look at your history, to see if you can spot a specific pattern. Is it the same time everyday? Is it completely random? Also, are your zwave devices connected to some cloud service (IFTTT, Stringify, or the manufacturer’s cloud)…if so, check to see if there is some kind of schedule or flow running within the app.
Thought that was the trick, but it did it again just after I finished. But it would still be nice to have a report that tells me which devices to look at. I have 103 devices to go through to check for associations. So a report would be nice.
Awesome. That seems like a perfect match with my problem because I had a 255 entry on my multisensor. I figured out how to remove this broadcast id. So all I can do now is just wait a couple of hours/days and see if the issue is solved.
How did you manage to remove the broadcast ID from the reporting group association? Did you end up excluding the device from the network and include it again?
if it came up with a group name, I selected it, otherwise I went on to the next device.
After selecting the group, the window expands a little and shows what devices are in that group.
if the 255 entity was in the group, clicked in the device to control field and selected my z-stick, this brought up the option to remove the broadcast group button at the bottom of the window.
Then I selected to remove the broadcast group. For powered devices this happened quickly. For battery devices I had to get the device, wake it up and click the remove broadcast group to get it to go away. Because these don’t stay awake for long, I had to repeat waking them up and clicking the button several times to get it to take.
After doing all that i thought I had it fixed. Got a decent nights sleep. Then this morning all the lights popped on at around 5:45. I found that one of my window sensors had gotten the 255 back. I am sure I removed it from this sensor last night. So I’m not sure how it came back.
Right now, I’m trying to find a way to get a list of zwave devices, their groups and associations so I can make a report and go directly to devices that get the 255 in them instead of having to search through all the devices. I could really use a good zwave developer right now. LOL
thanks. I’m on 0.83.3 right now, so maybe that’s why I can’t edit the group associations. There were a couple changes to Zwave in the recent release. I have a single node with node 255 in it but I have not experienced any issues with devices turning on or off.
count yourself lucky. I was really about to call a priest to bring his holy water. I had HA shut down, I had the z-stick unplugged from the server. I was so frustrating it was funny.
Any update on this, I’ve started seeing very similar stuff where a couple of lights just come on, at 5:32 at random times. In the past three weeks it’s happened twice
I can’t say for certain that this might help you but my problems were due to the fact that I had broadcast connected to group associations. I would start looking there. In my case it was my Aeotech ZW100 Multisensor 6 that had a weird default configuration. After I cleared out the broadcast everything was fine.
Happened again and this one error message set me on a journey.
2019-12-30 05:32:00 WARNING (MainThread) [homeassistant.components.light] Not passing an entity ID to a service to target all entities is deprecated. Update your call to light.turn_on to be instead: entity_id: all
I went through every automation and in node red I have a check after the hue lights turn on to make sure they are at 100% brightness. There is a “get entities” node in nodered that should query HA and return all the entities that match, in my case if the brightness was < 255 and named from a list it would return it. For what ever reason, randomly this would fail to work and try to pass in a blank entity id would would that turn on lights on based off that error message. The strange part is this happened 17 days apart so I’m still not clear where the bug is but I’m assuming it’s in the node red home assistant package.
Is your logic correct? Do you have a safety net to make sure the call is not being executed if you have no entities? Seems like a flaw in your automation.
