search

Koenkk / zigbee2mqtt

Zigbee 🐝 to MQTT bridge 🌉, get rid of your proprietary Zigbee bridges 🔨
https://www.zigbee2mqtt.io
GNU General Public License v3.0
11.79k stars 1.64k forks source link

OSRAM issues with Broadcast Messages and all lights #962

Closed jamestutton closed 5 years ago

jamestutton commented 5 years ago

Hi so I recently added "support" for the Osram/lightify Switch mini. But it seems the challenges with these device may not quite be over yet.

So the issue I seem to be having is although both the Bulbs (OSRAM AC03641) and the remote are both paired with zigbee2mqtt and can control the bulbs via MQTT mesages no issue. The issue is the switches seem to control the bulbs via some sort of broadcast messages. This would be fine but the messages seem to uncontrollable and effect all lights. So anOn/Off command on any switch turns on/off "ALL" my osram bulbs in the house. "Not good"

And to top it off this happens even when zibee2mqtt is stopped. So it appears the bulbs/remotes are doing so sort of direct pairing although no direct pairing has taken place.

I have a couple of CC2351 so can do some sniffing but ultimately hoping someone here will have some next steps to get to the bottom of this.

My current thinking is that when the remote joins it should probably be sent some sort of group or other command to disable its broadcast mode, but my zigbee knowledge is fairly limited at this point.

Have tried OSRAM support but they not been overly helpful and unfortunately don't have an original bridge/gateway to test how it works in the vendors own app.

jamestutton commented 5 years ago

It appears other have seen similar things on the Smart-things side

Smart things

And with deconz its been raised issue 294

We just to figure how the native APP does it or if anyone here has the gateway and can do a packet capture perhaps. Id love to get these working as currently one of the cheapest zigbee switches on the market and quite powerful as effectively a 6 button remote as all 3 buttons have short and long press options.

Koenkk commented 5 years ago

It's interesting to know what the device actually sends, I expect a broadcast to 0x0000 (all devices). Can you confirm this by doing zigbee sniffing?

In order to fix this, we indeed need to have sniffing of the original gateway.

jamestutton commented 5 years ago

Unfortunately don't have the gateway and am seeing if osram willing/able to provide some further detail around how the gateway operates.

As for sniffing currently away so will get packet captures sent in next couple of days but from recall it does indeed use the 0x0000 address.

In some ways the master on/off switch is off great use(by main door on leaving for example). Just not when I want to control light in a single room.

On Wed, 30 Jan 2019, 08:30 Koen Kanters <notifications@github.com wrote:

It's interesting to know what the device actually sends, I expect a broadcast to 0x0000 (all devices). Can you confirm this by doing zigbee sniffing?

In order to fix this, we indeed need to have sniffing of the original gateway.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Koenkk/zigbee2mqtt/issues/962#issuecomment-458855994, or mute the thread https://github.com/notifications/unsubscribe-auth/ACMWJ08r8L2qLTYX42JAzuXmTDpoYuqLks5vIVgygaJpZM4aYaRT .

jamestutton commented 5 years ago

Full Output of a single message below, hopefully it with give some clues:

Frame 12643: 48 bytes on wire (384 bits), 48 bytes captured (384 bits) on interface 0
    Interface id: 0 (-)
        Interface name: -
    Encapsulation type: IEEE 802.15.4 Wireless PAN (104)
    Arrival Time: Jan  1, 1970 02:13:49.053343000 BST
    [Time shift for this packet: 0.000000000 seconds]
    Epoch Time: 4429.053343000 seconds
    [Time delta from previous captured frame: 0.053262000 seconds]
    [Time delta from previous displayed frame: 0.053262000 seconds]
    [Time since reference or first frame: 4425.648148000 seconds]
    Frame Number: 12643
    Frame Length: 48 bytes (384 bits)
    Capture Length: 48 bytes (384 bits)
    [Frame is marked: False]
    [Frame is ignored: False]
    [Protocols in frame: wpan:zbee_nwk:zbee_aps:zbee_zcl:zbee_zcl_general.onoff]
IEEE 802.15.4 Data, Dst: Broadcast, Src: 0x4c09
    Frame Control Field: 0x8841, Frame Type: Data, PAN ID Compression, Destination Addressing Mode: Short/16-bit, Frame Version: IEEE Std 802.15.4-2003, Source Addressing Mode: Short/16-bit
        .... .... .... .001 = Frame Type: Data (0x1)
        .... .... .... 0... = Security Enabled: False
        .... .... ...0 .... = Frame Pending: False
        .... .... ..0. .... = Acknowledge Request: False
        .... .... .1.. .... = PAN ID Compression: True
        .... ...0 .... .... = Sequence Number Suppression: False
        .... ..0. .... .... = Information Elements Present: False
        .... 10.. .... .... = Destination Addressing Mode: Short/16-bit (0x2)
        ..00 .... .... .... = Frame Version: IEEE Std 802.15.4-2003 (0)
        10.. .... .... .... = Source Addressing Mode: Short/16-bit (0x2)
    Sequence Number: 88
    Destination PAN: 0x1a63
    Destination: 0xffff
    Source: 0x4c09
    [Extended Source: Osram_aa:00:ad:9a:2c (7c:b0:3e:aa:00:ad:9a:2c)]
    [Origin: 12434]
    FCS: 0x3510 (Correct)
ZigBee Network Layer Data, Dst: Broadcast, Src: 0x0ec8
    Frame Control Field: 0x0248, Frame Type: Data, Discover Route: Enable, Security Data
    Destination: 0xfffd
    Source: 0x0ec8
    Radius: 10
    Sequence Number: 59
    [Extended Source: Ember_00:0f:24:0e:b5 (00:0d:6f:00:0f:24:0e:b5)]
    [Origin: 1097]
    ZigBee Security Header
ZigBee Application Support Layer Data, Dst Endpt: 255, Src Endpt: 2
    Frame Control Field: Data (0x08)
    Destination Endpoint: 255
    Cluster: On/Off (0x0006)
    Profile: Home Automation (0x0104)
    Source Endpoint: 2
    Counter: 244
ZigBee Cluster Library Frame
    Frame Control Field: Cluster-specific (0x11)
        .... ..01 = Frame Type: Cluster-specific (0x1)
        .... .0.. = Manufacturer Specific: False
        .... 0... = Direction: Client to Server
        ...1 .... = Disable Default Response: True
    Sequence Number: 116
    Command: Off (0x00)
Koenkk commented 5 years ago

So as expected, this switch indeed send a broadcast request. We need to find out if this device requires additional configuration/how the OSRAM gateway deals with this.

pixeldoc2000 commented 5 years ago

