search

Koenkk / zigbee-herdsman

A Node.js Zigbee library
MIT License
456 stars 277 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.

snakesrules94 commented 3 years ago

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

ok , same as mine . I will came back after a fresh install and new tests.

barrtailor commented 3 years ago

I'm going to give it a shot on my HUSBZB-1 this weekend

snakesrules94 commented 3 years ago

I don't understand :-( fresh install of latest dev Z2M Zigbee2MQTT:info 2021-03-27 16:43:00: Starting Zigbee2MQTT version 1.18.1-dev (commit #41a4dea) Zigbee2MQTT:info 2021-03-27 16:43:00: Starting zigbee-herdsman (0.13.86)

My ikea remote is pairing OK Zigbee2MQTT:info 2021-03-27 16:44:53: Successfully interviewed '0x90fd9ffffed5c2db', device has successfully been paired Zigbee2MQTT:info 2021-03-27 16:44:53: Device '0x90fd9ffffed5c2db' is supported, identified as: IKEA TRADFRI remote control (E1524/E1810) Zigbee2MQTT:info 2021-03-27 16:44:53: MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"definition":{"description":"TRADFRI remote control","exposes":[{"access":1,"description":"Remaining battery in %","name":"battery","property":"battery","type":"numeric","unit":"%","value_max":100,"value_min":0},{"access":1,"description":"Triggered action (e.g. a button click)","name":"action","property":"action","type":"enum","values":["brightness_down_release","toggle_hold","toggle","arrow_left_click","arrow_right_click","arrow_left_hold","arrow_right_hold","arrow_left_release","arrow_right_release","brightness_up_click","brightness_down_click","brightness_up_hold","brightness_up_release"]},{"access":1,"description":"Link quality (signal strength)","name":"linkquality","property":"linkquality","type":"numeric","unit":"lqi","value_max":255,"value_min":0}],"model":"E1524/E1810","supports_ota":true,"vendor":"IKEA"},"friendly_name":"0x90fd9ffffed5c2db","ieee_address":"0x90fd9ffffed5c2db","status":"successful","supported":true},"type":"device_interview"}'

and that's it ... nothing more when i press buttons . I can see the frames in zigbee-herdsman debug log , but nothing on Z2M side.

