Lights turn on when one door sensor tripped (they shouldn't)

Configuration
1

So I finally have my config setup quite stable for me at the moment, except for one thing that is driving me nuts.

I have two z-wave bulbs in different rooms, but anytime I open my front door (front_door), the sensor goes to the “On (or Open)” state, both lights turn on (light.office_light_level & light.family_room_table_light_level) until I shut the front_door. Now I don’t have any automations that would trigger that, So I am super unsure of why it is happening.

My config is https://github.com/grikka/Home-AssistantConfig if anyone has any thoughts as to why thats happening, I am all ears.

Thanks!

2

Somehow you have a zwave association happening, mine was caused by my messing around with the groups, the only way I found to get out of it was to reset the sensor that had the group association. You should be able to do the same for yours. Basically it’s a zwave thing not a HA thing :slight_smile:

3

Interesting… When I look all my zwave devices are part of the same main group. Those three nodes (light, light & sensor) don’t have anything special about their group assignment either (same as all the others).

4

Check to see if the sensors are sending any alarm codes. We don’t know what sensor you’re using so we can’t guide you further than that.

5

Both Bulbs are ZW7101 (Embrighten bulb) and the door sensor is a Linear WADWAZ-1

In the log, I am seeing the following:

Door Open:

2017-10-23 09:01:00.380 Detail, Node003, Received: 0x01, 0x09, 0x00, 0x04, 0x04, 0x03, 0x03, 0x20, 0x01, 0xff, 0x28
2017-10-23 09:01:00.381 Detail,
2017-10-23 09:01:00.383 Info, Node003, Received Basic set from node 3: level=255. Sending event notification.
2017-10-23 09:01:00.386 Detail, Node003, Notification: NodeEvent
2017-10-23 09:01:00.412 Detail, Node003, Received: 0x01, 0x09, 0x00, 0x04, 0x00, 0x03, 0x03, 0x20, 0x01, 0xff, 0x2c
2017-10-23 09:01:00.426 Detail,
2017-10-23 09:01:00.430 Info, Node003, Received Basic set from node 3: level=255. Sending event notification.
2017-10-23 09:01:00.434 Detail, Node003, Notification: NodeEvent
2017-10-23 09:01:00.473 Detail, Node003, Received: 0x01, 0x10, 0x00, 0x04, 0x04, 0x03, 0x0a, 0x71, 0x05, 0x07, 0xff, 0x00, 0xff, 0x07, 0x02, 0x00, 0x00, 0x90
2017-10-23 09:01:00.485 Detail,
2017-10-23 09:01:00.488 Info, Node003, Received Alarm report: type=7, level=255, sensorSrcID=0, type:Burglar event:2, status=255
2017-10-23 09:01:00.490 Detail, Node003, Refreshed Value: old value=7, new value=7, type=byte
2017-10-23 09:01:00.491 Detail, Node003, Changes to this value are not verified
2017-10-23 09:01:00.493 Detail, Node003, Refreshed Value: old value=0, new value=255, type=byte
2017-10-23 09:01:00.495 Detail, Node003, Changes to this value are not verified
2017-10-23 09:01:00.497 Detail, Node003, Refreshed Value: old value=0, new value=0, type=byte
2017-10-23 09:01:00.499 Detail, Node003, Changes to this value are not verified
2017-10-23 09:01:00.502 Detail, Node003, Refreshed Value: old value=2, new value=2, type=byte
2017-10-23 09:01:00.503 Detail, Node003, Changes to this value are not verified
2017-10-23 09:01:00.506 Detail, Node003, Notification: ValueChanged
2017-10-23 09:01:00.591 Detail, Node003, Notification: ValueChanged
2017-10-23 09:01:00.752 Detail, Node003, Notification: ValueChanged
2017-10-23 09:01:00.907 Detail, Node003, Notification: ValueChanged
2017-10-23 09:01:01.040 Detail, Node003, Received: 0x01, 0x10, 0x00, 0x04, 0x00, 0x03, 0x0a, 0x71, 0x05, 0x07, 0xff, 0x00, 0xff, 0x07, 0x02, 0x00, 0x00, 0x94
2017-10-23 09:01:01.042 Detail,
2017-10-23 09:01:01.045 Info, Node003, Received Alarm report: type=7, level=255, sensorSrcID=0, type:Burglar event:2, status=255
2017-10-23 09:01:01.051 Detail, Node003, Refreshed Value: old value=7, new value=7, type=byte
2017-10-23 09:01:01.052 Detail, Node003, Changes to this value are not verified
2017-10-23 09:01:01.054 Detail, Node003, Refreshed Value: old value=255, new value=255, type=byte
2017-10-23 09:01:01.058 Detail, Node003, Changes to this value are not verified
2017-10-23 09:01:01.059 Detail, Node003, Refreshed Value: old value=0, new value=0, type=byte
2017-10-23 09:01:01.061 Detail, Node003, Changes to this value are not verified
2017-10-23 09:01:01.063 Detail, Node003, Refreshed Value: old value=2, new value=2, type=byte
2017-10-23 09:01:01.065 Detail, Node003, Changes to this value are not verified
2017-10-23 09:01:01.069 Detail, Node003, Notification: ValueChanged
2017-10-23 09:01:01.199 Detail, Node003, Notification: ValueChanged
2017-10-23 09:01:02.324 Detail, Node003, Notification: ValueChanged
2017-10-23 09:01:02.473 Detail, Node003, Notification: ValueChanged

Door Closed:

2017-10-23 09:01:16.404 Detail, Node010, Received: 0x01, 0x08, 0x00, 0x04, 0x00, 0x0a, 0x02, 0x84, 0x07, 0x78
2017-10-23 09:01:16.406 Detail,
2017-10-23 09:01:16.408 Info, Node010, Received Wakeup Notification from node 10
2017-10-23 09:01:16.410 Info, Node010, Node 10 has been marked as awake
2017-10-23 09:01:16.412 Detail, Node010, Queuing (WakeUp) WakeUpCmd_NoMoreInformation (Node=10): 0x01, 0x09, 0x00, 0x13, 0x0a, 0x02, 0x84, 0x08, 0x25, 0xff, 0xbb
2017-10-23 09:01:16.414 Detail, Node010, Notification: Notification - Node Awake
2017-10-23 09:01:16.438 Detail,
2017-10-23 09:01:16.440 Info, Node010, Sending (WakeUp) message (Callback ID=0xff, Expected Reply=0x13) - WakeUpCmd_NoMoreInformation (Node=10): 0x01, 0x09, 0x00, 0x13, 0x0a, 0x02, 0x84, 0x08, 0x25, 0xff, 0xbb
2017-10-23 09:01:16.450 Detail, Node010, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2017-10-23 09:01:16.452 Detail, Node010, ZW_SEND_DATA delivered to Z-Wave stack
2017-10-23 09:01:16.467 Detail, Node010, Received: 0x01, 0x07, 0x00, 0x13, 0xff, 0x00, 0x00, 0x02, 0x16
2017-10-23 09:01:16.469 Detail, Node010, ZW_SEND_DATA Request with callback ID 0xff received (expected 0xff)
2017-10-23 09:01:16.471 Info, Node010, Request RTT 28 Average Request RTT 27
2017-10-23 09:01:16.473 Info, Node010, Node 10 has been marked as asleep
2017-10-23 09:01:16.475 Detail, Expected callbackId was received
2017-10-23 09:01:16.476 Detail, Expected reply was received
2017-10-23 09:01:16.478 Detail, Message transaction complete
2017-10-23 09:01:16.480 Detail,
2017-10-23 09:01:16.482 Detail, Node010, Removing current message
2017-10-23 09:01:16.484 Detail, Node010, Notification: Notification - Node Asleep
2017-10-23 09:01:17.141 Detail, Node003, Received: 0x01, 0x09, 0x00, 0x04, 0x04, 0x03, 0x03, 0x20, 0x01, 0x00, 0xd7
2017-10-23 09:01:18.648 Detail,
2017-10-23 09:01:18.649 Info, Node003, Received Basic set from node 3: level=0. Sending event notification.
2017-10-23 09:01:18.652 Detail, Node003, Notification: NodeEvent
2017-10-23 09:01:18.702 Detail, Node003, Received: 0x01, 0x09, 0x00, 0x04, 0x04, 0x03, 0x03, 0x20, 0x01, 0x00, 0xd7
2017-10-23 09:01:18.721 Detail,
2017-10-23 09:01:18.724 Info, Node003, Received Basic set from node 3: level=0. Sending event notification.
2017-10-23 09:01:18.726 Detail, Node003, Notification: NodeEvent
2017-10-23 09:01:18.773 Detail, Node003, Received: 0x01, 0x09, 0x00, 0x04, 0x00, 0x03, 0x03, 0x20, 0x01, 0x00, 0xd3
2017-10-23 09:01:18.775 Detail,
2017-10-23 09:01:18.777 Info, Node003, Received Basic set from node 3: level=0. Sending event notification.
2017-10-23 09:01:18.779 Detail, Node003, Notification: NodeEvent
2017-10-23 09:01:18.820 Detail, Node003, Received: 0x01, 0x10, 0x00, 0x04, 0x04, 0x03, 0x0a, 0x71, 0x05, 0x07, 0x00, 0x00, 0xff, 0x07, 0x02, 0x00, 0x00, 0x6f
2017-10-23 09:01:18.822 Detail,
2017-10-23 09:01:18.824 Info, Node003, Received Alarm report: type=7, level=0, sensorSrcID=0, type:Burglar event:2, status=255
2017-10-23 09:01:18.845 Detail, Node003, Refreshed Value: old value=7, new value=7, type=byte
2017-10-23 09:01:18.847 Detail, Node003, Changes to this value are not verified
2017-10-23 09:01:18.849 Detail, Node003, Refreshed Value: old value=255, new value=0, type=byte
2017-10-23 09:01:18.851 Detail, Node003, Changes to this value are not verified
2017-10-23 09:01:18.853 Detail, Node003, Refreshed Value: old value=0, new value=0, type=byte
2017-10-23 09:01:18.855 Detail, Node003, Changes to this value are not verified
2017-10-23 09:01:18.856 Detail, Node003, Refreshed Value: old value=2, new value=2, type=byte
2017-10-23 09:01:18.858 Detail, Node003, Changes to this value are not verified
2017-10-23 09:01:18.861 Detail, Node003, Notification: ValueChanged
2017-10-23 09:01:19.076 Detail, Node003, Notification: ValueChanged
2017-10-23 09:01:19.418 Detail, Node003, Notification: ValueChanged
2017-10-23 09:01:19.711 Detail, Node003, Notification: ValueChanged

6

So instead of communicating via Home Assistant, Z-Wave devices can also communicate directly to eachother.

This is done via group associations. You can manage these (albeit kinda rudimentary) via the Home Assistant webui.

go to Configuration -> Z-Wave, then find your door sensor in the nodes list. Then scroll down to Group Associations and check if your lights are in one of the available groups. (not to be confused with home assistant’s group.whatever)

The only thing that should be configured is group 1 (called lifeline in all (recent) z-wave products), your controller (node 1) should be in the lifeline group.

7

Thats where I was looking,

03 PM
03 PM1478×750 42.2 KB

Not sure what "Unknown Node (id: 255) is.

8

255 is, from memory, the broadcast group (yup, the Hail group). It’s sending an Alarm to the broadcast group when you open the door - none of my door sensors do that.

9

Yeah, like @Tinkerer said, 255 is reseved for broadcasts. So your door sensor is letting every z-wave device on the network know it has opened. Maybe you can completely reset the sensor and see if that fixes it? (probably best if you first exclude it from your z-wave network).