Unable to get EM358 USB Stick working with Zigbee binding

kaage · October 13, 2018, 9:34am

Hi, I’m newbie in opneHAB. I managed to get openHAB installed on Ubuntu. Now I have ZM3588S-USB-LR (https://www.cortet.com/iot-hardware/cortet-usb-sticks/em358-usb-stick). I have installed Zigbee binding via PaperUI. I have added “Ember EM35x Coordinator” under things. State of the thing is “unknown”. I assume it needs to be Online or something like that. What I’m doing wrong?

2018-10-13 12:30:41.294 [DEBUG] [bee.discovery.ZigBeeDiscoveryService] - Creating ZigBee discovery service for zigbee:coordinator_ember:e73b52f7

2018-10-13 12:30:41.297 [DEBUG] [bee.discovery.ZigBeeDiscoveryService] - Activating ZigBee discovery service for zigbee:coordinator_ember:e73b52f7

2018-10-13 12:30:41.300 [DEBUG] [org.openhab.binding.zigbee.ember    ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.discovery.DiscoveryService}={service.id=329, service.bundleid=209, service.scope=singleton} - org.openhab.binding.zigbee.ember

2018-10-13 12:30:41.304 [DEBUG] [org.openhab.binding.zigbee.ember    ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.core.thing.binding.firmware.FirmwareUpdateHandler}={service.id=330, service.bundleid=209, service.scope=singleton} - org.openhab.binding.zigbee.ember

2018-10-13 12:30:41.321 [DEBUG] [ng.zigbee.ember.handler.EmberHandler] - Initializing ZigBee Ember serial bridge handler.

2018-10-13 12:30:41.321 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Initializing ZigBee network [zigbee:coordinator_ember:e73b52f7].

2018-10-13 12:30:41.322 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Channel -1

==> /var/log/openhab2/events.log <==

2018-10-13 12:30:41.321 [hingStatusInfoChangedEvent] - 'zigbee:coordinator_ember:e73b52f7' changed from UNINITIALIZED to INITIALIZING

==> /var/log/openhab2/openhab.log <==

2018-10-13 12:30:41.323 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - PANID 0

2018-10-13 12:30:41.323 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - EPANID 0000000000000000

2018-10-13 12:30:41.324 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Key 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

2018-10-13 12:30:41.325 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Initialising network

2018-10-13 12:30:41.328 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Created random ZigBee PAN ID [711C].

==> /var/log/openhab2/events.log <==

2018-10-13 12:30:41.344 [me.event.ThingUpdatedEvent] - Thing 'zigbee:coordinator_ember:e73b52f7' has been updated.

==> /var/log/openhab2/openhab.log <==

2018-10-13 12:30:41.348 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Created random ZigBee extended PAN ID [645F8459C3E20E7E].

==> /var/log/openhab2/events.log <==

2018-10-13 12:30:41.351 [me.event.ThingUpdatedEvent] - Thing 'zigbee:coordinator_ember:e73b52f7' has been updated.

2018-10-13 12:30:41.361 [me.event.ThingUpdatedEvent] - Thing 'zigbee:coordinator_ember:e73b52f7' has been updated.

==> /var/log/openhab2/openhab.log <==

2018-10-13 12:30:41.363 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Key String 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

2018-10-13 12:30:41.364 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Key initialised 1FFEAA52B2D6898F74FEAE45E2A00C1A

2018-10-13 12:30:41.365 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Key final array 1FFEAA52B2D6898F74FEAE45E2A00C1A

2018-10-13 12:30:41.366 [DEBUG] [ng.zigbee.ember.handler.EmberHandler] - ZigBee Ember Coordinator opening Port:'/dev/ttyUSB2' PAN:711c, EPAN:645F8459C3E20E7E, Channel:-1

2018-10-13 12:30:41.367 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Scheduling ZigBee start

==> /var/log/openhab2/events.log <==

2018-10-13 12:30:41.375 [hingStatusInfoChangedEvent] - 'zigbee:coordinator_ember:e73b52f7' changed from INITIALIZING to UNKNOWN

2018-10-13 12:30:41.382 [nt.FirmwareStatusInfoEvent] - Firmware status of thing zigbee:coordinator_ember:e73b52f7 changed to UNKNOWN

chris · October 13, 2018, 9:41am

What version are you using? If it’s not the latest, please update to the latest snapshot.

Otherwise, please enable debug logging as per the binding docs (right at the bottom) and I’ll see if I can spot anything.

kaage · October 13, 2018, 10:23am

I’m using openHAB 2.3.0.

I enabled logging in karaf using commands:
log:set debug org.openhab.binding.zigbee
log:set debug com.zsmartsystems.zigbee

But not getting too much to log file:

2018-10-13 13:20:54.768 [DEBUG] [ng.zigbee.ember.handler.EmberHandler] - Initializing ZigBee Ember serial bridge handler.
2018-10-13 13:20:54.768 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Initializing ZigBee network [zigbee:coordinator_ember:e73b52f7].
2018-10-13 13:20:54.768 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Channel -1
2018-10-13 13:20:54.769 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - PANID 28956
2018-10-13 13:20:54.769 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - EPANID 645F8459C3E20E7E
2018-10-13 13:20:54.770 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Key 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
2018-10-13 13:20:54.770 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Key String 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
2018-10-13 13:20:54.771 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Key initialised 8B05DAF9F3ABD8E4670F94CC29431C55
2018-10-13 13:20:54.775 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Key final array 8B05DAF9F3ABD8E4670F94CC29431C55
2018-10-13 13:20:54.779 [DEBUG] [ng.zigbee.ember.handler.EmberHandler] - ZigBee Ember Coordinator opening Port:'/dev/ttyUSB1' PAN:711c, EPAN:645F8459C3E20E7E, Channel:-1
2018-10-13 13:20:54.783 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Scheduling ZigBee start
2018-10-13 13:20:55.785 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - ZigBee network starting
2018-10-13 13:20:55.787 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Initialising ZigBee coordinator
2018-10-13 13:20:55.788 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Key initialise 8B05DAF9F3ABD8E4670F94CC29431C55
2018-10-13 13:20:55.789 [DEBUG] [zigbee.dongle.ember.ZigBeeDongleEzsp] - EZSP dongle initialize with protocol ASH2.
2018-10-13 13:20:55.790 [DEBUG] [ding.zigbee.handler.ZigBeeSerialPort] - Connecting to serial port [/dev/ttyUSB1] at 57600 baud, flow control FLOWCONTROL_OUT_XONOFF.
2018-10-13 13:20:55.801 [DEBUG] [ding.zigbee.handler.ZigBeeSerialPort] - Serial port [/dev/ttyUSB1] is initialized.
2018-10-13 13:20:55.802 [DEBUG] [e.ember.internal.ash.AshFrameHandler] - --> TX ASH frame: AshFrameRst []
2018-10-13 13:20:55.804 [DEBUG] [e.ember.internal.ash.AshFrameHandler] - ASH: TX EZSP queue: 1
2018-10-13 13:20:55.802 [DEBUG] [e.ember.internal.ash.AshFrameHandler] - AshFrameHandler thread started

chris · October 13, 2018, 10:46am

Please change to using 2.4 - 2.3 is now quite old and there have been a lot of changes.

From the log, it looks like the binding sends the reset command and gets no response. The new version will retry this.

What firmware are you using in the dongle?

kaage · October 13, 2018, 10:57am

I’m upgrading to 2.4 snapshot. I don’t know what firmware is included in dongle. Any idea how to verify that? I’m just wondering if firmware needs to be changed manually: https://www.cortet.com/docs/default-source/cortet-documents-and-files/zm357s_usb_sticks_quick_start_guide.pdf

chris · October 13, 2018, 11:02am

Hmmm - there is no firmware included with these dongles. You need to program it yourself which requires the developers kit.

I guess this is the problem then .

I could program this for you if needed - if you post it to me (in the UK) and send me a donation to at least cover the return postage.

kaage · October 13, 2018, 11:13am

Yeah, that must be the problem. By the way, do you know if any of the other Dongles in the binding documentation is shipped with correct firmware?

So do you need/have special hardware for firmware programming?

chris · October 13, 2018, 11:15am

Yes - you need the developer kit - or at least the ISA3 programmer. It’s possible to buy the programmer by itself (I think about 100 Euro, but I’m not 100% sure) but you then can’t access the firmware as you need to register the devkit with Silabs to get access to the firmware (although I could potentially provide this if you decided to purchase the programmer).

kaage · October 13, 2018, 11:20am

Well, I have this dongle already so would be best if you program it with correct firmware. I takes about 3 euros to send it to you and something + donation to send it back to me.

chris · October 13, 2018, 1:22pm

Sure - that should be fine. PM me and I’ll send you my address etc.

kaage · October 13, 2018, 3:25pm

Unfortunately I can’t find how to sen PM. Could it be disable for me as a new member?

chris · October 13, 2018, 3:53pm

All you need to do is to click on my name, and click the Message button…

I will PM you my details.

alexbibi · October 24, 2018, 12:59pm

Hello everyone,

I have the same problem here but I already bought an ISA3 programmer. The problem is I cant register the kit and dont have access to the SDK. Does anyone know where I could get the zigbee firmware?

thank you so much

chris · October 24, 2018, 2:02pm

Unfortunately you need to have a devkit otherwise you can’t get access to the SDK which is what contains the firmware etc.

alexbibi · October 25, 2018, 2:32pm

Is there any way I can get the firmware then?

chris · October 25, 2018, 2:41pm

Yes, the firmware becomes available once you register your developer kit with Silabs support. This will enable the download through Simplicity Studio.