search

Koenkk / zigbee-herdsman

A Node.js Zigbee library
MIT License
454 stars 278 forks source link

[WIP]: EFR32 EZSP adapter implementation and test #319

Open kirovilya opened 3 years ago

kirovilya commented 3 years ago

After accepting the alpha version of the code, now I propose to write comments here until we complete the development.

The adapter is designed to work with EFR32 chips using the EZSP v8 protocol. Recommended firmware NCP 6.7.8.

The work with devices with such chips was tested:

Settings:

Worked:

TODO:

I urge the developers to participate in the finalization of the adapter. I'm not an expert in TypeScript and EmberZNet, so I ask for help.

MattWestb commented 3 years ago

@kirovilya Is your E180 110% working OK with its EZSP firmware ? Its sounds like some parameters in the firmware is not good and its getting locked and not acking all packages.

I can being bad parameters setting in Z2M but or is being in the NCP firmware.

Have some one with other adapter trying doing OTA updating ?

Or trying doing one fast test with your E180 with ZHA and you can see its working OK doing OTA updating (you can modding ZHA doing firmware download 2 for testing OTA updating in Z2M).

If the problem is in the NCP firmware its very bad if you is trying finding somthing that is (not) bad in your Z2M code!!

kirovilya commented 3 years ago

@MattWestb I think the firmware for the E180 is working, the rest of the actions work. I think that I set some configuration parameters (in the z2m adapter) incorrectly. later I will try on another stick and on the sonoff bridge

MattWestb commented 3 years ago

Then its very OK only that you is not hunting things in the wrong place and going in the wall :-))

If you need downgrading firmware on IKEA device in ZHA you finding the patch here: https://github.com/home-assistant/core/issues/47177#issuecomment-797056118

deCONZ can do the same with manual selecting the firmware to updating the device with.

I have using both method and they is working well.

kirovilya commented 3 years ago

It's strange ... at first everything goes well, but as soon as it reaches 4000, the stick immediately stops responding to the request. Perhaps this is also due to some queues that I made inside the adapter ... But why - I don't know yet ...

z2m-ota3.zip

digiblur commented 3 years ago

Anyone test the HUSBZB-1 with this after upgrading it to 6.7.8 firmware? I tried the other day along with another user but it just made Z2M hang at start up indefinitely. I will give it a shot again this weekend.

MattWestb commented 3 years ago

For the EZSP 6.7.8.0 looks being stable on all devices i have getting firmware upgrades for and EZSP on the application APT level compatible but no machine cod compatible so all shall working the same with Z2M.

The only large problem ZHA is having is with Sonoff ZBB / ERF32MG2 devices that is making strange things.

Did you flashing the 115K2 or the 57K6 comport speed firmware on the HUSBZB-1 ?

digiblur commented 3 years ago

Did you flashing the 115K2 or the 57K6 comport speed firmware on the HUSBZB-1 ?

Both. Which is recommended? (asking for a friend that is going to try it this weekend)

MattWestb commented 3 years ago

The hardware dont have any problem with both but the 115K2 is getting the data thru the pipe 100% faster = good. (the packet trace is running on 1M6 without hardware flow control on the chip so the weak part is the USB side)

If have the coordinator installed in ZHA you need patching the config for getting it working if you is changing the comport speed or you must delete and reinstall the ZHA integration with the correct comport speed. Instruction for changing the comport speed fold the text out with the arrow.

PM You have the list (little above) with all known working EZSP 6.7.8.0 firmware we have getting working on ZHA and shall also working on Z2M 2.

digiblur commented 3 years ago

I wasn't using ZHA.

MattWestb commented 3 years ago

Then changing the comport speed in Z2M config and all shall working well :-)))

digiblur commented 3 years ago

Then changing the comport speed in Z2M config and all shall working well :-)))

Set the port to 57600 and z2m doesn't start, immediately fails saying it can't form the network. The same port and device work fine on ZHA though. 

Assertion failed

Assertion failed

Zigbee2MQTT:error 2021-03-18 17:48:13: Error while starting zigbee-herdsman

Zigbee2MQTT:error 2021-03-18 17:48:13: Failed to start zigbee

