Device turning on when another device is turned on

Posted on
Fri Jul 08, 2022 11:08 am
Turribeach offline
Posts: 429
Joined: Feb 06, 2015
Location: London, UK

Device turning on when another device is turned on

Hi, one of my Z-wave relays is turning unexpectedly on when another device goes on. Here are my logs:

Code: Select all
2022-07-07 21:08:47.394   Z-Wave   sent "Lights Utility Room" on
2022-07-07 21:08:47.615   Z-Wave   received "Radiator Heating Element Bathroom " status update is on

2022-07-08 17:10:47.322   Z-Wave   sent "Lights Utility Room" on
2022-07-08 17:10:47.662   Z-Wave   received "Radiator Heating Element Bathroom " status update is on


However this doesn't happen all the time, only on some weird cases! But basically sometimes when Lights Utility Room gets sent an On command, it seems "Radiator Heating Element Bathroom " goes on. So far I checked:

    1) No other triggers are using "Radiator Heating Element Bathroom "
    2) I checked all the group associations of both devices, and all seem to be set to 001 - Indigo Zwave Interface or not set.

How can this be possible? Anything I can do to prevent this?

Posted on
Fri Jul 08, 2022 12:09 pm
jay (support) offline
Site Admin
User avatar
Posts: 18247
Joined: Mar 19, 2008
Location: Austin, Texas

Re: Device turning on when another device is turned on

Since the log doesn't show any Indigo activity between the two and it's happening pretty much immediately, the implication is that there is a Z-Wave association between them despite what Indigo is seeing. I'd exclude/include them both - that usually factory resets them.

Jay (Indigo Support)
Twitter | Facebook | LinkedIn

Posted on
Fri Jul 08, 2022 2:14 pm
Turribeach offline
Posts: 429
Joined: Feb 06, 2015
Location: London, UK

Re: Device turning on when another device is turned on

Well if it was an association it should be reproduceable which is not. It only happens on rare occasions. This is not my first post with weird/unexpected Z-Wave behavior, see this post. So adding these two together makes me believe this is some sort Z-Wave packet corruption which is having some unintended consecuencies. Is this possible?

Posted on
Fri Jul 08, 2022 5:14 pm
jay (support) offline
Site Admin
User avatar
Posts: 18247
Joined: Mar 19, 2008
Location: Austin, Texas

Re: Device turning on when another device is turned on

I suppose anything is possible, though it seems unlikely. Did you try the factory reset on those devices?

Jay (Indigo Support)
Twitter | Facebook | LinkedIn

Posted on
Sat Jul 09, 2022 1:23 pm
Turribeach offline
Posts: 429
Joined: Feb 06, 2015
Location: London, UK

Re: Device turning on when another device is turned on

No, but I just noticed that the device that turns on unexpectedly doesn't sync properly. I get different errors:

Code: Select all
   Z-Wave                          Syncing - started for "Radiator Heating Element Bathroom"
   Z-Wave                          Syncing - retrieved module neighbors list: 1, 5, 15, 18, 28, 29, 31, 35, 39, 40, 45, 50, 52, 58, 60, 61, 62, 64, 66, 77, 78, 81, 82
   Z-Wave                          Syncing - assigning return route to "069 - Radiator Heating Element Bathroom"
   Z-Wave                          Syncing - assigned return route
   Z-Wave                          Syncing - retrieved manufacture and model names: Fibaro System - 010F, Double Relay Switch (FGS222) - 02021002
   Z-Wave                          Syncing - retrieved protocol version 3.52, app version 2.02
   Z-Wave                          Syncing - retrieved class hierarchy: Routing Slave : Relay Switch : Relay Power Switch (04 : 10 : 01, base 25)
   Z-Wave                          Syncing - retrieved command classes: 20v1 25v1 27v1 72v1 86v1 70v1 85v1 8Ev1 60v2 7Av1 73v1
   Z-Wave                          Syncing - retrieved encrypt commands: - none -
   Z-Wave                          Syncing - retrieved capabilities: routing, beaming
   Z-Wave                          Syncing - retrieved multi-endpoint types: 1:(10 : 01), 2:(10 : 01)
   Z-Wave                          Syncing - retrieved multi-endpoint classes: 1:[25], 2:[25]
   Z-Wave Error                    rcvd incomplete interface packet: 01 09 00 04 00 45 03 85 03 01 33 (missing 2 bytes)
   Z-Wave                          Syncing - retrieved group 1 associations: [1]
   Z-Wave                          Syncing - retrieved group 2 associations: [1]
   Z-Wave                          Syncing - retrieved group 3 associations: [1]
   Z-Wave                          Syncing - group 1 association to interface already exists (skipping)
   Z-Wave                          Syncing - group 2 association to interface already exists (skipping)
   Z-Wave                          Syncing - group 3 association to interface already exists (skipping)
   Z-Wave                          Syncing - retrieved parameter 14 "Enable switch toggle type (bi-stable)" is false
   Z-Wave                          Syncing - retrieved parameter 16 "Power up to last known state" is false