I have the Osram "Switch 4x EU-LIGHTIFY", Osram Mini Switch, Osram Lightify Gateway and Sniffer.

What part of the traffic do we need to sniff?

I guest the pairing and normal operation of the Switch(es) with the Gateway?

jamestutton commented 5 years ago

Just an update on this issue. Have made various attempts to contact OSRAM for information but no luck from them.

jamestutton commented 5 years ago

Hi Pixel, just seen your message. So do you have some bulbs as well? First thing is to prove it actually work as expected with the OSram gateway. So can you pair an "Osram Mini Switch" with the gateway and it only then control single bulb. If so can you list the steps to do this. Ie do you pair the switch to gateway then hold switch near bulb to pair bulb (like tradfri). Or do you link both bulb and switch to app then somehow add them to a group. Does the switch still control the bulb if you unplug the gateway.

pixeldoc2000 commented 5 years ago

Yes, i have Osram bulbs as well.

Switch Buttons: grafik

To pair hold Button 1 + 2 for 3 seconds. Led will flash blue multiple times. To reset hold Button 2 + 3 for 10 seconds. Led will flash green multiple times. This info is given in the Osram Lightify App to control the Osram Lightify Bridge.

Default setting for the Switch in Lightify App/Bridge are: Button 1 short press: All ON Button 1 long press: Brightness UP Button 2 short press: 2700K / Brightness 100% Button 2 long press: Change color (forward) Button 3 short press: All OFF Button 3 short press: Brightness DOWN So by default switch is "configured" for Broadcast (All Devices). But you can change Buttons to control a specific Device (probably via Cluster?)

Lightify App Switch Config Screenshot (German): grafik Alle Geräte = All Devices

Capture of pairing the Osram Mini Switch to Osram Lightify Bridge: https://pastebin.com/UxGJAWqL

Bridge IEEE: 84:18:26:00:00:8b:8f:16 Bridge WLAN FW Version: 1.3.1.0 Bridge Zigbee FW Version: 1.2.0.68 Mini Switch IEEE: 000d6f00101cf178 Mini Switch FW Version: 010B0000 (Updated via Osram Lightify Bridge) Mini Switch FW Version before Update: 01090000

Will do further sniffing ASAP.

pixeldoc2000 commented 5 years ago

Capture of pairing the Osram Lightify Switch 4x EU to Osram Lightify Bridge: https://pastebin.com/iNb1NE5S Bridge IEEE: 84:18:26:00:00:8b:8f:16 Switch 4x EU IEEE: 000d6f000c632502

jamestutton commented 5 years ago

So that all looks to make sense. So are you able to set one to control a single device and capture what ever is sent to the switch to update it and also what the switch sends afterwards. Guessing it must send something to disable broadcast mode and bind it to a cluster or something somehow.

pixeldoc2000 commented 5 years ago

Here is the capture of Osram Mini Switch Button 1 configured via Osram Lightify Bridge to control an Osram RGBW Bulb: https://pastebin.com/sUR1ceKd

Osram RGBW Bulb IEEE: 8418260000ca39b4

grafik

It works like this in Lightify. You select the switch in the Lightify app. Select the button of the switch you want to change (in case of the Osram Mini Switch all three buttons can be changed from all devices to a specific device). You can choose different action for short and long press of the button. grafik Translation: "kurzer Tastendrucker" = short press, "langer Tastendruck" = long press, "Knopf 1" = Button 1, "Anschalten" = switch on

Than the bridge will write the config to the switch after holding button 1 & 2 of the switch for 3 seconds (same as pairing). The Switch will flash blue and the config upload will start. grafik

Looks like the switch than will setup clusters with the device assigned to switch button and the bridge.

First two clusters with the bridge, than two with the bulb:

 92 01:00:40,821895    ZigBee ZDP 0x0001                0x5595                127    Bind Request Src: Ember_00:10:1c:f1:78, Dst: Osram_00:00:8b:8f:16, Power Configuration (Cluster ID: 0x0001)
119 01:00:43,830869    ZigBee ZDP 0x0001                0x5595                127    Bind Request Src: Ember_00:10:1c:f1:78, Dst: Osram_00:00:8b:8f:16, Poll Control (Cluster ID: 0x0020)
423 01:01:27,145586    ZigBee ZDP 0x0001                0x5595                127    Bind Request Src: Ember_00:10:1c:f1:78, Dst: Osram_00:00:ca:39:b4, On/Off (Cluster ID: 0x0006)
429 01:01:28,104005    ZigBee ZDP 0x0001                0x5595                127    Bind Request Src: Ember_00:10:1c:f1:78, Dst: Osram_00:00:ca:39:b4, Level Control (Cluster ID: 0x0008)
pixeldoc2000 commented 5 years ago

@jamestutton

So can you pair an "Osram Mini Switch" with the gateway and it only then control single bulb.

Yes. By default the switch control all lights. You have to configure every switch buttons in the Lightify App via the bridge to control a specific device.

If so can you list the steps to do this.

See above.

do you pair the switch to gateway then hold switch near bulb to pair bulb (like tradfri). Or do you link both bulb and switch to app then somehow add them to a group.

You pair the switch and the bulb with the bridge.

Does the switch still control the bulb if you unplug the gateway.

Yes.

aveseli commented 5 years ago

did someone make any progress here? would be cool if the all on/all off broadcast message could be stopped without the osram gateway

Koenkk commented 5 years ago

I will try to get my hands on this device, will let you know.

Koenkk commented 5 years ago

I've received the device.

aveseli commented 5 years ago

@Koenkk thanks a lot! I will give it a try!

RyuzakiKK commented 5 years ago

@Koenkk I just tried it with the dev branch and I can confirm that it works, with a caveat. If the switch is routed through a router, and not directly to the coordinator, the switch is still able to send a broadcast signal to the devices in my network.

As a router I'm using another cc2531.

Could this be fixable with a router firmware upgrade?

jamestutton commented 5 years ago

Are you sure that is the case? In my testing so far I found the switch sends broadcast on initial join and shortly afterwards if pressed but within 60s or so I'm guessing the new binds are sent and it no longer broadcasts.

On Sat, 18 May 2019, 19:34 Ludovico de Nittis, notifications@github.com wrote:

@Koenkk https://github.com/Koenkk I just tried it with the dev branch and I can confirm that it works, with a caveat. If the switch is routed through a router, and not directly to the coordinator, the switch is still able to send a broadcast signal to the devices in my network.

As a router I'm using another cc2531.