Zigbee2MQTT:error 2021-03-18 17:48:13: Exiting...

Zigbee2MQTT:error 2021-03-18 17:48:13: Error: Failure forming network:139
Status: Downloaded newer image for walthowd/husbzb-firmware:latest
{"ports": [{"stackVersion": "6.7.8-373", "deviceType": "zigbee", "pid": "8A2A", "port": "/dev/ttyUSB2", "vid": "10C4"}]}
Found zigbee port at /dev/ttyUSB2 running 6.7.8-373
oriolism commented 3 years ago

Im having issues pairing the IKEA Remote E1524/E1810. I can see the device on the webpage but it wont detect any button on the logs. Anyone has this working with the Sonoff ZbBrige?

Zigbee2MQTT:info 2021-03-18 19:52:27: Configuring '0x14b457fffe4f0a12'

Zigbee2MQTT:error 2021-03-18 19:52:27: Failed to configure '0x14b457fffe4f0a12', attempt 2 (Error: Bind 0x14b457fffe4f0a12/1 genOnOff from '901' failed (Incorrect value passed)

at new EmberEUI64 (/app/node_modules/zigbee-herdsman/dist/adapter/ezsp/driver/types/named.js:73:23)

at EZSPAdapter.<anonymous> (/app/node_modules/zigbee-herdsman/dist/adapter/ezsp/adapter/ezspAdapter.js:375:33)

at Generator.next (<anonymous>)

at /app/node_modules/zigbee-herdsman/dist/adapter/ezsp/adapter/ezspAdapter.js:27:71

at new Promise (<anonymous>)

at __awaiter (/app/node_modules/zigbee-herdsman/dist/adapter/ezsp/adapter/ezspAdapter.js:23:12)

at Object.func (/app/node_modules/zigbee-herdsman/dist/adapter/ezsp/adapter/ezspAdapter.js:373:52)

at Queue.<anonymous> (/app/node_modules/zigbee-herdsman/dist/utils/queue.js:29:46)

at Generator.next (<anonymous>)

at /app/node_modules/zigbee-herdsman/dist/utils/queue.js:8:71)

Zigbee2MQTT:info 2021-03-18 19:52:27: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"interview_successful","meta":{"description":"TRADFRI remote control","friendly_name":"0x14b457fffe4f0a12","model":"E1524/E1810","supported":true,"vendor":"IKEA"},"type":"pairing"}'

kirovilya commented 3 years ago

@digiblur Can you record debug logs? https://www.zigbee2mqtt.io/information/debug.html#zigbee-herdsman-debug-logging

digiblur commented 3 years ago

@digiblur Can you record debug logs? https://www.zigbee2mqtt.io/information/debug.html#zigbee-herdsman-debug-logging

Sure thing! I will get them as soon as I can.

snakesrules94 commented 3 years ago

Hi there, exactly the same problem with the same remote and the same Sonoff zigbee bride . I've also the same error when trying with a "hacked" silvercrest gateway . Here is a full debug log : https://pastebin.com/XqjH3PCz

kirovilya commented 3 years ago

@snakesrules94 @oriolism try checking on the latest dev-version

kirovilya commented 3 years ago

@digiblur try to use rtscts config option

kayiticindir commented 3 years ago

I use sonoff zigbee bridge to z2m. Load tasmota firmware v9.2 and ncp-uart-sw_6.7.8_115200. Always is ok. Sensor state and switch state is ok. But when I switch turn on / off timeout error.

(node:329) UnhandledPromiseRejectionWarning: Error: {"frameId":85,"sequence":260} after 10000ms at Timeout._onTimeout (/app/node_modules/zigbee-herdsman/dist/utils/waitress.js:67:35) at listOnTimeout (internal/timers.js:554:17) at processTimers (internal/timers.js:497:7) (node:329) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag--unhandled-rejections=strict(see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 12)

kirovilya commented 3 years ago

@kayiticindir Try pairing the switch again. Collect debug logs https://www.zigbee2mqtt.io/information/debug.html#zigbee-herdsman-debug-logging

kayiticindir commented 3 years ago