edit : same behaviour with latest from today Zigbee2MQTT:info 2021-03-27 16:12:01: Starting Zigbee2MQTT version 1.18.1-dev (commit #f8f79d3) Zigbee2MQTT:info 2021-03-27 16:12:01: Starting zigbee-herdsman (0.13.87)

juan11perez commented 3 years ago

@snakesrules94 I tried several times with an Ikea E1743 and have the same issue. It works with the cc2531 (Z 1.2), but not with this tuya gateway.

snakesrules94 commented 3 years ago

@snakesrules94 I tried several times with an Ikea E1743 and have the same issue. It works with the cc2531 (Z 1.2), but not with this tuya gateway.

@juan11perez : check posts from Oriolism , it works for him with a Sonoff gateway since a few days , but no way on my side with the same gateway and also a lidl one .

kirovilya commented 3 years ago

Guys, there is a problem with the IKEA remotes - they send their messages to the group they have created. For sticks cc2531, this is solved at the firmware level https://github.com/Koenkk/zigbee-herdsman/issues/319#issuecomment-804870132. There is no for ezsp-sticks yet. I tried to solve this by signing a coordinator for this group, but apparently not everything is as I wanted. I will study the problem

snakesrules94 commented 3 years ago

@kirovilya : this workaround is not working ? https://github.com/Koenkk/zigbee-herdsman/issues/319#issuecomment-806063641 seems to be OK regarding Oriolism in https://github.com/Koenkk/zigbee-herdsman/issues/319#issuecomment-807920146

oriolism commented 3 years ago

I have two E1524/E1810 remotes paired and working. The issue is that when the remote is not used for a while the first pressed button is not detected, after that it works fine. @snakesrules94 try pressing the center button a few times during the pairing process. Screen Shot 2021-03-27 at 2 26 02 PM

kirovilya commented 3 years ago

@snakesrules94 it also works for me, but apparently sometimes it is not correct. here you can see that the group was detected groupID 28133 https://github.com/Koenkk/zigbee-herdsman/issues/319#issuecomment-808399434 But in your logs groupID is 0 https://github.com/Koenkk/zigbee-herdsman/issues/319#issuecomment-804851209

snakesrules94 commented 3 years ago

@snakesrules94 try pressing the center button a few times during the pairing process.

Yes , this is exactly what i'm doing but as pointed by Kirovilya , maybe some issues with groupID.

juan11perez commented 3 years ago

@kirovilya Good day. On the tuya gateway sensors continue to work ok. The mains powered switch works fine until I add the mains powered thermostat. It seems to be spamming with messages that are slowing the system. As I mentioned before if I modify the physical device, the feedback is as expected, but If I modify from the gui it can take over a minute to respond. I dont observe this behaviour with the CC2531.

Adding some logs https://pastebin.com/aYRNtnhs

Thank you

snakesrules94 commented 3 years ago

@snakesrules94 it also works for me, but apparently sometimes it is not correct. here you can see that the group was detected groupID 28133 #319 (comment) But in your logs groupID is 0 #319 (comment)

Hello , i've tried today with a brand new Ikea remote E1524 and another brand new E1743 , same thing , they both pair OK , with groupID 0 , and no action in the end .

Hedda commented 3 years ago

Guys, there is a problem with the IKEA remotes - they send their messages to the group they have created. For sticks cc2531, this is solved at the firmware level #319 (comment). There is no for ezsp-sticks yet. I tried to solve this by signing a coordinator for this group, but apparently not everything is as I wanted. I will study the problem

If that is the case then could perhaps someone implemented a solution or workaround in zha-device-handlers, bellows, or zigpy?

https://github.com/zigpy/zha-device-handlers

https://github.com/zigpy/bellows

https://github.com/zigpy/zigpy

brugk000 commented 3 years ago

I am testing the new Itead zigbee 3.0 stick with the docker-dev version of zigbee2mqtt. Getting the next errors when starting the container:

Using '/app/data' as data directory

zigbee2mqtt@1.18.1-dev start /app node index.js Zigbee2MQTT:info 2021-03-29 17:47:53: Logging to console and directory: '/app/data/log/2021-03-29.17-47-52' filename: log.txt Zigbee2MQTT:info 2021-03-29 17:47:53: Starting Zigbee2MQTT version 1.18.1-dev (commit #ddbfa02) Zigbee2MQTT:info 2021-03-29 17:47:53: Starting zigbee-herdsman (0.13.87) Zigbee2MQTT:error 2021-03-29 17:48:13: Error while starting zigbee-herdsman Zigbee2MQTT:error 2021-03-29 17:48:13: Failed to start zigbee Zigbee2MQTT:error 2021-03-29 17:48:13: Exiting... Zigbee2MQTT:error 2021-03-29 17:48:13: Error: Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms) at ZStackAdapter. (/app/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js:94:31) at Generator.throw () at rejected (/app/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js:25:65) npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! zigbee2mqtt@1.18.1-dev start: node index.js npm ERR! Exit status 1  npm ERR! Failed at the zigbee2mqtt@1.18.1-dev start script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above. npm ERR! A complete log of this run can be found in: npm ERR! /root/.npm/_logs/2021-03-29T15_48_13_517Z-debug.log

The stick is placed in an usb 3.0 port on a rpi4 in /dev/ttyUSB0 Any suggestions?

kirovilya commented 3 years ago

@brugk000 ZStackAdapter does not apply to ezsp. you may not have specified the adapter type in the configuration file. read the first post here

brugk000 commented 3 years ago

@brugk000 ZStackAdapter does not apply to ezsp. you may not have specified the adapter type in the configuration file. read the first post here

Thanks for the pointer. Missed that information. Now its working

fludstank commented 3 years ago 
Error: Failure forming network:139

I am getting the same error on my HUSBZB-1 that was flashed with the 115k 6.7.8 firmware. When I tried with the regular 6.7.8 firmware it would just hang at Starting zigbee-herdsman

debug log below:

0 info it worked if it ends with ok
1 verbose cli [ '/usr/local/bin/node', '/usr/local/bin/npm', 'start' ]
2 info using npm@6.14.11
3 info using node@v14.16.0
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle zigbee2mqtt@1.18.1-dev~prestart: zigbee2mqtt@1.18.1-dev
6 info lifecycle zigbee2mqtt@1.18.1-dev~start: zigbee2mqtt@1.18.1-dev
7 verbose lifecycle zigbee2mqtt@1.18.1-dev~start: unsafe-perm in lifecycle true
8 verbose lifecycle zigbee2mqtt@1.18.1-dev~start: PATH: /usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/app/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
9 verbose lifecycle zigbee2mqtt@1.18.1-dev~start: CWD: /app
10 silly lifecycle zigbee2mqtt@1.18.1-dev~start: Args: [ '-c', 'node index.js' ]
11 silly lifecycle zigbee2mqtt@1.18.1-dev~start: Returned: code: 1  signal: null
12 info lifecycle zigbee2mqtt@1.18.1-dev~start: Failed to exec start script
13 verbose stack Error: zigbee2mqtt@1.18.1-dev start: `node index.js`
13 verbose stack Exit status 1
13 verbose stack     at EventEmitter.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16)
13 verbose stack     at EventEmitter.emit (events.js:315:20)
13 verbose stack     at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack     at ChildProcess.emit (events.js:315:20)
13 verbose stack     at maybeClose (internal/child_process.js:1048:16)
13 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:288:5)
14 verbose pkgid zigbee2mqtt@1.18.1-dev
15 verbose cwd /app
16 verbose Linux 4.14.222-odroidxu4
17 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "start"
18 verbose node v14.16.0
19 verbose npm  v6.14.11
20 error code ELIFECYCLE
21 error errno 1
22 error zigbee2mqtt@1.18.1-dev start: `node index.js`
22 error Exit status 1
23 error Failed at the zigbee2mqtt@1.18.1-dev start script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]
kirovilya commented 3 years ago

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

