Comments (546)
It should work with ConBee I / II and RaspBee I / II since the protocol for all is the same. The difference is the device path:
- ConBee I /dev/ttyUSBx
- ConBee II /dev/ttyACMx
- RaspBee I / II /dev/ttyAMA0 or /dev/ttyS0
from zigbee-herdsman.
Any news, expected timeline ?
Looking forward to test this out
from zigbee-herdsman.
@felixstorm no it's not supported yet, you might want to give the CC2652R a try though Koenkk/zigbee2mqtt#1429 (which is fully supported in latest dev).
Just fyi for anybody following - I switched to the CC2652R and it has been working flawlessly for a few weeks now.
from zigbee-herdsman.
This has now been integrated and is available in the latest zigbee2mqtt dev branch. Many thanks @ChrisHae !
Keep in mind that this is not ready for production yet.
It seems to start fine but unfortunately I couldn't pair any devices, nothing appeared in the log after resetting a device (tried with some Xiaomi plugs, sensors and an Innr bulb), log: https://pastebin.com/gBLANJHn
from zigbee-herdsman.
I will update this over time and try to eliminate bugs, improve performance and add features.
Please note that interPAN functions likte touchlink are not implemented yet.
Right now I investigate why no devices are joining any more. This already worked but now I no longer receive any deviceAnnounce events when a device is powered on or was reset.
from zigbee-herdsman.
Another thing to improve USB startup was found today by disabling Linux MTP probes and Network Manager messing with serial interface. This might be useful for the CC2531 too.
Source: dresden-elektronik/deconz-rest-plugin#2419 (comment)
MTP probes and Network Manager access for ConBee II can be disabled by following udev rules:
cat /etc/udev/rules.d/69-conbee.rules
# ConBee II disbale modem manager and mtp probing
ATTRS{idVendor}=="1cf1", ATTRS{idProduct}=="0030", ENV{ID_MM_DEVICE_IGNORE}="1"
ATTRS{idVendor}=="1cf1", ATTRS{idProduct}=="0030", ENV{MTP_NO_PROBE}="1"
After creating this file the udev rules needs to be reloaded:
sudo udevadm control --reload-rules
The difference should be visible in journald when plugging the USB dongle:
sudo journald -xb -f
from zigbee-herdsman.
I uploaded a fix to this problem to the deconz branch. In addition to the zdp permit join request there is now also a write parameter request that sets the permit join parameter. I created a pull request for the master branch. Then you can test if it works.
from zigbee-herdsman.
@tafilz this really looks like a bug in deCONZ adapter. I will have a look. I didn't test it with RaspBee yet
Edit: the problem is wrong handling of incomming messages with a 64bit src address. It seems the RaspBee always sends messages with a 64bit src address. I need a little time for the fix. I think until next week.
from zigbee-herdsman.
@felixstorm no it's not supported yet, you might want to give the CC2652R a try though Koenkk/zigbee2mqtt#1429 (which is fully supported in latest dev).
from zigbee-herdsman.
Is it possible to test the Conbee build using the deconz branch?
from zigbee-herdsman.
@kelvin5290
@mike182uk
I uploaded some fixes and your problems with configure reporting or malformed packets should be gone.
Although I'm not completely done perhaps some devices could still make some errors when pairing or reporting but I'm on it.
from zigbee-herdsman.
I did some updates
- Renamed conbee to deconz
- zigbee-herdsman will automatically activate the deconz adapter when it detects one
- Path auto detection is also support, for zigbee2mqtt just set
serial:
port: null
from zigbee-herdsman.
@Koenkk Is Conbee 2 support considered to be working as of now?
I am currently pretty displeased with the CC2531 in my environment using HA 1.2 firmware (unable to pair more than 20 routing devices (ubisys), loosing devices from time to time and ended up splitting my network, also tried source routing variant, but that seemed to make it even worse). And since the Zigbee side used to work fine and appeared to be very stable with deCONZ and a Conbee (1) for about 1 year before switching to zigbee2mqtt (besides incomplete support for the ubisys window covering devices 😉), being able to use a Conbee (2) might be another option for me to try...
Thanks,
Felix
from zigbee-herdsman.
@Koenkk Thanks, the CC2652R would also have been my next option - I will order one from TI and try it. The ConBee (1) was really stable in the past and the CC2652R is pretty new, that was the only reason for preference 😉.
from zigbee-herdsman.
u/potedesballj posted this on Reddit
from zigbee-herdsman.
Thanks for everyone involved! For me with iobroker, Conbee II has started and devices are also connected
from zigbee-herdsman.
The same problem (/dev/ttyACM0) in combination with zigbee2mqtt and the conbee 2.
from zigbee-herdsman.
@tafilz implemented, you can now specify the adapter like (https://github.com/Koenkk/zigbee2mqtt.io/blob/develop/docs/information/configuration.md#configuration)
serial:
adapter: deconz
Will be available in the latest hassio edge in +- 4 hours from now.
from zigbee-herdsman.
I'm using the docker-compose approach @Nailik
from zigbee-herdsman.
UNSUPPORTED_ATTRIBUTE
errors are likely not related to conbee, please create an zigbee2mqtt issue containing a traffic sniff while this errors occurs. https://www.zigbee2mqtt.io/how_tos/how_to_sniff_zigbee_traffic.html
from zigbee-herdsman.
I can pair the tradfri signal repeater and it shows up in the dashboard. It seems to work as repeater but from time to time the system ask for configuration and than the errors appears... and sometimes the zigbee adapter restarts.
ok, I will have to observe this...
from zigbee-herdsman.
Hi!
Could you perhaps contact me on telegram (@Koenkk)?
from zigbee-herdsman.
Should this one be closed if Conbee/deconz is supported now as suggested by your answer... Sorry I have been and out of domotic and try to make progress on free time so I have been poking you on this topic here and there, sorry about that... Difficult to keep up will all the fork redirect I fall on and understand where the train is going exactly... :D
from zigbee-herdsman.
New reddit post says that Dresden Elektronik estimated that support will be ready mid-March 2020
https://www.reddit.com/r/homeassistant/comments/f8v81p/conbee_2_support_for_zigbee2mqtt_confirmed/
I wonder if this will only work with the newer ConBee II (ConBee 2) adapter or if it will also work with the older first-generation ConBee and RaspBee adapters as well?
I know that both the new and the old ConBee adapters support the same serial UART protocol: https://github.com/dresden-elektronik/deconz-rest-plugin/issues/158
from zigbee-herdsman.
Is this also working on windows? I have a conbee II plugged into my windows PC which I use for testing. It is connected as COM3 in device manager. How can I use it with zigbee2mqtt?
from zigbee-herdsman.
@Koenkk It seems devices not joining is a fw problem. Please try FW version deCONZ_ConBeeII_0x264a0700.bin
http://deconz.dresden-elektronik.de/deconz-firmware/
from zigbee-herdsman.
@ChrisHae Thank you for your work on the ConBeeII support. I have a ConBeeII stick an I plan to use it with zigbee2mqtt. As mentioned, it starts correctly now on the dev
branch but no device can join. Flashing the 0x264a0700 firmware didn't help for me.
from zigbee-herdsman.
I just tried zigbee2mqtt using the deconz
branch of zigbee-herdsman and my device joined successfully!
from zigbee-herdsman.
@ChrisHae We successfully start the stick Conbee II based on zigbee-heardsman 0.12.64 in iobroker.zigbee. Thank you!
from zigbee-herdsman.
Hi, do you have to flash the Conbee II or is it simply recognized automatically in the Zigbee2mqtt?
from zigbee-herdsman.
Hi, do you have to flash the Conbee II or is it simply recognized automatically in the Zigbee2mqtt?
Just plug it in. But I have the last firmware on it
from zigbee-herdsman.
from zigbee-herdsman.
Yes
from zigbee-herdsman.
Not working for me yet.
I have HomeAssistant setup on Docker and use the addon (https://github.com/danielwelch/hassio-zigbee2mqtt/blob/master/CHANGELOG.md)
Stacktrace:
zigbee2mqtt:info 2020-03-19 12:25:19: Logging to console and directory: '/share/zigbee2mqtt/log/2020-03-19.12-25-19' filename: log.txt
zigbee2mqtt:debug 2020-03-19 12:25:19: Removing old log directory '/share/zigbee2mqtt/log/2020-03-19.12-23-47'
zigbee2mqtt:debug 2020-03-19 12:25:19: Can't load state from file /share/zigbee2mqtt/state.json (doesn't exist)
zigbee2mqtt:info 2020-03-19 12:25:19: Starting zigbee2mqtt version 1.12.0 (commit #unknown)
zigbee2mqtt:info 2020-03-19 12:25:19: Starting zigbee-herdsman...
zigbee2mqtt:debug 2020-03-19 12:25:19: Using zigbee-herdsman with settings: '{"network":{"panID":6754,"extendedPanID":[221,221,221,221,221,221,221,221],"channelList":[11],"networkKey":"HIDDEN"},"databasePath":"/share/zigbee2mqtt/database.db","databaseBackupPath":"/share/zigbee2mqtt/database.db.backup","backupPath":"/share/zigbee2mqtt/coordinator_backup.json","serialPort":{"baudRate":115200,"rtscts":true,"path":"/dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2121195-if00"}}'
zigbee2mqtt:error 2020-03-19 12:25:26: Error while starting zigbee-herdsman
zigbee2mqtt:error 2020-03-19 12:25:26: Failed to start zigbee
zigbee2mqtt:error 2020-03-19 12:25:26: Exiting...
zigbee2mqtt:error 2020-03-19 12:25:26: Error: Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)
at ZStackAdapter.<anonymous> (/zigbee2mqtt-1.12.0/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js:71:23)
at Generator.throw (<anonymous>)
at rejected (/zigbee2mqtt-1.12.0/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js:6:65)
npm
ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start: `node index.js`
npm ERR!
Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] 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/2020-03-19T11_25_26_613Z-debug.log
2020-03-19T12:25:27: PM2 log: App [npm:0] exited with code [1] via signal [SIGINT]
2020-03-19T12:25:27: PM2 log: App [npm:0] starting in -fork mode-
2020-03-19T12:25:27: PM2 log: App [npm:0] online
> [email protected] start /zigbee2mqtt-1.12.0
> node index.js
from zigbee-herdsman.
"serialPort":{"baudRate":115200,"rtscts":true,"path":"/dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2121195-if00"}
maybe try port /dev/ttyACM0
from zigbee-herdsman.
"serialPort":{"baudRate":115200,"rtscts":true,"path":"/dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2121195-if00"}
maybe try port /dev/ttyACM0
I already tried it, same issue. The deconz addon https://github.com/home-assistant/hassio-addons/tree/master/deconz works with /dev/ttyACM0
from zigbee-herdsman.
"serialPort":{"baudRate":115200,"rtscts":true,"path":"/dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2121195-if00"}
maybe try port /dev/ttyACM0
I already tried it, same issue. The deconz addon https://github.com/home-assistant/hassio-addons/tree/master/deconz works with /dev/ttyACM0
i face the same issue and look like the debug log is not full print out. ref to the adapter.js, it will determine the device is zStack or deconz. Those log is missing. and it go to start zStack by default.
from zigbee-herdsman.
The detection is not working indeed, is the hassio adon running as privileged? https://www.zigbee2mqtt.io/information/docker.html#parameters-explanation
from zigbee-herdsman.
The detection is not working indeed, is the hassio adon running as privileged? https://www.zigbee2mqtt.io/information/docker.html#parameters-explanation
yes , the addon should run as privileged.
from zigbee-herdsman.
Note that this adapter not only work with the ConBee USB stick but also with the RaspBee Zigbee module for Raspberry Pi, because they share the same serial protocol. A more generic adapter name, like phoscon or deconz adapter, might be more fitting.
The deconz adapter should also work with the RaspBee module. The auto detection works only with USB devices.
Can we have maybe a setting like this, so it's possible to set the adapter manually to use serial only devices like the RaspBee?
serial:
adapter: <z-stack|deconz>
port: /dev/ttyS0
from zigbee-herdsman.
It seems to start now. But it doesnt seem to work right now
mosquitto_1 | 1584651976: mosquitto version 1.6.9 starting
mosquitto_1 | 1584651976: Config loaded from /mosquitto/config/mosquitto.conf.
mosquitto_1 | 1584651976: Opening ipv4 listen socket on port 1883.
mosquitto_1 | 1584651976: Opening ipv6 listen socket on port 1883.
zigbee2mqtt_1 | Using '/app/data' as data directory
zigbee2mqtt_1 |
zigbee2mqtt_1 | > [email protected] start /app
zigbee2mqtt_1 | > node index.js
zigbee2mqtt_1 |
zigbee2mqtt_1 | zigbee2mqtt:info 2020-03-19 22:06:17: Logging to console and directory: '/app/data/log/2020-03-19.22-06-17' filename: log.txt
zigbee2mqtt_1 | zigbee2mqtt:info 2020-03-19 22:06:17: Starting zigbee2mqtt version 1.12.0-dev (commit #e3fafcd) zigbee2mqtt_1 | zigbee2mqtt:info 2020-03-19 22:06:17: Starting zigbee-herdsman...
zigbee2mqtt_1 | CREATED DECONZ ADAPTER
zigbee2mqtt_1 | zigbee2mqtt:info 2020-03-19 22:06:18: zigbee-herdsman started
zigbee2mqtt_1 | zigbee2mqtt:info 2020-03-19 22:06:18: Coordinator firmware version: '{"type":"RaspBee","meta":{"transportrev":0,"product":0,"majorrel":38,"minorrel":53,"maintrel":0,"revision":"0x26350500"}}'
zigbee2mqtt_1 | zigbee2mqtt:info 2020-03-19 22:06:19: Currently 0 devices are joined:
zigbee2mqtt_1 | zigbee2mqtt:warn 2020-03-19 22:06:19: `permit_join` set to `true` in configuration.yaml.
zigbee2mqtt_1 | zigbee2mqtt:warn 2020-03-19 22:06:19: Allowing new devices to join.
zigbee2mqtt_1 | zigbee2mqtt:warn 2020-03-19 22:06:19: Set `permit_join` to `false` once you joined all devices. zigbee2mqtt_1 | zigbee2mqtt:info 2020-03-19 22:06:19: Zigbee: allowing new devices to join.
zigbee2mqtt_1 | zigbee2mqtt:info 2020-03-19 22:06:20: Connecting to MQTT server at mqtt://mosquitto
mosquitto_1 | 1584651980: New connection from 172.19.0.2 on port 1883.
mosquitto_1 | 1584651980: New client connected from 172.19.0.2 as mqttjs_55b5a1d6 (p2, c1, k60).
zigbee2mqtt_1 | zigbee2mqtt:info 2020-03-19 22:06:20: Connected to MQTT server
zigbee2mqtt_1 | zigbee2mqtt:info 2020-03-19 22:06:20: MQTT publish: topic 'zigbee2mqtt/bridge/state', payload 'online'
zigbee2mqtt_1 | zigbee2mqtt:info 2020-03-19 22:06:20: MQTT publish: topic 'zigbee2mqtt/bridge/config', payload '{"version":"1.12.0-dev","commit":"e3fafcd","coordinator":{"type":"RaspBee","meta":{"transportrev":0,"product":0,"majorrel":38,"minorrel":53,"maintrel":0,"revision":"0x26350500"}},"log_level":"info","permit_join":true}'
zigbee2mqtt_1 | (node:17) UnhandledPromiseRejectionWarning: RangeError: Offset is outside the bounds of the DataView
zigbee2mqtt_1 | at DataView.getUint8 (<anonymous>)
zigbee2mqtt_1 | at parseReadReceivedDataResponse (/app/node_modules/zigbee-herdsman/dist/adapter/deconz/driver/frameParser.js:210:27)
zigbee2mqtt_1 | at parseFrame (/app/node_modules/zigbee-herdsman/dist/adapter/deconz/driver/frameParser.js:334:32)zigbee2mqtt_1 | at Object.<anonymous> (/app/node_modules/zigbee-herdsman/dist/adapter/deconz/driver/frameParser.js:289:63)
zigbee2mqtt_1 | at Generator.next (<anonymous>)
zigbee2mqtt_1 | at /app/node_modules/zigbee-herdsman/dist/adapter/deconz/driver/frameParser.js:8:71
zigbee2mqtt_1 | at new Promise (<anonymous>)
zigbee2mqtt_1 | at __awaiter (/app/node_modules/zigbee-herdsman/dist/adapter/deconz/driver/frameParser.js:4:12) zigbee2mqtt_1 | at Object.processFrame [as default] (/app/node_modules/zigbee-herdsman/dist/adapter/deconz/driver/frameParser.js:288:12)
zigbee2mqtt_1 | at Driver.<anonymous> (/app/node_modules/zigbee-herdsman/dist/adapter/deconz/adapter/deconzAdapter.js:37:69)
zigbee2mqtt_1 | (node:17) 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: 1)
zigbee2mqtt_1 | (node:17) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
zigbee2mqtt_1 | (node:17) UnhandledPromiseRejectionWarning: RangeError: Offset is outside the bounds of the DataView
zigbee2mqtt_1 | at DataView.getUint8 (<anonymous>)
zigbee2mqtt_1 | at parseReadReceivedDataResponse (/app/node_modules/zigbee-herdsman/dist/adapter/deconz/driver/frameParser.js:210:27)
zigbee2mqtt_1 | at parseFrame (/app/node_modules/zigbee-herdsman/dist/adapter/deconz/driver/frameParser.js:334:32)zigbee2mqtt_1 | at Object.<anonymous> (/app/node_modules/zigbee-herdsman/dist/adapter/deconz/driver/frameParser.js:289:63)
zigbee2mqtt_1 | at Generator.next (<anonymous>)
zigbee2mqtt_1 | at /app/node_modules/zigbee-herdsman/dist/adapter/deconz/driver/frameParser.js:8:71
zigbee2mqtt_1 | at new Promise (<anonymous>)
zigbee2mqtt_1 | at __awaiter (/app/node_modules/zigbee-herdsman/dist/adapter/deconz/driver/frameParser.js:4:12) zigbee2mqtt_1 | at Object.processFrame [as default] (/app/node_modules/zigbee-herdsman/dist/adapter/deconz/driver/frameParser.js:288:12)
zigbee2mqtt_1 | at Driver.<anonymous> (/app/node_modules/zigbee-herdsman/dist/adapter/deconz/adapter/deconzAdapter.js:37:69)
zigbee2mqtt_1 | (node:17) 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: 2)
Edit: Need a debug log?
from zigbee-herdsman.
A debug log would help indeed but this probably has to be fixed by @ChrisHae (as its inside the deconz adapter)
from zigbee-herdsman.
How could you run it? For me the addon always removes the adapter type.
from zigbee-herdsman.
I have a ConBeeII.
I'll get this error, why is it not using adapter deconz? (see configuration.yaml futher down)
zigbee2mqtt:info 2020-03-22 11:21:32: Logging to console and directory: '/app/data/log/2020-03-22.11-21-32' filename: log.txt
zigbee2mqtt:info 2020-03-22 11:21:32: Starting zigbee2mqtt version 1.12.0 (commit #840b9d9)
zigbee2mqtt:info 2020-03-22 11:21:32: Starting zigbee-herdsman...
zigbee2mqtt:error 2020-03-22 11:21:40: Error while starting zigbee-herdsman
zigbee2mqtt:error 2020-03-22 11:21:40: Failed to start zigbee
zigbee2mqtt:error 2020-03-22 11:21:40: Exiting...
zigbee2mqtt:error 2020-03-22 11:21:40: 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:71:23)
at Generator.throw ()
at rejected (/app/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js:6:65)
configuration.yaml
...
Serial settings
serial:
adapter: deconz
port: /dev/ttyACM0
from zigbee-herdsman.
I have a ConBeeII.
I'll get this error, why is it not using adapter deconz? (see configuration.yaml futher down)zigbee2mqtt:info 2020-03-22 11:21:32: Logging to console and directory: '/app/data/log/2020-03-22.11-21-32' filename: log.txt
zigbee2mqtt:info 2020-03-22 11:21:32: Starting zigbee2mqtt version 1.12.0 (commit #840b9d9)
zigbee2mqtt:info 2020-03-22 11:21:32: Starting zigbee-herdsman...
zigbee2mqtt:error 2020-03-22 11:21:40: Error while starting zigbee-herdsman
zigbee2mqtt:error 2020-03-22 11:21:40: Failed to start zigbee
zigbee2mqtt:error 2020-03-22 11:21:40: Exiting...
zigbee2mqtt:error 2020-03-22 11:21:40: 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:71:23)
at Generator.throw ()
at rejected (/app/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js:6:65)
@muellererwin I was getting this error too until I added the following to my docker-compose.yaml
version: "3.5"
services:
z2m:
image: koenkk/zigbee2mqtt:latest
devices:
- /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2120741-if00:/dev/ttyACM0
volumes:
- /run/udev:/run/udev:ro
environment:
- TZ=Europe/London
privileged: true
Note the privileged: true
and the /run/udev:/run/udev:ro
volume mapping.
from zigbee-herdsman.
I have a ConBeeII.
I'll get this error, why is it not using adapter deconz? (see configuration.yaml futher down)zigbee2mqtt:info 2020-03-22 11:21:32: Logging to console and directory: '/app/data/log/2020-03-22.11-21-32' filename: log.txt
zigbee2mqtt:info 2020-03-22 11:21:32: Starting zigbee2mqtt version 1.12.0 (commit #840b9d9)
zigbee2mqtt:info 2020-03-22 11:21:32: Starting zigbee-herdsman...
zigbee2mqtt:error 2020-03-22 11:21:40: Error while starting zigbee-herdsman
zigbee2mqtt:error 2020-03-22 11:21:40: Failed to start zigbee
zigbee2mqtt:error 2020-03-22 11:21:40: Exiting...
zigbee2mqtt:error 2020-03-22 11:21:40: 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:71:23)
at Generator.throw ()
at rejected (/app/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js:6:65)configuration.yaml
...Serial settings
serial:
adapter: deconz
port: /dev/ttyACM0
I think the npm version doesn't have the setting adapter
yet.
Your version is running on commit 840b9d9 and the setting was intruduced with commit 6b9baf0.
Are you using the dev-branch of zigbee2mqtt? There is should work.
Also the ConBee stick should be able to get auto detected.
Path auto detection is also support, for zigbee2mqtt just set
serial: port: null
from zigbee-herdsman.
@msnelling: Thanks for your tips. Up and running now!
from zigbee-herdsman.
I uploaded a fix for RaspBee. It now uses 16bit NWK addresses that will solve some problems. I think it will be available soon.
from zigbee-herdsman.
My setup:
I am running zigbee2mqtt in a docker container on a raspberry pi.
WIth your help the interaction with a directly connected ConBeeII-USB-device worked.
Now I tried to have the ConBeeII on a remote raspberry pi published by ser2net and from a zigbee2mqtt docker to connect it via serial: adapter: deconz port: 'tcp://ip:port'.
This failed. Is this in general not possible with the current status of ConBeeII integration?
Are there any chances to integrate it? Would be great!
from zigbee-herdsman.
Hi all, my conbee2 can successfully control the device, but after a day look like having some problems and I can’t control the device anymore.
The log:
2020-03-24T15:42:45.299Z zigbee-herdsman:deconz:adapter PERMIT_JOIN FAILED - APS TIMEOUT
(node:236) UnhandledPromiseRejectionWarning: undefined
(node:236) 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(). (rejection id: 894)
2020-03-24T15:42:50.502Z zigbee-herdsman:deconz:driver Timeout for request - CMD: 0x7 seqNr: 32
2020-03-24T15:42:50.671Z zigbee-herdsman:deconz:driver send read device state from queue. seqNr: 33
2020-03-24T15:43:00.718Z zigbee-herdsman:deconz:driver Timeout for request - CMD: 0x7 seqNr: 33
2020-03-24T15:43:00.884Z zigbee-herdsman:deconz:driver send read device state from queue. seqNr: 34
2020-03-24T15:43:10.936Z zigbee-herdsman:deconz:driver Timeout for request - CMD: 0x7 seqNr: 34
2020-03-24T15:43:11.092Z zigbee-herdsman:deconz:driver send read device state from queue. seqNr: 35
2020-03-24T15:43:21.162Z zigbee-herdsman:deconz:driver Timeout for request - CMD: 0x7 seqNr: 35
2020-03-24T15:43:21.304Z zigbee-herdsman:deconz:driver send read device state from queue. seqNr: 36
from zigbee-herdsman.
Same for me. Crashes after a few hours of running. I'm using the latest Hass with zigbee2mqtt addon and Conbee II.
zigbee2mqtt:info 2020-03-24 20:47:44: MQTT publish: topic 'zigbee2mqtt/0x00158d00024ee1c8', payload '{"battery":100,"voltage":3015,"illuminance":8,"linkquality":50,"occupancy":false,"illuminance_lux":8}'
(node:234) UnhandledPromiseRejectionWarning: undefined
(node:234) 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(). (rejection id: 26)
from zigbee-herdsman.
I'm use conbee 1.
Not work for me with this options:
serial:
adapter: deconz
port: /dev/serial/by-id/usb-FTDI_FT230X_Basic_UART_DM0103RY-if00-port0
Log file:
zigbee2mqtt:error 2020-03-24 23:22:35: Error while starting zigbee-herdsman
zigbee2mqtt:error 2020-03-24 23:22:35: Failed to start zigbee
zigbee2mqtt:error 2020-03-24 23:22:35: Exiting...
zigbee2mqtt:error 2020-03-24 23:22:35: Error: Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)
at ZStackAdapter.<anonymous> (/app/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js:71:23)
at Generator.throw (<anonymous>)
at rejected (/app/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js:6:65)
from zigbee-herdsman.
I'm use conbee 1.
Not work for me with this options:serial: adapter: deconz port: /dev/serial/by-id/usb-FTDI_FT230X_Basic_UART_DM0103RY-if00-port0
Log file:
zigbee2mqtt:error 2020-03-24 23:22:35: Error while starting zigbee-herdsman zigbee2mqtt:error 2020-03-24 23:22:35: Failed to start zigbee zigbee2mqtt:error 2020-03-24 23:22:35: Exiting... zigbee2mqtt:error 2020-03-24 23:22:35: Error: Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms) at ZStackAdapter.<anonymous> (/app/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js:71:23) at Generator.throw (<anonymous>) at rejected (/app/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js:6:65)
The addon from danielwelch isn't ready for the serial addition. The config.json must be modified to accept the serial addition. For now can try my fork of zigbee2mqtt-edge; https://github.com/arjankanis/hassio-zigbee2mqtt
from zigbee-herdsman.
I'm use conbee 1.
Not work for me with this options:serial: adapter: deconz port: /dev/serial/by-id/usb-FTDI_FT230X_Basic_UART_DM0103RY-if00-port0
Log file:
zigbee2mqtt:error 2020-03-24 23:22:35: Error while starting zigbee-herdsman zigbee2mqtt:error 2020-03-24 23:22:35: Failed to start zigbee zigbee2mqtt:error 2020-03-24 23:22:35: Exiting... zigbee2mqtt:error 2020-03-24 23:22:35: Error: Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms) at ZStackAdapter.<anonymous> (/app/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js:71:23) at Generator.throw (<anonymous>) at rejected (/app/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js:6:65)
The addon from danielwelch isn't ready for the serial addition. The config.json must be modified to accept the serial addition. For now can try my fork of zigbee2mqtt-edge; https://github.com/arjankanis/hassio-zigbee2mqtt
Your addon was started, but not configured devices. For example Konke temperature sensor:
zigbee2mqtt:info 2020-03-25 02:40:38: Configuring '0x086bd7fffee976be'
zigbee2mqtt:error 2020-03-25 02:41:40: Failed to configure '0x086bd7fffee976be', attempt 1 (Error: Bind 0x086bd7fffee976be/1 msTemperatureMeasurement from '0x00212effff03b4b2/1' failed (undefined)
at Endpoint.<anonymous> (/app/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:235:23)
at Generator.throw (<anonymous>)
at rejected (/app/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:6:65))
from zigbee-herdsman.
For me pairing worked.
Sometimes i have seen this error
(node:234) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'stack' of undefined
at Controller.callExtensionMethod (/app/lib/controller.js:349:103)
(node:234) 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(). (rejection id: 2)
(node:234) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
(node:234) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'stack' of undefined
at Controller.callExtensionMethod (/app/lib/controller.js:349:103)
(node:234) 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(). (rejection id: 4)
And light dimming is not working at all. On and Off is working (On -> light goes 100% on) but dimming has no effekt. E.g when the Light is off and i set it to 5% i see mqtt says light on and 5% but it's not turning on. When i set the light to 0% it's going off.
(Innr light bulbs and some dimmer i don't know the name. When i use deconz without mqtt the dimming works)
from zigbee-herdsman.
ConBee II loses connection after some time is a known problem. I investigate it right now. Until now you have to restart zigbee2mqtt to make ConBeeII work again. Perhaps there is a Firmware update in the near future that will improve stability.
Then there is also this tweak that @manup posted some days ago that should also improve stability:
Another thing to improve USB startup was found today by disabling Linux MTP probes and Network Manager messing with serial interface. This might be useful for the CC2531 too.
Source: dresden-elektronik/deconz-rest-plugin#2419 (comment)
MTP probes and Network Manager access for ConBee II can be disabled by following udev rules:
cat /etc/udev/rules.d/69-conbee.rules
# ConBee II disbale modem manager and mtp probing ATTRS{idVendor}=="1cf1", ATTRS{idProduct}=="0030", ENV{ID_MM_DEVICE_IGNORE}="1" ATTRS{idVendor}=="1cf1", ATTRS{idProduct}=="0030", ENV{MTP_NO_PROBE}="1"
After creating this file the udev rules needs to be reloaded:
sudo udevadm control --reload-rules
The difference should be visible in journald when plugging the USB dongle:
sudo journald -xb -f
from zigbee-herdsman.
For me pairing worked.
Sometimes i have seen this error
(node:234) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'stack' of undefined at Controller.callExtensionMethod (/app/lib/controller.js:349:103) (node:234) 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(). (rejection id: 2) (node:234) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code. (node:234) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'stack' of undefined at Controller.callExtensionMethod (/app/lib/controller.js:349:103) (node:234) 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(). (rejection id: 4)
And light dimming is not working at all. On and Off is working (On -> light goes 100% on) but dimming has no effekt. E.g when the Light is off and i set it to 5% i see mqtt says light on and 5% but it's not turning on. When i set the light to 0% it's going off.
(Innr light bulbs and some dimmer i don't know the name. When i use deconz without mqtt the dimming works)
I will test this next. What Client/GUI are you using to control the lights ?
from zigbee-herdsman.
I will test this next. What Client/GUI are you using to control the lights ?
I am using HomeAssistant with the fork of the addon mentioned above (https://github.com/arjankanis/hassio-zigbee2mqtt)
In the MQtt logs the brightness looks good so i assume this is not a gui problem (or i hope)
from zigbee-herdsman.
@ChrisHae I see that the waitFor method has not been implemented yet (https://github.com/Koenkk/zigbee-herdsman/blob/master/src/adapter/deconz/adapter/deconzAdapter.ts#L480). This is required for e.g. OTA updates. Could this be implemented? (original issue: Koenkk/zigbee2mqtt#3210)
from zigbee-herdsman.
HI all, may i know the channel of conbee ii is following the configuration.yaml or it is a constant
i am trying to sniff the packet but cannot sniff any packet on certain channel.
from zigbee-herdsman.
I uploaded a fix to for dimming and change the color of lights.
@Koenkk ok I will implement the waitFor function next.
from zigbee-herdsman.
@kelvin5290 yes it seems the configuration from configuration.yaml will not be written to the ConBee2 device. I will have a look and add this feature in the next few days.
If you are interested what the current channel is look for a zigbee2mqtt debug message right after you start zigbee2mqtt. It looks like this:
zigbee2mqtt:debug 2020-03-31 17:02:04: Zigbee network parameters: "panID":49515,"extendedPanID":"0x00212effff03d49a","channel":15}
from zigbee-herdsman.
@ChrisHae Thank you for reply.
also, i face another issue. When i going to pairing a in wall switch. The configuration of reporting packet look like contain some problem. The below image shown the information. Thank you.
from zigbee-herdsman.
After half an hour or so this stopped to be working and my whole log was lines like:
(node:226) UnhandledPromiseRejectionWarning: undefined
(node:226) 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(). (rejection id: 244)
from zigbee-herdsman.
I'm also testing it with a ConBee II stick. I was able to connect an Aqara Switch yesterday, but today it stopped working.
I had applied udev rules in advance.
PS: I have the latest ConBee firmware installed.
from zigbee-herdsman.
I uploaded some commits. Now it is possible to set the network parameters as written in the configuration.yaml (panId, extPanId, channel and network key) If one entry is missing the default value as written in the configuration documentation is used.
We are currently working and testing to improve stability of ConBeeII sticks running in zigbee2mqtt.
Next thing to be implemented is the waitFor function used by OTA updates.
from zigbee-herdsman.
@val-arg
Could you post the bootloader and firmware version of your ConBeeII?
You can retrieve it with this command: sudo GCFFlasher_internal -d /dev/ttyACM0 -r
from zigbee-herdsman.
@ChrisHae it shows this:
root@f47418933c0d:/# GCFFlasher_internal -d /dev/ttyACM1 -r
GCFFlasher V3_05 (c) dresden elektronik ingenieurtechnik gmbh
Reboot device /dev/ttyACM1 (ConBee II)
deCONZ firmware version 264A0700
Looks like the latest stable version.
from zigbee-herdsman.
If we can now setup panId, network key and channel, would it be possible to migrate from deconz without repairing? Simply setting the same network parameters?
I am sorry if it has been discussed several times already :/.
from zigbee-herdsman.
This should work because the needed network parameters would be the same. But i think zigbee2mqtt would not show the devices beacause they are not in its database. Perhaps open the network and powercylce the devices should do the trick but I'm not sure.
from zigbee-herdsman.
Hi @ChrisHae So if I currently use the TI Zigbee device and want to move to using the Conbee as my hardware dongle instead, it’s now fully supported to do so? Again same as @MarhyCZ sorry if this has been asked again.
from zigbee-herdsman.
@mar005 If there's a way to add your devices to the database of currently used devices then it's "fully supported".
It has to be tested anyway.
from zigbee-herdsman.
@ChrisHae Thank you for reply.
also, i face another issue. When i going to pairing a in wall switch. The configuration of reporting packet look like contain some problem. The below image shown the information. Thank you.
hi everyone, do anyone have ideas? Thank you
from zigbee-herdsman.
Hey,
Whenever zigbee2mqtt
tries to configure a device, it always fails with: Error: Status 'INVALID_DATA_TYPE'
zigbee2mqtt:info 2020-04-30 23:56:30: Configuring 'SmartThings GP-WOU019BBDWG'
2020-04-30T22:56:30.357Z zigbee-herdsman:controller:endpoint Bind 0x14b457fffecbfceb/1 genOnOff from '0x00212effff05996f/1'
2020-04-30T22:56:30.389Z zigbee-herdsman:deconz:driver DATA_REQUEST - sending data request - destAddr: 0x7f33 EP:9 SeqNr. 23 request id: 5
2020-04-30T22:56:30.401Z zigbee-herdsman:deconz:frameParser DATA_REQUEST Response - status: 0 request id: 5 new device state: 100010
2020-04-30T22:56:30.409Z zigbee-herdsman:deconz:frameParser DEVICE_STATE changed: 10100110
2020-04-30T22:56:30.439Z zigbee-herdsman:deconz:driver DATA_REQUEST - sending data request - destAddr: 0x4273 EP:0 SeqNr. 24 request id: 6
2020-04-30T22:56:30.450Z zigbee-herdsman:deconz:frameParser DATA_REQUEST Response - status: 0 request id: 6 new device state: 100110
2020-04-30T22:56:30.464Z zigbee-herdsman:deconz:frameParser DEVICE_STATE changed: 10100110
2020-04-30T22:56:30.491Z zigbee-herdsman:deconz:driver DATA_CONFIRM - sending data state request - SeqNr. 25
2020-04-30T22:56:30.493Z zigbee-herdsman:deconz:frameParser DATA_CONFIRM Response - destAddr: 0x7f33 request id: 5 confirm status: 0 new device state: 00100110
2020-04-30T22:56:30.494Z zigbee-herdsman:deconz:adapter sendZclFrameToEndpoint - message send
2020-04-30T22:56:30.523Z zigbee-herdsman:deconz:frameParser DEVICE_STATE changed: 10101110
2020-04-30T22:56:30.541Z zigbee-herdsman:deconz:driver DATA_CONFIRM - sending data state request - SeqNr. 26
2020-04-30T22:56:30.592Z zigbee-herdsman:deconz:driver DATA_CONFIRM - sending data state request - SeqNr. 27
2020-04-30T22:56:30.602Z zigbee-herdsman:deconz:frameParser DATA_CONFIRM Response - destAddr: 0x4273 request id: 6 confirm status: 0 new device state: 00101010
2020-04-30T22:56:30.643Z zigbee-herdsman:deconz:driver DATA_CONFIRM - sending data state request - SeqNr. 28
2020-04-30T22:56:30.651Z zigbee-herdsman:deconz:frameParser DATA_CONFIRM Response - rejected - seqNr.: 28 status: 5
2020-04-30T22:56:30.693Z zigbee-herdsman:deconz:driver DATA_CONFIRM - sending data state request - SeqNr. 29
2020-04-30T22:56:30.700Z zigbee-herdsman:deconz:frameParser DATA_CONFIRM Response - rejected - seqNr.: 29 status: 5
2020-04-30T22:56:30.743Z zigbee-herdsman:deconz:driver DATA_INDICATION - sending read data request - SeqNr. 30
2020-04-30T22:56:30.749Z zigbee-herdsman:deconz:frameParser DATA_INDICATION Response - seqNr. 30 srcAddr: 0x4273 destAddr: 0x0 profile id: 0x0 cluster id: 0x8021 new state: 00100010
2020-04-30T22:56:30.750Z zigbee-herdsman:deconz:frameParser payload: 6,0
2020-04-30T22:56:30.750Z zigbee-herdsman:deconz:adapter BIND RESPONSE - addr: 0x4273 status: 0
2020-04-30T22:56:30.751Z zigbee-herdsman:controller:endpoint Bind 0x14b457fffecbfceb/1 haElectricalMeasurement from '0x00212effff05996f/1'
2020-04-30T22:56:30.793Z zigbee-herdsman:deconz:driver DATA_REQUEST - sending data request - destAddr: 0x4273 EP:0 SeqNr. 31 request id: 7
2020-04-30T22:56:30.800Z zigbee-herdsman:deconz:frameParser DATA_REQUEST Response - status: 0 request id: 7 new device state: 100010
2020-04-30T22:56:30.810Z zigbee-herdsman:deconz:frameParser DEVICE_STATE changed: 10100110
2020-04-30T22:56:30.843Z zigbee-herdsman:deconz:driver DATA_CONFIRM - sending data state request - SeqNr. 32
2020-04-30T22:56:30.852Z zigbee-herdsman:deconz:frameParser DATA_CONFIRM Response - destAddr: 0x4273 request id: 7 confirm status: 0 new device state: 00100010
2020-04-30T22:56:30.862Z zigbee-herdsman:deconz:frameParser DEVICE_STATE changed: 10101010
2020-04-30T22:56:30.893Z zigbee-herdsman:deconz:driver DATA_INDICATION - sending read data request - SeqNr. 33
2020-04-30T22:56:30.903Z zigbee-herdsman:deconz:frameParser DATA_INDICATION Response - seqNr. 33 srcAddr: 0x4273 destAddr: 0x0 profile id: 0x0 cluster id: 0x8021 new state: 00100010
2020-04-30T22:56:30.903Z zigbee-herdsman:deconz:frameParser payload: 7,0
2020-04-30T22:56:30.904Z zigbee-herdsman:deconz:adapter BIND RESPONSE - addr: 0x4273 status: 0
2020-04-30T22:56:30.905Z zigbee-herdsman:controller:endpoint ConfigureReporting 0x14b457fffecbfceb/1 genOnOff([{"attribute":"onOff","minimumReportInterval":0,"maximumReportInterval":3600,"reportableChange":0}], {"timeout":10000,"manufacturerCode":null,"disableDefaultResponse":true})
2020-04-30T22:56:30.943Z zigbee-herdsman:deconz:driver DATA_REQUEST - sending data request - destAddr: 0x4273 EP:1 SeqNr. 34 request id: 8
2020-04-30T22:56:30.954Z zigbee-herdsman:deconz:frameParser DATA_REQUEST Response - status: 0 request id: 8 new device state: 100010
2020-04-30T22:56:30.965Z zigbee-herdsman:deconz:frameParser DEVICE_STATE changed: 10100110
2020-04-30T22:56:30.993Z zigbee-herdsman:deconz:driver DATA_CONFIRM - sending data state request - SeqNr. 35
2020-04-30T22:56:30.995Z zigbee-herdsman:deconz:frameParser DATA_CONFIRM Response - destAddr: 0x4273 request id: 8 confirm status: 0 new device state: 00100010
2020-04-30T22:56:30.996Z zigbee-herdsman:deconz:adapter sendZclFrameToEndpoint - message send
2020-04-30T22:56:31.029Z zigbee-herdsman:deconz:frameParser DEVICE_STATE changed: 10101010
2020-04-30T22:56:31.043Z zigbee-herdsman:deconz:driver DATA_INDICATION - sending read data request - SeqNr. 36
2020-04-30T22:56:31.047Z zigbee-herdsman:deconz:frameParser DATA_INDICATION Response - seqNr. 36 srcAddr: 0x4273 destAddr: 0x0 profile id: 0x104 cluster id: 0x6 new state: 00100010
2020-04-30T22:56:31.047Z zigbee-herdsman:deconz:frameParser payload: 8,4,7,141,0,0,0,133,16,14,0
2020-04-30T22:56:31.048Z zigbee-herdsman:controller:log Received 'zcl' data '{"frame":{"Header":{"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":false},"transactionSequenceNumber":4,"manufacturerCode":null,"commandIdentifier":7},"Payload":[{"status":141,"direction":0,"attrId":0},{"status":133,"direction":16,"attrId":14}]},"address":17011,"endpoint":1,"linkquality":10,"groupID":null}'
2020-04-30T22:56:31.048Z zigbee-herdsman:controller:endpoint DefaultResponse 0x14b457fffecbfceb/1 6(7, {"timeout":10000,"manufacturerCode":null,"disableDefaultResponse":true})
2020-04-30T22:56:31.049Z zigbee-herdsman:deconz:adapter cmdId: 7
2020-04-30T22:56:31.049Z zigbee-herdsman:deconz:adapter statusCode: 0
2020-04-30T22:56:31.049Z zigbee-herdsman:deconz:adapter response received
2020-04-30T22:56:31.049Z zigbee-herdsman:controller:endpoint ConfigureReporting 0x14b457fffecbfceb/1 genOnOff([{"attribute":"onOff","minimumReportInterval":0,"maximumReportInterval":3600,"reportableChange":0}], {"timeout":10000,"manufacturerCode":null,"disableDefaultResponse":true}) failed (Error: Status 'INVALID_DATA_TYPE')
zigbee2mqtt:error 2020-04-30 23:56:31: Failed to configure 'SmartThings GP-WOU019BBDWG', attempt 1 (Error: ConfigureReporting 0x14b457fffecbfceb/1 genOnOff([{"attribute":"onOff","minimumReportInterval":0,"maximumReportInterval":3600,"reportableChange":0}], {"timeout":10000,"manufacturerCode":null,"disableDefaultResponse":true}) failed (Error: Status 'INVALID_DATA_TYPE')
at Endpoint.<anonymous> (/app/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:326:23)
at Generator.next (<anonymous>)
at fulfilled (/app/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:5:58))
I get the same error for 2 different supported devices (Salus SP600, SmartThings GP-WOU019BBDWG)
I'm using the Conbee 2 on the latest firmware (0x264a0700
).
Not sure how to debug the problem further, looks like an issue coming from the adapter?
Edit
After a little debugging it seems its failing here. result.frame.Payload
=
[
{ status: 141, direction: 0, attrId: 0 },
{ status: 133, direction: 16, attrId: 14 }
]
from zigbee-herdsman.
I implemented the waitFor method and OTA update is now running. But when testing I have an issue that the update the update runs a while then when it requests image data with an offset of 800 (~ update progress of 0.38%) it always repeats the same request and always gets the same data. Then the device cancels the update.
Can someone test it and confirm the issue? I have tested it with an ikea tradfri 1000lm light.
from zigbee-herdsman.
@kelvin5290
@mike182uk
thanks for the help. I will have a look.
from zigbee-herdsman.
I have a lot (meaning every 3 seconds) of this:
Mai 07 18:57:13 nodered npm[593]: (node:649) UnhandledPromiseRejectionWarning: Error: unknown parameter id
Mai 07 18:57:13 nodered npm[593]: at parseReadParameterResponse (/opt/zigbee2mqtt/node_modules/zigbee-herdsman/dist/adapter/deconz/driver/frameParser.js:94:19)
Mai 07 18:57:13 nodered npm[593]: at parseFrame (/opt/zigbee2mqtt/node_modules/zigbee-herdsman/dist/adapter/deconz/driver/frameParser.js:368:32)
Mai 07 18:57:13 nodered npm[593]: at Object. (/opt/zigbee2mqtt/node_modules/zigbee-herdsman/dist/adapter/deconz/driver/frameParser.js:323:63)
Mai 07 18:57:13 nodered npm[593]: at Generator.next ()
Mai 07 18:57:13 nodered npm[593]: at /opt/zigbee2mqtt/node_modules/zigbee-herdsman/dist/adapter/deconz/driver/frameParser.js:8:71
Mai 07 18:57:13 nodered npm[593]: at new Promise ()
Mai 07 18:57:13 nodered npm[593]: at __awaiter (/opt/zigbee2mqtt/node_modules/zigbee-herdsman/dist/adapter/deconz/driver/frameParser.js:4:12)
Mai 07 18:57:13 nodered npm[593]: at Object.processFrame [as default] (/opt/zigbee2mqtt/node_modules/zigbee-herdsman/dist/adapter/deconz/driver/frameParser.js:322:12)
Mai 07 18:57:13 nodered npm[593]: at Driver. (/opt/zigbee2mqtt/node_modules/zigbee-herdsman/dist/adapter/deconz/adapter/deconzAdapter.js:41:69)
Mai 07 18:57:13 nodered npm[593]: at Driver.emit (events.js:310:20)
Mai 07 18:57:13 nodered npm[593]: (node:649) 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: 54)
from zigbee-herdsman.
Interview for ikea symfonisk (any ikea device, really) fails with unsupported attribute and the device doesn't work: https://pastebin.com/vGw1d41K
After a few hours the device inexplicably started to work, while still throwing an error:
https://pastebin.com/61NL03yv
I've tried the new fixes (I think) by reinstalling z2m (the HASSIO addon) but it doesn't seem to have fixed the issue.
EDIT:
I have now installed the zigbee2mqtt-edge (aka dev) version of the addon and modified it correctly to be able to use deconz (as before) and now the devices do seem to pair and configure properly! I suspect when I tried reinstalling before, I still had an older package cached.
It does, however, still take a long time for the devices to start reporting after they've been configured, I have been waiting for over 10 minutes now and no action on the device is being reported to z2m. Additionally, it threw another error, here is the log with debug output enabled: https://pastebin.com/Wg62iVzk
For all I know, the device might start working sometime in the next few hours, like it did last time, but this does not seem ideal
from zigbee-herdsman.
@ChrisHae Would your approach also be workable for the RaspBee then? Would be an interesting combination to try out once things got ironed out. Maybe there's also a rough estimate for an ETA? I see work is catching some pace :)
Maybe one additional offer, sorry for highjacking this a bit here, but maybe you'd consider joining the deconz discord channel to stay in touch regarding the latest developments floating around. There'll be certainly also some posibilities of privacy should you consider it. Thanks!
https://discord.gg/ynGQAr
from zigbee-herdsman.
Hi, I just had a similar problem like @hutchinsane with a Tradfri signal repeater and the UNSUPPORTED_ATTRIBUTE error message
`
2020-05-09 04:38:35.847 - info: zigbee.0 (12337) Configuring 0x000d6ffffea61fe1 TRADFRI signal repeater
2020-05-09 04:38:36.447 - error: zigbee.0 (12337) Failed to configure 0x000d6ffffea61fe1 TRADFRI signal repeater, attempt 5 (Error: ConfigureReporting 0x000d6ffffea61fe1/1 genBasic([{"attribute":"modelId","minimumReportInterval":3600,"maximumReportInterval":14400}], {"timeout":10000,"manufacturerCode":null,"disableDefaultResponse":true}) failed (Error: Status 'UNSUPPORTED_ATTRIBUTE')
at Endpoint. (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:326:23)
at Generator.next ()
at fulfilled (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:5:58))
`
I am running on Conbee II and the newest Zigbee Adapter Github version. I killed my complete network and start a new installation (with a new PanID etc). If I try topair the Tradfri signal repeater with the ConBee II I got this configuration message. This message comes again from time to time in the logfile.
from zigbee-herdsman.
Just dropping by as a complete "programming noob" to ask if the ConBee II stick is in any way a usable device with Zigbee2MQTT already? :) Thanks for answering!
from zigbee-herdsman.
@Koenkk just clarifying for myself. I do have some more error message since I use the Conbee II. (Before I used the CC2531 and everything works).
(7456) TypeError: Cannot read property 'stack' of undefined at process.exceptionHandler (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:8238:17) at process.emit (events.js:31 zigbee.0 | 2020-05-10 07:50:01.443 | error | (7456) uncaught exception: Cannot read property 'stack' of undefined zigbee.0 | 2020-05-10 07:50:01.441 | error | (7456) uncaught exception: undefined
or:
2020-05-09 15:28:39.346 - error: zigbee.0 (29847) Failed to do action 0x00158d00042176ed undefined, attempt 1 (TypeError: Cannot read property 'stack' of undefined at Object.action (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:360:69))
or:
2020-05-10 07:51:36.173 - error: zigbee.0 (15179) Failed to configure 0x000d6ffffea61fe1 TRADFRI signal repeater, attempt 1 (Error: Bind 0x000d6ffffea61fe1/1 genBasic from '0x00212effff04ec17/1' failed (undefined) at Endpoint. (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:244:23) at Generator.throw () at rejected (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:6:65)) 2020-05-10 07:51:36.175 - debug: zigbee.0 (15179) shouldConfigure? 0xccccccfffeb3f29f TRADFRI Signal Repeater 2020-05-10 07:51:36.176 - debug: zigbee.0 (15179) Yes! 2020-05-10 07:51:36.177 - info: zigbee.0 (15179) Configuring 0xccccccfffeb3f29f TRADFRI Signal Repeater 2020-05-10 07:52:37.178 - error: zigbee.0 (15179) Failed to configure 0xccccccfffeb3f29f TRADFRI Signal Repeater, attempt 1 (Error: Bind 0xccccccfffeb3f29f/1 genBasic from '0x00212effff04ec17/1' failed (undefined) at Endpoint. (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:244:23) at Generator.throw () at rejected (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:6:65) at runMicrotasks () at runNextTicks (internal/process/task_queues.js:62:5) at processTimers (internal/timers.js:489:9))
These are all Zigbee2mqtt issues?
Thanks for your help.
from zigbee-herdsman.
Those arent I think
from zigbee-herdsman.
@manup just pointed to a new firmware: dresden-elektronik/deconz-rest-plugin#1261 (comment)
could be worth a try
from zigbee-herdsman.
Just dropping by as a complete "programming noob" to ask if the ConBee II stick is in any way a usable device with Zigbee2MQTT already? :) Thanks for answering!
It's still in development and has some issues.
from zigbee-herdsman.
I could pair a tradfri signal repeater with the current version successfully:
`Successfully interviewed '0xec1bbdfffe47c108', device has successfully been paired
zigbee2mqtt:info 2019-02-14 12:57:30: Device '0xec1bbdfffe47c108' is supported, identified as: IKEA TRADFRI signal repeater (E1746)
zigbee2mqtt:info 2019-02-14 12:57:30: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"pairing","message":"interview_successful","meta":{"friendly_name":"0xec1bbdfffe47c108","model":"E1746","vendor":"IKEA","description":"TRADFRI signal repeater","supported":true}}'
zigbee2mqtt:info 2019-02-14 12:57:30: Configuring '0xec1bbdfffe47c108'
ConfigureReporting 0xec1bbdfffe47c108/1 genBasic([{"attribute":"modelId","minimumReportInterval":3600,"maximumReportInterval":14400}], {"timeout":10000,"manufacturerCode":null,"disableDefaultResponse":true})
zigbee2mqtt:info 2019-02-14 12:57:31: Successfully configured '0xec1bbdfffe47c108'
Successfully interviewed '0xec1bbdfffe47c108', device has successfully been paired
zigbee2mqtt:info 2019-02-14 12:57:30: Device '0xec1bbdfffe47c108' is supported, identified as: IKEA TRADFRI signal repeater (E1746)
zigbee2mqtt:info 2019-02-14 12:57:30: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"pairing","message":"interview_successful","meta":{"friendly_name":"0xec1bbdfffe47c108","model":"E1746","vendor":"IKEA","description":"TRADFRI signal repeater","supported":true}}'
zigbee2mqtt:info 2019-02-14 12:57:30: Configuring '0xec1bbdfffe47c108'
ConfigureReporting 0xec1bbdfffe47c108/1 genBasic([{"attribute":"modelId","minimumReportInterval":3600,"maximumReportInterval":14400}], {"timeout":10000,"manufacturerCode":null,"disableDefaultResponse":true})
zigbee2mqtt:info 2019-02-14 12:57:31: Successfully configured '0xec1bbdfffe47c108'`
from zigbee-herdsman.
Thanks @ChrisHae for the information.
Thanks @osos for the link to the new firmware.
I tested the new firmware and the conbee II runs better some error are gone. The only think that is strange is that the signal quality is very low after the update. It starts by 1 and after 15 hours it is by 22. But it will bend and wait :)
Back to @ChrisHae post:
Currently, the only error is the configuration as for a tradfri signal repeater, which I mentioned about:
`
2020-05-11 07:07:46.262 - info: zigbee.0 (8148) Configuring 0x000d6ffffe2e4a54 TRADFRI signal repeater
2020-05-11 07:07:46.263 - debug: zigbee.0 (8148) Publish {"linkquality":17}
2020-05-11 07:07:46.264 - debug: zigbee.0 (8148) Successfully pinged 0x000d6ffffe2e4a54 TRADFRI signal repeater
2020-05-11 07:07:47.712 - error: zigbee.0 (8148) Failed to configure 0x000d6ffffe2e4a54 TRADFRI signal repeater, attempt 4 (Error: ConfigureReporting 0x000d6ffffe2e4a54/1 genBasic([{"attribute":"modelId","minimumReportInterval":3600,"maximumReportInterval":14400}], {"timeout":10000,"manufacturerCode":null,"disableDefaultResponse":true}) failed (Error: Status 'UNSUPPORTED_ATTRIBUTE')
at Endpoint. (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:326:23)
at Generator.next ()
at fulfilled (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:5:58))
`
I can pair the tradfri signal repeater and it shows up in the dashboard. It seems to work as repeater but from time to time the system ask for configuration and than the errors appears... and sometimes the zigbee adapter restarts.
from zigbee-herdsman.
I have now installed the zigbee2mqtt-edge (aka dev) version of the addon and modified it correctly to be able to use deconz (as before) and now the devices do seem to pair and configure properly! I suspect when I tried reinstalling before, I still had an older package cached.
It does, however, still take a long time for the devices to start reporting after they've been configured, I have been waiting for over 10 minutes now and no action on the device is being reported to z2m. Additionally, it threw another error, here is the log with debug output enabled: https://pastebin.com/Wg62iVzk
I see there is a parameter id that I didn't implemented. I can add it then the error should be gone.
from zigbee-herdsman.
I have reworked my code a little bit. Now the standard implementation for zclFrame.toBuffer() of zigbee2mqtt is used. This should improve Attribute reporting, configuring, etc. and some errors could be gone.
Also receiving an unknown command does not trigger an exception so the error from @hutchinsane should also be gone.
I have tested with IKEA synfonic and signal repeater and both paired well.
P.S. as @osos mentioned, please try the new ConBeeII FW dresden-elektronik/deconz-rest-plugin#1261 (comment) and see if the stability is better.
P.P.S. All this works also for RaspBeeII
from zigbee-herdsman.
@Koenkk
I have nearly the same issue as @hutchinsane when using the IKEA synfonic switch.
Pairing goes well and it reports attributes as I use the switch. but after a while there are nor more messages from zigbee2mqtt that report the attributes (Received Zigbee message from...). Although I see that the ConBeeII still receives messages from it and my underlying implementation still receives data_indications. Do you have an idea why this is so?
> zigbee-herdsman:deconz:driver DATA_INDICATION - sending read data request - SeqNr. 138 +49ms
> zigbee-herdsman:deconz:driver <Buffer c0 17 8a 00 08 00 01 00 01 55 ff c0> +1ms
> zigbee-herdsman:deconz:frameParser DATA_INDICATION Response - seqNr. 138 srcAddr: 0x38aa destAddr: 0x0 profile id: 0x104 cluster id: 0x8 new state: 00100010 +50ms
> zigbee-herdsman:deconz:frameParser payload: 17,15,3,0,0 +0ms
> zigbee2mqtt:debug 2019-02-14 15:57:05: Received Zigbee message from '0xccccccfffebca4cd', type 'commandStop', cluster 'genLevelCtrl', data '{}' from endpoint 1 with groupID null
> zigbee2mqtt:info 2019-02-14 15:57:05: MQTT publish: topic 'zigbee2mqtt/0xccccccfffebca4cd', payload '{"rate":195,"linkquality":4,"last_seen":1550156225642,"brightness":255,"battery":30,"action":"rotate_stop"}'
> zigbee-herdsman:deconz:driver DATA_INDICATION - sending read data request - SeqNr. 139 +49ms
> zigbee-herdsman:deconz:driver <Buffer c0 17 8b 00 08 00 01 00 01 54 ff c0> +0ms
> zigbee-herdsman:deconz:frameParser DATA_INDICATION Response - rejected - seqNr.: 139 status: 5 +50ms
> zigbee-herdsman:deconz:frameParser DEVICE_STATE changed: 10101010 +368ms
> zigbee-herdsman:deconz:frameParser DEVICE_STATE changed: 10101010 +8ms
> zigbee-herdsman:deconz:driver DATA_INDICATION - sending read data request - SeqNr. 140 +400ms
> zigbee-herdsman:deconz:driver <Buffer c0 17 8c 00 08 00 01 00 01 53 ff c0> +1ms
> zigbee-herdsman:deconz:frameParser DATA_INDICATION Response - seqNr. 140 srcAddr: 0x38aa destAddr: 0x0 profile id: 0x104 cluster id: 0x8 new state: 00101010 +25ms
> zigbee-herdsman:deconz:frameParser payload: 17,16,1,0,195,0,0 +1ms
> zigbee2mqtt:debug 2019-02-14 15:57:06: Received Zigbee message from '0xccccccfffebca4cd', type 'commandMove', cluster 'genLevelCtrl', data '{"movemode":0,"rate":195}' from endpoint 1 with groupID null
> zigbee2mqtt:info 2019-02-14 15:57:06: MQTT publish: topic 'zigbee2mqtt/0xccccccfffebca4cd', payload '{"rate":195,"linkquality":4,"last_seen":1550156226094,"brightness":255,"battery":30,"action":"rotate_right"}'
> zigbee-herdsman:deconz:driver DATA_INDICATION - sending read data request - SeqNr. 141 +49ms
> zigbee-herdsman:deconz:driver <Buffer c0 17 8d 00 08 00 01 00 01 52 ff c0> +1ms
> zigbee-herdsman:deconz:frameParser DATA_INDICATION Response - seqNr. 141 srcAddr: 0x38aa destAddr: 0x0 profile id: 0x104 cluster id: 0x8 new state: 00100010 +48ms
> zigbee-herdsman:deconz:frameParser payload: 17,16,1,0,195,0,0 +0ms
> zigbee2mqtt:debug 2019-02-14 15:57:06: Received Zigbee message from '0xccccccfffebca4cd', type 'commandMove', cluster 'genLevelCtrl', data '{"movemode":0,"rate":195}' from endpoint 1 with groupID null
> zigbee-herdsman:deconz:driver DATA_INDICATION - sending read data request - SeqNr. 142 +49ms
> zigbee-herdsman:deconz:driver <Buffer c0 17 8e 00 08 00 01 00 01 51 ff c0> +1ms
> zigbee-herdsman:deconz:frameParser DATA_INDICATION Response - rejected - seqNr.: 142 status: 5 +51ms
> zigbee-herdsman:deconz:frameParser DEVICE_STATE changed: 10101010 +53ms
> zigbee-herdsman:deconz:frameParser DEVICE_STATE changed: 10101010 +12ms
> zigbee-herdsman:deconz:driver DATA_INDICATION - sending read data request - SeqNr. 143 +99ms
> zigbee-herdsman:deconz:driver <Buffer c0 17 8f 00 08 00 01 00 01 50 ff c0> +1ms
> zigbee-herdsman:deconz:frameParser DATA_INDICATION Response - seqNr. 143 srcAddr: 0x38aa destAddr: 0x0 profile id: 0x104 cluster id: 0x8 new state: 00101010 +36ms
> zigbee-herdsman:deconz:frameParser payload: 17,17,3,0,0 +0ms
> zigbee-herdsman:deconz:driver DATA_INDICATION - sending read data request - SeqNr. 144 +49ms
> zigbee-herdsman:deconz:driver <Buffer c0 17 90 00 08 00 01 00 01 4f ff c0> +0ms
> zigbee-herdsman:deconz:frameParser DATA_INDICATION Response - seqNr. 144 srcAddr: 0x38aa destAddr: 0x0 profile id: 0x104 cluster id: 0x8 new state: 00100010 +50ms
> zigbee-herdsman:deconz:frameParser payload: 17,17,3,0,0 +0ms
> zigbee-herdsman:deconz:driver DATA_INDICATION - sending read data request - SeqNr. 145 +50ms
> zigbee-herdsman:deconz:driver <Buffer c0 17 91 00 08 00 01 00 01 4e ff c0> +0ms
from zigbee-herdsman.
@ChrisHae My errors with the 'UNSUPPORTED_ATTRIBUTE' are gone. I can pair the TRADFRI Signal Repeater and the configuration is a success. Thank you!
from zigbee-herdsman.
I tried with Conbee version 1 and it didnt work with firmware deCONZ_Rpi_0x26350500.bin.GCF. Is only Conbee II supported? is it possible to change inetadrr for the cordinator so i dont need to repair all the devices?
from zigbee-herdsman.
I implemented the waitFor method and OTA update is now running. But when testing I have an issue that the update the update runs a while then when it requests image data with an offset of 800 (~ update progress of 0.38%) it always repeats the same request and always gets the same data. Then the device cancels the update.
Can someone test it and confirm the issue? I have tested it with an ikea tradfri 1000lm light.
@ChrisHae I can confirm the issue you mentioned. Below are the logs from my setup. Let me know if I can help debugging this further.
z2m | zigbee2mqtt:debug 2020-05-16 00:36:37: Received MQTT message on 'zigbee2mqtt/bridge/ota_update/update' with data '0x000d6ffffe152eb5'
z2m | zigbee2mqtt:info 2020-05-16 00:36:37: Updating '0x000d6ffffe152eb5' to latest firmware
z2m | zigbee2mqtt:info 2020-05-16 00:36:37: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"ota_update","message":"Updating '0x000d6ffffe152eb5' to latest firmware","meta":{"status":"update_in_progress","device":"0x000d6ffffe152eb5"}}'
z2m | zigbee2mqtt:debug 2020-05-16 00:36:37: Received Zigbee message from '0x000d6ffffe152eb5', type 'readResponse', cluster 'genBasic', data '{"dateCode":"20190308","swBuildId":"2.0.022"}' from endpoint 1 with groupID null
z2m | zigbee2mqtt:debug 2020-05-16 00:36:37: Updating to latest '0x000d6ffffe152eb5' (TRADFRI bulb E27 WS opal 1000lm)
z2m | zigbee2mqtt:debug 2020-05-16 00:36:37: Using endpoint '1'
z2m | zigbee2mqtt:debug 2020-05-16 00:36:38: Received Zigbee message from '0x000d6ffffe152eb5', type 'commandQueryNextImageRequest', cluster 'genOta', data '{"fieldControl":1,"manufacturerCode":4476,"imageType":16900,"fileVersion":537011747}' from endpoint 1 with groupID null
z2m | zigbee2mqtt:debug 2020-05-16 00:36:38: Got OTA request '{"fieldControl":1,"manufacturerCode":4476,"imageType":16900,"fileVersion":537011747}'
z2m | zigbee2mqtt:debug 2020-05-16 00:36:41: Received Zigbee message from '0x000d6ffffe152eb5', type 'commandQueryNextImageRequest', cluster 'genOta', data '{"fieldControl":1,"manufacturerCode":4476,"imageType":16900,"fileVersion":537011747}' from endpoint 1 with groupID null
z2m | zigbee2mqtt:debug 2020-05-16 00:36:41: Got new image for '0x000d6ffffe152eb5'
z2m | zigbee2mqtt:debug 2020-05-16 00:36:41: Starting upgrade
z2m | zigbee2mqtt:debug 2020-05-16 00:36:41: Received Zigbee message from '0x000d6ffffe152eb5', type 'commandQueryNextImageRequest', cluster 'genOta', data '{"fieldControl":1,"manufacturerCode":4476,"imageType":16900,"fileVersion":537011747}' from endpoint 1 with groupID null
z2m | zigbee2mqtt:debug 2020-05-16 00:36:49: OTA update at 0%, remaining Infinity seconds
z2m | zigbee2mqtt:info 2020-05-16 00:36:49: Update of '0x000d6ffffe152eb5' at 0.00%
z2m | zigbee2mqtt:info 2020-05-16 00:36:49: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"ota_update","message":"Update of '0x000d6ffffe152eb5' at 0.00%","meta":{"status":"update_progress","device":"0x000d6ffffe152eb5","progress":0}}'
z2m | zigbee2mqtt:debug 2020-05-16 00:37:21: OTA update at 0.38%, remaining 10429.92145 seconds
z2m | zigbee2mqtt:info 2020-05-16 00:37:21: Update of '0x000d6ffffe152eb5' at 0.38%, +- 174 minutes remaining
z2m | zigbee2mqtt:info 2020-05-16 00:37:21: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"ota_update","message":"Update of '0x000d6ffffe152eb5' at 0.38%, +- 174 minutes remaining","meta":{"status":"update_progress","device":"0x000d6ffffe152eb5","progress":0.38}}'
z2m | zigbee2mqtt:debug 2020-05-16 00:37:51: Got upgrade end request for '0x000d6ffffe152eb5': {"status":149,"manufacturerCode":4476,"imageType":16900,"fileVersion":537015843}
z2m | zigbee2mqtt:debug 2020-05-16 00:37:51: Update failed with reason: 'aborted by device'
z2m | zigbee2mqtt:error 2020-05-16 00:37:51: Update of '0x000d6ffffe152eb5' failed (Update failed with reason: 'aborted by device')
z2m | zigbee2mqtt:info 2020-05-16 00:37:51: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"ota_update","message":"Update of '0x000d6ffffe152eb5' failed (Update failed with reason: 'aborted by device')","meta":{"status":"update_failed","device":"0x000d6ffffe152eb5"}}'
from zigbee-herdsman.
@ChrisHae On another note, how are you currently working on this topic? Shall we report bugs/problems in this issue directly for now?
from zigbee-herdsman.
zigbee2mqtt version 1.13.0-dev (commit #9a28f11)
herdsman 0.12.90 (just recently updated)
ConBeeII: 0x26580700
@ChrisHae
Thanks for improving the support for ConBeeII. It seems to be near stability.
I from time to time get the following message:
(node:17) UnhandledPromiseRejectionWarning: TIMEOUT
(node:17) 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: 9)
I don't know if this a herdsman message.
Besides that I still have the issue that approx. after a day zigbee2mqtt stops only these messages stay and repeate:
zigbee2mqtt:debug 2020-05-17 19:53:26: Saving state to file /app/data/state.json
from zigbee-herdsman.
zigbee2mqtt version 1.13.0-dev (commit #9a28f11)
herdsman 0.12.90 (just recently updated)
ConBeeII: 0x26580700
@ChrisHae
Another issue:
I have a Xiaomi WXCJKG13LM - Xiaomi Aqara Opple switch 3 bands. It works for single press.
But I cannot produce double or multiple press or long press.
As I read in another thread by Koenkk, multiple press are detected by the switch and not zigbee2mqtt (appart form long press). So what could be the issue here?
Besides that I get the following error for this switch:
zigbee2mqtt:error 2020-05-17 20:33:43: Failed to configure 'WXCJKG13LM Opple switch 3', attempt 2 (Error: Write 0x04cf8cdf3c794995/1 aqaraOpple({"mode":1}, {"timeout":10000,"manufacturerCode":4447,"disableDefaultResponse":true}) failed (TypeError: Cannot read property 'frame' of null)
at Endpoint. (/app/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:158:23)
at Generator.next ()
at fulfilled (/app/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:5:58)
at runMicrotasks ()
at runNextTicks (internal/process/task_queues.js:62:5)
at processTimers (internal/timers.js:489:9))
from zigbee-herdsman.
zigbee2mqtt version 1.13.0-dev (commit #134f671)
herdsman 0.12.90 (just recently updated)
ConBeeII: 0x26580700
Now after a full restart I am finally on the latest dev commit.
But sorry to say everything seems to be a bit more unstable now.
My Xiamoi illumination sensors work for a while (around an hour) but then they fail.
My Xiamoi Opple Switch 6-button presses aren't even registered as a single press.
But the Xiamoi Opple Switch 4-button is now registered as the correct device whereas before it was somehow rejected as unknown device.
There's quite a lot text in the log after the update following these (new) commands:
debug 2020-05-18 15:36:00: Received MQTT message on 'zigbee2mqtt/bridge/config/devices/get' with data ''
- this might happen, when I actively call from zigbee2mqttAssistant, but it also happens without using the Assistant (but maybe it's running in the background on the docker container)
Errors are:
error 2020-05-18 15:28:52: Failed to configure 'GZCGQ01LM light intensity east', attempt 1 (Error: Bind 0x04cf8cdf3c7880e4/1 genPowerCfg from '0x00212effff048770/1' failed (undefined)
at Endpoint. (/app/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:244:23)
at Generator.throw ()
at rejected (/app/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:6:65))
or
error 2020-05-18 15:31:08: Failed to configure 'GZCGQ01LM light intensity west', attempt 3 (Error: Bind 0x04cf8cdf3c78d571/1 genPowerCfg from '0x00212effff048770/1' failed (undefined)
at Endpoint. (/app/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:244:23)
at Generator.throw ()
at rejected (/app/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:6:65)
at runMicrotasks ()
at runNextTicks (internal/process/task_queues.js:62:5)
at processTimers (internal/timers.js:489:9))
or
error 2020-05-18 15:30:53: Failed to configure 'WXCJKG13LM Opple switch 3', attempt 1 (Error: Write 0x04cf8cdf3c794995/1 aqaraOpple({"mode":1}, {"timeout":10000,"manufacturerCode":4447,"disableDefaultRespo$
at Endpoint. (/app/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:158:23)
at Generator.next ()
at fulfilled (/app/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:5:58))
This devices have been configured before and I not actively updated them.
P.S.: Sorry for being so elaborated, but I hope it helps to improve your good and highly appreciated work on the ConBeeII and zigbee2mqtt cooperation.
from zigbee-herdsman.
Messages before crash (already known):
(node:16) UnhandledPromiseRejectionWarning: TIMEOUT
(node:16) 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: 13)
(node:16) UnhandledPromiseRejectionWarning: TIMEOUT
(node:16) 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: 14)
(node:16) UnhandledPromiseRejectionWarning: TIMEOUT
(node:16) 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: 15)
from zigbee-herdsman.
zigbee2mqtt: docker.io/koenkk/zigbee2mqtt@sha256:7b0ee3b22714ebb1be947f921639a75af30154528f8660899635f6676dd379ed
ConBee II f/w: 0x26580700
I've started re-pairing devices from an existing CC2531 network and I've successfully paired a TRADFRI Signal Repeater.
In the logs, however, I get these messages repeated 4 times a second:
[zigbee2mqtt-55c99bb5cb-hmgkm] zigbee2mqtt:debug 2020-05-20 17:54:16: Mocking 'update_available' value for Home Assistant
[zigbee2mqtt-55c99bb5cb-hmgkm] zigbee2mqtt:info 2020-05-20 17:54:16: MQTT publish: topic 'zigbee2mqtt-dconz/0x086bd7fffe5b3350', payload '{"linkquality":76}'
Is anyone else experiencing console spam?
from zigbee-herdsman.
I have changed my CC2531 to ConBee II for a day and was able to pair 29 of my devices (mostly Aqara sensors, curtain motors and wall switches + Eurotronic Radiator Valve + GLEDOPTO driver). It worked great but everything went unresponsive during the night.
Everything went back online after system reboot. I have looked into the logs and just saw that around 6-7 AM devices stopped sending messages: Received Zigbee message from...
. After this logs only show:
�[34mzigbee2mqtt:debug�[39m 2020-05-23 07:02:53: Saving state to file /app/data/state.json
�[34mzigbee2mqtt:debug�[39m 2020-05-23 07:07:53: Saving state to file /app/data/state.json
�[34mzigbee2mqtt:debug�[39m 2020-05-23 07:12:00: Received MQTT message on 'zigbee2mqtt/bridge/config/devices/get' with data ''
�[32mzigbee2mqtt:info �[39m 2020-05-23 07:12:00: MQTT publish: topic 'zigbee2mqtt/bridge/config/devices', payload '[{"ieeeAddr":"0x00212effff04de69","type":"Coordinator","networkAddress":0,"friendly_name":"Coordinator","softwareBuildID":"ConBee2","dateCode":"0x26490700","lastSeen":1590210720006},{"ieeeAddr":"0x00158d0004019537","type":"Router","networkAddress":53545,"model":"QBKG12LM","vendor":"Xiaomi","description":"Aqara double key wired wall switch","friendly_name":"bedroom_wall_switch","manufacturerID":4447,"manufacturerName":"LUMI","powerSource":"Mains (single phase)","modelID":"lumi.ctrl_ln2.aq1","hardwareVersion":18,"dateCode":"06-25-2018","lastSeen":1590210004643},{"ieeeAddr":"0x04cf8cdf3c74a41b","type":"EndDevice","networkAddress":50548,"model":"ZNCLDJ12LM","vendor":"Xiaomi","description":"Aqara B1 curtain motor ","friendly_name":"office_cover","manufacturerID":4447,"manufacturerName":"LUMI","powerSource":"Battery","modelID":"lumi.curtain.hagl04","hardwareVersion":1,"softwareBuildID":"2019\u0000www.","dateCode":"20190329","lastSeen":1590206407544},{"ieeeAddr":"0x00158d0003c3fc7a","type":"EndDevice","networkAddress":50634,"model":"SPZB0001","vendor":"Eurotronic","description":"Spirit Zigbee wireless heater thermostat","friendly_name":"office_radiator","manufacturerID":4151,"manufacturerName":"Eurotronic","powerSource":"Battery","modelID":"SPZB0001","hardwareVersion":35,"softwareBuildID":"22190930","dateCode":"20191014","lastSeen":1590209901948},{"ieeeAddr":"0x00158d0001e8724b","type":"EndDevice","networkAddress":40328,"model":"WXKG01LM","vendor":"Xiaomi","description":"MiJia wireless switch","friendly_name":"bedroom_switch_karolina","manufacturerID":4151,"manufacturerName":"LUMI","powerSource":"Battery","modelID":"lumi.sensor_switch","lastSeen":1590209617531},{"ieeeAddr":"0x00158d0003d4378b","type":"EndDevice","networkAddress":57024,"model":"WSDCGQ11LM","vendor":"Xiaomi","description":"Aqara temperature, humidity and pressure sensor","friendly_name":"bedroom_sensor","manufacturerID":4151,"manufacturerName":"LUMI","powerSource":"Battery","modelID":"lumi.weather","lastSeen":1590207083133},{"ieeeAddr":"0x00158d0004267a2d","type":"EndDevice","networkAddress":9553,"model":"QBKG12LM","vendor":"Xiaomi","description":"Aqara double key wired wall switch","friendly_name":"office_wall_switch","manufacturerID":4151,"manufacturerName":"LUMI","powerSource":"Battery","modelID":"lumi.ctrl_ln2.aq1","lastSeen":1590209827937},{"ieeeAddr":"0x00158d000205ae96","type":"EndDevice","networkAddress":61505,"model":"WXKG01LM","vendor":"Xiaomi","description":"MiJia wireless switch","friendly_name":"bedroom_switch_arek","manufacturerID":4151,"manufacturerName":"LUMI","powerSource":"Battery","modelID":"lumi.sensor_switch","lastSeen":1590208602563},{"ieeeAddr":"0x00158d00034542a8","type":"Router","networkAddress":25447,"model":"QBKG03LM","vendor":"Xiaomi","description":"Aqara double key wired wall switch without neutral wire. Doesn't work as a router and doesn't support power meter","friendly_name":"bathroom_wall_switch","manufacturerID":4151,"manufacturerName":"LUMI","powerSource":"DC Source","modelID":"lumi.ctrl_neutral2","hardwareVersion":38,"dateCode":"04-25-2018","lastSeen":1590210029235},{"ieeeAddr":"0x00158d000423ec9c","type":"EndDevice","networkAddress":5047,"model":"WSDCGQ11LM","vendor":"Xiaomi","description":"Aqara temperature, humidity and pressure sensor","friendly_name":"bathroom_sensor","manufacturerID":4151,"manufacturerName":"LUMI","powerSource":"Battery","modelID":"lumi.weather","lastSeen":1590208066331},{"ieeeAddr":"0x00158d000343c9a4","type":"Router","networkAddress":4887,"model":"QBKG03LM","vendor":"Xiaomi","description":"Aqara double key wired wall switch without neutral wire. Doesn't work as a router and doesn't support power meter","friendly_name":"livingroom_wall_switch","manufacturerID":4151,"manufacturerName":"LUMI","powerSource":"DC Source","modelID":"lumi.ctrl_neutral2","hardwareVersion":38,"dateCode":"04-25-2018","lastSeen":1590210041003},{"ieeeAddr":"0x00158d0003c47319","type":"EndDevice","networkAddress":35309,"model":"SPZB0001","vendor":"Eurotronic","description":"Spirit Zigbee wireless heater thermostat","friendly_name":"bedroom_radiator","manufacturerID":4151,"manufacturerName":"Eurotronic","powerSource":"Battery","modelID":"SPZB0001","hardwareVersion":35,"softwareBuildID":"22190930","dateCode":"20191014","lastSeen":1590209979154},{"ieeeAddr":"0x00158d00028a9064","type":"EndDevice","networkAddress":4469,"model":"WXKG01LM","vendor":"Xiaomi","description":"MiJia wireless switch","friendly_name":"office_desk_switch","manufacturerID":4151,"manufacturerName":"LUMI","powerSource":"Battery","modelID":"lumi.sensor_switch","lastSeen":1590207914710},{"ieeeAddr":"0x00158d000407469e","type":"EndDevice","networkAddress":13390,"model":"WSDCGQ11LM","vendor":"Xiaomi","description":"Aqara temperature, humidity and pressure sensor","friendly_name":"office_sensor","manufacturerID":4151,"manufacturerName":"LUMI","powerSource":"Battery","modelID":"lumi.weather","lastSeen":1590206637967},{"ieeeAddr":"0x00158d00030a21ba","type":"EndDevice","networkAddress":3604,"model":"QBKG04LM","vendor":"Xiaomi","description":"Aqara single key wired wall switch without neutral wire. Doesn't work as a router and doesn't support power meter","friendly_name":"corridor_wall_switch","manufacturerID":4151,"manufacturerName":"LUMI","powerSource":"Battery","modelID":"lumi.ctrl_neutral1","lastSeen":1590210009917},{"ieeeAddr":"0x00158d00041451af","type":"EndDevice","networkAddress":49032,"model":"RTCGQ11LM","vendor":"Xiaomi","description":"Aqara human body movement and illuminance sensor","friendly_name":"corridor_motion","manufacturerID":4151,"manufacturerName":"LUMI","powerSource":"Battery","modelID":"lumi.sensor_motion.aq2","lastSeen":1590207295735},{"ieeeAddr":"0x00158d000302f092","type":"EndDevice","networkAddress":35104,"model":"QBKG03LM","vendor":"Xiaomi","description":"Aqara double key wired wall switch without neutral wire. Doesn't work as a router and doesn't support power meter","friendly_name":"kitchen_wall_switch","manufacturerID":4151,"manufacturerName":"LUMI","powerSource":"Battery","modelID":"lumi.ctrl_neutral2","lastSeen":1590210044873},{"ieeeAddr":"0x00158d0002a9ba45","type":"EndDevice","networkAddress":9441,"model":"QBKG04LM","vendor":"Xiaomi","description":"Aqara single key wired wall switch without neutral wire. Doesn't work as a router and doesn't support power meter","friendly_name":"diningroom_wall_switch","manufacturerID":4151,"manufacturerName":"LUMI","powerSource":"Battery","modelID":"lumi.ctrl_neutral1","lastSeen":1590210054028},{"ieeeAddr":"0x00158d00023ce81a","type":"EndDevice","networkAddress":23594,"model":"WSDCGQ01LM","vendor":"Xiaomi","description":"MiJia temperature & humidity sensor","friendly_name":"livingroom_sensor","manufacturerID":4151,"manufacturerName":"LUMI","powerSource":"Battery","modelID":"lumi.sensor_ht","lastSeen":1590207436357},{"ieeeAddr":"0x04cf8cdf3c74ad87","type":"EndDevice","networkAddress":53856,"model":"ZNCLDJ12LM","vendor":"Xiaomi","description":"Aqara B1 curtain motor ","friendly_name":"livingroom_cover","manufacturerID":4447,"manufacturerName":"LUMI","powerSource":"Battery","modelID":"lumi.curtain.hagl04","hardwareVersion":1,"softwareBuildID":"2019\u0000www.","dateCode":"20190329","lastSeen":1590206407593},{"ieeeAddr":"0x00158d0003e71128","type":"EndDevice","networkAddress":481,"model":"WXKG01LM","vendor":"Xiaomi","description":"MiJia wireless switch","friendly_name":"diningroom_switch","manufacturerID":4151,"manufacturerName":"LUMI","powerSource":"Battery","modelID":"lumi.sensor_switch","lastSeen":1590207478485},{"ieeeAddr":"0x00158d0004073fb0","type":"EndDevice","networkAddress":63898,"model":"WXKG01LM","vendor":"Xiaomi","description":"MiJia wireless switch","friendly_name":"livingroom_switch","manufacturerID":4151,"manufacturerName":"LUMI","powerSource":"Battery","modelID":"lumi.sensor_switch","lastSeen":1590208876730},{"ieeeAddr":"0x00158d0003c45fea","type":"EndDevice","networkAddress":53400,"model":"SPZB0001","vendor":"Eurotronic","description":"Spirit Zigbee wireless heater thermostat","friendly_name":"diningroom_radiator","manufacturerID":4151,"manufacturerName":"Eurotronic","powerSource":"Battery","modelID":"SPZB0001","hardwareVersion":35,"softwareBuildID":"22190930","dateCode":"20191014","lastSeen":1590209943382},{"ieeeAddr":"0x00158d0003c4602e","type":"EndDevice","networkAddress":15497,"model":"SPZB0001","vendor":"Eurotronic","description":"Spirit Zigbee wireless heater thermostat","friendly_name":"livingroom_radiator","manufacturerID":4151,"manufacturerName":"Eurotronic","powerSource":"Battery","modelID":"SPZB0001","hardwareVersion":35,"softwareBuildID":"22190930","dateCode":"20191014","lastSeen":1590209632704},{"ieeeAddr":"0x00124b001effab8e","type":"Router","networkAddress":50684,"model":"GL-C-008","vendor":"Gledopto","description":"Zigbee LED controller RGB + CCT","friendly_name":"kitchen_countertop","manufacturerID":0,"manufacturerName":"GLEDOPTO","powerSource":"Mains (single phase)","modelID":"GL-C-008","hardwareVersion":1,"softwareBuildID":"2.0.0","dateCode":"20131206","lastSeen":1590095405223},{"ieeeAddr":"0x00158d00023ac220","type":"EndDevice","networkAddress":64021,"model":"WSDCGQ01LM","vendor":"Xiaomi","description":"MiJia temperature & humidity sensor","friendly_name":"outdoor_sensor","manufacturerID":4151,"manufacturerName":"LUMI","powerSource":"Battery","modelID":"lumi.sensor_ht","lastSeen":1590208349473},{"ieeeAddr":"0x00158d00020f454f","type":"EndDevice","networkAddress":13760,"model":"WXKG01LM","vendor":"Xiaomi","description":"MiJia wireless switch","friendly_name":"kitchen_switch","manufacturerID":4151,"manufacturerName":"LUMI","powerSource":"Battery","modelID":"lumi.sensor_switch","lastSeen":1590207726145}]'
�[34mzigbee2mqtt:debug�[39m 2020-05-23 07:12:00: Received MQTT message on 'zigbee2mqtt/bridge/config/devices' with data '[{"ieeeAddr":"0x00212effff04de69","type":"Coordinator","networkAddress":0,"friendly_name":"Coordinator","softwareBuildID":"ConBee2","dateCode":"0x26490700","lastSeen":1590210720006},{"ieeeAddr":"0x00158d0004019537","type":"Router","networkAddress":53545,"model":"QBKG12LM","vendor":"Xiaomi","description":"Aqara double key wired wall switch","friendly_name":"bedroom_wall_switch","manufacturerID":4447,"manufacturerName":"LUMI","powerSource":"Mains (single phase)","modelID":"lumi.ctrl_ln2.aq1","hardwareVersion":18,"dateCode":"06-25-2018","lastSeen":1590210004643},{"ieeeAddr":"0x04cf8cdf3c74a41b","type":"EndDevice","networkAddress":50548,"model":"ZNCLDJ12LM","vendor":"Xiaomi","description":"Aqara B1 curtain motor ","friendly_name":"office_cover","manufacturerID":4447,"manufacturerName":"LUMI","powerSource":"Battery","modelID":"lumi.curtain.hagl04","hardwareVersion":1,"softwareBuildID":"2019\u0000www.","dateCode":"20190329","lastSeen":1590206407544},{"ieeeAddr":"0x00158d0003c3fc7a","type":"EndDevice","networkAddress":50634,"model":"SPZB0001","vendor":"Eurotronic","description":"Spirit Zigbee wireless heater thermostat","friendly_name":"office_radiator","manufacturerID":4151,"manufacturerName":"Eurotronic","powerSource":"Battery","modelID":"SPZB0001","hardwareVersion":35,"softwareBuildID":"22190930","dateCode":"20191014","lastSeen":1590209901948},{"ieeeAddr":"0x00158d0001e8724b","type":"EndDevice","networkAddress":40328,"model":"WXKG01LM","vendor":"Xiaomi","description":"MiJia wireless switch","friendly_name":"bedroom_switch_karolina","manufacturerID":4151,"manufacturerName":"LUMI","powerSource":"Battery","modelID":"lumi.sensor_switch","lastSeen":1590209617531},{"ieeeAddr":"0x00158d0003d4378b","type":"EndDevice","networkAddress":57024,"model":"WSDCGQ11LM","vendor":"Xiaomi","description":"Aqara temperature, humidity and pressure sensor","friendly_name":"bedroom_sensor","manufacturerID":4151,"manufacturerName":"LUMI","powerSource":"Battery","modelID":"lumi.weather","lastSeen":1590207083133},{"ieeeAddr":"0x00158d0004267a2d","type":"EndDevice","networkAddress":9553,"model":"QBKG12LM","vendor":"Xiaomi","description":"Aqara double key wired wall switch","friendly_name":"office_wall_switch","manufacturerID":4151,"manufacturerName":"LUMI","powerSource":"Battery","modelID":"lumi.ctrl_ln2.aq1","lastSeen":1590209827937},{"ieeeAddr":"0x00158d000205ae96","type":"EndDevice","networkAddress":61505,"model":"WXKG01LM","vendor":"Xiaomi","description":"MiJia wireless switch","friendly_name":"bedroom_switch_arek","manufacturerID":4151,"manufacturerName":"LUMI","powerSource":"Battery","modelID":"lumi.sensor_switch","lastSeen":1590208602563},{"ieeeAddr":"0x00158d00034542a8","type":"Router","networkAddress":25447,"model":"QBKG03LM","vendor":"Xiaomi","description":"Aqara double key wired wall switch without neutral wire. Doesn't work as a router and doesn't support power meter","friendly_name":"bathroom_wall_switch","manufacturerID":4151,"manufacturerName":"LUMI","powerSource":"DC Source","modelID":"lumi.ctrl_neutral2","hardwareVersion":38,"dateCode":"04-25-2018","lastSeen":1590210029235},{"ieeeAddr":"0x00158d000423ec9c","type":"EndDevice","networkAddress":5047,"model":"WSDCGQ11LM","vendor":"Xiaomi","description":"Aqara temperature, humidity and pressure sensor","friendly_name":"bathroom_sensor","manufacturerID":4151,"manufacturerName":"LUMI","powerSource":"Battery","modelID":"lumi.weather","lastSeen":1590208066331},{"ieeeAddr":"0x00158d000343c9a4","type":"Router","networkAddress":4887,"model":"QBKG03LM","vendor":"Xiaomi","description":"Aqara double key wired wall switch without neutral wire. Doesn't work as a router and doesn't support power meter","friendly_name":"livingroom_wall_switch","manufacturerID":4151,"manufacturerName":"LUMI","powerSource":"DC Source","modelID":"lumi.ctrl_neutral2","hardwareVersion":38,"dateCode":"04-25-2018","lastSeen":1590210041003},{"ieeeAddr":"0x00158d0003c47319","type":"EndDevice","networkAddress":35309,"model":"SPZB0001","vendor":"Eurotronic","description":"Spirit Zigbee wireless heater thermostat","friendly_name":"bedroom_radiator","manufacturerID":4151,"manufacturerName":"Eurotronic","powerSource":"Battery","modelID":"SPZB0001","hardwareVersion":35,"softwareBuildID":"22190930","dateCode":"20191014","lastSeen":1590209979154},{"ieeeAddr":"0x00158d00028a9064","type":"EndDevice","networkAddress":4469,"model":"WXKG01LM","vendor":"Xiaomi","description":"MiJia wireless switch","friendly_name":"office_desk_switch","manufacturerID":4151,"manufacturerName":"LUMI","powerSource":"Battery","modelID":"lumi.sensor_switch","lastSeen":1590207914710},{"ieeeAddr":"0x00158d000407469e","type":"EndDevice","networkAddress":13390,"model":"WSDCGQ11LM","vendor":"Xiaomi","description":"Aqara temperature, humidity and pressure sensor","friendly_name":"office_sensor","manufacturerID":4151,"manufacturerName":"LUMI","powerSource":"Battery","modelID":"lumi.weather","lastSeen":1590206637967},{"ieeeAddr":"0x00158d00030a21ba","type":"EndDevice","networkAddress":3604,"model":"QBKG04LM","vendor":"Xiaomi","description":"Aqara single key wired wall switch without neutral wire. Doesn't work as a router and doesn't support power meter","friendly_name":"corridor_wall_switch","manufacturerID":4151,"manufacturerName":"LUMI","powerSource":"Battery","modelID":"lumi.ctrl_neutral1","lastSeen":1590210009917},{"ieeeAddr":"0x00158d00041451af","type":"EndDevice","networkAddress":49032,"model":"RTCGQ11LM","vendor":"Xiaomi","description":"Aqara human body movement and illuminance sensor","friendly_name":"corridor_motion","manufacturerID":4151,"manufacturerName":"LUMI","powerSource":"Battery","modelID":"lumi.sensor_motion.aq2","lastSeen":1590207295735},{"ieeeAddr":"0x00158d000302f092","type":"EndDevice","networkAddress":35104,"model":"QBKG03LM","vendor":"Xiaomi","description":"Aqara double key wired wall switch without neutral wire. Doesn't work as a router and doesn't support power meter","friendly_name":"kitchen_wall_switch","manufacturerID":4151,"manufacturerName":"LUMI","powerSource":"Battery","modelID":"lumi.ctrl_neutral2","lastSeen":1590210044873},{"ieeeAddr":"0x00158d0002a9ba45","type":"EndDevice","networkAddress":9441,"model":"QBKG04LM","vendor":"Xiaomi","description":"Aqara single key wired wall switch without neutral wire. Doesn't work as a router and doesn't support power meter","friendly_name":"diningroom_wall_switch","manufacturerID":4151,"manufacturerName":"LUMI","powerSource":"Battery","modelID":"lumi.ctrl_neutral1","lastSeen":1590210054028},{"ieeeAddr":"0x00158d00023ce81a","type":"EndDevice","networkAddress":23594,"model":"WSDCGQ01LM","vendor":"Xiaomi","description":"MiJia temperature & humidity sensor","friendly_name":"livingroom_sensor","manufacturerID":4151,"manufacturerName":"LUMI","powerSource":"Battery","modelID":"lumi.sensor_ht","lastSeen":1590207436357},{"ieeeAddr":"0x04cf8cdf3c74ad87","type":"EndDevice","networkAddress":53856,"model":"ZNCLDJ12LM","vendor":"Xiaomi","description":"Aqara B1 curtain motor ","friendly_name":"livingroom_cover","manufacturerID":4447,"manufacturerName":"LUMI","powerSource":"Battery","modelID":"lumi.curtain.hagl04","hardwareVersion":1,"softwareBuildID":"2019\u0000www.","dateCode":"20190329","lastSeen":1590206407593},{"ieeeAddr":"0x00158d0003e71128","type":"EndDevice","networkAddress":481,"model":"WXKG01LM","vendor":"Xiaomi","description":"MiJia wireless switch","friendly_name":"diningroom_switch","manufacturerID":4151,"manufacturerName":"LUMI","powerSource":"Battery","modelID":"lumi.sensor_switch","lastSeen":1590207478485},{"ieeeAddr":"0x00158d0004073fb0","type":"EndDevice","networkAddress":63898,"model":"WXKG01LM","vendor":"Xiaomi","description":"MiJia wireless switch","friendly_name":"livingroom_switch","manufacturerID":4151,"manufacturerName":"LUMI","powerSource":"Battery","modelID":"lumi.sensor_switch","lastSeen":1590208876730},{"ieeeAddr":"0x00158d0003c45fea","type":"EndDevice","networkAddress":53400,"model":"SPZB0001","vendor":"Eurotronic","description":"Spirit Zigbee wireless heater thermostat","friendly_name":"diningroom_radiator","manufacturerID":4151,"manufacturerName":"Eurotronic","powerSource":"Battery","modelID":"SPZB0001","hardwareVersion":35,"softwareBuildID":"22190930","dateCode":"20191014","lastSeen":1590209943382},{"ieeeAddr":"0x00158d0003c4602e","type":"EndDevice","networkAddress":15497,"model":"SPZB0001","vendor":"Eurotronic","description":"Spirit Zigbee wireless heater thermostat","friendly_name":"livingroom_radiator","manufacturerID":4151,"manufacturerName":"Eurotronic","powerSource":"Battery","modelID":"SPZB0001","hardwareVersion":35,"softwareBuildID":"22190930","dateCode":"20191014","lastSeen":1590209632704},{"ieeeAddr":"0x00124b001effab8e","type":"Router","networkAddress":50684,"model":"GL-C-008","vendor":"Gledopto","description":"Zigbee LED controller RGB + CCT","friendly_name":"kitchen_countertop","manufacturerID":0,"manufacturerName":"GLEDOPTO","powerSource":"Mains (single phase)","modelID":"GL-C-008","hardwareVersion":1,"softwareBuildID":"2.0.0","dateCode":"20131206","lastSeen":1590095405223},{"ieeeAddr":"0x00158d00023ac220","type":"EndDevice","networkAddress":64021,"model":"WSDCGQ01LM","vendor":"Xiaomi","description":"MiJia temperature & humidity sensor","friendly_name":"outdoor_sensor","manufacturerID":4151,"manufacturerName":"LUMI","powerSource":"Battery","modelID":"lumi.sensor_ht","lastSeen":1590208349473},{"ieeeAddr":"0x00158d00020f454f","type":"EndDevice","networkAddress":13760,"model":"WXKG01LM","vendor":"Xiaomi","description":"MiJia wireless switch","friendly_name":"kitchen_switch","manufacturerID":4151,"manufacturerName":"LUMI","powerSource":"Battery","modelID":"lumi.sensor_switch","lastSeen":1590207726145}]'
�[32mzigbee2mqtt:info �[39m 2020-05-23 07:12:00: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"devices","message":[{"ieeeAddr":"0x00212effff04de69","type":"Coordinator","networkAddress":0,"friendly_name":"Coordinator","softwareBuildID":"ConBee2","dateCode":"0x26490700","lastSeen":1590210720015},{"ieeeAddr":"0x00158d0004019537","type":"Router","networkAddress":53545,"model":"QBKG12LM","vendor":"Xiaomi","description":"Aqara double key wired wall switch","friendly_name":"bedroom_wall_switch","manufacturerID":4447,"manufacturerName":"LUMI","powerSource":"Mains (single phase)","modelID":"lumi.ctrl_ln2.aq1","hardwareVersion":18,"dateCode":"06-25-2018","lastSeen":1590210004643},{"ieeeAddr":"0x04cf8cdf3c74a41b","type":"EndDevice","networkAddress":50548,"model":"ZNCLDJ12LM","vendor":"Xiaomi","description":"Aqara B1 curtain motor ","friendly_name":"office_cover","manufacturerID":4447,"manufacturerName":"LUMI","powerSource":"Battery","modelID":"lumi.curtain.hagl04","hardwareVersion":1,"softwareBuildID":"2019\u0000www.","dateCode":"20190329","lastSeen":1590206407544},{"ieeeAddr":"0x00158d0003c3fc7a","type":"EndDevice","networkAddress":50634,"model":"SPZB0001","vendor":"Eurotronic","description":"Spirit Zigbee wireless heater thermostat","friendly_name":"office_radiator","manufacturerID":4151,"manufacturerName":"Eurotronic","powerSource":"Battery","modelID":"SPZB0001","hardwareVersion":35,"softwareBuildID":"22190930","dateCode":"20191014","lastSeen":1590209901948},{"ieeeAddr":"0x00158d0001e8724b","type":"EndDevice","networkAddress":40328,"model":"WXKG01LM","vendor":"Xiaomi","description":"MiJia wireless switch","friendly_name":"bedroom_switch_karolina","manufacturerID":4151,"manufacturerName":"LUMI","powerSource":"Battery","modelID":"lumi.sensor_switch","lastSeen":1590209617531},{"ieeeAddr":"0x00158d0003d4378b","type":"EndDevice","networkAddress":57024,"model":"WSDCGQ11LM","vendor":"Xiaomi","description":"Aqara temperature, humidity and pressure sensor","friendly_name":"bedroom_sensor","manufacturerID":4151,"manufacturerName":"LUMI","powerSource":"Battery","modelID":"lumi.weather","lastSeen":1590207083133},{"ieeeAddr":"0x00158d0004267a2d","type":"EndDevice","networkAddress":9553,"model":"QBKG12LM","vendor":"Xiaomi","description":"Aqara double key wired wall switch","friendly_name":"office_wall_switch","manufacturerID":4151,"manufacturerName":"LUMI","powerSource":"Battery","modelID":"lumi.ctrl_ln2.aq1","lastSeen":1590209827937},{"ieeeAddr":"0x00158d000205ae96","type":"EndDevice","networkAddress":61505,"model":"WXKG01LM","vendor":"Xiaomi","description":"MiJia wireless switch","friendly_name":"bedroom_switch_arek","manufacturerID":4151,"manufacturerName":"LUMI","powerSource":"Battery","modelID":"lumi.sensor_switch","lastSeen":1590208602563},{"ieeeAddr":"0x00158d00034542a8","type":"Router","networkAddress":25447,"model":"QBKG03LM","vendor":"Xiaomi","description":"Aqara double key wired wall switch without neutral wire. Doesn't work as a router and doesn't support power meter","friendly_name":"bathroom_wall_switch","manufacturerID":4151,"manufacturerName":"LUMI","powerSource":"DC Source","modelID":"lumi.ctrl_neutral2","hardwareVersion":38,"dateCode":"04-25-2018","lastSeen":1590210029235},{"ieeeAddr":"0x00158d000423ec9c","type":"EndDevice","networkAddress":5047,"model":"WSDCGQ11LM","vendor":"Xiaomi","description":"Aqara temperature, humidity and pressure sensor","friendly_name":"bathroom_sensor","manufacturerID":4151,"manufacturerName":"LUMI","powerSource":"Battery","modelID":"lumi.weather","lastSeen":1590208066331},{"ieeeAddr":"0x00158d000343c9a4","type":"Router","networkAddress":4887,"model":"QBKG03LM","vendor":"Xiaomi","description":"Aqara double key wired wall switch without neutral wire. Doesn't work as a router and doesn't support power meter","friendly_name":"livingroom_wall_switch","manufacturerID":4151,"manufacturerName":"LUMI","powerSource":"DC Source","modelID":"lumi.ctrl_neutral2","hardwareVersion":38,"dateCode":"04-25-2018","lastSeen":1590210041003},{"ieeeAddr":"0x00158d0003c47319","type":"EndDevice","networkAddress":35309,"model":"SPZB0001","vendor":"Eurotronic","description":"Spirit Zigbee wireless heater thermostat","friendly_name":"bedroom_radiator","manufacturerID":4151,"manufacturerName":"Eurotronic","powerSource":"Battery","modelID":"SPZB0001","hardwareVersion":35,"softwareBuildID":"22190930","dateCode":"20191014","lastSeen":1590209979154},{"ieeeAddr":"0x00158d00028a9064","type":"EndDevice","networkAddress":4469,"model":"WXKG01LM","vendor":"Xiaomi","description":"MiJia wireless switch","friendly_name":"office_desk_switch","manufacturerID":4151,"manufacturerName":"LUMI","powerSource":"Battery","modelID":"lumi.sensor_switch","lastSeen":1590207914710},{"ieeeAddr":"0x00158d000407469e","type":"EndDevice","networkAddress":13390,"model":"WSDCGQ11LM","vendor":"Xiaomi","description":"Aqara temperature, humidity and pressure sensor","friendly_name":"office_sensor","manufacturerID":4151,"manufacturerName":"LUMI","powerSource":"Battery","modelID":"lumi.weather","lastSeen":1590206637967},{"ieeeAddr":"0x00158d00030a21ba","type":"EndDevice","networkAddress":3604,"model":"QBKG04LM","vendor":"Xiaomi","description":"Aqara single key wired wall switch without neutral wire. Doesn't work as a router and doesn't support power meter","friendly_name":"corridor_wall_switch","manufacturerID":4151,"manufacturerName":"LUMI","powerSource":"Battery","modelID":"lumi.ctrl_neutral1","lastSeen":1590210009917},{"ieeeAddr":"0x00158d00041451af","type":"EndDevice","networkAddress":49032,"model":"RTCGQ11LM","vendor":"Xiaomi","description":"Aqara human body movement and illuminance sensor","friendly_name":"corridor_motion","manufacturerID":4151,"manufacturerName":"LUMI","powerSource":"Battery","modelID":"lumi.sensor_motion.aq2","lastSeen":1590207295735},{"ieeeAddr":"0x00158d000302f092","type":"EndDevice","networkAddress":35104,"model":"QBKG03LM","vendor":"Xiaomi","description":"Aqara double key wired wall switch without neutral wire. Doesn't work as a router and doesn't support power meter","friendly_name":"kitchen_wall_switch","manufacturerID":4151,"manufacturerName":"LUMI","powerSource":"Battery","modelID":"lumi.ctrl_neutral2","lastSeen":1590210044873},{"ieeeAddr":"0x00158d0002a9ba45","type":"EndDevice","networkAddress":9441,"model":"QBKG04LM","vendor":"Xiaomi","description":"Aqara single key wired wall switch without neutral wire. Doesn't work as a router and doesn't support power meter","friendly_name":"diningroom_wall_switch","manufacturerID":4151,"manufacturerName":"LUMI","powerSource":"Battery","modelID":"lumi.ctrl_neutral1","lastSeen":1590210054028},{"ieeeAddr":"0x00158d00023ce81a","type":"EndDevice","networkAddress":23594,"model":"WSDCGQ01LM","vendor":"Xiaomi","description":"MiJia temperature & humidity sensor","friendly_name":"livingroom_sensor","manufacturerID":4151,"manufacturerName":"LUMI","powerSource":"Battery","modelID":"lumi.sensor_ht","lastSeen":1590207436357},{"ieeeAddr":"0x04cf8cdf3c74ad87","type":"EndDevice","networkAddress":53856,"model":"ZNCLDJ12LM","vendor":"Xiaomi","description":"Aqara B1 curtain motor ","friendly_name":"livingroom_cover","manufacturerID":4447,"manufacturerName":"LUMI","powerSource":"Battery","modelID":"lumi.curtain.hagl04","hardwareVersion":1,"softwareBuildID":"2019\u0000www.","dateCode":"20190329","lastSeen":1590206407593},{"ieeeAddr":"0x00158d0003e71128","type":"EndDevice","networkAddress":481,"model":"WXKG01LM","vendor":"Xiaomi","description":"MiJia wireless switch","friendly_name":"diningroom_switch","manufacturerID":4151,"manufacturerName":"LUMI","powerSource":"Battery","modelID":"lumi.sensor_switch","lastSeen":1590207478485},{"ieeeAddr":"0x00158d0004073fb0","type":"EndDevice","networkAddress":63898,"model":"WXKG01LM","vendor":"Xiaomi","description":"MiJia wireless switch","friendly_name":"livingroom_switch","manufacturerID":4151,"manufacturerName":"LUMI","powerSource":"Battery","modelID":"lumi.sensor_switch","lastSeen":1590208876730},{"ieeeAddr":"0x00158d0003c45fea","type":"EndDevice","networkAddress":53400,"model":"SPZB0001","vendor":"Eurotronic","description":"Spirit Zigbee wireless heater thermostat","friendly_name":"diningroom_radiator","manufacturerID":4151,"manufacturerName":"Eurotronic","powerSource":"Battery","modelID":"SPZB0001","hardwareVersion":35,"softwareBuildID":"22190930","dateCode":"20191014","lastSeen":1590209943382},{"ieeeAddr":"0x00158d0003c4602e","type":"EndDevice","networkAddress":15497,"model":"SPZB0001","vendor":"Eurotronic","description":"Spirit Zigbee wireless heater thermostat","friendly_name":"livingroom_radiator","manufacturerID":4151,"manufacturerName":"Eurotronic","powerSource":"Battery","modelID":"SPZB0001","hardwareVersion":35,"softwareBuildID":"22190930","dateCode":"20191014","lastSeen":1590209632704},{"ieeeAddr":"0x00124b001effab8e","type":"Router","networkAddress":50684,"model":"GL-C-008","vendor":"Gledopto","description":"Zigbee LED controller RGB + CCT","friendly_name":"kitchen_countertop","manufacturerID":0,"manufacturerName":"GLEDOPTO","powerSource":"Mains (single phase)","modelID":"GL-C-008","hardwareVersion":1,"softwareBuildID":"2.0.0","dateCode":"20131206","lastSeen":1590095405223},{"ieeeAddr":"0x00158d00023ac220","type":"EndDevice","networkAddress":64021,"model":"WSDCGQ01LM","vendor":"Xiaomi","description":"MiJia temperature & humidity sensor","friendly_name":"outdoor_sensor","manufacturerID":4151,"manufacturerName":"LUMI","powerSource":"Battery","modelID":"lumi.sensor_ht","lastSeen":1590208349473},{"ieeeAddr":"0x00158d00020f454f","type":"EndDevice","networkAddress":13760,"model":"WXKG01LM","vendor":"Xiaomi","description":"MiJia wireless switch","friendly_name":"kitchen_switch","manufacturerID":4151,"manufacturerName":"LUMI","powerSource":"Battery","modelID":"lumi.sensor_switch","lastSeen":1590207726145}]}'
�[34mzigbee2mqtt:debug�[39m 2020-05-23 07:12:53: Saving state to file /app/data/state.json
�[34mzigbee2mqtt:debug�[39m 2020-05-23 07:17:53: Saving state to file /app/data/state.json
...and 2 hours after last device message I saw few of these:
�[34mzigbee2mqtt:debug�[39m 2020-05-23 08:52:53: Saving state to file /app/data/state.json
(node:16) UnhandledPromiseRejectionWarning: undefined
(node:16) 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: 30)
...and 4 hours ater last device message I found this:
�[34mzigbee2mqtt:debug�[39m 2020-05-23 08:00:04: Received MQTT message on 'zigbee2mqtt/bridge/networkmap' with data 'raw'
�[32mzigbee2mqtt:info �[39m 2020-05-23 08:00:04: Starting network scan (includeRoutes 'false')
�[31mzigbee2mqtt:error�[39m 2020-05-23 08:01:04: Failed to execute LQI for 'Coordinator'
�[31mzigbee2mqtt:error�[39m 2020-05-23 08:02:04: Failed to execute LQI for 'bedroom_wall_switch'
�[34mzigbee2mqtt:debug�[39m 2020-05-23 08:02:53: Saving state to file /app/data/state.json
�[31mzigbee2mqtt:error�[39m 2020-05-23 08:03:04: Failed to execute LQI for 'bathroom_wall_switch'
�[31mzigbee2mqtt:error�[39m 2020-05-23 08:04:04: Failed to execute LQI for 'livingroom_wall_switch'
�[31mzigbee2mqtt:error�[39m 2020-05-23 08:05:04: Failed to execute LQI for 'kitchen_countertop'
�[32mzigbee2mqtt:info �[39m 2020-05-23 08:05:04: Network scan finished
�[32mzigbee2mqtt:info �[39m 2020-05-23 08:05:04: MQTT publish: topic 'zigbee2mqtt/bridge/networkmap/raw', payload '{"nodes":[{"ieeeAddr":"0x00212effff04de69","friendlyName":"Coordinator","type":"Coordinator","networkAddress":0,"failed":["lqi"],"lastSeen":1590064897616},{"ieeeAddr":"0x00158d0004019537","friendlyName":"bedroom_wall_switch","type":"Router","networkAddress":53545,"manufacturerName":"LUMI","modelID":"lumi.ctrl_ln2.aq1","failed":["lqi"],"lastSeen":1590210004643},{"ieeeAddr":"0x04cf8cdf3c74a41b","friendlyName":"office_cover","type":"EndDevice","networkAddress":50548,"manufacturerName":"LUMI","modelID":"lumi.curtain.hagl04","lastSeen":1590206407544},{"ieeeAddr":"0x00158d0003c3fc7a","friendlyName":"office_radiator","type":"EndDevice","networkAddress":50634,"manufacturerName":"Eurotronic","modelID":"SPZB0001","lastSeen":1590209901948},{"ieeeAddr":"0x00158d0001e8724b","friendlyName":"bedroom_switch_karolina","type":"EndDevice","networkAddress":40328,"manufacturerName":"LUMI","modelID":"lumi.sensor_switch","lastSeen":1590209617531},{"ieeeAddr":"0x00158d0003d4378b","friendlyName":"bedroom_sensor","type":"EndDevice","networkAddress":57024,"manufacturerName":"LUMI","modelID":"lumi.weather","lastSeen":1590207083133},{"ieeeAddr":"0x00158d0004267a2d","friendlyName":"office_wall_switch","type":"EndDevice","networkAddress":9553,"manufacturerName":"LUMI","modelID":"lumi.ctrl_ln2.aq1","lastSeen":1590209827937},{"ieeeAddr":"0x00158d000205ae96","friendlyName":"bedroom_switch_arek","type":"EndDevice","networkAddress":61505,"manufacturerName":"LUMI","modelID":"lumi.sensor_switch","lastSeen":1590208602563},{"ieeeAddr":"0x00158d00034542a8","friendlyName":"bathroom_wall_switch","type":"Router","networkAddress":25447,"manufacturerName":"LUMI","modelID":"lumi.ctrl_neutral2","failed":["lqi"],"lastSeen":1590210029235},{"ieeeAddr":"0x00158d000423ec9c","friendlyName":"bathroom_sensor","type":"EndDevice","networkAddress":5047,"manufacturerName":"LUMI","modelID":"lumi.weather","lastSeen":1590208066331},{"ieeeAddr":"0x00158d000343c9a4","friendlyName":"livingroom_wall_switch","type":"Router","networkAddress":4887,"manufacturerName":"LUMI","modelID":"lumi.ctrl_neutral2","failed":["lqi"],"lastSeen":1590210041003},{"ieeeAddr":"0x00158d0003c47319","friendlyName":"bedroom_radiator","type":"EndDevice","networkAddress":35309,"manufacturerName":"Eurotronic","modelID":"SPZB0001","lastSeen":1590209979154},{"ieeeAddr":"0x00158d00028a9064","friendlyName":"office_desk_switch","type":"EndDevice","networkAddress":4469,"manufacturerName":"LUMI","modelID":"lumi.sensor_switch","lastSeen":1590207914710},{"ieeeAddr":"0x00158d000407469e","friendlyName":"office_sensor","type":"EndDevice","networkAddress":13390,"manufacturerName":"LUMI","modelID":"lumi.weather","lastSeen":1590206637967},{"ieeeAddr":"0x00158d00030a21ba","friendlyName":"corridor_wall_switch","type":"EndDevice","networkAddress":3604,"manufacturerName":"LUMI","modelID":"lumi.ctrl_neutral1","lastSeen":1590210009917},{"ieeeAddr":"0x00158d00041451af","friendlyName":"corridor_motion","type":"EndDevice","networkAddress":49032,"manufacturerName":"LUMI","modelID":"lumi.sensor_motion.aq2","lastSeen":1590207295735},{"ieeeAddr":"0x00158d000302f092","friendlyName":"kitchen_wall_switch","type":"EndDevice","networkAddress":35104,"manufacturerName":"LUMI","modelID":"lumi.ctrl_neutral2","lastSeen":1590210044873},{"ieeeAddr":"0x00158d0002a9ba45","friendlyName":"diningroom_wall_switch","type":"EndDevice","networkAddress":9441,"manufacturerName":"LUMI","modelID":"lumi.ctrl_neutral1","lastSeen":1590210054028},{"ieeeAddr":"0x00158d00023ce81a","friendlyName":"livingroom_sensor","type":"EndDevice","networkAddress":23594,"manufacturerName":"LUMI","modelID":"lumi.sensor_ht","lastSeen":1590207436357},{"ieeeAddr":"0x04cf8cdf3c74ad87","friendlyName":"livingroom_cover","type":"EndDevice","networkAddress":53856,"manufacturerName":"LUMI","modelID":"lumi.curtain.hagl04","lastSeen":1590206407593},{"ieeeAddr":"0x00158d0003e71128","friendlyName":"diningroom_switch","type":"EndDevice","networkAddress":481,"manufacturerName":"LUMI","modelID":"lumi.sensor_switch","lastSeen":1590207478485},{"ieeeAddr":"0x00158d0004073fb0","friendlyName":"livingroom_switch","type":"EndDevice","networkAddress":63898,"manufacturerName":"LUMI","modelID":"lumi.sensor_switch","lastSeen":1590208876730},{"ieeeAddr":"0x00158d0003c45fea","friendlyName":"diningroom_radiator","type":"EndDevice","networkAddress":53400,"manufacturerName":"Eurotronic","modelID":"SPZB0001","lastSeen":1590209943382},{"ieeeAddr":"0x00158d0003c4602e","friendlyName":"livingroom_radiator","type":"EndDevice","networkAddress":15497,"manufacturerName":"Eurotronic","modelID":"SPZB0001","lastSeen":1590209632704},{"ieeeAddr":"0x00124b001effab8e","friendlyName":"kitchen_countertop","type":"Router","networkAddress":50684,"manufacturerName":"GLEDOPTO","modelID":"GL-C-008","failed":["lqi"],"lastSeen":1590095405223},{"ieeeAddr":"0x00158d00023ac220","friendlyName":"outdoor_sensor","type":"EndDevice","networkAddress":64021,"manufacturerName":"LUMI","modelID":"lumi.sensor_ht","lastSeen":1590208349473},{"ieeeAddr":"0x00158d00020f454f","friendlyName":"kitchen_switch","type":"EndDevice","networkAddress":13760,"manufacturerName":"LUMI","modelID":"lumi.sensor_switch","lastSeen":1590207726145}],"links":[]}'
@Koenkk can I somehow get you more info on this? I can test it for few more days. If not then I will go back to CC2531.
Edit:
One time after restarting the docker I had these messages looping:
2020-05-23T12:19:41.842Z zigbee-herdsman:deconz:driver Timeout for aps request CMD: 0x12 seq: 239
2020-05-23T12:19:41.843Z zigbee-herdsman:deconz:adapter PERMIT_JOIN FAILED - APS TIMEOUT
2020-05-23T12:19:41.877Z zigbee-herdsman:deconz:driver DATA_REQUEST - sending data request - destAddr: 0xfffc EP:0 SeqNr. 241 request id: 118
Restarting the system solved the problem.
from zigbee-herdsman.
Related Issues (20)
- Ember driver : Error while parsing received frame, status=NO_RX_SPACE. HOT 1
- Ember driver: SET "APS_UNICAST_MESSAGE_COUNT" TO "32" with status=ERROR_OUT_OF_MEMORY. HOT 1
- State of ZiGate support HOT 17
- [Cluster Type] Align cluster definition for 'name' attribute HOT 1
- zigbee2mqtt<->EZSP incompatible with latest Gecko SDK v4.4.0.0 (EmberZNet 7.4.0.0) firmware build HOT 23
- Waitress timer is being set at the wrong time HOT 16
- Make waitress timeout configurable HOT 1
- Lower bound of "turnsOffAtBrightness1" ignored by "brightness_move" & "brightness_step" commands HOT 1
- Issue with serialport v12 and node > v20.2.0 HOT 1
- Get strange error in latest z2m with the latest zigbee-herdsman HOT 6
- [Task] ZCL definition update HOT 4
- Want better endpoint.writeStructured() HOT 1
- Z2M 1.35.2 stops with "Adapter disconnected, stopping" after few minutes of uptime (Sonoff-E / EZSP v12 / FW 7.3.2.0 build 212) HOT 3
- Load additional manufacturer-specific clusters from device converter HOT 4
- [Proposal] Removal of "forever" Permit Join HOT 11
- Adapters hardware flow control issues HOT 30
- Ikea Motion Sensor E1525/E1745 not updating properly HOT 6
- proposal: deprecation of legacy clicks HOT 1
- Move special readResponse out of zhc/src/index.ts (fixes legrand pairing issues) HOT 8
- Changes to payload when sending zclData to a device breaks iobroker.zigbee function
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from zigbee-herdsman.