Or sometimes I get:

Code: Select all
   Z-Wave                          Syncing - started for "Radiator Heating Element Bathroom"
   Z-Wave                          Syncing - retrieved module neighbors list: 1, 5, 15, 18, 28, 29, 31, 35, 39, 40, 45, 50, 52, 58, 60, 61, 62, 64, 66, 77, 78, 81, 82
   Z-Wave                          Syncing - assigning return route to "069 - Radiator Heating Element Bathroom"
   Z-Wave                          Syncing - assigned return route
   Z-Wave                          received "Motion Sensor Kitchen" status update is off
   Z-Wave                          Syncing - retrieved protocol version 3.52, app version 2.02
   Z-Wave                          Syncing - retrieved class hierarchy: Routing Slave : Relay Switch : Relay Power Switch (04 : 10 : 01, base 25)
   Z-Wave                          Syncing - retrieved command classes: 20v1 25v1 27v1 72v1 86v1 70v1 85v1 8Ev1 60v2 7Av1 73v1
   Z-Wave                          Syncing - retrieved encrypt commands: - none -
   Z-Wave                          Syncing - retrieved capabilities: routing, beaming
   Z-Wave                          Syncing - retrieved multi-endpoint types: 1:(10 : 01), 2:(10 : 01)
   Z-Wave                          Syncing - retrieved multi-endpoint classes: 1:[25], 2:[25]
   Z-Wave                          Syncing - retrieved group 1 associations: [1]
   Z-Wave                          Syncing - retrieved group 2 associations: [1]
   Z-Wave                          Syncing - retrieved group 3 associations: [1]
   Z-Wave                          Syncing - group 1 association to interface already exists (skipping)
   Z-Wave                          Syncing - complete
   Z-Wave                          sent "Radiator Heating Element Bathroom" status request
   Z-Wave                          sent "Underfloor Heating Bathroom" status request
   Z-Wave Error                    failed to find device parm description for module 69, index 14


Should I try to reset it?

Posted on
Sat Jul 09, 2022 1:57 pm
jay (support) offline
Site Admin
User avatar
Posts: 18247
Joined: Mar 19, 2008
Location: Austin, Texas

Re: Device turning on when another device is turned on

I would definitely try it (which is why I recommended it). The intermittent nature of that specific device may mean something else - do you notice other devices in that same area (or perhaps the same circuit) also having intermittent issues?

Jay (Indigo Support)
Twitter | Facebook | LinkedIn

Posted on
Sun Jul 10, 2022 2:07 pm
Turribeach offline
Posts: 429
Joined: Feb 06, 2015
Location: London, UK

Re: Device turning on when another device is turned on

Sorry I haven't been able to reset this device, been in bed with covid! But I managed to get it to sync without errors, after retrying many times and now I get a consistent albeit still incorrect behavior. In others words when "Lights Utility Room" goes On "Radiator Heating Element Bathroom" goes On too now. So think the inconsistency was to do with the other device not getting the Z-wave packet most of the times. By me resyncing it it has altered the way the packet is travelling in my network and now my other device is always getting it so it takes action. I will try a reset of the "Radiator Heating Element Bathroom" devide once I get out of bed to see if I can prevent the unwanted trigger...

Page 1 of 1

Who is online

Users browsing this forum: No registered users and 3 guests