Zigbee Switch magically switches bulb without connection

Add-ons Bindings
1

I have a Osram Lightify Zigbee bulp, with all it’s channels linkes to items, working fine.
I newly got an Aquara 6-way Zigbee wall switch, having trouble connecting it - but that’s another story.
I have nothing defined for my switch, it’s only registered as a thing (as the wrong thing - a Lumi.remote - btw), no items linked, I only see one “Level Control” dimmer-channel.
There is no rules file.

Now here’s the thing:
When I press button 2 on my switch the bulp goes to 50%, pressing button 1 the bulp goes off.
This is kinda what I’d like to achieve - but I haven’t told them to do anything yet.
The simple question is:
How? Why?
How can this be possible?
Anyone got an idea what component could implicitly connect those two devices?
In the log I only see

00:04:53.107 [INFO ] [smarthome.event.ItemStateChangedEvent] - BLP_Attic3_W_Dimmer changed from 0 to 50
00:04:56.337 [INFO ] [smarthome.event.ItemStateChangedEvent] - BLP_Attic3_W_Dimmer changed from 50 to 0

BLP_Attic3_W_Dimmer is the bulp dimmer item
(I’ve already set org.openhab.binding.zigbee to INFO, but nothing more is logged)

2

This is effectively disabling logging. You need to set it to DEBUG, but please read the binding documentation as there is more logging that needs to be enabled than this when debug issues.

3

oops, thanks. Set it to DEBUG and now I see this (starting from pressing the button):