@kayiticindir Try pairing the switch again. Collect debug logs https://www.zigbee2mqtt.io/information/debug.html#zigbee-herdsman-debug-logging

https://pastebin.com/PrLeyMWW

snakesrules94 commented 3 years ago

@snakesrules94 @oriolism try checking on the latest dev-version

Hi Kirovilya , device seems to be paired OK now , but no reaction on button press . Here the log when i press the main center button on the remote : zigbee-herdsman:adapter:ezsp:uart <-- [7132b1a96b2a164fa6904b23aa546d499d4e2721eda867943b7e] [113,50,177,169,107,42,22,79,166,144,75,35,170,84,109,73,157,78,39,33,237,168,103,148,59,126] +6s zigbee-herdsman:adapter:ezsp:uart Recv DATA frame (7,1,0): 7132b1a96b2a164fa6904b23aa546d499d4e2721eda867943b7e +5ms zigbee-herdsman:adapter:ezsp:uart Send ACK frame (0) +5ms zigbee-herdsman:adapter:ezsp:uart --> [8070787e] [128,112,120,126] +5ms zigbee-herdsman:adapter:ezsp:log <=== Frame: 7090013f0003fdff0401060001ff000100008a006600 +6s zigbee-herdsman:adapter:ezsp:log <=== Application frame 63 (messageSentHandler) received: 03fdff0401060001ff000100008a006600 +5ms zigbee-herdsman:adapter:ezsp:log <=== Application frame 63 (messageSentHandler) parsed: 3,65533,EmberApsFrame: {"profileId":260,"clusterId":6,"sourceEndpoint":1,"destinationEndpoint":255,"options":256,"groupId":0,"sequence":138},0,102, +7ms but nothing published on MQTT side so no action ...

kirovilya commented 3 years ago

@snakesrules94 "destinationEndpoint":255 hmm... we don't have such an endpoint ... strange.

snakesrules94 commented 3 years ago

@snakesrules94 "destinationEndpoint":255 hmm... we don't have such an endpoint ... strange.

Indeed ... To be clear , remote is an IKEA Remote E1524/E1810 , tested/working 100% on Z2M master branch and CC2531 dongle . I've tested this morning with latest Z2M dev branch with a Sonoff bridge ( tasmota ) and a Lidl flashed gateway with same behaviour , pairing Ok but no reaction to buttons.

kirovilya commented 3 years ago

@snakesrules94 I guess it works thanks to the special hack of the ZNP firmware :) https://github.com/Koenkk/Z-Stack-firmware/blob/master/coordinator/Z-Stack_Home_1.2/firmware.patch#L105 I'll think about how this can be repeated for EZSP without changing the firmware

digiblur commented 3 years ago

Error log https://paste.ubuntu.com/p/vzrSs6fZMb/

kirovilya commented 3 years ago

@digiblur error 0x8B on formNetwork mean

An unsupported power setting was specified.

PHY_INVALID_POWER = 0x8B

I don’t know how to fix it yet ... I’ll look

MattWestb commented 3 years ago

Setting EZSP_CONFIG_TX_POWER_MODE ? Or EmberNetworkParameters uint8_t radioTxPower A power setting, in dBm. ?

Search for power in the: https://www.silabs.com/documents/public/user-guides/ug100-ezsp-reference-guide.pdf

kirovilya commented 3 years ago

@MattWestb currently CONFIG_TX_POWER_MODE = 3 and radioTxPower = 20

MattWestb commented 3 years ago

But its depends of the chip is its one 0 6 10 or 20 dBm chip in the adapter and i dont knowing if its working forcing one 0 dBm chip accepting 20 as TXPower.

kirovilya commented 3 years ago

@MattWestb hmm. then you need to take from the settings ... or set common value. thank you.

MattWestb commented 3 years ago

I think one default is needed and one "user setting" if setting it higher (is not needed if your network is having some god routers that doing god radio coverage).

kirovilya commented 3 years ago

@digiblur can you try in your installation make change in file zigbee-herdsman/dist/adapter/ezsp/driver/driver.js line 170 from: parameters.radioTxPower = 20; to parameters.radioTxPower = 10; and check

