I have a generic zigbee device eWeLink ZB-SW02 relay that is turning itself on and off. when the event is source DEVICE and the type is blank. I want to rule out any app doing this would you point to the device as an issue?
What's it showing in the logs itself? Can you also turn on debug logging for that device? Which driver are you using for it?
1 Like
In addition to what @rlithgow1 asked about, can you list the apps that are using this device (on the Device page, look at the "In Use By" section)?
Thank you for the reply, The only thing the child device is in use by is the Dashboard. and the parent device is not is use by anything.
As far as the device driver question, is that the "Generic Zigbee Multi-Endpoint Switch"
endpointId: 01
model: ZB-SW02
application: 04
isMultiEP: true
manufacturer: eWeLink
Here is what the debug looks like. dev:229 is parent device and device 230 and 231 are the child devices.
search
dev:2292022-06-20 11:18:33.752 am infoXlight-relay was turned on
dev:2292022-06-20 11:18:33.750 am debugdescMap:[raw:913D0200060800001001, dni:913D, endpoint:02, cluster:0006, size:08, attrId:0000, encoding:10, command:0A, value:01, clusterInt:6, attrInt:0]
dev:2292022-06-20 11:18:33.745 am debugdescMap:[raw:913D0100060800001000, dni:913D, endpoint:01, cluster:0006, size:08, attrId:0000, encoding:10, command:0A, value:00, clusterInt:6, attrInt:0]
dev:2312022-06-20 11:18:26.738 am infoGeneric Zigbee Multi-Endpoint Switch EP02 was turned on
dev:2292022-06-20 11:18:26.738 am infoXlight-relay was turned off
dev:2302022-06-20 11:18:26.734 am infoGutters was turned off
dev:2292022-06-20 11:18:26.729 am debugdescMap:[raw:913D0200060800001001, dni:913D, endpoint:02, cluster:0006, size:08, attrId:0000, encoding:10, command:0A, value:01, clusterInt:6, attrInt:0]
dev:2292022-06-20 11:18:26.724 am debugdescMap:[raw:913D0100060800001000, dni:913D, endpoint:01, cluster:0006, size:08, attrId:0000, encoding:10, command:0A, value:00, clusterInt:6, attrInt:0]
dev:2312022-06-20 11:17:56.019 am infoGeneric Zigbee Multi-Endpoint Switch EP02 was turned off
dev:2292022-06-20 11:17:56.010 am debugdescMap:[raw:913D0200060800001000, dni:913D, endpoint:02, cluster:0006, size:08, attrId:0000, encoding:10, command:0A, value:00, clusterInt:6, attrInt:0]
dev:2292022-06-20 11:17:55.998 am infoXlight-relay was turned on
dev:2302022-06-20 11:17:55.996 am infoGutters was turned on
dev:2292022-06-20 11:17:55.987 am debugdescMap:[raw:913D0100060800001001, dni:913D, endpoint:01, cluster:0006, size:08, attrId:0000, encoding:10, command:0A, value:01, clusterInt:6, attrInt:0]
dev:2292022-06-20 11:16:53.679 am infoXlight-relay was turned off
dev:2312022-06-20 11:16:53.678 am infoGeneric Zigbee Multi-Endpoint Switch EP02 was turned on
dev:2302022-06-20 11:16:53.675 am infoGutters was turned off
dev:2292022-06-20 11:16:53.671 am debugdescMap:[raw:913D0200060800001001, dni:913D, endpoint:02, cluster:0006, size:08, attrId:0000, encoding:10, command:0A, value:01, clusterInt:6, attrInt:0]
dev:2292022-06-20 11:16:53.667 am debugdescMap:[raw:913D0100060800001000, dni:913D, endpoint:01, cluster:0006, size:08, attrId:0000, encoding:10, command:0A, value:00, clusterInt:6, attrInt:0]
If you change the driver to generic zigbee switch, does it stop?
So there are a couple interesting things:
- When the parent switch (Xlight-relay) turns on, one of the child switches turns on (Gutters), while the other child switch turns off (EP02).
- When the parent turns off, Gutters turns off, while EP02 turns on.
Gutters turning on/off seems to initiate the cascade.
So what apps is "Gutters" used in?
That is just the name of the child device since this is a two "device" switch.
So I think I can explain the flip-flop pattern, in the manual the device has a mode where the two relays toggle/switch state, the parent device makes the two swap. I'm only using one so I would not have noticed if the other was changing state. I'm thinking I need to check the physical switch on the device next. Maybe it being pressed down by the housing.
Just tried this, I see the same behavior.
Does the command 0A mean the device reported that it changed state? That would rule out the hub sending any command to the device?
Check for Hunches or whatever they are called on Alexa and/or Google.
1 Like
Is this the device?
Device has 3 operating modes: normal, interlock and inching Must be set by manually pushing the Mode button
yes that appears correct. BTW, I reset the device and it seems to have stopped.
1 Like
its not in the Alexa app. dashboard is the only app using it.
I reset the device and it appears to have stopped, so I believe the device was misbehaving, ill keep am eye on that you all for the replies.
1 Like
Excellent. @bobbyD - there seems to be a solution here. Can this thread be closed?
1 Like