01:10:29.477 [DEBUG] [ing.zigbee.handler.ZigBeeThingHandler] - 7CB03EAA0A00C728: Polling...
01:10:29.482 [DEBUG] [ing.zigbee.handler.ZigBeeThingHandler] - 7CB03EAA0A00C728: Polling zigbee:device:0137F5A2:7cb03eaa0a00c728:7CB03EAA0A00C728_3_dimmer
01:10:29.511 [DEBUG] [.converter.ZigBeeConverterSwitchLevel] - 04CF8CDF3C7D9CD5: ZigBee command received OnCommand [On/Off: 8BCA/1 -> 0000/255, cluster=0006, TID=47]
01:10:29.517 [DEBUG] [.converter.ZigBeeBaseChannelConverter] - 04CF8CDF3C7D9CD5: Channel zigbee:device:0137F5A2:04cf8cdf3c7d9cd5:04CF8CDF3C7D9CD5_1_dimmer updated to 100
01:10:29.523 [DEBUG] [ing.zigbee.handler.ZigBeeThingHandler] - 04CF8CDF3C7D9CD5: Updating ZigBee channel state zigbee:device:0137F5A2:04cf8cdf3c7d9cd5:04CF8CDF3C7D9CD5_1_dimmer to 100
01:10:29.533 [DEBUG] [.converter.ZigBeeConverterSwitchLevel] - 7CB03EAA0A00C728: ZigBee attribute reports ZclAttribute [cluster=Level Control, id=0, name=Current Level, dataType=UNSIGNED_8_BIT_INTEGER, lastValue=254, lastReportTime=Wed Sep 02 01:10:29 CEST 2020, implemented=true]
01:10:29.537 [DEBUG] [g.zigbee.handler.ZigBeeIsAliveTracker] - IsAlive Tracker reset for handler with thingUID=zigbee:device:0137F5A2:04cf8cdf3c7d9cd5
01:10:29.546 [DEBUG] [g.zigbee.handler.ZigBeeIsAliveTracker] - IsAlive Tracker cancelled task for thingUID=zigbee:device:0137F5A2:04cf8cdf3c7d9cd5
01:10:29.554 [DEBUG] [g.zigbee.handler.ZigBeeIsAliveTracker] - IsAlive Tracker scheduled task for thingUID=zigbee:device:0137F5A2:04cf8cdf3c7d9cd5 in 28 seconds
01:10:29.577 [DEBUG] [.converter.ZigBeeConverterSwitchLevel] - 7CB03EAA0A00C728: ZigBee attribute reports ZclAttribute [cluster=On/Off, id=0, name=On Off, dataType=BOOLEAN, lastValue=true, lastReportTime=Wed Sep 02 01:10:29 CEST 2020, implemented=false]
01:10:29.582 [DEBUG] [.converter.ZigBeeBaseChannelConverter] - 7CB03EAA0A00C728: Channel zigbee:device:0137F5A2:7cb03eaa0a00c728:7CB03EAA0A00C728_3_dimmer updated to 100
01:10:29.586 [DEBUG] [ing.zigbee.handler.ZigBeeThingHandler] - 7CB03EAA0A00C728: Updating ZigBee channel state zigbee:device:0137F5A2:7cb03eaa0a00c728:7CB03EAA0A00C728_3_dimmer to 100
01:10:29.596 [DEBUG] [g.zigbee.handler.ZigBeeIsAliveTracker] - IsAlive Tracker reset for handler with thingUID=zigbee:device:0137F5A2:7cb03eaa0a00c728
01:10:29.596 [INFO ] [smarthome.event.ItemStateChangedEvent] - BLP_Attic3_W_Dimmer changed from 0 to 100
01:10:29.601 [DEBUG] [g.zigbee.handler.ZigBeeIsAliveTracker] - IsAlive Tracker cancelled task for thingUID=zigbee:device:0137F5A2:7cb03eaa0a00c728
01:10:29.609 [DEBUG] [g.zigbee.handler.ZigBeeIsAliveTracker] - IsAlive Tracker scheduled task for thingUID=zigbee:device:0137F5A2:7cb03eaa0a00c728 in 1830 seconds
01:10:29.730 [DEBUG] [.converter.ZigBeeConverterSwitchLevel] - 7CB03EAA0A00C728: ZigBee attribute reports ZclAttribute [cluster=On/Off, id=0, name=On Off, dataType=BOOLEAN, lastValue=true, lastReportTime=Wed Sep 02 01:10:29 CEST 2020, implemented=false]
01:10:29.741 [DEBUG] [.converter.ZigBeeBaseChannelConverter] - 7CB03EAA0A00C728: Channel zigbee:device:0137F5A2:7cb03eaa0a00c728:7CB03EAA0A00C728_3_dimmer updated to 100
01:10:29.750 [DEBUG] [ing.zigbee.handler.ZigBeeThingHandler] - 7CB03EAA0A00C728: Updating ZigBee channel state zigbee:device:0137F5A2:7cb03eaa0a00c728:7CB03EAA0A00C728_3_dimmer to 100
01:10:29.762 [DEBUG] [g.zigbee.handler.ZigBeeIsAliveTracker] - IsAlive Tracker reset for handler with thingUID=zigbee:device:0137F5A2:7cb03eaa0a00c728
01:10:29.773 [DEBUG] [g.zigbee.handler.ZigBeeIsAliveTracker] - IsAlive Tracker cancelled task for thingUID=zigbee:device:0137F5A2:7cb03eaa0a00c728
01:10:29.779 [DEBUG] [g.zigbee.handler.ZigBeeIsAliveTracker] - IsAlive Tracker scheduled task for thingUID=zigbee:device:0137F5A2:7cb03eaa0a00c728 in 1830 seconds
01:10:29.861 [DEBUG] [.converter.ZigBeeConverterSwitchLevel] - 7CB03EAA0A00C728: ZigBee attribute reports ZclAttribute [cluster=Level Control, id=0, name=Current Level, dataType=UNSIGNED_8_BIT_INTEGER, lastValue=254, lastReportTime=Wed Sep 02 01:10:29 CEST 2020, implemented=true]
01:10:29.861 [DEBUG] [ing.zigbee.handler.ZigBeeThingHandler] - 7CB03EAA0A00C728: Polling zigbee:device:0137F5A2:7cb03eaa0a00c728:7CB03EAA0A00C728_3_colortemperature
01:10:29.866 [DEBUG] [.converter.ZigBeeBaseChannelConverter] - 7CB03EAA0A00C728: Channel zigbee:device:0137F5A2:7cb03eaa0a00c728:7CB03EAA0A00C728_3_dimmer updated to 100
01:10:29.875 [DEBUG] [ing.zigbee.handler.ZigBeeThingHandler] - 7CB03EAA0A00C728: Updating ZigBee channel state zigbee:device:0137F5A2:7cb03eaa0a00c728:7CB03EAA0A00C728_3_dimmer to 100
01:10:29.897 [DEBUG] [g.zigbee.handler.ZigBeeIsAliveTracker] - IsAlive Tracker reset for handler with thingUID=zigbee:device:0137F5A2:7cb03eaa0a00c728
01:10:29.902 [DEBUG] [g.zigbee.handler.ZigBeeIsAliveTracker] - IsAlive Tracker cancelled task for thingUID=zigbee:device:0137F5A2:7cb03eaa0a00c728
01:10:29.907 [DEBUG] [g.zigbee.handler.ZigBeeIsAliveTracker] - IsAlive Tracker scheduled task for thingUID=zigbee:device:0137F5A2:7cb03eaa0a00c728 in 1830 seconds
01:10:30.065 [DEBUG] [erter.ZigBeeConverterColorTemperature] - 7CB03EAA0A00C728: ZigBee attribute reports ZclAttribute [cluster=Color Control, id=7, name=Color Temperature, dataType=UNSIGNED_16_BIT_INTEGER, lastValue=153, lastReportTime=Wed Sep 02 01:10:30 CEST 2020, implemented=true]  on endpoint 3
01:10:30.071 [DEBUG] [.converter.ZigBeeBaseChannelConverter] - 7CB03EAA0A00C728: Channel zigbee:device:0137F5A2:7cb03eaa0a00c728:7CB03EAA0A00C728_3_colortemperature updated to 0
01:10:30.077 [DEBUG] [ing.zigbee.handler.ZigBeeThingHandler] - 7CB03EAA0A00C728: Updating ZigBee channel state zigbee:device:0137F5A2:7cb03eaa0a00c728:7CB03EAA0A00C728_3_colortemperature to 0
01:10:30.085 [DEBUG] [g.zigbee.handler.ZigBeeIsAliveTracker] - IsAlive Tracker reset for handler with thingUID=zigbee:device:0137F5A2:7cb03eaa0a00c728
01:10:30.091 [DEBUG] [g.zigbee.handler.ZigBeeIsAliveTracker] - IsAlive Tracker cancelled task for thingUID=zigbee:device:0137F5A2:7cb03eaa0a00c728
01:10:30.096 [DEBUG] [g.zigbee.handler.ZigBeeIsAliveTracker] - IsAlive Tracker scheduled task for thingUID=zigbee:device:0137F5A2:7cb03eaa0a00c728 in 1830 seconds