Hedda commented 3 years ago

But its depends of the chip is its one 0 6 10 or 20 dBm chip in the adapter and i dont knowing if its working forcing one 0 dBm chip accepting 20 as TXPower.

@MattWestb hmm. then you need to take from the settings ... or set common value. thank you.

@kirovilya TX Power Output Settings would be good but maybe hardcode different defaults for all the known chips if FW has info?

https://www.silabs.com/wireless/zigbee/efr32mg21-series-2-socs

Part Number MCU Core Frequency (MHz) Flash RAM Output Power Range (dBm) Receive Sensitivity
EFR32MG21B020F1024IM32 ARM Cortex-M33 80 1024 96 Min -20 and Max +20 -104 (250 kbps O-QPSK DSSS)
EFR32MG21B010F1024IM32 ARM Cortex-M33 80 1024 96 Min -20  and Max +10.5 -104 (250 kbps O-QPSK DSSS)
EFR32MG21B010F512IM32 ARM Cortex-M33 80 512 64 Min -20  and Max +10.5 -104 (250 kbps O-QPSK DSSS)
EFR32MG21B010F768IM32 ARM Cortex-M33 80 768 64 Min -20  and Max +10.5 -104 (250 kbps O-QPSK DSSS)
EFR32MG21B020F512IM32 ARM Cortex-M33 80 512 64 Min -20  and Max +20 -104 (250 kbps O-QPSK DSSS)
EFR32MG21B020F768IM32 ARM Cortex-M33 80 768 64 Min -20  and Max +20 -104 (250 kbps O-QPSK DSSS)
EFR32MG21A010F1024IM32 ARM Cortex-M33 80 1024 96 Min -20  and Max +10 -104 (250 kbps O-QPSK DSSS)
EFR32MG21A010F512IM32 ARM Cortex-M33 80 512 64 Min -20  and Max +10 -104 (250 kbps O-QPSK DSSS)
EFR32MG21A010F768IM32 ARM Cortex-M33 80 768 64 Min -20  and Max +10 -104 (250 kbps O-QPSK DSSS)
EFR32MG21A020F1024IM32 ARM Cortex-M33 80 1024 96 Min -20  and Max +20 -104 (250 kbps O-QPSK DSSS)
EFR32MG21A020F512IM32 ARM Cortex-M33 80 512 64 Min -20  and Max +20 -104 (250 kbps O-QPSK DSSS)
EFR32MG21A020F768IM32 ARM Cortex-M33 80 768 64 Min -20  and Max +20 -104 (250 kbps O-QPSK DSSS)

https://www.silabs.com/wireless/zigbee/efr32mg12-series-1-modules

Part Number MCU Core Flash RAM Radio Output Power Range (dBm)
MGM12P02F1024GA ARM Cortex-M4 1024 256 2.4 GHz Min -30 and Max +10
MGM12P02F1024GE ARM Cortex-M4 1024 256 2.4 GHz Min -30 and Max +10
MGM12P22F1024GA ARM Cortex-M4 1024 256 2.4 GHz Min -30 and Max +10
MGM12P22F1024GE ARM Cortex-M4 1024 256 2.4 GHz Min -30 and Max +10
MGM12P32F1024GA ARM Cortex-M4 1024 256 2.4 GHz Min -30  and Max +17
MGM12P32F1024GE ARM Cortex-M4 1024 256 2.4 GHz Min -30 and Max +17

https://www.silabs.com/wireless/zigbee/efr32mg13-series-1-modules

Part Number MCU Core Flash RAM Output Power Range (dBm)
MGM13P02F512GA ARM Cortex-M4 512 64 Min-30 Max +10
MGM13P02F512GE ARM Cortex-M4 512 64 Min-30  Max +10
MGM13P12F512GA ARM Cortex-M4 512 64 Min-30 Max +19
MGM13P12F512GE ARM Cortex-M4 512 64 Min-30 Max +19
MGM13S02F512GA ARM Cortex-M4 512 64 Min-30 Max +10
MGM13S02F512GN ARM Cortex-M4 512 64 Min-30 Max +10
MGM13S12F512GA ARM Cortex-M4 512 64 Min-30 Max +19
MGM13S12F512GN ARM Cortex-M4 512 64 Min-30 Max +19