Could this be fixable with a router firmware upgrade?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Koenkk/zigbee2mqtt/issues/962?email_source=notifications&email_token=AARRMJ5HTQHMRCCR3FHPERLPWBD4FA5CNFSM4GTBURJ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVWTXCA#issuecomment-493697928, or mute the thread https://github.com/notifications/unsubscribe-auth/AARRMJ3MXBWZ2KEI6M4FEKLPWBD4FANCNFSM4GTBURJQ .

RyuzakiKK commented 5 years ago

@jamestutton After I saw that the broadcast messages continued, I disconnected my router and re paired the switch very close to the coordinator. Then I re plugged the router and since then the switch is working as expected without any more broadcast messages.

So I assumed that the problem was the router but I'm not 100% sure. Now it is working but I don't know if the switch is still routing through the router or not (is there a way to see the message route?).

But if it is working also for you then probably we can assume that there was something odd in my configuration that a reset and a re pair solved.

martin3000 commented 5 years ago

I'm using ZHA and after pairing the switch with the zigbee stick, the switch did not control my lights. Only after binding the switch with lights, they get switched. So maybe there is something in the ZHA code or ZHAQUIRKS that does this. https://github.com/dmulcahey/zha-device-handlers/tree/dev/zhaquirks/osram https://github.com/home-assistant/home-assistant/tree/dev/homeassistant/components/zha

Ascia42 commented 4 years ago

SOLVED:

My issue is solved, the error was self-made: The docker-compose.yml referenced :latest-dev, but the start-script actually still started the latest stable image. Now running with latest-dev everything is fine.

Cheers Ascia

` Hello everyone. I read this thread with great interest because i have the same problem. I bougth a OSRAM switch mini "AC0251600NJ/AC0251100NJ" to switch my lights. But after pairing the switch with my RaspBerryPi-powered zigbee2mqtt, it broadcasts to all my Osram Smart+ Plugs (zigbee switchable socket).

When looking through the debug-output I can see that zigbee2mqtt detects all messages from the switch, but all sockets turn on/off also, even if the RaspberryPi is powered down. So assume I have this broadcast-probleme described in this issue.

Following this thread I switched to dev-branch. I am using the project from https://github.com/ct-Open-Source/ct-Smart-Home, which uses the zigbee2mqqt docker. My docker-compose.yml looks like this.

[...] zigbee: image: koenkk/zigbee2mqtt:latest-dev volumes:

  • ./data/zigbee:/app/data
  • /opt/zigbee-herdsman-converters:/app/node_modules/zigbee-herdsman-converters devices:
  • "/dev/ttyACM0:/dev/ttyACM0" restart: always [...]

To get the newest devices.js I followed the steps

cd /opt git clone https://github.com/Koenkk/zigbee-herdsman-converters.git

and added the following setting to my compose.yml as you can see above.

-v /opt/zigbee-herdsman-converters:/app/node_modules/zigbee-herdsman-converters

What have I done wrong or what have I missed?

Additional question: Is it "right github-style" to add to an existing issue or would it be more correct to open a new one.

Thanks in advance, any hint will be appreciated.

Cheers Ascia

p.s: Thanks for all the great work you put in zigbee2mqtt, such a great project!!`

sebastianovide commented 3 years ago

I've used the OSRAM Smart+ mini switch without problems until today. Today I've upgraded my coordinator to a electrolama zzh! and now I'm experiencing this problem... has not problem not been fixed in this firmware ?

Koenkk commented 3 years ago

@sebastianovide try to reconfigure the device via https://www.zigbee2mqtt.io/information/mqtt_topics_and_message_structure.html#zigbee2mqttbridgeconfigure (make sure to wakeup the remote by clickng a button right before doing so), check log if OK.

sebastianovide commented 3 years ago

@sebastianovide try to reconfigure the device via https://www.zigbee2mqtt.io/information/mqtt_topics_and_message_structure.html#zigbee2mqttbridgeconfigure (make sure to wakeup the remote by clickng a button right before doing so), check log if OK.

no luck... I've did it, then the switch stop working completely. So I've reset it and repaired again. The problem persisted. I've tried again to reconfigure with "zigbee2mqtt/bridge/configure" but I get this error

info  2020-10-17 15:38:12: MQTT publish: topic 'zigbee2mqtt/osram switch/action', payload 'down'
info  2020-10-17 15:38:12: MQTT publish: topic 'zigbee2mqtt/osram switch/action', payload 'down'
debug 2020-10-17 15:38:18: Received MQTT message on 'zigbee2mqtt/bridge/configure' with data 'osram switch'
info  2020-10-17 15:38:18: Configuring 'osram switch'
error 2020-10-17 15:38:28: Failed to configure 'osram switch', attempt 1 (Error: Bind 0x000d6f000e1b7b68/1 genOnOff from '0x00124b0018e1f550/1' failed (AREQ - ZDO - bindRsp after 10000ms)
    at Timeout._onTimeout (/app/node_modules/zigbee-herdsman/dist/utils/waitress.js:46:35)
    at listOnTimeout (internal/timers.js:549:17)
    at processTimers (internal/timers.js:492:7))

ok... that error was just because the switch was not awake..

pressing some button to keep it await, I can reconfigure...

info  2020-10-17 15:42:11: Successfully configured 'osram switch'

but after that, the switch doesn't send any signal anymore

Koenkk commented 3 years ago

@sebastianovide can you provide the herdsman debug log when pressing a button?

To enable herdsman debug logging, see https://www.zigbee2mqtt.io/information/debug.html#zigbee-herdsman-debug-logging

sebastianovide commented 3 years ago

after reconfiguring, nothing at all.... clicking the buttons will not give any log...

so i had to reset and repair. 

