Something is turning on and off my stuff by itself at what seems random intervalls

Configuration
21

I went into all 103 zwave devices

  1. selected the device
  2. clicked on “node group associations”
  3. if it came up with a group name, I selected it, otherwise I went on to the next device.
  4. After selecting the group, the window expands a little and shows what devices are in that group.
  5. 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.
  6. 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

1 Like
22

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.

23

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.

24

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

25

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.

26

That might be it if it happened all the time but in my case it happens once every few weeks. if it was a group it would happen everyday.

27

I’m not saying you’re wrong but in my case it happened totally random. Sometimes not for a day or two and sometimes more frequent.

28

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.

29

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.