As you can see below, even when only looking at efr32mg12 and efr32mg21 the TX power dBm range goes from -30 to +20

Note that this might be lower or higher but it is really rare that dBm is higher in consumer Zigbee products because in many/most countries you need to seek a legal exception from the general law which limitation for PSD (Power Spectral Density) of not going above 20 dBm output power in this frequency range. https://www.silabs.com/community/wireless/zigbee-and-thread/knowledge-base.entry.html/2019/01/15/maximum_allowed_powe-DtbX

kirovilya commented 3 years ago

@snakesrules94 @oriolism @digiblur try checking on the latest dev-version, again... for the IKEA remote control, I have made a dynamic binding to the group so far. those. when the first notification arrives that a button has been pressed on the remote control, then bind the coordinator to the group specified in the notification. this is not very correct and the first event will be skipped. but for now so be it.

MattWestb commented 3 years ago

@kirovilya Is it needed setting the power out put from the host system ? ZHA/bellows is letting the most parameters that the firmware / chip is having for not braking devices then setting to high parameters and letting the optimal for the device. Perhaps better letting is as firmware / chip and only changing it with custom config that the user is putting in self if like doing some "tuning".

kirovilya commented 3 years ago

@MattWestb yes, mqtt-commands can set TransmitPower, but so far for this adapter I have not implemented

juan11perez commented 3 years ago

zigbee-herdsman/dist/adapter/ezsp/driver/driver.js

@kirovilya where is this file? I donloaded koenkk/zigbee2mqtt:latest-dev and cant see this directory. Do I have to manually add from somewhere?

thank you

kirovilya commented 3 years ago

@juan11perez these changes have already in the dev-version z2m

digiblur commented 3 years ago

zigbee-herdsman/dist/adapter/ezsp/driver/driver.js

@kirovilya where is this file? I donloaded koenkk/zigbee2mqtt:latest-dev and cant see this directory. Do I have to manually add from somewhere?

thank you

You need to bash into the container itself.

juan11perez commented 3 years ago

@digiblur thank you. I cant do that now. It's not completing the start up.

digiblur commented 3 years ago

@digiblur thank you. I cant do that now. It's not completing the start up.

I had the same issue so I changed the config to make it get stuck but then I saw the version I had already had the change made.

juan11perez commented 3 years ago

@digiblur thank you. ok so I got this Ethernet-connected tuya gateway working. just paired a xiaomi contact sensor and seems ok. will be trying a zigbee thermostat I've added via this

juan11perez commented 3 years ago

@kirovilya yes thank you; reason I was getting an error, was a silly conf. oversight on my part.

I can report below mentioned coordinator starts and is accepting devices without issue.

Tuya TYGWZ01 / Lidl / Silvercrest Smart Gateway hacked with DIY firmware zigpy/zigpy#650

barrtailor commented 3 years ago

@kirovilya yes thank you; reason I was getting an error, was a silly conf. oversight on my part.

I can report below mentioned coordinator starts and is accepting devices without issue.

Tuya TYGWZ01 / Lidl / Silvercrest Smart Gateway hacked with DIY firmware zigpy/zigpy#650

sooo it's working?

oriolism commented 3 years ago

@snakesrules94 @oriolism @digiblur try checking on the latest dev-version, again... for the IKEA remote control, I have made a dynamic binding to the group so far. those. when the first notification arrives that a button has been pressed on the remote control, then bind the coordinator to the group specified in the notification. this is not very correct and the first event will be skipped. but for now so be it.

I can confirm that the Ikea remote is paired and receiving the commands. The only issue so far is the first command is lost.

juan11perez commented 3 years ago

