markymark
(Mark Baumann)
February 6, 2020, 8:21pm
1
Hello I have following problem:
2020-02-06 20:19:07.031 [me.event.ThingUpdatedEvent] - Thing 'zigbee:coordinator_cc2531:6d1beb44' has been updated.
2020-02-06 20:19:07.034 [hingStatusInfoChangedEvent] - 'zigbee:coordinator_cc2531:6d1beb44' changed from INITIALIZING to UNKNOWN
==> /var/log/openhab2/openhab.log <==
2020-02-06 20:19:13.072 [WARN ] [.cc2531.network.ZigBeeNetworkManager] - Dongle reset failed. Assuming bootloader is running and sending magic byte 0xef.
2020-02-06 20:19:18.079 [WARN ] [.cc2531.network.ZigBeeNetworkManager] - Attempt to get out from bootloader failed.
Can someone help me please? Thx!
markymark
(Mark Baumann)
February 6, 2020, 8:47pm
2
you can set the bottloader number to another number but a random one does not solve my problem.
chris
(Chris Jackson)
February 6, 2020, 8:50pm
3
No - it won’t. This must be set to the default unless you know that the firmware was changed. If it’s not correct, then the binding won’t be able to communicate with the bootloader.
1 Like
markymark
(Mark Baumann)
February 6, 2020, 9:47pm
4
Ok cool but the default does not work too and says the same problem with the bootloader
chris
(Chris Jackson)
February 6, 2020, 9:48pm
5
That likely means that there is a communication problem, or the stick doesn’t work, or the stick doesn’t have the correct firmware, or maybe it’s not programmed.
1 Like
markymark
(Mark Baumann)
April 18, 2020, 11:48am
8
finally the device is online
So what did you, to make it work?
D1rk
(Dirk)
October 23, 2021, 4:13pm
10
Hi @markymark . How did you resolve the issue? I am getting exactly the same Warnings. Thanks, Dirk
+1
Did anyone find the cure… and how?
To answer my own question:
In my case i got the port wrong. It was /dev/ttyACM0 NOT /dev/ttyAMA0
all good now
markymark
(Mark Baumann)
May 16, 2022, 7:25am
13
Thanks @NOOBintown for helping at this post here. I think there are multiple possibilities why it does not work.