fludstank commented 3 years ago

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

https://pastebin.com/siR5nBLu

kirovilya commented 3 years ago

@fludstank again EMBER_PHY_INVALID_POWER - do you use the latest version of z2m-dev? this bug has already been fixed

fludstank commented 3 years ago

from docker-compose

  zigbee2mqtt:
    container_name: zigbee2mqtt
    image: koenkk/zigbee2mqtt:latest-dev
fludstank commented 3 years ago

just pulled the latest and got this https://pastebin.com/69RQMzwN

Getting closer!

edit: Still getting 2021-03-30T08:32:09.347Z zigbee-herdsman:adapter:ezsp:uart Send DATA frame (2,2,0): 32000168000c035a6967426565416c6c69616e6365303901030507090b0d0f00020406080a0c0d000000000000000000 2021-03-30T08:32:09.347Z zigbee-herdsman:adapter:ezsp:uart waiting (3) 2021-03-30T08:32:09.347Z zigbee-herdsman:adapter:ezsp:uart --> [227021a93c2a19b103fd2d67cf30d325f02746c58eab57b2fcc5668ef57532a8ebcfda6987f5cbd6d5d2698c4623a9ec76849f7e] [34,112,33,169,60,42,25,177,3,253,45,103,207,48,211,37,240,39,70,197,142,171,87,178,252,197,102,142,245,117,50,168,235,207,218,105,135,245,203,214,213,210,105,140,70,35,169,236,118,132,159,126] 2021-03-30T08:32:09.347Z zigbee-herdsman:adapter:ezsp:uart waiting (3) success 2021-03-30T08:32:09.355Z zigbee-herdsman:adapter:ezsp:uart <-- [2370a1a93c2a15806f7e] [35,112,161,169,60,42,21,128,111,126] 2021-03-30T08:32:09.355Z zigbee-herdsman:adapter:ezsp:uart Recv DATA frame (2,3,0): 2370a1a93c2a15806f7e 2021-03-30T08:32:09.355Z zigbee-herdsman:adapter:ezsp:uart Send ACK frame (3) 2021-03-30T08:32:09.355Z zigbee-herdsman:adapter:ezsp:uart --> [83401b7e] [131,64,27,126] 2021-03-30T08:32:09.356Z zigbee-herdsman:adapter:ezsp:log <=== Frame: 328001680000 2021-03-30T08:32:09.356Z zigbee-herdsman:adapter:ezsp:log <=== Application frame 104 (setInitialSecurityState) received: 00 2021-03-30T08:32:09.356Z zigbee-herdsman:adapter:ezsp:log <=== Application frame 104 (setInitialSecurityState) parsed: 0 2021-03-30T08:32:09.357Z zigbee-herdsman:adapter:ezsp:log ===> Send command formNetwork: (EmberNetworkParameters: {"panId":6754,"extendedPanId":[221,221,221,221,221,221,221,221],"radioTxPower":10,"radioChannel":11,"joinMethod":0,"nwkManagerId":0,"nwkUpdateId":0,"channels":134215680}) 2021-03-30T08:32:09.358Z zigbee-herdsman:adapter:ezsp:log ===> Send data formNetwork: (3300011e00dddddddddddddddd621a0a0b0000000000f8ff07) 2021-03-30T08:32:09.358Z zigbee-herdsman:adapter:ezsp:uart Send DATA frame (3,3,0): 3300011e00dddddddddddddddd621a0a0b0000000000f8ff07 2021-03-30T08:32:09.359Z zigbee-herdsman:adapter:ezsp:uart waiting (4) 2021-03-30T08:32:09.359Z zigbee-herdsman:adapter:ezsp:uart --> [337121a94a2ac86f844997f87788f053964527abedce677302c1c4227e] [51,113,33,169,74,42,200,111,132,73,151,248,119,136,240,83,150,69,39,171,237,206,103,115,2,193,196,34,126] 2021-03-30T08:32:09.359Z zigbee-herdsman:adapter:ezsp:uart waiting (4) success 2021-03-30T08:32:09.364Z zigbee-herdsman:adapter:ezsp:uart <-- [3471a1a94a2a9ea1bb7e] [52,113,161,169,74,42,158,161,187,126] 2021-03-30T08:32:09.364Z zigbee-herdsman:adapter:ezsp:uart Recv DATA frame (3,4,0): 3471a1a94a2a9ea1bb7e 2021-03-30T08:32:09.364Z zigbee-herdsman:adapter:ezsp:uart Send ACK frame (4) 2021-03-30T08:32:09.364Z zigbee-herdsman:adapter:ezsp:uart --> [8430fc7e] [132,48,252,126] 2021-03-30T08:32:09.364Z zigbee-herdsman:adapter:ezsp:log <=== Frame: 3380011e008b 2021-03-30T08:32:09.365Z zigbee-herdsman:adapter:ezsp:log <=== Application frame 30 (formNetwork) received: 8b 2021-03-30T08:32:09.365Z zigbee-herdsman:adapter:ezsp:log <=== Application frame 30 (formNetwork) parsed: 139 2021-03-30T08:32:09.365Z zigbee-herdsman:adapter:ezsp:log Failure forming network:139 Zigbee2MQTT:error 2021-03-30 04:32:09: Error while starting zigbee-herdsman Zigbee2MQTT:error 2021-03-30 04:32:09: Failed to start zigbee Zigbee2MQTT:error 2021-03-30 04:32:09: Check https://www.zigbee2mqtt.io/information/FAQ.html#help-zigbee2mqtt-fails-to-start for possible solutions Zigbee2MQTT:error 2021-03-30 04:32:09: Exiting... Zigbee2MQTT:error 2021-03-30 04:32:09: Error: Failure forming network:139 at Ezsp. (/app/node_modules/zigbee-herdsman/dist/adapter/ezsp/driver/ezsp.js:375:23) at Generator.next () at fulfilled (/app/node_modules/zigbee-herdsman/dist/adapter/ezsp/driver/ezsp.js:24:58) npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! zigbee2mqtt@1.18.1-dev start: node index.js npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the zigbee2mqtt@1.18.1-dev start script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