@kirovilya @barrtailor To clarify I initially modified the gateway using this which referred to the first serialgateway.bin, Today I updated to latest serialgateway and I stopped seeing the "Assertion failed" error except when connecting to one device which is not in z2m devices.js yet. (I've added it here using cc2531 and it works).

I have paired these devices:

The 3 first devices with "native" integration work fine. The one I've manually added is half working. From the thermostat to z2m any action I execute is instantaneously reflected in the z2m gui. i.e on/off, temp set, etc. When I try to change from the gui to the thermostat, it takes about 2 minutes to execute. It first fires the "assertion failed" error and eventually carries out the command.

The one device I could not get to work is the Ikea E1743 button. It shows up, but does nothing.

snakesrules94 commented 3 years ago

hi all, really strange , i use the latest version Zigbee2MQTT:info 2021-03-26 17:22:08: Starting Zigbee2MQTT version 1.18.1-dev (commit #e56f6b6) Zigbee2MQTT:info 2021-03-26 17:22:08: Starting zigbee-herdsman (0.13.85) and while still playing with my ikea remote , pairing is ok , but sill no actions ... @oriolism : can you see the buttons action in the log ?

oriolism commented 3 years ago

hi all, really strange , i use the latest version Zigbee2MQTT:info 2021-03-26 17:22:08: Starting Zigbee2MQTT version 1.18.1-dev (commit #e56f6b6) Zigbee2MQTT:info 2021-03-26 17:22:08: Starting zigbee-herdsman (0.13.85) and while still playing with my ikea remote , pairing is ok , but sill no actions ... @oriolism : can you see the buttons action in the log ?

Yes I see them.

Zigbee2MQTT:debug 2021-03-26 13:32:49: Received Zigbee message from 'IKEA_Family', type 'commandToggle', cluster 'genOnOff', data '{}' from endpoint 1 with groupID 28133

Zigbee2MQTT:info 2021-03-26 13:32:49: MQTT publish: topic 'zigbee2mqtt/IKEA_Family', payload '{"action":"toggle","battery":87,"linkquality":92,"update":{"state":"idle"},"update_available":false}'

Zigbee2MQTT:info 2021-03-26 13:32:49: MQTT publish: topic 'zigbee2mqtt/IKEA_Family', payload '{"action":"","battery":87,"linkquality":92,"update":{"state":"idle"},"update_available":false}'

Zigbee2MQTT:info 2021-03-26 13:32:49: MQTT publish: topic 'zigbee2mqtt/IKEA_Family/action', payload 'toggle'

Zigbee2MQTT:debug 2021-03-26 13:32:54: Received Zigbee message from 'IKEA_Family', type 'commandStepWithOnOff', cluster 'genLevelCtrl', data '{"stepmode":0,"stepsize":43,"transtime":5}' from endpoint 1 with groupID 28133

Zigbee2MQTT:info 2021-03-26 13:32:54: MQTT publish: topic 'zigbee2mqtt/IKEA_Family', payload '{"action":"brightness_up_click","battery":87,"linkquality":48,"update":{"state":"idle"},"update_available":false}'

Zigbee2MQTT:info 2021-03-26 13:32:54: MQTT publish: topic 'zigbee2mqtt/IKEA_Family', payload '{"action":"","battery":87,"linkquality":48,"update":{"state":"idle"},"update_available":false}'

Zigbee2MQTT:info 2021-03-26 13:32:54: MQTT publish: topic 'zigbee2mqtt/IKEA_Family/action', payload 'brightness_up_click'

Zigbee2MQTT:debug 2021-03-26 13:32:58: Received Zigbee message from 'IKEA_Family', type 'commandStep', cluster 'genLevelCtrl', data '{"stepmode":1,"stepsize":43,"transtime":5}' from endpoint 1 with groupID 28133

Zigbee2MQTT:info 2021-03-26 13:32:58: MQTT publish: topic 'zigbee2mqtt/IKEA_Family', payload '{"action":"brightness_down_click","battery":87,"linkquality":56,"update":{"state":"idle"},"update_available":false}'

Zigbee2MQTT:info 2021-03-26 13:32:58: MQTT publish: topic 'zigbee2mqtt/IKEA_Family', payload '{"action":"","battery":87,"linkquality":56,"update":{"state":"idle"},"update_available":false}'

Zigbee2MQTT:info 2021-03-26 13:32:58: MQTT publish: topic 'zigbee2mqtt/IKEA_Family/action', payload 'brightness_down_click'

Zigbee2MQTT:debug 2021-03-26 13:33:02: Received Zigbee message from 'IKEA_Family', type 'commandTradfriArrowSingle', cluster 'genScenes', data '{"value":256,"value2":13}' from endpoint 1 with groupID 28133

Zigbee2MQTT:info 2021-03-26 13:33:02: MQTT publish: topic 'zigbee2mqtt/IKEA_Family', payload '{"action":"arrow_right_click","battery":87,"linkquality":68,"update":{"state":"idle"},"update_available":false}'

Zigbee2MQTT:info 2021-03-26 13:33:02: MQTT publish: topic 'zigbee2mqtt/IKEA_Family', payload '{"action":"","battery":87,"linkquality":68,"update":{"state":"idle"},"update_available":false}'

Zigbee2MQTT:info 2021-03-26 13:33:02: MQTT publish: topic 'zigbee2mqtt/IKEA_Family/action', payload 'arrow_right_click'

Zigbee2MQTT:debug 2021-03-26 13:33:11: Received Zigbee message from 'IKEA_Family', type 'commandTradfriArrowSingle', cluster 'genScenes', data '{"value":257,"value2":13}' from endpoint 1 with groupID 28133

Zigbee2MQTT:info 2021-03-26 13:33:11: MQTT publish: topic 'zigbee2mqtt/IKEA_Family', payload '{"action":"arrow_left_click","battery":87,"linkquality":52,"update":{"state":"idle"},"update_available":false}'

Zigbee2MQTT:info 2021-03-26 13:33:11: MQTT publish: topic 'zigbee2mqtt/IKEA_Family', payload '{"action":"","battery":87,"linkquality":52,"update":{"state":"idle"},"update_available":false}'

Zigbee2MQTT:info 2021-03-26 13:33:11: MQTT publish: topic 'zigbee2mqtt/IKEA_Family/action', payload 'arrow_left_click'

Zigbee2MQTT:debug 2021-03-26 13:33:15: Received Zigbee message from 'IKEA_Family', type 'commandTradfriArrowSingle', cluster 'genScenes', data '{"value":256,"value2":13}' from endpoint 1 with groupID 28133

Zigbee2MQTT:info 2021-03-26 13:33:15: MQTT publish: topic 'zigbee2mqtt/IKEA_Family', payload '{"action":"arrow_right_click","battery":87,"linkquality":64,"update":{"state":"idle"},"update_available":false}'

Zigbee2MQTT:info 2021-03-26 13:33:15: MQTT publish: topic 'zigbee2mqtt/IKEA_Family', payload '{"action":"","battery":87,"linkquality":64,"update":{"state":"idle"},"update_available":false}'

Zigbee2MQTT:info 2021-03-26 13:33:15: MQTT publish: topic 'zigbee2mqtt/IKEA_Family/action', payload 'arrow_right_click'

Zigbee2MQTT:debug 2021-03-26 13:33:20: Received Zigbee message from 'IKEA_Family', type 'commandToggle', cluster 'genOnOff', data '{}' from endpoint 1 with groupID 28133

Zigbee2MQTT:info 2021-03-26 13:33:20: MQTT publish: topic 'zigbee2mqtt/IKEA_Family', payload '{"action":"toggle","battery":87,"linkquality":48,"update":{"state":"idle"},"update_available":false}'

Zigbee2MQTT:info 2021-03-26 13:33:20: MQTT publish: topic 'zigbee2mqtt/IKEA_Family', payload '{"action":"","battery":87,"linkquality":48,"update":{"state":"idle"},"update_available":false}'

Zigbee2MQTT:info 2021-03-26 13:33:20: MQTT publish: topic 'zigbee2mqtt/IKEA_Family/action', payload 'toggle'

snakesrules94 commented 3 years ago

@oriolism : indeed , it works for you ! what is your main coordinator ? on my side i've tested with a sonoff gateway ( Tasmota ) and a "hacked" lidl gateway , but same behaviour on both . I will try tomorrow to start from scratch with Z2B install .

oriolism commented 3 years ago

My coordinator is a Sonoff ZBBridge Zigbee WiFi Bridge re-flashed with Tasmota.