debug 2020-10-17 15:53:23: Received Zigbee message from 'osram switch', type 'commandOn', cluster 'genOnOff', data '{}' from endpoint 1 with groupID 0
info  2020-10-17 15:53:23: MQTT publish: topic 'zigbee2mqtt/osram switch', payload '{"action":"up","battery":100,"elapsed":676970,"last_seen":"2020-10-17T15:53:23+01:00","linkquality":81,"update_available":false,"voltage":3000}'
info  2020-10-17 15:53:23: MQTT publish: topic 'zigbee2mqtt/osram switch', payload '{"action":"","battery":100,"last_seen":"2020-10-17T15:53:23+01:00","linkquality":81,"update_available":false,"voltage":3000}'
info  2020-10-17 15:53:23: MQTT publish: topic 'zigbee2mqtt/osram switch/action', payload 'up'
debug 2020-10-17 15:53:23: Received Zigbee message from 'osram switch', type 'commandOn', cluster 'genOnOff', data '{}' from endpoint 1 with groupID 0
info  2020-10-17 15:53:23: MQTT publish: topic 'zigbee2mqtt/osram switch', payload '{"action":"up","battery":100,"elapsed":26,"last_seen":"2020-10-17T15:53:23+01:00","linkquality":81,"update_available":false,"voltage":3000}'
debug 2020-10-17 15:53:23: Received Zigbee message from 'osram switch', type 'commandOn', cluster 'genOnOff', data '{}' from endpoint 1 with groupID 0
info  2020-10-17 15:53:23: MQTT publish: topic 'zigbee2mqtt/osram switch', payload '{"action":"up","battery":100,"elapsed":7,"last_seen":"2020-10-17T15:53:23+01:00","linkquality":81,"update_available":false,"voltage":3000}'
debug 2020-10-17 15:53:23: Received Zigbee message from 'osram switch', type 'commandOn', cluster 'genOnOff', data '{}' from endpoint 1 with groupID 0
info  2020-10-17 15:53:23: MQTT publish: topic 'zigbee2mqtt/osram switch', payload '{"action":"up","battery":100,"elapsed":8,"last_seen":"2020-10-17T15:53:23+01:00","linkquality":81,"update_available":false,"voltage":3000}'
debug 2020-10-17 15:53:23: Received Zigbee message from 'osram switch', type 'commandOn', cluster 'genOnOff', data '{}' from endpoint 1 with groupID 0
info  2020-10-17 15:53:23: MQTT publish: topic 'zigbee2mqtt/osram switch', payload '{"action":"up","battery":100,"elapsed":9,"last_seen":"2020-10-17T15:53:23+01:00","linkquality":81,"update_available":false,"voltage":3000}'
debug 2020-10-17 15:53:23: Received Zigbee message from 'osram switch', type 'commandOn', cluster 'genOnOff', data '{}' from endpoint 1 with groupID 0
info  2020-10-17 15:53:23: MQTT publish: topic 'zigbee2mqtt/osram switch', payload '{"action":"up","battery":100,"elapsed":8,"last_seen":"2020-10-17T15:53:23+01:00","linkquality":81,"update_available":false,"voltage":3000}'
info  2020-10-17 15:53:23: MQTT publish: topic 'zigbee2mqtt/osram switch', payload '{"action":"","battery":100,"last_seen":"2020-10-17T15:53:23+01:00","linkquality":81,"update_available":false,"voltage":3000}'
info  2020-10-17 15:53:23: MQTT publish: topic 'zigbee2mqtt/osram switch', payload '{"action":"","battery":100,"last_seen":"2020-10-17T15:53:23+01:00","linkquality":81,"update_available":false,"voltage":3000}'
info  2020-10-17 15:53:23: MQTT publish: topic 'zigbee2mqtt/osram switch', payload '{"action":"","battery":100,"last_seen":"2020-10-17T15:53:23+01:00","linkquality":81,"update_available":false,"voltage":3000}'
info  2020-10-17 15:53:23: MQTT publish: topic 'zigbee2mqtt/osram switch', payload '{"action":"","battery":100,"last_seen":"2020-10-17T15:53:23+01:00","linkquality":81,"update_available":false,"voltage":3000}'
info  2020-10-17 15:53:23: MQTT publish: topic 'zigbee2mqtt/osram switch', payload '{"action":"","battery":100,"last_seen":"2020-10-17T15:53:23+01:00","linkquality":81,"update_available":false,"voltage":3000}'
info  2020-10-17 15:53:23: MQTT publish: topic 'zigbee2mqtt/osram switch/action', payload 'up'
info  2020-10-17 15:53:23: MQTT publish: topic 'zigbee2mqtt/osram switch/action', payload 'up'
info  2020-10-17 15:53:23: MQTT publish: topic 'zigbee2mqtt/osram switch/action', payload 'up'
info  2020-10-17 15:53:23: MQTT publish: topic 'zigbee2mqtt/osram switch/action', payload 'up'
info  2020-10-17 15:53:23: MQTT publish: topic 'zigbee2mqtt/osram switch/action', payload 'up'
sebastianovide commented 3 years ago

and from docker-compose logs

➜  hass git:(master) ✗ docker-compose logs --tail=10 -f | grep zigbee-herdsman