snakesrules94 commented 3 years ago

Hi there ! good news : commands from Ikea E1524 & E1743 are now received and interpreted ! nice work !

kai74 commented 3 years ago

Thanks, @Koenkk foe pointing me to the right place.

What happened

I can't start Zigbee2mqtt Edge, it worked perfectly, but for some reason, I now get the following message

What did you expect to happen

To run as it did earlier :)

How to reproduce it (minimal and precise)

Start Zigbee2MQTT edge.

Debug info

Zigbee2MQTT version: Edge Adapter hardware: Sonoff ZHABridge Adapter firmware version: 9.3.1.2(zbbridge)

Log: https://pastebin.com/YSn7U9yb

I can connect to the unit with the IP, I can update the firmware. all working good. Maybe I need to flash it once more?

Solution: After a new flash, it is back to normal

Update : the problem is back. I think sonoff is not working with this solution. It works for a couple of days, and then it stops. Is it any other users with the same problem?

fludstank commented 3 years ago

major progress on the HUSBZB-1 with the newest dev release. I did get this error message, but the container started for the first time.

https://pastebin.com/cUxBRFxL

Next up will be to attempt to pair devices!!! Thank you for all of your great code!

fludstank commented 3 years ago

Also been getting quite a few Watchdog heartbeat timeout Error

