O.k. thanks for the explanation. I’ve been digging for some more information about these plugs: But all documentation/tutorials I’ve found are referring to touchlink pairing - even when connecting to a HUE bridge.
More than this, there seems to be no way to do a real factory reset of it - only option is an unpair from a remote using touchlink as well 
Anywway - seems I have to buy something new for it 
This is the same for Hue (AFAIK anyway). I have a touchlink controller just to reset my bulbs 
.
Here you go! This time didn’t give the full trace, but the error still shows.
2017-06-28 18:05:47.866 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - RX CMD: ManagementRoutingResponse [0/0 -> 0/0, cluster=8032, TID=NULL, status=SUCCESS, routingTableEntries=1, startIndex=0, routingTableListCount=1, routingTableList=[RoutingTable [destinationAddress=22249, status=DISCOVERY_UNDERWAY, memoryConstrained=false, manyToOne=false, routeRecordRequired=false, nextHopAddress=65534]]]
2017-06-28 18:05:47.875 [DEBUG] [31.network.impl.CommandInterfaceImpl] - <- AF_DATA_SRSP (FE 01 64 01 00 64)
2017-06-28 18:05:57.353 [DEBUG] [31.network.impl.CommandInterfaceImpl] - <-- AF_INCOMING_MSG (FE 1A 44 81 00 00 00 05 80 FA 01 01 00 6E 00 FD EE 04 00 00 06 19 4C 00 31 00 00 80 FA 1D DC)
2017-06-28 18:05:57.354 [DEBUG] [31.network.impl.CommandInterfaceImpl] - Received Async Cmd: Packet: subsystem=null, length=26, apiId=44 81, data=FE 1A 44 81 00 00 00 05 80 FA 01 01 00 6E 00 FD EE 04 00 00 06 19 4C 00 31 00 00 80 FA 1D DC, checksum=DC, error=false
2017-06-28 18:05:57.354 [ERROR] [kManagerImpl$AFMessageListenerFilter] - Error AF message listener notify.
java.lang.ArrayIndexOutOfBoundsException
2017-06-28 18:05:57.828 [DEBUG] [ee.internal.ZigBeeNetworkMeshMonitor] - 22249: ManagementLqiRequest returned null
2017-06-28 18:05:57.828 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - TX CMD: IeeeAddressRequest [0/0 -> 22249/0, cluster=0001, TID=FF, nwkAddrOfInterest=22249, requestType=1, startIndex=0]
2017-06-28 18:05:57.828 [DEBUG] [31.network.impl.CommandInterfaceImpl] - -> AF_DATA_REQUEST (Packet: subsystem=null, length=15, apiId=24 01, data=FE 0F 24 01 E9 56 00 00 01 00 FF 30 1F 05 00 E9 56 01 00 FF, checksum=FF, error=false)
2017-06-28 18:05:57.828 [DEBUG] [ee.internal.ZigBeeNetworkMeshMonitor] - 64128: ManagementLqiRequest returned null
2017-06-28 18:05:57.828 [DEBUG] [ee.internal.ZigBeeNetworkMeshMonitor] - 64128: Not updating routing table: type is END_DEVICE
2017-06-28 18:05:57.829 [DEBUG] [ee.internal.ZigBeeNetworkMeshMonitor] - 64128: Ending mesh update
2017-06-28 18:05:57.829 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - D052A8001C140003: Node updated - IEEE=D052A8001C140003, NWK=FA80, Type=END_DEVICE
2017-06-28 18:05:57.844 [DEBUG] [31.network.impl.CommandInterfaceImpl] - <- AF_DATA_SRSP (FE 01 64 01 00 64)
2017-06-28 18:05:58.335 [DEBUG] [31.network.impl.CommandInterfaceImpl] - <-- AF_INCOMING_MSG (FE 1A 44 81 00 00 00 05 80 FA 01 01 00 69 00 F6 FA 04 00 00 06 19 4D 00 30 00 00 80 FA 1D C4)
2017-06-28 18:05:58.335 [DEBUG] [31.network.impl.CommandInterfaceImpl] - Received Async Cmd: Packet: subsystem=null, length=26, apiId=44 81, data=FE 1A 44 81 00 00 00 05 80 FA 01 01 00 69 00 F6 FA 04 00 00 06 19 4D 00 30 00 00 80 FA 1D C4, checksum=C4, error=false
2017-06-28 18:05:58.335 [ERROR] [kManagerImpl$AFMessageListenerFilter] - Error AF message listener notify.
java.lang.ArrayIndexOutOfBoundsExceptionThanks - I’ll take a look at this tonight.
As best as I can tell at the moment, this frame is corrupt.
06 19 4C 00 31 00 00
6 means 6 bytes,
19 4C 00 is the ZCL header
31 00 is an attribute,
00 remaining is too short - it should also be 2 bytes long.
So, either the 6 bytes length is wrong, or something else…
I’ll park this for now - maybe I’m missing something and I’ll take a look at this when I get a chance with the sensor I have here.
OH2.1, zigbee binding 2.2.0.201706290942, HUSBZB-1 (Silicon Labs EM3581, EmberZNet Pro 5.4)
The Coordinator is stuck at Initializing:
2017-06-30 07:30:55.602 [zigbee ] - BundleEvent [unknown:512] - org.openhab.binding.zigbee
2017-06-30 07:30:55.617 [zigbee ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.core.thing.binding.ThingHandlerFactory}={component.name=org.openhab.binding.zigbee.internal.ZigBeeHandlerFactory, component.id=8, service.id=115, service.bundleid=220, service.scope=bundle} - org.openhab.binding.zigbee
2017-06-30 07:30:55.624 [zigbee ] - BundleEvent STARTING - org.openhab.binding.zigbee
2017-06-30 07:30:55.625 [zigbee ] - BundleEvent STARTED - org.openhab.binding.zigbee
2017-06-30 07:30:58.218 [zigbee ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.core.ConfigOptionProvider, org.eclipse.smarthome.config.core.ConfigDescriptionProvider}={component.name=org.openhab.binding.zigbee.internal.ZigBeeConfigProvider, component.id=9, service.id=182, service.bundleid=220, service.scope=bundle} - org.openhab.binding.zigbee
2017-06-30 07:30:58.242 [zigbee ] - ServiceEvent REGISTERED - {org.openhab.binding.zigbee.internal.ZigBeeConfigProvider}={component.name=org.openhab.binding.zigbee.ConfigDescription, component.id=10, service.id=183, service.bundleid=220, service.scope=bundle} - org.openhab.binding.zigbee
2017-06-30 08:50:56.515 [ZigBeeHandlerFactory ] - Creating coordinator handler for org.eclipse.smarthome.core.thing.internal.BridgeImpl@b5982076
2017-06-30 08:50:56.566 [BeeCoordinatorEmberHandler] - Initializing ZigBee Ember serial bridge handler.
2017-06-30 08:50:56.566 [ZigBeeCoordinatorHandler ] - Initializing ZigBee network [zigbee:coordinator_ember:f8d7abbc].
2017-06-30 08:50:56.566 [ZigBeeCoordinatorHandler ] - Channel -1
2017-06-30 08:50:56.567 [ZigBeeCoordinatorHandler ] - PANID 0
2017-06-30 08:50:56.567 [ZigBeeCoordinatorHandler ] - EPANID 0000000000000000
2017-06-30 08:50:56.568 [ZigBeeCoordinatorHandler ] - Key 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
2017-06-30 08:50:56.569 [ZigBeeCoordinatorHandler ] - Initialising network
2017-06-30 08:50:56.569 [ZigBeeCoordinatorHandler ] - Created random ZigBee PAN ID [8E9A].
2017-06-30 08:51:01.574 [ZigBeeCoordinatorHandler ] - Created random ZigBee extended PAN ID [7DAFAD7D5A1F3B92].
2017-06-30 08:51:01.653 [ZigBeeCoordinatorHandler ] - Key String 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
2017-06-30 08:51:01.655 [ZigBeeCoordinatorHandler ] - Key array [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0]
2017-06-30 08:51:01.657 [ZigBeeCoordinatorHandler ] - Creating random ZigBee network key.
2017-06-30 08:51:01.739 [ZigBeeCoordinatorHandler ] - Created random ZigBee network key.
2017-06-30 08:51:01.744 [ZigBeeCoordinatorHandler ] - Key initialised String 36 1C C4 8A 1E 1E 27 7B EB FC 0A D9 96 B2 B6 AA
2017-06-30 08:51:01.745 [ZigBeeCoordinatorHandler ] - Key initialised array [54, 28, 196, 138, 30, 30, 39, 123, 235, 252, 10, 217, 150, 178, 182, 170]
2017-06-30 08:51:01.745 [ZigBeeCoordinatorHandler ] - Key final array [54, 28, 196, 138, 30, 30, 39, 123, 235, 252, 10, 217, 150, 178, 182, 170]
2017-06-30 08:51:01.764 [BeeCoordinatorEmberHandler] - ZigBee Coordinator Ember opening Port:'/dev/ttyUSB1' PAN:8e9a, EPAN:7DAFAD7D5A1F3B92, Channel:-1
2017-06-30 08:51:01.767 [ZigBeeCoordinatorHandler ] - Scheduling ZigBee start
2017-06-30 08:51:02.768 [ZigBeeCoordinatorHandler ] - ZigBee network starting
2017-06-30 08:51:02.769 [ZigBeeCoordinatorHandler ] - Initialising ZigBee coordinator
2017-06-30 08:51:02.770 [ZigBeeDiscoveryService ] - Creating ZigBee discovery service for zigbee:coordinator_ember:f8d7abbc
2017-06-30 08:51:02.771 [ZigBeeDiscoveryService ] - Activating ZigBee discovery service for zigbee:coordinator_ember:f8d7abbc
2017-06-30 08:51:02.774 [zigbee ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.discovery.DiscoveryService}={service.id=447, service.bundleid=220, service.scope=singleton} - org.openhab.binding.zigbee
2017-06-30 08:51:02.802 [ZigBeeCoordinatorHandler ] - Key initialise [54, 28, 196, 138, 30, 30, 39, 123, 235, 252, 10, 217, 150, 178, 182, 170]
2017-06-30 08:51:02.803 [ZigBeeDongleEzsp ] - EZSP dongle initialize.
2017-06-30 08:51:02.805 [BeeCoordinatorEmberHandler] - Connecting to serial port [/dev/ttyUSB1]
2017-06-30 08:51:02.845 [BeeCoordinatorEmberHandler] - Serial port [/dev/ttyUSB1] is initialized.
2017-06-30 08:51:02.871 [AshFrameHandler ] - Trying to send when not connected.
And OH will crash hard when the binding is stopped (let me know if you’re interested in the core dump):
get_java_var: invalid file descriptor
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007ff7eb8f47d5, pid=2667, tid=0x00007ff7e530a700
#
# JRE version: OpenJDK Runtime Environment (8.0_131-b12) (build 1.8.0_131-b12)
# Java VM: OpenJDK 64-Bit Server VM (25.131-b12 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C [libNRJavaSerial.so+0x77d5] read_byte_array+0x55
#
# Core dump written. Default location: /opt/openhab2/userdata/core or core.2667
#
# An error report file with more information is saved as:
# /opt/openhab2/userdata/hs_err_pid2667.log
Compiled method (c2) 1696268 14685 s! 4 gnu.io.RXTXPort$SerialInputStream::read (98 bytes)
total in heap [0x00007ff83b1f2c10,0x00007ff83b1f3b38] = 3880
relocation [0x00007ff83b1f2d38,0x00007ff83b1f2dd8] = 160
main code [0x00007ff83b1f2de0,0x00007ff83b1f33c0] = 1504
stub code [0x00007ff83b1f33c0,0x00007ff83b1f3420] = 96
oops [0x00007ff83b1f3420,0x00007ff83b1f3428] = 8
metadata [0x00007ff83b1f3428,0x00007ff83b1f3498] = 112
scopes data [0x00007ff83b1f3498,0x00007ff83b1f38b0] = 1048
scopes pcs [0x00007ff83b1f38b0,0x00007ff83b1f3a60] = 432
dependencies [0x00007ff83b1f3a60,0x00007ff83b1f3a70] = 16
handler table [0x00007ff83b1f3a70,0x00007ff83b1f3ae8] = 120
nul chk table [0x00007ff83b1f3ae8,0x00007ff83b1f3b38] = 80
On a positive note, I transferred primary controller from a zstick to the zwave side (using OZW and Zensys), then transferred SIS/SUC, and everything seems good after changing the associations to the new controller!
Please enable debug logging on com.zsmartsystems.zigbee so we can see what’s happening.
Ummm… This is ZWave right? Im not sure I understand the link with the Zigbee crash 
I have the following loggers and appender in org.ops4j.pax.logging.cfg. I must be missing something to provide more logging.
log4j.logger.org.openhab.binding.zigbee = DEBUG, zigbee
log4j.logger.com.zsmartsystems.zigbee = DEBUG, zigbee
log4j.appender.zigbee=org.apache.log4j.RollingFileAppender
log4j.appender.zigbee.layout=org.apache.log4j.PatternLayout
log4j.appender.zigbee.layout.ConversionPattern=%d{yyyy-MM-dd HH:mm:ss.SSS} [%-26.26c{1}] - %m%n
log4j.appender.zigbee.file=${openhab.logdir}/zigbee/zigbee.log
log4j.appender.zigbee.append=true
log4j.appender.zigbee.maxFileSize=10MB
log4j.appender.zigbee.maxBackupIndex=40
Yes, zwave… on a combo device. Serial communication is functioning to that side of the stick from OH. So it’s half working! 
Ok - not sure why I don’t see anything then. Without more information I don’t think I can do anything 
.
You mean you have a single stick with both zwave and zigbee? What is the device?
Here…
Interesting - I missed the fact that it had ZWave included. This is quite nice 
.
Yes! There’s also a model (HUSBZ-1) with just the zigbee for nearly the same price. IIRC, the zwave is zw500 with v4.05 firmware. So very similar to zstick but newer firmware. And cost me less than a backup zstick! I will likely post a separate thread about it… maybe after zigbee is working on it. IMO, it would be a perfect off the shelf unit. I have a lot of Linear devices and they’ve been very solid for me.
I’ll play with the logging to see what I’m missing.
Hi @chris,
would you have a look at the color channel again? The “brightness” control do not act as expected:
When moving the brightness slider in Paper UI, the saturation of the bulb is set to the value selected by the brightness slider - BUT: the brightness value has been set internally as well and will become effective through some subsequent command (e.g. color, saturation)… hard to explain
Sorry for not reporting earlier. I haven’t noticed before since I was more keen on the white spectrum control and so did just basic testing on the color channel which is working fine when leaving the brightness slider untouched.
Hmmm - ok, I see it here too… I’ll take a look over the weekend.
Cheers
Chris
I have tried everything I can think of and can’t figure out why I’m not getting all of the logging. But I’m also not seeing any more details in other peoples logs, so I’m not sure exactly what is missing from them. I’ve only seen people reporting use of the TI controllers. Does the code have a difference in the logging between the Ember and cc2531? Has anyone else gotten an Ember device working?
I’m looking for the low level commands to the interface. This sort of thing (taken from a log above) -:
2017-06-28 18:05:57.828 [DEBUG] [31.network.impl.CommandInterfaceImpl] - -> AF_DATA_REQUEST (Packet: subsystem=null, length=15, apiId=24 01, data=FE 0F 24 01 E9 56 00 00 01 00 FF 30 1F 05 00 E9 56 01 00 FF, checksum=FF, error=false)
Well, the logging is obviously different, but they are both under the same com.zsmartsystems.zigbee namespace. Enabling this works for me. I do see some basic stuff from the ember driver, but I’d have expected more as I don’t see any low level frames being sent.
Yes - me. It’s being used commercially by a customer, so I think it works ;). Maybe the dongle you have isn’t quite compatible with the NCP code (I did say I wasn’t sure it would be)…
I’am using an CC2531EMK Coordinator which is already programmed to my Zigbee network. (PAN ID, channel and network key is already set) I’ve added the coordinator as a thing and changed all the values exactly as they are programmed on the stick. Except the “extended PAN ID”, which I don’t now. (I tried to find it out using Ubiqua packet analyzer, but my network doesn’t seam to have such an ID)
But the coordinator cannot be initialized with those values. Here are the logs regarding the problem.
2017-07-03 23:03:18.611 [INFO ] [ndler.ZigBeeCoordinatorCC2531Handler] - Serial port [/dev/ttyACM1] is initialized.
2017-07-03 23:03:23.616 [WARN ] [etwork.impl.ZigBeeNetworkManagerImpl] - Dongle reset failed. Assuming bootloader is running and sending magic byte 0x01.
2017-07-03 23:03:28.618 [WARN ] [etwork.impl.ZigBeeNetworkManagerImpl] - Attempt to get out from bootloader failed.
2017-07-03 23:03:28.629 [INFO ] [ndler.ZigBeeCoordinatorCC2531Handler] - Serial port [/dev/ttyACM1] is closed.
Is there a way to configure the binding to accept the already programmed values?
My guess is the issue isn’t related to the EPAN ID - if you don’t reinitialise the network, then it should use the existing settings. I’d suggest to enable more debugging by enabling the com.zsmartsystems.zigbee namespace.
Hi Chris, I’ve enabled the debug log for org.openhab.binding.zigbee and com.zsmartsystems.zigbee. Here is the output. I’ve removed the PAN ID’s an the network key, but everything is set. The EPANID was generated automatically.
2017-07-04 10:07:08.609 [zigbee ] - BundleEvent STOPPING - org.openhab.binding.zigbee
2017-07-04 10:07:08.627 [zigbee ] - ServiceEvent UNREGISTERING - {org.eclipse.smarthome.config.core.ConfigOptionProvider, org.eclipse.smarthome.config.core.ConfigDescriptionProvider}={component.name=org.openhab.binding.zigbee.internal.ZigBeeConfigProvider, component.id=247, service.id=423, service.bundleid=229, service.scope=bundle} - org.openhab.binding.zigbee
2017-07-04 10:07:08.646 [zigbee ] - ServiceEvent UNREGISTERING - {org.openhab.binding.zigbee.internal.ZigBeeConfigProvider}={component.name=org.openhab.binding.zigbee.ConfigDescription, component.id=248, service.id=424, service.bundleid=229, service.scope=bundle} - org.openhab.binding.zigbee
2017-07-04 10:07:08.658 [zigbee ] - ServiceEvent UNREGISTERING - {org.eclipse.smarthome.core.thing.binding.ThingHandlerFactory}={component.name=org.openhab.binding.zigbee.internal.ZigBeeHandlerFactory, component.id=249, service.id=425, service.bundleid=229, service.scope=bundle} - org.openhab.binding.zigbee
2017-07-04 10:07:08.661 [eeCoordinatorCC2531Handler] - Closing ZigBee CC2531 serial port
2017-07-04 10:07:08.701 [zigbee ] - ServiceEvent UNREGISTERING - {org.eclipse.smarthome.config.discovery.DiscoveryService}={service.id=426, service.bundleid=229, service.scope=singleton} - org.openhab.binding.zigbee
2017-07-04 10:07:08.710 [zigbee ] - BundleEvent STOPPED - org.openhab.binding.zigbee
2017-07-04 10:07:10.513 [zigbee ] - BundleEvent STARTING - org.openhab.binding.zigbee
2017-07-04 10:07:10.576 [zigbee ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.core.ConfigOptionProvider, org.eclipse.smarthome.config.core.ConfigDescriptionProvider}={component.name=org.openhab.binding.zigbee.internal.ZigBeeConfigProvider, component.id=250, service.id=427, service.bundleid=229, service.scope=bundle} - org.openhab.binding.zigbee
2017-07-04 10:07:10.594 [zigbee ] - ServiceEvent REGISTERED - {org.openhab.binding.zigbee.internal.ZigBeeConfigProvider}={component.name=org.openhab.binding.zigbee.ConfigDescription, component.id=251, service.id=428, service.bundleid=229, service.scope=bundle} - org.openhab.binding.zigbee
2017-07-04 10:07:10.605 [zigbee ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.core.thing.binding.ThingHandlerFactory}={component.name=org.openhab.binding.zigbee.internal.ZigBeeHandlerFactory, component.id=252, service.id=429, service.bundleid=229, service.scope=bundle} - org.openhab.binding.zigbee
2017-07-04 10:07:10.615 [zigbee ] - BundleEvent STARTED - org.openhab.binding.zigbee
2017-07-04 10:07:10.681 [ZigBeeHandlerFactory ] - Creating coordinator handler for org.eclipse.smarthome.core.thing.internal.BridgeImpl@6a922bbe
2017-07-04 10:07:10.723 [eeCoordinatorCC2531Handler] - Initializing ZigBee ZNP serial bridge handler.
2017-07-04 10:07:10.723 [ZigBeeCoordinatorHandler ] - Initializing ZigBee network [zigbee:coordinator_cc2531:8debd1b3].
2017-07-04 10:07:10.724 [ZigBeeCoordinatorHandler ] - Channel 11.0
2017-07-04 10:07:10.724 [ZigBeeCoordinatorHandler ] - PANID ....
2017-07-04 10:07:10.725 [ZigBeeCoordinatorHandler ] - EPANID C9....
2017-07-04 10:07:10.725 [ZigBeeCoordinatorHandler ] - Key AF 6A ....
2017-07-04 10:07:10.726 [ZigBeeCoordinatorHandler ] - Key String AF 6A ....
2017-07-04 10:07:10.727 [ZigBeeCoordinatorHandler ] - Key array [175, 106, ....]
2017-07-04 10:07:10.728 [ZigBeeCoordinatorHandler ] - Key final array [175, 106, ....]
2017-07-04 10:07:10.729 [eeCoordinatorCC2531Handler] - Channel 11.0
2017-07-04 10:07:10.730 [eeCoordinatorCC2531Handler] - ZigBee Coordinator ZNP opening Port:'/dev/ttyACM1' PAN:...., Channel:11
2017-07-04 10:07:10.731 [ZigBeeCoordinatorHandler ] - Scheduling ZigBee start
2017-07-04 10:07:11.732 [ZigBeeCoordinatorHandler ] - ZigBee network starting
2017-07-04 10:07:11.733 [ZigBeeCoordinatorHandler ] - Initialising ZigBee coordinator
2017-07-04 10:07:11.734 [ZigBeeDiscoveryService ] - Creating ZigBee discovery service for zigbee:coordinator_cc2531:8debd1b3
2017-07-04 10:07:11.735 [ZigBeeDiscoveryService ] - Activating ZigBee discovery service for zigbee:coordinator_cc2531:8debd1b3
2017-07-04 10:07:11.745 [zigbee ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.discovery.DiscoveryService}={service.id=430, service.bundleid=229, service.scope=singleton} - org.openhab.binding.zigbee
2017-07-04 10:07:11.751 [ZigBeeCoordinatorHandler ] - Key initialise [175, 106, ....]
2017-07-04 10:07:11.753 [ZigBeeDongleTiCc2531 ] - CC2531 transport initialize
2017-07-04 10:07:11.763 [eeCoordinatorCC2531Handler] - Opening ZigBee CC2531 serial port
2017-07-04 10:07:11.766 [eeCoordinatorCC2531Handler] - Connecting to serial port [/dev/ttyACM1]
2017-07-04 10:07:11.789 [eeCoordinatorCC2531Handler] - Serial port [/dev/ttyACM1] is initialized.
2017-07-04 10:07:11.797 [CommandInterfaceImpl ] - -> SYS_RESET (Packet: subsystem=null, length=1, apiId=41 00, data=FE 01 41 00 01 41, checksum=41, error=false)
2017-07-04 10:07:16.802 [ZigBeeNetworkManagerImpl ] - Dongle reset failed. Assuming bootloader is running and sending magic byte 0x01.
2017-07-04 10:07:21.804 [ZigBeeNetworkManagerImpl ] - Attempt to get out from bootloader failed.
2017-07-04 10:07:21.805 [eeCoordinatorCC2531Handler] - Closing ZigBee CC2531 serial port
2017-07-04 10:07:23.806 [ZToolPacketParser ] - ZToolPacketParser parserThread exited.
2017-07-04 10:07:23.892 [eeCoordinatorCC2531Handler] - Serial port [/dev/ttyACM1] is closed.
What could cause this problem? I also tried the console app of zsmartsystems on my Mac with the same adapter an there I was able to initialize the coordinator and I was able to see the network packets. Could this maybe be a problem that the device does not work properly on my Rasberry Pi? Maybe a driver problem?
I see the binding is sending the magic byte - I’m not sure that this is correct though so this might be a problem. I would suggest to make sure that you plug in the device, leave it for 1 minute, then start the binding and see if that helps. In theory the stick should be out of the bootloader by then so an incorrect magic byte shouldn’t matter…
If it’s not that, then it might be issues with the serial driver. I’ve seen some problems with the communications to the TI sticks when running in OH versus running with the debug console. The errors I’ve seen are low level COM port issues so I have a theory (rightly or wrongly!) that it might be related to the drivers which are different in the console.