zigbee2mqtt      | 2020-10-18T11:26:21.757Z zigbee-herdsman:adapter:zStack:unpi:parser <-- [254,26,68,129,0,0,8,0,208,172,3,47,1,93,0,51,76,65,0,0,6,17,15,4,254,10,0,21,119,10,101,254]
zigbee2mqtt      | 2020-10-18T11:26:21.758Z zigbee-herdsman:adapter:zStack:unpi:parser --- parseNext [254,26,68,129,0,0,8,0,208,172,3,47,1,93,0,51,76,65,0,0,6,17,15,4,254,10,0,21,119,10,101,254]
zigbee2mqtt      | 2020-10-18T11:26:21.758Z zigbee-herdsman:adapter:zStack:unpi:parser --> parsed 26 - 2 - 4 - 129 - [0,0,8,0,208,172,3,47,1,93,0,51,76,65,0,0,6,17,15,4,254,10,0,21,119,10] - 101
zigbee2mqtt      | 2020-10-18T11:26:21.758Z zigbee-herdsman:adapter:zStack:znp:AREQ <-- AF - incomingMsg - {"groupid":0,"clusterid":8,"srcaddr":44240,"srcendpoint":3,"dstendpoint":47,"wasbroadcast":1,"linkquality":93,"securityuse":0,"timestamp":4279347,"transseqnumber":0,"len":6,"data":{"type":"Buffer","data":[17,15,4,254,10,0]}}
zigbee2mqtt      | 2020-10-18T11:26:21.760Z zigbee-herdsman:controller:log Received 'zcl' data '{"frame":{"Header":{"frameControl":{"frameType":1,"manufacturerSpecific":false,"direction":0,"disableDefaultResponse":true,"reservedBits":0},"transactionSequenceNumber":15,"manufacturerCode":null,"commandIdentifier":4},"Payload":{"level":254,"transtime":10}},"address":44240,"endpoint":3,"linkquality":93,"groupID":0}'
zigbee2mqtt      | 2020-10-18T11:26:21.775Z zigbee-herdsman:adapter:zStack:unpi:parser --- parseNext [254]
zigbee2mqtt      | 2020-10-18T11:26:21.795Z zigbee-herdsman:adapter:zStack:unpi:parser <-- [26,68,129,0,0,8,0,208,172,3,13,1,93,0,51,76,65,0,0,6,17,15,4,254,10,0,21,119,10,71,254,26,68,129,0,0,8,0,208,172,3,110,1,93,0,51,76,65,0,0,6,17,15,4,254,10,0,21,119,10,36,254,26,68,129,0,0,8,0,208,172,3,11,1,93,0,51,76,65,0,0,6,17,15,4,254,10,0,21,119,10,65,254,26,68,129,0,0,8,0,208,172,3,8,1,93,0,51,76,65,0,0,6,17,15,4,254,10,0,21,119,10,66,254,26,68,129,0,0,8,0,208,172,3,1,1,93,0,51,76,65,0,0,6,17,15,4,254,10,0,21,119,10,75]
zigbee2mqtt      | 2020-10-18T11:26:21.795Z zigbee-herdsman:adapter:zStack:unpi:parser --- parseNext [254,26,68,129,0,0,8,0,208,172,3,13,1,93,0,51,76,65,0,0,6,17,15,4,254,10,0,21,119,10,71,254,26,68,129,0,0,8,0,208,172,3,110,1,93,0,51,76,65,0,0,6,17,15,4,254,10,0,21,119,10,36,254,26,68,129,0,0,8,0,208,172,3,11,1,93,0,51,76,65,0,0,6,17,15,4,254,10,0,21,119,10,65,254,26,68,129,0,0,8,0,208,172,3,8,1,93,0,51,76,65,0,0,6,17,15,4,254,10,0,21,119,10,66,254,26,68,129,0,0,8,0,208,172,3,1,1,93,0,51,76,65,0,0,6,17,15,4,254,10,0,21,119,10,75]
zigbee2mqtt      | 2020-10-18T11:26:21.795Z zigbee-herdsman:adapter:zStack:unpi:parser --> parsed 26 - 2 - 4 - 129 - [0,0,8,0,208,172,3,13,1,93,0,51,76,65,0,0,6,17,15,4,254,10,0,21,119,10] - 71
zigbee2mqtt      | 2020-10-18T11:26:21.796Z zigbee-herdsman:adapter:zStack:znp:AREQ <-- AF - incomingMsg - {"groupid":0,"clusterid":8,"srcaddr":44240,"srcendpoint":3,"dstendpoint":13,"wasbroadcast":1,"linkquality":93,"securityuse":0,"timestamp":4279347,"transseqnumber":0,"len":6,"data":{"type":"Buffer","data":[17,15,4,254,10,0]}}
zigbee2mqtt      | 2020-10-18T11:26:21.797Z zigbee-herdsman:controller:log Received 'zcl' data '{"frame":{"Header":{"frameControl":{"frameType":1,"manufacturerSpecific":false,"direction":0,"disableDefaultResponse":true,"reservedBits":0},"transactionSequenceNumber":15,"manufacturerCode":null,"commandIdentifier":4},"Payload":{"level":254,"transtime":10}},"address":44240,"endpoint":3,"linkquality":93,"groupID":0}'
zigbee2mqtt      | 2020-10-18T11:26:21.806Z zigbee-herdsman:adapter:zStack:unpi:parser --- parseNext [254,26,68,129,0,0,8,0,208,172,3,110,1,93,0,51,76,65,0,0,6,17,15,4,254,10,0,21,119,10,36,254,26,68,129,0,0,8,0,208,172,3,11,1,93,0,51,76,65,0,0,6,17,15,4,254,10,0,21,119,10,65,254,26,68,129,0,0,8,0,208,172,3,8,1,93,0,51,76,65,0,0,6,17,15,4,254,10,0,21,119,10,66,254,26,68,129,0,0,8,0,208,172,3,1,1,93,0,51,76,65,0,0,6,17,15,4,254,10,0,21,119,10,75]
zigbee2mqtt      | 2020-10-18T11:26:21.807Z zigbee-herdsman:adapter:zStack:unpi:parser --> parsed 26 - 2 - 4 - 129 - [0,0,8,0,208,172,3,110,1,93,0,51,76,65,0,0,6,17,15,4,254,10,0,21,119,10] - 36
zigbee2mqtt      | 2020-10-18T11:26:21.807Z zigbee-herdsman:adapter:zStack:znp:AREQ <-- AF - incomingMsg - {"groupid":0,"clusterid":8,"srcaddr":44240,"srcendpoint":3,"dstendpoint":110,"wasbroadcast":1,"linkquality":93,"securityuse":0,"timestamp":4279347,"transseqnumber":0,"len":6,"data":{"type":"Buffer","data":[17,15,4,254,10,0]}}
zigbee2mqtt      | 2020-10-18T11:26:21.809Z zigbee-herdsman:controller:log Received 'zcl' data '{"frame":{"Header":{"frameControl":{"frameType":1,"manufacturerSpecific":false,"direction":0,"disableDefaultResponse":true,"reservedBits":0},"transactionSequenceNumber":15,"manufacturerCode":null,"commandIdentifier":4},"Payload":{"level":254,"transtime":10}},"address":44240,"endpoint":3,"linkquality":93,"groupID":0}'
zigbee2mqtt      | 2020-10-18T11:26:21.818Z zigbee-herdsman:adapter:zStack:unpi:parser --- parseNext [254,26,68,129,0,0,8,0,208,172,3,11,1,93,0,51,76,65,0,0,6,17,15,4,254,10,0,21,119,10,65,254,26,68,129,0,0,8,0,208,172,3,8,1,93,0,51,76,65,0,0,6,17,15,4,254,10,0,21,119,10,66,254,26,68,129,0,0,8,0,208,172,3,1,1,93,0,51,76,65,0,0,6,17,15,4,254,10,0,21,119,10,75]
zigbee2mqtt      | 2020-10-18T11:26:21.818Z zigbee-herdsman:adapter:zStack:unpi:parser --> parsed 26 - 2 - 4 - 129 - [0,0,8,0,208,172,3,11,1,93,0,51,76,65,0,0,6,17,15,4,254,10,0,21,119,10] - 65
zigbee2mqtt      | 2020-10-18T11:26:21.819Z zigbee-herdsman:adapter:zStack:znp:AREQ <-- AF - incomingMsg - {"groupid":0,"clusterid":8,"srcaddr":44240,"srcendpoint":3,"dstendpoint":11,"wasbroadcast":1,"linkquality":93,"securityuse":0,"timestamp":4279347,"transseqnumber":0,"len":6,"data":{"type":"Buffer","data":[17,15,4,254,10,0]}}
zigbee2mqtt      | 2020-10-18T11:26:21.820Z zigbee-herdsman:controller:log Received 'zcl' data '{"frame":{"Header":{"frameControl":{"frameType":1,"manufacturerSpecific":false,"direction":0,"disableDefaultResponse":true,"reservedBits":0},"transactionSequenceNumber":15,"manufacturerCode":null,"commandIdentifier":4},"Payload":{"level":254,"transtime":10}},"address":44240,"endpoint":3,"linkquality":93,"groupID":0}'
zigbee2mqtt      | 2020-10-18T11:26:21.831Z zigbee-herdsman:adapter:zStack:unpi:parser --- parseNext [254,26,68,129,0,0,8,0,208,172,3,8,1,93,0,51,76,65,0,0,6,17,15,4,254,10,0,21,119,10,66,254,26,68,129,0,0,8,0,208,172,3,1,1,93,0,51,76,65,0,0,6,17,15,4,254,10,0,21,119,10,75]
zigbee2mqtt      | 2020-10-18T11:26:21.832Z zigbee-herdsman:adapter:zStack:unpi:parser --> parsed 26 - 2 - 4 - 129 - [0,0,8,0,208,172,3,8,1,93,0,51,76,65,0,0,6,17,15,4,254,10,0,21,119,10] - 66
zigbee2mqtt      | 2020-10-18T11:26:21.832Z zigbee-herdsman:adapter:zStack:znp:AREQ <-- AF - incomingMsg - {"groupid":0,"clusterid":8,"srcaddr":44240,"srcendpoint":3,"dstendpoint":8,"wasbroadcast":1,"linkquality":93,"securityuse":0,"timestamp":4279347,"transseqnumber":0,"len":6,"data":{"type":"Buffer","data":[17,15,4,254,10,0]}}
zigbee2mqtt      | 2020-10-18T11:26:21.834Z zigbee-herdsman:controller:log Received 'zcl' data '{"frame":{"Header":{"frameControl":{"frameType":1,"manufacturerSpecific":false,"direction":0,"disableDefaultResponse":true,"reservedBits":0},"transactionSequenceNumber":15,"manufacturerCode":null,"commandIdentifier":4},"Payload":{"level":254,"transtime":10}},"address":44240,"endpoint":3,"linkquality":93,"groupID":0}'
zigbee2mqtt      | 2020-10-18T11:26:21.845Z zigbee-herdsman:adapter:zStack:unpi:parser --- parseNext [254,26,68,129,0,0,8,0,208,172,3,1,1,93,0,51,76,65,0,0,6,17,15,4,254,10,0,21,119,10,75]
zigbee2mqtt      | 2020-10-18T11:26:21.845Z zigbee-herdsman:adapter:zStack:unpi:parser --> parsed 26 - 2 - 4 - 129 - [0,0,8,0,208,172,3,1,1,93,0,51,76,65,0,0,6,17,15,4,254,10,0,21,119,10] - 75
zigbee2mqtt      | 2020-10-18T11:26:21.846Z zigbee-herdsman:adapter:zStack:znp:AREQ <-- AF - incomingMsg - {"groupid":0,"clusterid":8,"srcaddr":44240,"srcendpoint":3,"dstendpoint":1,"wasbroadcast":1,"linkquality":93,"securityuse":0,"timestamp":4279347,"transseqnumber":0,"len":6,"data":{"type":"Buffer","data":[17,15,4,254,10,0]}}
zigbee2mqtt      | 2020-10-18T11:26:21.848Z zigbee-herdsman:controller:log Received 'zcl' data '{"frame":{"Header":{"frameControl":{"frameType":1,"manufacturerSpecific":false,"direction":0,"disableDefaultResponse":true,"reservedBits":0},"transactionSequenceNumber":15,"manufacturerCode":null,"commandIdentifier":4},"Payload":{"level":254,"transtime":10}},"address":44240,"endpoint":3,"linkquality":93,"groupID":0}'
zigbee2mqtt      | 2020-10-18T11:26:21.859Z zigbee-herdsman:adapter:zStack:unpi:parser --- parseNext []
zigbee2mqtt      | 2020-10-18T11:26:22.762Z zigbee-herdsman:adapter:zStack:unpi:parser <-- [254,27,68,129,0,0,0,3,208,172,3,47,1,93,0,212,64,66,0,0,7,17,16,10,114,1,10,0,21,119,10,26]
zigbee2mqtt      | 2020-10-18T11:26:22.763Z zigbee-herdsman:adapter:zStack:unpi:parser --- parseNext [254,27,68,129,0,0,0,3,208,172,3,47,1,93,0,212,64,66,0,0,7,17,16,10,114,1,10,0,21,119,10,26]
zigbee2mqtt      | 2020-10-18T11:26:22.764Z zigbee-herdsman:adapter:zStack:unpi:parser --> parsed 27 - 2 - 4 - 129 - [0,0,0,3,208,172,3,47,1,93,0,212,64,66,0,0,7,17,16,10,114,1,10,0,21,119,10] - 26
zigbee2mqtt      | 2020-10-18T11:26:22.766Z zigbee-herdsman:adapter:zStack:znp:AREQ <-- AF - incomingMsg - {"groupid":0,"clusterid":768,"srcaddr":44240,"srcendpoint":3,"dstendpoint":47,"wasbroadcast":1,"linkquality":93,"securityuse":0,"timestamp":4341972,"transseqnumber":0,"len":7,"data":{"type":"Buffer","data":[17,16,10,114,1,10,0]}}
zigbee2mqtt      | 2020-10-18T11:26:22.771Z zigbee-herdsman:controller:log Received 'zcl' data '{"frame":{"Header":{"frameControl":{"frameType":1,"manufacturerSpecific":false,"direction":0,"disableDefaultResponse":true,"reservedBits":0},"transactionSequenceNumber":16,"manufacturerCode":null,"commandIdentifier":10},"Payload":{"colortemp":370,"transtime":10}},"address":44240,"endpoint":3,"linkquality":93,"groupID":0}'
zigbee2mqtt      | 2020-10-18T11:26:22.777Z zigbee-herdsman:adapter:zStack:unpi:parser --- parseNext []
zigbee2mqtt      | 2020-10-18T11:26:22.784Z zigbee-herdsman:adapter:zStack:unpi:parser <-- [254,27,68,129,0,0,0,3,208,172,3,13,1,93,0,212,64,66,0,0,7,17,16,10,114,1,10,0,21,119,10,56,254,27,68,129,0,0,0,3,208,172,3,110,1,93,0,212,64,66,0,0,7,17,16,10,114,1,10,0,21,119,10,91,254,27,68,129,0,0,0,3,208,172,3,11,1,93,0,212,64,66,0,0,7,17,16,10,114,1,10,0,21,119,10,62,254,27,68,129,0,0,0,3,208,172,3,8,1,93,0,212,64,66,0,0,7,17,16,10,114,1,10,0,21,119,10,61,254,27,68,129,0,0,0,3,208,172,3,1,1,93,0,212,64,66,0,0,7,17,16,10,114,1,10,0,21,119,10,52]
zigbee2mqtt      | 2020-10-18T11:26:22.786Z zigbee-herdsman:adapter:zStack:unpi:parser --- parseNext [254,27,68,129,0,0,0,3,208,172,3,13,1,93,0,212,64,66,0,0,7,17,16,10,114,1,10,0,21,119,10,56,254,27,68,129,0,0,0,3,208,172,3,110,1,93,0,212,64,66,0,0,7,17,16,10,114,1,10,0,21,119,10,91,254,27,68,129,0,0,0,3,208,172,3,11,1,93,0,212,64,66,0,0,7,17,16,10,114,1,10,0,21,119,10,62,254,27,68,129,0,0,0,3,208,172,3,8,1,93,0,212,64,66,0,0,7,17,16,10,114,1,10,0,21,119,10,61,254,27,68,129,0,0,0,3,208,172,3,1,1,93,0,212,64,66,0,0,7,17,16,10,114,1,10,0,21,119,10,52]
zigbee2mqtt      | 2020-10-18T11:26:22.787Z zigbee-herdsman:adapter:zStack:unpi:parser --> parsed 27 - 2 - 4 - 129 - [0,0,0,3,208,172,3,13,1,93,0,212,64,66,0,0,7,17,16,10,114,1,10,0,21,119,10] - 56
zigbee2mqtt      | 2020-10-18T11:26:22.789Z zigbee-herdsman:adapter:zStack:znp:AREQ <-- AF - incomingMsg - {"groupid":0,"clusterid":768,"srcaddr":44240,"srcendpoint":3,"dstendpoint":13,"wasbroadcast":1,"linkquality":93,"securityuse":0,"timestamp":4341972,"transseqnumber":0,"len":7,"data":{"type":"Buffer","data":[17,16,10,114,1,10,0]}}
zigbee2mqtt      | 2020-10-18T11:26:22.796Z zigbee-herdsman:controller:log Received 'zcl' data '{"frame":{"Header":{"frameControl":{"frameType":1,"manufacturerSpecific":false,"direction":0,"disableDefaultResponse":true,"reservedBits":0},"transactionSequenceNumber":16,"manufacturerCode":null,"commandIdentifier":10},"Payload":{"colortemp":370,"transtime":10}},"address":44240,"endpoint":3,"linkquality":93,"groupID":0}'
zigbee2mqtt      | 2020-10-18T11:26:22.801Z zigbee-herdsman:adapter:zStack:unpi:parser --- parseNext [254,27,68,129,0,0,0,3,208,172,3,110,1,93,0,212,64,66,0,0,7,17,16,10,114,1,10,0,21,119,10,91,254,27,68,129,0,0,0,3,208,172,3,11,1,93,0,212,64,66,0,0,7,17,16,10,114,1,10,0,21,119,10,62,254,27,68,129,0,0,0,3,208,172,3,8,1,93,0,212,64,66,0,0,7,17,16,10,114,1,10,0,21,119,10,61,254,27,68,129,0,0,0,3,208,172,3,1,1,93,0,212,64,66,0,0,7,17,16,10,114,1,10,0,21,119,10,52]
zigbee2mqtt      | 2020-10-18T11:26:22.802Z zigbee-herdsman:adapter:zStack:unpi:parser --> parsed 27 - 2 - 4 - 129 - [0,0,0,3,208,172,3,110,1,93,0,212,64,66,0,0,7,17,16,10,114,1,10,0,21,119,10] - 91
zigbee2mqtt      | 2020-10-18T11:26:22.802Z zigbee-herdsman:adapter:zStack:znp:AREQ <-- AF - incomingMsg - {"groupid":0,"clusterid":768,"srcaddr":44240,"srcendpoint":3,"dstendpoint":110,"wasbroadcast":1,"linkquality":93,"securityuse":0,"timestamp":4341972,"transseqnumber":0,"len":7,"data":{"type":"Buffer","data":[17,16,10,114,1,10,0]}}
zigbee2mqtt      | 2020-10-18T11:26:22.807Z zigbee-herdsman:controller:log Received 'zcl' data '{"frame":{"Header":{"frameControl":{"frameType":1,"manufacturerSpecific":false,"direction":0,"disableDefaultResponse":true,"reservedBits":0},"transactionSequenceNumber":16,"manufacturerCode":null,"commandIdentifier":10},"Payload":{"colortemp":370,"transtime":10}},"address":44240,"endpoint":3,"linkquality":93,"groupID":0}'
zigbee2mqtt      | 2020-10-18T11:26:22.811Z zigbee-herdsman:adapter:zStack:unpi:parser --- parseNext [254,27,68,129,0,0,0,3,208,172,3,11,1,93,0,212,64,66,0,0,7,17,16,10,114,1,10,0,21,119,10,62,254,27,68,129,0,0,0,3,208,172,3,8,1,93,0,212,64,66,0,0,7,17,16,10,114,1,10,0,21,119,10,61,254,27,68,129,0,0,0,3,208,172,3,1,1,93,0,212,64,66,0,0,7,17,16,10,114,1,10,0,21,119,10,52]
zigbee2mqtt      | 2020-10-18T11:26:22.812Z zigbee-herdsman:adapter:zStack:unpi:parser --> parsed 27 - 2 - 4 - 129 - [0,0,0,3,208,172,3,11,1,93,0,212,64,66,0,0,7,17,16,10,114,1,10,0,21,119,10] - 62
zigbee2mqtt      | 2020-10-18T11:26:22.813Z zigbee-herdsman:adapter:zStack:znp:AREQ <-- AF - incomingMsg - {"groupid":0,"clusterid":768,"srcaddr":44240,"srcendpoint":3,"dstendpoint":11,"wasbroadcast":1,"linkquality":93,"securityuse":0,"timestamp":4341972,"transseqnumber":0,"len":7,"data":{"type":"Buffer","data":[17,16,10,114,1,10,0]}}
zigbee2mqtt      | 2020-10-18T11:26:22.817Z zigbee-herdsman:controller:log Received 'zcl' data '{"frame":{"Header":{"frameControl":{"frameType":1,"manufacturerSpecific":false,"direction":0,"disableDefaultResponse":true,"reservedBits":0},"transactionSequenceNumber":16,"manufacturerCode":null,"commandIdentifier":10},"Payload":{"colortemp":370,"transtime":10}},"address":44240,"endpoint":3,"linkquality":93,"groupID":0}'
zigbee2mqtt      | 2020-10-18T11:26:22.820Z zigbee-herdsman:adapter:zStack:unpi:parser --- parseNext [254,27,68,129,0,0,0,3,208,172,3,8,1,93,0,212,64,66,0,0,7,17,16,10,114,1,10,0,21,119,10,61,254,27,68,129,0,0,0,3,208,172,3,1,1,93,0,212,64,66,0,0,7,17,16,10,114,1,10,0,21,119,10,52]
zigbee2mqtt      | 2020-10-18T11:26:22.820Z zigbee-herdsman:adapter:zStack:unpi:parser --> parsed 27 - 2 - 4 - 129 - [0,0,0,3,208,172,3,8,1,93,0,212,64,66,0,0,7,17,16,10,114,1,10,0,21,119,10] - 61
zigbee2mqtt      | 2020-10-18T11:26:22.820Z zigbee-herdsman:adapter:zStack:znp:AREQ <-- AF - incomingMsg - {"groupid":0,"clusterid":768,"srcaddr":44240,"srcendpoint":3,"dstendpoint":8,"wasbroadcast":1,"linkquality":93,"securityuse":0,"timestamp":4341972,"transseqnumber":0,"len":7,"data":{"type":"Buffer","data":[17,16,10,114,1,10,0]}}
zigbee2mqtt      | 2020-10-18T11:26:22.823Z zigbee-herdsman:controller:log Received 'zcl' data '{"frame":{"Header":{"frameControl":{"frameType":1,"manufacturerSpecific":false,"direction":0,"disableDefaultResponse":true,"reservedBits":0},"transactionSequenceNumber":16,"manufacturerCode":null,"commandIdentifier":10},"Payload":{"colortemp":370,"transtime":10}},"address":44240,"endpoint":3,"linkquality":93,"groupID":0}'
zigbee2mqtt      | 2020-10-18T11:26:22.826Z zigbee-herdsman:adapter:zStack:unpi:parser --- parseNext [254,27,68,129,0,0,0,3,208,172,3,1,1,93,0,212,64,66,0,0,7,17,16,10,114,1,10,0,21,119,10,52]
zigbee2mqtt      | 2020-10-18T11:26:22.826Z zigbee-herdsman:adapter:zStack:unpi:parser --> parsed 27 - 2 - 4 - 129 - [0,0,0,3,208,172,3,1,1,93,0,212,64,66,0,0,7,17,16,10,114,1,10,0,21,119,10] - 52
zigbee2mqtt      | 2020-10-18T11:26:22.826Z zigbee-herdsman:adapter:zStack:znp:AREQ <-- AF - incomingMsg - {"groupid":0,"clusterid":768,"srcaddr":44240,"srcendpoint":3,"dstendpoint":1,"wasbroadcast":1,"linkquality":93,"securityuse":0,"timestamp":4341972,"transseqnumber":0,"len":7,"data":{"type":"Buffer","data":[17,16,10,114,1,10,0]}}
zigbee2mqtt      | 2020-10-18T11:26:22.829Z zigbee-herdsman:controller:log Received 'zcl' data '{"frame":{"Header":{"frameControl":{"frameType":1,"manufacturerSpecific":false,"direction":0,"disableDefaultResponse":true,"reservedBits":0},"transactionSequenceNumber":16,"manufacturerCode":null,"commandIdentifier":10},"Payload":{"colortemp":370,"transtime":10}},"address":44240,"endpoint":3,"linkquality":93,"groupID":0}'
zigbee2mqtt      | 2020-10-18T11:26:22.832Z zigbee-herdsman:adapter:zStack:unpi:parser --- parseNext []
Koenkk commented 3 years ago

