Zigbee Binding 2.4 and Stick with Firmware CC2531ZNP-Prod.hex (19.06.2019) von Koenkk

Hi Guys,

i have read all the threads but can not till now activate my CC2531 Stick.
I got it already flashed with Firmware CC2531ZNP-Prod.hex (19.06.2019) von Koenkk.
I added it manualy (i have not added user openhap to tty and dialup, because i already had active port to choose http://prntscr.com/p9y0zh and http://prntscr.com/p9y15r) to my OH2,4 on Raspberry 3.
But till now i get status Unknown.

2019-09-23 19:15:40.207 [hingStatusInfoChangedEvent] - 'zigbee:coordinator_cc2531:3ed95377' changed from UNINITIALIZED to INITIALIZING

2019-09-23 19:15:40.353 [me.event.ThingUpdatedEvent] - Thing 'zigbee:coordinator_cc2531:3ed95377' has been updated.

2019-09-23 19:15:41.037 [me.event.ThingUpdatedEvent] - Thing 'zigbee:coordinator_cc2531:3ed95377' has been updated.

2019-09-23 19:15:41.388 [me.event.ThingUpdatedEvent] - Thing 'zigbee:coordinator_cc2531:3ed95377' has been updated.

2019-09-23 19:15:41.501 [me.event.ThingUpdatedEvent] - Thing 'zigbee:coordinator_cc2531:3ed95377' has been updated.

2019-09-23 19:15:41.616 [hingStatusInfoChangedEvent] - 'zigbee:coordinator_cc2531:3ed95377' changed from INITIALIZING to UNKNOWN

2019-09-23 19:15:47.829 [WARN ] [.cc2531.network.ZigBeeNetworkManager] - Dongle reset failed. Assuming bootloader is running and sending magic byte 0xef.

2019-09-23 19:15:52.832 [WARN ] [.cc2531.network.ZigBeeNetworkManager] - Attempt to get out from bootloader failed.

Please help me to do activate it!
Thanks a lot!

I would first suggest to generate a debug level log so we can see what is happening. It looks from the warning that the device is not communicating.

I’m not really sure what the firmware is that you are using so I’m not 100% sure it is compatible with the ZigBee binding.

1 Like

Please tell me witch debug level should i set and how?

Also to add, it has automatically got all this values in setup http://prntscr.com/p9yaih
So i thning it communicates

The required debug level is DEBUG.

Please read the documentation for the binding. There is a section called something like “what to do when things don’t go as planned”.

I have made it with commands (maybe someone also need them)

log:set debug org.openhab.binding.zigbee
log:set debug com.zsmartsystems.zigbee
log:set info com.zsmartsystems.zigbee.dongle.ember.internal.ash

not i get following erros. What would you say?

2019-09-23 20:39:28.348 [hingStatusInfoChangedEvent] - 'zigbee:coordinator_cc2531:3ed95377' changed from UNKNOWN to UNINITIALIZED

2019-09-23 20:39:28.394 [DEBUG] [nal.ZigBeeNetworkStateSerializerImpl] - Saving ZigBee network state: Start.

2019-09-23 20:39:28.402 [DEBUG] [nal.ZigBeeNetworkStateSerializerImpl] - Saving ZigBee network state: Done.

2019-09-23 20:39:28.409 [ERROR] [nal.common.AbstractInvocationHandler] - An error occurred while calling method 'ThingHandler.dispose()' on 'org.openhab.binding.zigbee.cc2531.handler.CC2531Handler@1e7e847': null

	at com.zsmartsystems.zigbee.app.discovery.ZigBeeDiscoveryExtension.extensionShutdown(ZigBeeDiscoveryExtension.java:96) ~[?:?]

	at com.zsmartsystems.zigbee.ZigBeeNetworkManager.shutdown(ZigBeeNetworkManager.java:529) ~[?:?]

	at org.openhab.binding.zigbee.handler.ZigBeeCoordinatorHandler.dispose(ZigBeeCoordinatorHandler.java:303) ~[?:?]

2019-09-23 20:39:28.488 [ERROR] [core.thing.internal.ThingManagerImpl] - Exception occurred while disposing handler of thing 'zigbee:coordinator_cc2531:3ed95377': null

	at com.zsmartsystems.zigbee.app.discovery.ZigBeeDiscoveryExtension.extensionShutdown(ZigBeeDiscoveryExtension.java:96) ~[?:?]

	at com.zsmartsystems.zigbee.ZigBeeNetworkManager.shutdown(ZigBeeNetworkManager.java:529) ~[?:?]

	at org.openhab.binding.zigbee.handler.ZigBeeCoordinatorHandler.dispose(ZigBeeCoordinatorHandler.java:303) ~[?:?]

2019-09-23 20:39:28.512 [DEBUG] [org.openhab.binding.zigbee.cc2531   ] - ServiceEvent UNREGISTERING - {org.openhab.binding.zigbee.handler.ZigBeeCoordinatorHandler}={service.id=433, service.bundleid=266, service.scope=singleton} - org.openhab.binding.zigbee.cc2531

2019-09-23 20:39:28.542 [hingStatusInfoChangedEvent] - 'zigbee:coordinator_cc2531:3ed95377' changed from UNINITIALIZED to UNINITIALIZED (DISABLED)

2019-09-23 20:39:32.356 [DEBUG] [org.openhab.binding.zigbee.cc2531   ] - ServiceEvent REGISTERED - {org.openhab.binding.zigbee.handler.ZigBeeCoordinatorHandler}={service.id=621, service.bundleid=266, service.scope=singleton} - org.openhab.binding.zigbee.cc2531

2019-09-23 20:39:32.395 [hingStatusInfoChangedEvent] - 'zigbee:coordinator_cc2531:3ed95377' changed from UNINITIALIZED (DISABLED) to INITIALIZING

2019-09-23 20:39:32.396 [DEBUG] [.zigbee.cc2531.handler.CC2531Handler] - Initializing ZigBee CC2531 serial bridge handler.

2019-09-23 20:39:32.402 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Initializing ZigBee network [zigbee:coordinator_cc2531:3ed95377].

2019-09-23 20:39:32.406 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Channel 11

2019-09-23 20:39:32.410 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - PANID 37596

2019-09-23 20:39:32.414 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - EPANID F40AC7D81E80EA2E

2019-09-23 20:39:32.418 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Network Key EB8BA4A0430A79EBF4BE725A2A4271D5

2019-09-23 20:39:32.422 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Link Key 5A6967426565416C6C69616E63653039

2019-09-23 20:39:32.426 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Config: zigbee_initialise found, initializeNetwork=false

2019-09-23 20:39:32.430 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Network Key String EB8BA4A0430A79EBF4BE725A2A4271D5

2019-09-23 20:39:32.434 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Network key final array EB8BA4A0430A79EBF4BE725A2A4271D5

2019-09-23 20:39:32.438 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Link Key String 5A6967426565416C6C69616E63653039

2019-09-23 20:39:32.443 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Link key final array 5A6967426565416C6C69616E63653039

2019-09-23 20:39:32.448 [DEBUG] [.zigbee.cc2531.handler.CC2531Handler] - ZigBee CC2531 Coordinator opening Port:'/dev/ttyAMA0' PAN:92dc, EPAN:F40AC7D81E80EA2E, Channel:11

2019-09-23 20:39:32.453 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Scheduling ZigBee start

2019-09-23 20:39:32.455 [hingStatusInfoChangedEvent] - 'zigbee:coordinator_cc2531:3ed95377' changed from INITIALIZING to UNKNOWN

2019-09-23 20:39:33.458 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - ZigBee network starting

2019-09-23 20:39:33.769 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Initialising ZigBee coordinator

2019-09-23 20:39:33.777 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - Adding supported cluster 1280

2019-09-23 20:39:33.786 [DEBUG] [com.zsmartsystems.zigbee.ZigBeeNode ] - ClusterMatcher starting

2019-09-23 20:39:33.794 [DEBUG] [com.zsmartsystems.zigbee.ZigBeeNode ] - ClusterMatcher adding cluster IAS_ZONE

2019-09-23 20:39:33.810 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - Adding supported cluster 25

2019-09-23 20:39:33.817 [DEBUG] [com.zsmartsystems.zigbee.ZigBeeNode ] - ClusterMatcher adding cluster OTA_UPGRADE

2019-09-23 20:39:33.831 [DEBUG] [nal.ZigBeeNetworkStateSerializerImpl] - Loading ZigBee network state: Start.

2019-09-23 20:39:33.845 [DEBUG] [nal.ZigBeeNetworkStateSerializerImpl] - Loading ZigBee network state: Done.

2019-09-23 20:39:33.849 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - Network state is updated to UNINITIALISED

2019-09-23 20:39:33.849 [DEBUG] [e.dongle.cc2531.ZigBeeDongleTiCc2531] - CC2531 transport initialize

2019-09-23 20:39:33.854 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - null: networkStateUpdated called with state=UNINITIALISED

2019-09-23 20:39:33.855 [DEBUG] [ding.zigbee.handler.ZigBeeSerialPort] - Connecting to serial port [/dev/ttyAMA0] at 38400 baud, flow control FLOWCONTROL_OUT_RTSCTS.

2019-09-23 20:39:33.866 [DEBUG] [ding.zigbee.handler.ZigBeeSerialPort] - Serial port [/dev/ttyAMA0] is initialized.

2019-09-23 20:39:38.877 [WARN ] [.cc2531.network.ZigBeeNetworkManager] - Dongle reset failed. Assuming bootloader is running and sending magic byte 0xef.

2019-09-23 20:39:43.886 [WARN ] [.cc2531.network.ZigBeeNetworkManager] - Attempt to get out from bootloader failed.

2019-09-23 20:39:43.978 [DEBUG] [ding.zigbee.handler.ZigBeeSerialPort] - Serial port '/dev/ttyAMA0' closed.

I think this is what is stated in the docs? We should try to refer to the documentation as this should be the reference.

This again indicates that there is no response from the dongle.

Reference to DEBUG
https://www.openhab.org/addons/bindings/zigbee/#when-things-don-t-appear-to-be-working

So what does it mean? I can not let it run or some steps can be done to try?

I don’t know - there is no response. It could be that the firmware isn’t working, it could be a hardware issue, it could be a problem with the USB or a problem with the serial driver, or the wrong port is selected?

1 Like

Thnaks Chris,
i have checked
the port - ok
driver - ok

Firmware must be according to seller Firmware CC2531ZNP-Prod.hex (19.06.2019) von Koenkk.
Please tell if you know how to check if firmwarу and hardware are ok?

Thanks a lot!

I’m not particularly familiar with the TI firmware so can’t really provide a lot of help here. I definitely know nothing about this version as it is a custom firmware - not provided by TI. I would have expected it to work at least enough to get through the initialisation, but I can’t be sure - sorry.

Thanks

i looked for DMESG and foud out this

[    0.063093] usbcore: registered new interface driver usbfs
[    0.063163] usbcore: registered new interface driver hub
[    0.063263] usbcore: registered new device driver usb
[    0.221323] usbcore: registered new interface driver lan78xx
[    0.222734] usbcore: registered new interface driver smsc95xx
[    0.253131] dwc_otg 3f980000.usb: base=0xf0980000
[    0.678965] dwc_otg 3f980000.usb: DWC OTG Controller
[    0.680300] dwc_otg 3f980000.usb: new USB bus registered, assigned bus number 1
[    0.681693] dwc_otg 3f980000.usb: irq 62, io mem 0x00000000
[    0.685843] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    0.687186] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    0.688519] usb usb1: Product: DWC OTG Controller
[    0.689826] usb usb1: Manufacturer: Linux 4.14.79-v7+ dwc_otg_hcd
[    0.691145] usb usb1: SerialNumber: 3f980000.usb
[    0.693048] hub 1-0:1.0: USB hub found
[    0.696282] usbcore: registered new interface driver usb-storage
[    0.725093] usbcore: registered new interface driver usbhid
[    0.726426] usbhid: USB HID core driver
[    1.131467] usb 1-1: new high-speed USB device number 2 using dwc_otg
[    1.371765] usb 1-1: New USB device found, idVendor=0424, idProduct=2514
[    1.373353] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    1.375523] hub 1-1:1.0: USB hub found
[    1.691478] usb 1-1.1: new high-speed USB device number 3 using dwc_otg
[    1.831771] usb 1-1.1: New USB device found, idVendor=0424, idProduct=2514
[    1.833399] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    1.835575] hub 1-1.1:1.0: USB hub found
[    2.151499] usb 1-1.1.2: new full-speed USB device number 4 using dwc_otg
[    2.296066] usb 1-1.1.2: New USB device found, idVendor=0451, idProduct=16ae
[    2.297652] usb 1-1.1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    2.300621] usb 1-1.1.2: Product: CC2531 USB Dongle
[    2.302187] usb 1-1.1.2: Manufacturer: Texas Instruments
[    2.411496] usb 1-1.1.3: new full-speed USB device number 5 using dwc_otg
[    2.557441] usb 1-1.1.3: New USB device found, idVendor=2341, idProduct=0010
[    2.559101] usb 1-1.1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=220
[    2.562370] usb 1-1.1.3: Product: Arduino Mega 2560
[    2.564015] usb 1-1.1.3: Manufacturer: Arduino (www.arduino.cc)
[    2.565628] usb 1-1.1.3: SerialNumber: 7563830323735140B221
[    2.871498] usb 1-1.1.1: new high-speed USB device number 6 using dwc_otg
[    3.001952] usb 1-1.1.1: New USB device found, idVendor=0424, idProduct=7800
[    3.001968] usb 1-1.1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    3.414374] cdc_acm 1-1.1.3:1.0: ttyACM0: USB ACM device
[    3.415739] usbcore: registered new interface driver cdc_acm
[    3.415752] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[    4.126205] usbcore: registered new interface driver brcmfmac