where 7cb…728 is the bulp and 04c…cd5 is the switch

4

Sorry to be a pain, but can you paste in the logs with code fences please. However you’ve added this has put quote marks on the front of the logs which screws up the processor.

5

sorry, changed that!

6

I’m actually not sure I understand the issue here - sorry.

If you have a switch, it will work like a switch. It will turn the item on and off when you press the buttons - you don’t need to do anything. Can you explain what you think the problem is so I can understand better?

7

Thanks, that you keep asking and try to understand my problem!
(maybe I shouldn’t have called the “thing” a switch - it’s in ioT terms a sensor. I never mean the item-type “switch”)
the “problem” is:
there is no item. no switch item that could receive an update. Only a naked “thing” (the aquara multi-switch sensor) which only has unlinked channels.
And this thing (the switch/sensor) magically sends an ON/OFF command to a different, not connected thing (the bulp, which has items).
So if I want to change what bulp this switch/sensor shall turn on and off, or what button should do that - I simply cannot, because I nowhere told openhab/zigbee to turn on/off the first bulp.
To be even more precise: Two physically different things are interacting where they shouldn’t. Or shouldn’t be able to without openhab/me telling them to do so.

8

I think if you stop openHAB this will still happen. Zigbee devices can talk to each other directly, you probably need to look at the settings in your control switch.

2 Likes
9

I agree with what @rossko57 said - it seems like the devices are “bound” together - you would need to reset the switch completely and this should hopefully reset the binding table.

10

thanks, @rossko57, I didn’t know that!
Could you give me a hint where I possibly could find the settings of my control switch?
I use the Ember EM35x Coordinator from BitronVideo " BV 2010/10 (ZigBee USB dongle)"
I couldn’t find yet a way to either see (out of OH) zigbee-logs or any settings.

11

I have no idea how you manage these things, sorry.

12

As I said above, the best way to resolve this is to reset the device. Currently we don’t have a system in the OH binding and UI that allows manipulation of the binding table. The binding manages the binding table for it’s own reports, but not others that were configured outside of the binding.