@sebastianovide does it work now? Looking at https://github.com/Koenkk/zigbee2mqtt/issues/962#issuecomment-711024551 it seems events are provided now.

sebastianovide commented 3 years ago

no. It still turning on and off all the lights...

Koenkk commented 3 years ago

@sebastianovide and what happens if you configure now? (while making sure the remote is awake and seeing Successfully configured in the logs)

sebastianovide commented 3 years ago

for some reason now it is refusing to configure. I've press a button, I see the switch is sending that command ("up") and immediately after I send the configure but it breaks...

info  2020-10-19 15:14:34: MQTT publish: topic 'zigbee2mqtt/osram switch', payload '{"action":"","battery":100,"last_seen":"2020-10-19T15:14:33+01:00","linkquality":54,"update_available":false,"voltage":3000}'
info  2020-10-19 15:14:34: MQTT publish: topic 'zigbee2mqtt/osram switch/action', payload 'up'
info  2020-10-19 15:14:34: MQTT publish: topic 'zigbee2mqtt/osram switch/action', payload 'up'
info  2020-10-19 15:14:34: MQTT publish: topic 'zigbee2mqtt/osram switch/action', payload 'up'
info  2020-10-19 15:14:34: MQTT publish: topic 'zigbee2mqtt/osram switch/action', payload 'up'
info  2020-10-19 15:14:34: MQTT publish: topic 'zigbee2mqtt/osram switch/action', payload 'up'
debug 2020-10-19 15:14:35: Received MQTT message on 'zigbee2mqtt/bridge/configure' with data 'osram switch'
info  2020-10-19 15:14:35: Configuring 'osram switch'
error 2020-10-19 15:14:45: Failed to configure 'osram switch', attempt 2 (Error: Bind 0x000d6f000e1b7b68/1 genOnOff from '0x00124b0021600247/1' failed (AREQ - ZDO - bindRsp after 10000ms)
    at Timeout._onTimeout (/app/node_modules/zigbee-herdsman/dist/utils/waitress.js:46:35)
    at listOnTimeout (internal/timers.js:549:17)
    at processTimers (internal/timers.js:492:7))
Koenkk commented 3 years ago

@sebastianovide maybe bind fails when the device is connected trough a router. Try repairing it very close to the coordinator.

sebastianovide commented 3 years ago

cool.... it helped... did it 3 times. The last time worked 👍

frank-f commented 3 years ago

@sebastianovide maybe bind fails when the device is connected trough a router. Try repairing it very close to the coordinator.

This helped me too. IMO it should be added as a note on the device page, because the behaviour was very unexpected for me.

bkbilly commented 12 months ago

I just bought this device and I tried adding it on my zigbee network, but it controls all the lights and switches I have connected, even if I stop the zigbee2mqtt service.

I've tried resetting the device (middle + down buttons for 10 sec) and pairing it near the coordinator (middle + up buttons for 3 sec), but everytime it connects, it still controls all the devices.

Could you suggest what else to try?

dziedzic99 commented 2 months ago

For future reference a hackish solution which worked for me: Create an empty group Bind each button to this group with On off cluster Now the button just produces events. No more random turning stuff on and off.