It means that my Arduino is recognised as ACM device and got the Port and CC2531 not or i understand it wrong?

And here i get only Arduiono

[23:38:08] openhabian@openHABianPi:~$ ls -l /dev/serial/by-id
total 0
lrwxrwxrwx 1 root root 13 Sep 23 23:18 usb-Arduino__www.arduino.cc__Arduino_Mega_2560_7563830323735140B221-if00 -> ../../ttyACM0

Wait, I’m reading this and I’m not sure if I have something mixed up.

I have used this firmware from Koenkk, and is for zigbee2mqtt which additionally has a node.js app that is installed on the rpi3. It is translating zigbee msgs from the devices and sends them to mqtt broker.
The zigbee binding is for openHAB to talk to the devices via the zigbee stick and not via mqtt protocol

What do you want to achieve at the end?

Cheers
Miki

It is using the same fundamental firmware - it is however customised. It should communicate with the binding and this isn’t what is happening. Zigbee2Mqtt uses a node.js app - the binding uses Java - it shouldn’t really matter.

The issue seems to be at the interface level - ie the dongle is not communicating. The point about the firmware may be relevant (I stated this earlier) but in general the firmware should at least work enough to connect to the binding, and this is not happening.

Aha, right, that’s why I mentioned if I’m missing something. Apparently I was.

Tnx for the clarification, I had no idea I could mix the two, since I was planing on using this(zigbee2mqtt) to send mqtt msgs and then use the mqtt binding to read/control.

@thisisIO maybe try the stick on another rpi3(if you have a spare one) ?

1 Like

You may of course still be right that the firmware is not compatible (I think I also raised this previously), but I think it should get a little further than it is :wink:

I have ordered one more the same stick with same software the from another seller (tis time not chinese) that certifed me that it works with OH Biding and MQTT at once.
Lets check some days later)

I have just got new stick with the same mqtt firmware from koenkk! Works good with Zigbee Binding! It means that first stick have a problem.

1 Like