https://pastebin.com/MRQvwKZ2

juan11perez commented 3 years ago

Good day. Running the tuya gateway

with last -dev the ikea 1743 button now works. Cant report on battery life yet; but it does report action/clicks correctly. Additionally I don't observe the usual message spamming this device produces with cc253x. Right now 1 click one message.

Also, xiaomi motion and contact sensors working as well as tuya ambient sensor and mains powered light switch.

Thank you.

brugk000 commented 3 years ago

Hi all, Using the new Itead V3.0 zigbee dongle on Z2M 1.18.1-dev on docker Successfully paired a Tuya compatible switch TS0121_plug, BW-SPH13 Getting the following errors : https://pastebin.com/T7heMNft

kirovilya commented 3 years ago

@brugk000 try to record debug log for configure moment https://www.zigbee2mqtt.io/information/debug.html#zigbee-herdsman-debug-logging

kirovilya commented 3 years ago

@fludstank hmm. some strange frame code comes FrameID 33781 (0x83F5). watchdog timeout - it's not scary, but suspicious, the stick did not respond to an nop-request in time

brugk000 commented 3 years ago

@brugk000 try to record debug log for configure moment https://www.zigbee2mqtt.io/information/debug.html#zigbee-herdsman-debug-logging

This is the log-file, i think the problem is around line 420. https://pastebin.com/92VAzxpA

snakesrules94 commented 3 years ago

Hello , i've got this in my log: https://pastebin.com/xjia5ad2

Error at line 6 , and also often the "assertion failed"

kirovilya commented 3 years ago

@snakesrules94 assertion - not critical, but other error need more debug logs

snakesrules94 commented 3 years ago

@snakesrules94 assertion - not critical, but other error need more debug logs

Ok , i relaunch in full debug mode .

kirovilya commented 3 years ago

@brugk000 looking at the log, device 0x588e81fffed3934a cannot bind. There may be several reasons: the device has left the network (for some reason), the device does not support bind. is this device now controlled from z2m? previously worked fine?

snakesrules94 commented 3 years ago

@kirovilya : cannot reproduce error until now , but sometimes strange bahaviour in the log : https://pastebin.com/4JteypWZ from line 9

brugk000 commented 3 years ago

