Closed SteveWiFi closed 3 years ago
@chas-iot any ideas?
Please restart the ZigBee adapter with debug = serialProber If the probe sequence is sent and no response received then there is a patch. I’ll get the details later today
Regards, Charles
On 23 Dec 2020, at 7:00 AM, Michael Stegeman notifications@github.com wrote:
@chas-iot any ideas?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.
the two patches (which work most of the time) are at
They are awaiting testing to ensure that the change does not break adapters with the older firmware. Also, I'd like the documentation requested at https://github.com/dresden-elektronik/deconz-rest-plugin/issues/3787
I should get time in the next 10 days to get back to this and enhance the serial prober to allow multiple variant probes to be sent in 1 probe package, which should prevent the occasional failure that I noticed.
This is the output from using debug = serialProber:
2020-12-23 08:40:45.069 INFO : zigbee-adapter: DEBUG config = 'serialProber' 2020-12-23 08:40:45.070 INFO : zigbee-adapter: Enabling DEBUG_serialProber 2020-12-23 08:41:02.112 INFO : zigbee-adapter: SerialProber: /dev/ttyACM0 filter for XBee didn't match. 2020-12-23 08:41:02.114 INFO : zigbee-adapter: SerialProber: Probing /dev/ttyACM0 at 38400 for deConz 2020-12-23 08:41:02.115 INFO : zigbee-adapter: SerialProber: Opening /dev/ttyACM0 at 38400 baud 2020-12-23 08:41:02.122 INFO : zigbee-adapter: SerialProber: Probing /dev/ttyACM0 ... 2020-12-23 08:41:02.125 INFO : zigbee-adapter: SerialProber: Sent: <Buffer c0 0d 01 00 05 00 ed ff c0> 2020-12-23 08:41:02.627 INFO : zigbee-adapter: SerialProber: closing /dev/ttyACM0 2020-12-23 08:41:02.629 INFO : zigbee-adapter: SerialProber: timeout: deConz dongle not detected on /dev/ttyACM0 2020-12-23 08:41:02.632 ERROR : zigbee-adapter: SerialProber: timeout: deConz dongle not detected on /dev/ttyACM0 2020-12-23 08:41:02.634 INFO : zigbee-adapter: SerialProber: /dev/ttyACM0 filter for cc2531 didn't match. 2020-12-23 08:41:02.635 INFO : zigbee-adapter: SerialProber: /dev/ttyAMA filter for XBee didn't match. 2020-12-23 08:41:02.636 INFO : zigbee-adapter: SerialProber: allowAMASerial 2020-12-23 08:41:02.637 INFO : zigbee-adapter: SerialProber: Probing /dev/ttyAMA at 38400 for deConz 2020-12-23 08:41:02.639 INFO : zigbee-adapter: SerialProber: Opening /dev/ttyAMA at 38400 baud 2020-12-23 08:41:02.640 INFO : zigbee-adapter: SerialProber: /dev/ttyAMA filter for cc2531 didn't match. 2020-12-23 08:41:02.641 INFO : zigbee-adapter: Serial ports that were found: 2020-12-23 08:41:02.642 ERROR : zigbee-adapter: [Error: Error: No such file or directory, cannot open /dev/ttyAMA] 2020-12-23 08:41:02.643 ERROR : zigbee-adapter: [Error: Error: No such file or directory, cannot open /dev/ttyAMA] 2020-12-23 08:41:02.713 INFO : zigbee-adapter: USB Serial Device 1cf1:0030 Vendor: dresden elektronik ingenieurtechnik GmbH Serial: DE2123125 found @ /dev/ttyACM0 2020-12-23 08:41:02.714 INFO : zigbee-adapter: Serial Device found @ /dev/ttyAMA* 2020-12-23 08:41:02.715 ERROR : zigbee-adapter: Failed to start add-on zigbee-adapter: No Zigbee dongle found
Should I attempt to use the patches to see if it resolves my issues?
I applied the two fixes and this has resolved my problem.
Thank you very much for the help!
Hi,
I upgraded my Docker container from a 6 month old version of the Mozilla IoT Gateway to the v1.0.0 of the WebThingsIO Docker image.
When I upgraded, my Conbee 2 dongle was detected, but not functioning. Upon reading a few other issues on this Github page, I figured I would try to upgrade the firmware to the latest version (20th Nov) for which I now get the following errors:
Before the firmware update, this is what I would see:
I am 100% certain I have the correct permissions set as this has worked flawlessly for the past year. I am using Arch with the permissions set as:
I have set a udev rule to set these permissions at boot and I can confirm that the device is detected by both Windows and the Arch host.
Output of lsusb