@brugk000 looking at the log, device 0x588e81fffed3934a cannot bind. There may be several reasons: the device has left the network (for some reason), the device does not support bind. is this device now controlled from z2m? previously worked fine?

I will investigate the problem further

juan11perez commented 3 years ago

Good day, running the tuya gateway

Ikea button 1743: system completely drained a brand new battery in 24 hrs.

snakesrules94 commented 3 years ago

Ikea button 1743: system completely drained a brand new battery in 24 hrs.

Hello , i face the same problem in 2 IKEA remotes (E1524 & E1743) . I had some doubt about my battery , but after changing it , it also drains a brand new one in 24h.

MattWestb commented 3 years ago

@juan11perez @snakesrules94 Sonoff have not calibrating the radio on the chip then manufacturing the SM-011 module and the new USB Zigbe 3 stick so its working of tuned and many devices is having problem communicating with it. And most sleeping end device is burning batteries then trying communicating with the coordinator. They have patching the last firmware for compensating it in the EZSP 6.7.9.0 but its not yet verified too working 100%.

snakesrules94 commented 3 years ago

@MattWestb : right now i'm using an "hacked" lidl gateway with NCP_UHW_MG1B232_678_PA0-PA1-PB11_PA5-PA4.gbl firmware , not my sonoff gateway , but i guess the problem is the same.

MattWestb commented 3 years ago

I have not checking my 2 tuya ZBG if they is calibrated or not but i is doing that then i have time and resources free.

walthowd commented 3 years ago

Tested latest dev with Sonoff/Itead stick flashed with 6.7.9 -- can't join any devices, same behavior on ZHA in Home Assistant too, so seems like root issue is with stick or firmware.

Z2M full debug logs: https://paste.ubuntu.com/p/h9MgW94ts7/

juan11perez commented 3 years ago

@MattWestb thank you. I'm also using tuya gateway. not sure how to convert 6.7.9 to .gbl and is it possible to go back to 6.7.8 if .9 fails?

MattWestb commented 3 years ago

@juan11perez The firmware is only for Sonoff ZBB and its having different CPU (EFR32MG1X and EFR32MG21) and flash so its not possible flashing on tuya ZBGW.

For "other" (no Sonoff) its no use to flashing 6.7.9.0 then its no bug fixes in it and the Sonoff devs have patching the hardware calibrating of the radio then its not made in the factory that shall have being done.

I hope that tuya not have making the same mistake and need patched firmware for not getting problems with sleeping end device.

juan11perez commented 3 years ago

@MattWestb thank you. I can confirm that the gateway is draining the battery of the Ikea button. It does not have the same problem with xiaomi and tuya sensors.

snakesrules94 commented 3 years ago

Hi , still in test mode with latest dev commit & lidl gateway : Binding a Ikea E1743 remote with an Ikea LED1836G9 is not OK . Binding is successfull but no action on the light in the end .

juan11perez commented 3 years ago

Update. Still using the tuya gateway. In fact running 2 and in general works very well. On docker start it connects immediately without errors. The range is also very good. I ran a 2652 and the range is probably better, at least in my case.

Only issue I still see is the battery drainage on this ikea remote.

Thank you to the developers (@kirovilya and others) for bringing this additional option to the community.

MattWestb commented 3 years ago

Sounds great @juan11perez I have 2 tuya ZBGW and they is working very god if updating the firmware to EZSP 6.7.8.0 but i think they have doing the same mistake as Sonoff (ZBB and USB ZB3) = not calibrating the the radio so it can being miss tuned as also reported by some deCONZ radios. I still on the hunt for more info on tuya devices and also trying diagnosing deCONZ adapters how they (not) doing things in the mesh.

juan11perez commented 3 years ago

@MattWestb the gateway is working very well with the xiaomi sensors, motion, contact. I also have a xiaomi cube and works perfect as well. Tuya mains-powered switch also good. From ikea i only have that remote. (so no big deal to me) All in all I think it's very good. And the best attribute is this ability to place it anywhere. No need to physically connect to a server.