I got it working allright. Had to do some exclude and include a few times, then it started to work, and has been working since the day before yesterday, even the dimmer switch is working again.
1 Like
I lost the connection to the Hue dimmmer Switch, again.
I cleared cache and tmp, rebooted my Rpi, (due to some z-wave problems mentioned in another thread).
Now the switch status âNode is not found on networkâ according to Habmin.
If I push the âsetupâ button on the bag of the dimmer switch, and put the binding into scan for new devices. It starts working again. Binding doesn´t find any new devices thoughâŚ
Hue motion sensor works fineâŚ
@chris
Hmm lost the connection again. This is the log entry after at reboot⌠I suspect there is no communication to the controller, or?
I havn´t made any debug yet.
2018-07-22 01:12:32.864 [hingStatusInfoChangedEvent] - 'zigbee:device:6ec05458:001788011032a21b' changed from ONLINE to UNINITIALIZED
2018-07-22 01:12:32.870 [hingStatusInfoChangedEvent] - 'zigbee:device:6ec05458:001788011032a21b' changed from UNINITIALIZED to UNINITIALIZED (HANDLER_MISSING_ERROR)
2018-07-22 01:12:32.876 [hingStatusInfoChangedEvent] - 'zigbee:device:6ec05458:7cb03eaa00a05370' changed from ONLINE to UNINITIALIZED
2018-07-22 01:12:32.881 [hingStatusInfoChangedEvent] - 'zigbee:device:6ec05458:7cb03eaa00a05370' changed from UNINITIALIZED to UNINITIALIZED (HANDLER_MISSING_ERROR)
2018-07-22 01:12:32.883 [hingStatusInfoChangedEvent] - 'zigbee:device:6ec05458:0017880102139d00' changed from ONLINE to UNINITIALIZED
2018-07-22 01:12:32.887 [hingStatusInfoChangedEvent] - 'zigbee:device:6ec05458:0017880102139d00' changed from UNINITIALIZED to UNINITIALIZED (HANDLER_MISSING_ERROR)
2018-07-22 01:12:32.889 [hingStatusInfoChangedEvent] - 'zigbee:coordinator_ember:6ec05458' changed from ONLINE to UNINITIALIZED
2018-07-22 01:12:33.300 [hingStatusInfoChangedEvent] - 'zigbee:coordinator_ember:6ec05458' changed from UNINITIALIZED to UNINITIALIZED (HANDLER_MISSING_ERROR)
2018-07-22 01:12:41.692 [temChannelLinkRemovedEvent] - Link 'HUE_Motion => zigbee:device:6ec05458:0017880102139d00:0017880102139D00_1_switch_onoff' has been removed.
2018-07-22 01:12:41.693 [temChannelLinkRemovedEvent] - Link 'HUE_Temp => zigbee:device:6ec05458:0017880102139d00:0017880102139D00_2_measurement_temperature' has been removed.
2018-07-22 01:12:41.697 [temChannelLinkRemovedEvent] - Link 'HUE_illumiance => zigbee:device:6ec05458:0017880102139d00:0017880102139D00_2_measurement_illuminance' has been removed.
2018-07-22 01:12:41.699 [temChannelLinkRemovedEvent] - Link 'HUE_Occu => zigbee:device:6ec05458:0017880102139d00:0017880102139D00_2_sensor_occupancy' has been removed.
2018-07-22 01:12:41.703 [temChannelLinkRemovedEvent] - Link 'HUE_batteryPercent => zigbee:device:6ec05458:0017880102139d00:0017880102139D00_2_battery_level' has been removed.
2018-07-22 01:12:41.705 [temChannelLinkRemovedEvent] - Link 'HUE_batteryVoltage => zigbee:device:6ec05458:0017880102139d00:0017880102139D00_2_battery_voltage' has been removed.
2018-07-22 01:12:41.708 [temChannelLinkRemovedEvent] - Link 'HueSwitch1 => zigbee:device:6ec05458:001788011032a21b:001788011032A21B_1_switch_onoff' has been removed.
2018-07-22 01:12:41.711 [temChannelLinkRemovedEvent] - Link 'HueSwitch1_batteryPercent => zigbee:device:6ec05458:001788011032a21b:001788011032A21B_2_battery_level' has been removed.
2018-07-22 01:12:41.714 [temChannelLinkRemovedEvent] - Link 'HueSwitch1_batteryVoltage => zigbee:device:6ec05458:001788011032a21b:001788011032A21B_2_battery_voltage' has been removed.
2018-07-22 01:12:41.717 [temChannelLinkRemovedEvent] - Link 'OsramPlug_TotalPower => zigbee:device:6ec05458:7cb03eaa00a05370:7CB03EAA00A05370_3_electrical_activepower' has been removed.
2018-07-22 01:12:41.720 [temChannelLinkRemovedEvent] - Link 'OsramPlug_OnOff => zigbee:device:6ec05458:7cb03eaa00a05370:7CB03EAA00A05370_3_switch_onoff' has been removed.
2018-07-22 01:12:41.692 [temChannelLinkRemovedEvent] - Link 'HUE_Motion => zigbee:device:6ec05458:0017880102139d00:0017880102139D00_1_switch_onoff' has been removed.
2018-07-22 01:12:41.693 [temChannelLinkRemovedEvent] - Link 'HUE_Temp => zigbee:device:6ec05458:0017880102139d00:0017880102139D00_2_measurement_temperature' has been removed.
2018-07-22 01:12:41.697 [temChannelLinkRemovedEvent] - Link 'HUE_illumiance => zigbee:device:6ec05458:0017880102139d00:0017880102139D00_2_measurement_illuminance' has been removed.
2018-07-22 01:12:41.699 [temChannelLinkRemovedEvent] - Link 'HUE_Occu => zigbee:device:6ec05458:0017880102139d00:0017880102139D00_2_sensor_occupancy' has been removed.
2018-07-22 01:12:41.703 [temChannelLinkRemovedEvent] - Link 'HUE_batteryPercent => zigbee:device:6ec05458:0017880102139d00:0017880102139D00_2_battery_level' has been removed.
2018-07-22 01:12:41.705 [temChannelLinkRemovedEvent] - Link 'HUE_batteryVoltage => zigbee:device:6ec05458:0017880102139d00:0017880102139D00_2_battery_voltage' has been removed.
2018-07-22 01:12:41.708 [temChannelLinkRemovedEvent] - Link 'HueSwitch1 => zigbee:device:6ec05458:001788011032a21b:001788011032A21B_1_switch_onoff' has been removed.
2018-07-22 01:12:41.711 [temChannelLinkRemovedEvent] - Link 'HueSwitch1_batteryPercent => zigbee:device:6ec05458:001788011032a21b:001788011032A21B_2_battery_level' has been removed.
2018-07-22 01:12:41.714 [temChannelLinkRemovedEvent] - Link 'HueSwitch1_batteryVoltage => zigbee:device:6ec05458:001788011032a21b:001788011032A21B_2_battery_voltage' has been removed.
2018-07-22 01:12:41.717 [temChannelLinkRemovedEvent] - Link 'OsramPlug_TotalPower => zigbee:device:6ec05458:7cb03eaa00a05370:7CB03EAA00A05370_3_electrical_activepower' has been removed.
2018-07-22 01:12:41.720 [temChannelLinkRemovedEvent] - Link 'OsramPlug_OnOff => zigbee:device:6ec05458:7cb03eaa00a05370:7CB03EAA00A05370_3_switch_onoff' has been removed.
2018-07-22 01:15:23.250 [.ItemChannelLinkAddedEvent] - Link 'HUE_Temp-zigbee:device:6ec05458:0017880102139d00:0017880102139D00_2_measurement_temperature' has been added.
2018-07-22 01:15:23.264 [.ItemChannelLinkAddedEvent] - Link 'HUE_Motion-zigbee:device:6ec05458:0017880102139d00:0017880102139D00_1_switch_onoff' has been added.
2018-07-22 01:15:23.319 [.ItemChannelLinkAddedEvent] - Link 'HUE_illumiance-zigbee:device:6ec05458:0017880102139d00:0017880102139D00_2_measurement_illuminance' has been added.
2018-07-22 01:15:23.332 [.ItemChannelLinkAddedEvent] - Link 'OsramPlug_OnOff-zigbee:device:6ec05458:7cb03eaa00a05370:7CB03EAA00A05370_3_switch_onoff' has been added.
2018-07-22 01:15:23.398 [.ItemChannelLinkAddedEvent] - Link 'HUE_batteryVoltage-zigbee:device:6ec05458:0017880102139d00:0017880102139D00_2_battery_voltage' has been added.
2018-07-22 01:15:23.422 [.ItemChannelLinkAddedEvent] - Link 'HueSwitch1_batteryPercent-zigbee:device:6ec05458:001788011032a21b:001788011032A21B_2_battery_level' has been added.
2018-07-22 01:15:23.425 [.ItemChannelLinkAddedEvent] - Link 'HUE_Occu-zigbee:device:6ec05458:0017880102139d00:0017880102139D00_2_sensor_occupancy' has been added.
2018-07-22 01:15:23.480 [.ItemChannelLinkAddedEvent] - Link 'HueSwitch1_batteryVoltage-zigbee:device:6ec05458:001788011032a21b:001788011032A21B_2_battery_voltage' has been added.
2018-07-22 01:15:23.485 [.ItemChannelLinkAddedEvent] - Link 'OsramPlug_TotalPower-zigbee:device:6ec05458:7cb03eaa00a05370:7CB03EAA00A05370_3_electrical_activepower' has been added.
2018-07-22 01:15:23.509 [.ItemChannelLinkAddedEvent] - Link 'HUE_batteryPercent-zigbee:device:6ec05458:0017880102139d00:0017880102139D00_2_battery_level' has been added.
2018-07-22 01:15:23.611 [.ItemChannelLinkAddedEvent] - Link 'HueSwitch1-zigbee:device:6ec05458:001788011032a21b:001788011032A21B_1_switch_onoff' has been added.
2018-07-22 01:15:28.104 [hingStatusInfoChangedEvent] - 'zigbee:coordinator_ember:6ec05458' changed from UNINITIALIZED to INITIALIZING
2018-07-22 01:15:28.197 [hingStatusInfoChangedEvent] - 'zigbee:coordinator_ember:6ec05458' changed from INITIALIZING to UNKNOWN
2018-07-22 01:15:29.498 [hingStatusInfoChangedEvent] - 'zigbee:device:6ec05458:001788011032a21b' changed from UNINITIALIZED to INITIALIZING
2018-07-22 01:15:29.588 [hingStatusInfoChangedEvent] - 'zigbee:device:6ec05458:001788011032a21b' changed from INITIALIZING to OFFLINE
2018-07-22 01:15:30.080 [hingStatusInfoChangedEvent] - 'zigbee:device:6ec05458:0017880102139d00' changed from UNINITIALIZED to INITIALIZING
2018-07-22 01:15:30.099 [hingStatusInfoChangedEvent] - 'zigbee:device:6ec05458:0017880102139d00' changed from INITIALIZING to OFFLINE
2018-07-22 01:15:30.110 [hingStatusInfoChangedEvent] - 'zigbee:device:6ec05458:7cb03eaa00a05370' changed from UNINITIALIZED to INITIALIZING
2018-07-22 01:15:30.113 [hingStatusInfoChangedEvent] - 'zigbee:device:6ec05458:7cb03eaa00a05370' changed from INITIALIZING to OFFLINE
2018-07-22 01:15:30.884 [hingStatusInfoChangedEvent] - 'zigbee:coordinator_ember:6ec05458' changed from UNKNOWN to OFFLINE: Failed to startup ZigBee transport layer
2018-07-22 01:15:42.637 [hingStatusInfoChangedEvent] - 'zigbee:coordinator_ember:6ec05458' changed from OFFLINE: Failed to startup ZigBee transport layer to ONLINE
2018-07-22 01:15:42.654 [nt.FirmwareStatusInfoEvent] - Firmware status of thing zigbee:coordinator_ember:6ec05458 changed to UNKNOWN.
2018-07-22 01:15:43.813 [me.event.ThingUpdatedEvent] - Thing 'zigbee:coordinator_ember:6ec05458' has been updated.
EDIT.
And 6 minutes after I see this in the log:
2018-07-22 01:21:26.801 [nt.FirmwareStatusInfoEvent] - Firmware status of thing zigbee:device:6ec05458:001788011032a21b changed to UNKNOWN.
2018-07-22 01:21:26.870 [nt.FirmwareStatusInfoEvent] - Firmware status of thing zigbee:device:6ec05458:0017880102139d00 changed to UNKNOWN.
2018-07-22 01:21:26.881 [nt.FirmwareStatusInfoEvent] - Firmware status of thing zigbee:device:6ec05458:7cb03eaa00a05370 changed to UNKNOWN.
Acording to PaperUI, the coordinator is ONLINE.
Good evening Chris. This evening, I installed the Telegesis ETRX3 on my Windows laptop, and then used the Telegesis Terminal software to connect. Everything appears to work successfully through their terminal software. I was able to access it, execute various AT commands. I also reset the USB stick to factory default. However, after reinserting into my Raspberry Pi 3b+, I still receive the same error unfortunately. Just wondering if you happen to have any further ideas on this issue?
Thanks again sir
To me confirm the basics first, is there a way to see or determine which serial port the Telegesis ETRX3USB device would be using on my Raspberry Pi 3b+? Iâm not all too familiar with the command prompt or commands on the Raspberry Pi just yet. In openHab, I have the coordinator device set to use /dev/ttyAMA0, and in the logs, it seems like the USB device is initializing; however, Iâm wondering if thereâs really just a more basic issue here where I donât have the correct serial port selected. In some past readings, Iâve read that I may need to edit some of the java files just to give openHab access to the serial port(s) which may be used.
Telegesis dongle initialize.
2018-07-21 22:54:20.850 [DEBUG] [ding.zigbee.handler.ZigBeeSerialPort] - Connecting to serial port [/dev/ttyAMA0] at 19200 baud, flow control FLOWCONTROL_OUT_NONE.
2018-07-21 22:54:20.862 [DEBUG] [ding.zigbee.handler.ZigBeeSerialPort] - Serial port [/dev/ttyAMA0] is initialized.
Is there any news about the Conbee Stick ?
Is there a way to test the Conbee Stick with the Zigbeebinding ?
I have set debug log for:
log:set debug org.openhab.binding.zigbee
log:set debug com.zsmartsystems.zigbee
This is this only thing happning:
2018-07-22 12:10:43.831 [DEBUG] [internal.ZigBeeNodeServiceDiscoverer] - 000D6F000FA0C316: Node SVC Discovery already scheduled or running
2018-07-22 12:10:43.838 [DEBUG] [internal.ZigBeeNodeServiceDiscoverer] - 7CB03EAA00A05370: Node SVC Discovery already scheduled or running
2018-07-22 12:10:43.842 [DEBUG] [internal.ZigBeeNodeServiceDiscoverer] - 001788011032A21B: Node SVC Discovery already scheduled or running
2018-07-22 12:10:43.846 [DEBUG] [internal.ZigBeeNodeServiceDiscoverer] - 0017880102139D00: Node SVC Discovery already scheduled or running
2018-07-22 12:15:43.831 [DEBUG] [internal.ZigBeeNodeServiceDiscoverer] - 000D6F000FA0C316: Node SVC Discovery already scheduled or running
2018-07-22 12:15:43.837 [DEBUG] [internal.ZigBeeNodeServiceDiscoverer] - 7CB03EAA00A05370: Node SVC Discovery already scheduled or running
2018-07-22 12:15:43.842 [DEBUG] [internal.ZigBeeNodeServiceDiscoverer] - 001788011032A21B: Node SVC Discovery already scheduled or running
2018-07-22 12:15:43.847 [DEBUG] [internal.ZigBeeNodeServiceDiscoverer] - 0017880102139D00: Node SVC Discovery already scheduled or running
2018-07-22 12:20:43.831 [DEBUG] [internal.ZigBeeNodeServiceDiscoverer] - 000D6F000FA0C316: Node SVC Discovery already scheduled or running
2018-07-22 12:20:43.838 [DEBUG] [internal.ZigBeeNodeServiceDiscoverer] - 7CB03EAA00A05370: Node SVC Discovery already scheduled or running
2018-07-22 12:20:43.843 [DEBUG] [internal.ZigBeeNodeServiceDiscoverer] - 001788011032A21B: Node SVC Discovery already scheduled or running
2018-07-22 12:20:43.848 [DEBUG] [internal.ZigBeeNodeServiceDiscoverer] - 0017880102139D00: Node SVC Discovery already scheduled or running
The coordinator is ONLINE according to PaperUI. But my Zigbee devices are OFFLINE.
Now what?
For some time now the Zigbee binding has been quite reliable for me, but on rare occasions, a node does go OFFLINE. I find that if I cycle power to that node, it will more often than not return to ONLINE.
Had to start all over. Removed things and binding, added everything back. For now it seems to work again. Probably just for a few days.
Maybe this Elelabs Rpi Zigbee Shield isn´t that realiable.
So I have had the CC2531 working, though I havenât had any devices. Today I got my first device and noticed that the zigbee binding was no longer working. I have several problems Iâm hoping someone can help me with:
14:34:10.039 [DEBUG] [gbee.handler.ZigBeeCoordinatorHandler] - ZigBee network starting
14:34:10.042 [DEBUG] [gbee.handler.ZigBeeCoordinatorHandler] - Initialising ZigBee coordinator
14:34:10.050 [DEBUG] [gbee.handler.ZigBeeCoordinatorHandler] - Key initialise 4DD86DF9327D57D4F7AB22F35C7A08A4
14:34:10.054 [DEBUG] [nding.zigbee.handler.ZigBeeSerialPort] - Connecting to serial port [/dev/ttyACM1] at 115200 baud, flow control FLOWCONTROL_OUT_RTSCTS.
14:34:10.058 [ERROR] [nding.zigbee.handler.ZigBeeSerialPort] - Serial Error: Port /dev/ttyACM1 does not exist.
14:34:10.059 [ERROR] [e.cc2531.network.ZigBeeNetworkManager] - Failed to open the dongle.
Two things, first when I get this error in this setup it also prevents my Zwave stick from starting and prevents any zwave from working, the only way to get Zwave back that I have found is to delete the thing for the zigbee stick.
Second in order to get here I have to add the CC2531 in paperui with the port as the only choice â/dev/ttyUSB0â, I then have to stop openhab and edit the .json file and change the port line to â/dev/ACM1â.
This method at least initialized on openhab2.2 but now on 2.3 no dice!? Thoughts anyone?
@gundark2 which Platform / OS do you use?
I have the same issus with the zigbee binding (2.2.0, 2.3.0 and 2.4.0-beta) not detecting the serial port of my CC2531 Stick (Firmware CC2531ZNP-Pro-Secure_Standard.hex from zstack-1.2.2a.44539-master) . I had to manually edit org.eclipse.smarthome.core.thing.Thing.json (/var/lib/openhab2/jsondb/org.eclipse.smarthome.core.thing.Thing.json on debian linux) to change zigbee_port to the correct serial port.
"zigbee:coordinator_cc2531:88d3d51b": {
"class": "org.eclipse.smarthome.core.thing.internal.BridgeImpl",
"value": {
"label": "CC2531EMK Coordinator",
"channels": [],
"configuration": {
"properties": {
"zigbee_port": "/dev/ttyUSB_cc2531",
"zigbee_baud": 115200,
"zigbee_initialise": false,
"zigbee_channel": 11,
"zigbee_panid": 24235,
"zigbee_znp_magicnumber": 239,
"zigbee_extendedpanid": "XXXXXXXXXXXXXXXXX",
"zigbee_networkkey": "00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00"
}
},
Weird thing is the âCC2531EMK Coordinatorâ Thing Config says âSelect a Valueâ for Serial Port even after editing the port in the org.eclipse.smarthome.core.thing.Thing.json file.
Your logs says 14:34:10.058 [ERROR] [nding.zigbee.handler.ZigBeeSerialPort] - Serial Error: Port /dev/ttyACM1 does not exist. I think either openhab has no access to the serial port or the port is wrong.
To fix permission error you have to edit /etc/default/openhab2 on debian linux and include your serial ports there:
EXTRA_JAVA_OPTS="-Dgnu.io.rxtx.SerialPorts=/dev/ttyUSB_mysensorsserialgw:/dev/ttyUSB_cc2531"
To fix problems with more than one serial based hardware stick i suggest to create udev rules like me.
my /etc/udev/rules.d/99-usb-serial.rules:
SUBSYSTEM=="tty", ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6001", ATTRS{serial}=="AI05CPRS", SYMLINK+="ttyUSB_traxcul"
SUBSYSTEM=="tty", ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6001", ATTRS{serial}=="A7006TNu", SYMLINK+="ttyUSB_mysensorsserialgw"
SUBSYSTEM=="tty", ATTRS{idVendor}=="0451", ATTRS{idProduct}=="16a8", ATTRS{serial}=="__0X00123a0012345B1B", SYMLINK+="ttyUSB_cc2531"
This will creates a mapping for my CC2531 Stick from /dev/ttyACM0 to /dev/ttyUSB_cc2531. So the order the system detects your serial devices does not matter as the mapping will be the same. Of cause your have change the udev rules for your hardware 
Manual: https://github.com/openhab/openhab1-addons/wiki/symlinks
Also serial hardware support vary with the java runtime and serial dependencies your system is using. Iâm currently using this on debian linux 9.4:
$ java -version
openjdk version "1.8.0_172"
OpenJDK Runtime Environment (Zulu 8.30.0.1-linux64) (build 1.8.0_172-b01)
OpenJDK 64-Bit Server VM (Zulu 8.30.0.1-linux64) (build 25.172-b01, mixed mode)Today I lost connection to the Hue dimmer switch.
Hue Motion Sensor and Osram Plug still running. I guess they´ll dissapear in the next coupple of days. And then I back to where I started!
This Zigbee is just not good enough. But I can´t tell if it´s due to the binding or the coordinator.
Hey pixeldoc81
I am running an ubuntu box on an intel core2 duo.
In previous openhab2 version doing as you mentioned has worked.
First:
My /etc/default/openhab2:
EXTRA_JAVA_OPTS="-Dgnu.io.rxtx.SerialPorts=/dev/ttyACM0:/dev/ttyACM1:/dev/ttyUSB0"
and in the logs I get conformation from openhab âFinal ports list ttyACM0, ttyACM1, ttyUSB0â
java -version:
java version "1.8.0_171"
Java(TM) SE Runtime Environment (build 1.8.0_171-b11)
Java HotSpot(TM) 64-Bit Server VM (build 25.171-b11, mixed mode)
so I can do the udev mapping rules if you think it may help? But this was working as recent as last week and I have no idea what has changed to make it not work⌠and also when enabled it also knocks out my zwave network?
Hi chris, whatâs the status regarding the transaction manager? Is there already something I could test? And is there an issue for this on GitHub that I could subscribe to?
This hasnât been done at the moment. It still needs to be looked at, but there were other issues that were considered more pressing for now.
[quote=âchris, post:1028, topic:15763, full:trueâ]You just need to manually install the library and uninstall the existing version. For this change, the only file that is required is the main com.zsmartsystems.zigbee JAR.
[/quote]
I have switched to a raspi. Can I just put the .jar in the âaddonsâ directory, or do I have to do something more elaborate?
You can just put the JAR in the addons, but you will also need to uninstall the existing 1.0.11 JAR. Note though that the latest version should include the latest zigbee libraries - or at least if itâs not available yet, the next version will (it was merged last week).
Here are some more logs after doing as pixledoc recommended
19:41:47.836 [DEBUG] [org.openhab.binding.zigbee.cc2531 ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.core.thing.binding.ThingHandlerFactory}={service.id=424, service.bundleid=266, service.scope=bundle, component.name=org.openhab.binding.zigbee.cc2531.internal.CC2531HandlerFactory, component.id=290} - org.openhab.binding.zigbee.cc2531
19:41:47.844 [DEBUG] [org.openhab.binding.zigbee.cc2531 ] - BundleEvent STARTING - org.openhab.binding.zigbee.cc2531
19:41:47.849 [DEBUG] [org.openhab.binding.zigbee.cc2531 ] - BundleEvent STARTED - org.openhab.binding.zigbee.cc2531
19:41:47.881 [DEBUG] [gbee.discovery.ZigBeeDiscoveryService] - Creating ZigBee discovery service for zigbee:coordinator_cc2531:f88421c9
19:41:47.884 [DEBUG] [gbee.discovery.ZigBeeDiscoveryService] - Activating ZigBee discovery service for zigbee:coordinator_cc2531:f88421c9
19:41:47.900 [DEBUG] [org.openhab.binding.zigbee.cc2531 ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.discovery.DiscoveryService}={service.id=427, service.bundleid=266, service.scope=singleton} - org.openhab.binding.zigbee.cc2531
19:41:47.950 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'zigbee:coordinator_cc2531:f88421c9' changed from UNINITIALIZED to INITIALIZING
19:41:47.952 [DEBUG] [g.zigbee.cc2531.handler.CC2531Handler] - Initializing ZigBee CC2531 serial bridge handler.
19:41:47.952 [DEBUG] [gbee.handler.ZigBeeCoordinatorHandler] - Initializing ZigBee network [zigbee:coordinator_cc2531:f88421c9].
19:41:47.953 [DEBUG] [gbee.handler.ZigBeeCoordinatorHandler] - Channel -1
19:41:47.953 [DEBUG] [gbee.handler.ZigBeeCoordinatorHandler] - PANID *edited*
19:41:47.953 [DEBUG] [gbee.handler.ZigBeeCoordinatorHandler] - EPANID *edited*
19:41:47.954 [DEBUG] [gbee.handler.ZigBeeCoordinatorHandler] - Key 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
19:41:47.955 [DEBUG] [gbee.handler.ZigBeeCoordinatorHandler] - Key String 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
19:41:47.957 [DEBUG] [gbee.handler.ZigBeeCoordinatorHandler] - Key initialised 7E3D10A3DB30AA7CB838F319D87CBF43
19:41:47.960 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'chromecast:chromecast:2ffc1dff132b09a32720372e56f97a86' changed from UNINITIALIZED to INITIALIZING
19:41:47.962 [DEBUG] [gbee.handler.ZigBeeCoordinatorHandler] - Key final array 7E3D10A3DB30AA7CB838F319D87CBF43
19:41:47.997 [DEBUG] [g.zigbee.cc2531.handler.CC2531Handler] - ZigBee CC2531 Coordinator opening Port:'/dev/ttyACM1' PAN:*edited*, EPAN:*edited*, Channel:-1
19:41:48.000 [DEBUG] [gbee.handler.ZigBeeCoordinatorHandler] - Scheduling ZigBee start
19:41:48.001 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'zigbee:coordinator_cc2531:f88421c9' changed from INITIALIZING to UNKNOWN
19:41:48.494 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'chromecast:chromecast:2ffc1dff132b09a32720372e56f97a86' changed from INITIALIZING to ONLINE
19:41:48.545 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'chromecast:chromecast:LongDogDOTgov' changed from UNINITIALIZED to INITIALIZING
19:41:48.604 [WARN ] [su.litvak.chromecast.api.v2.Channel ] - Error while reading
su.litvak.chromecast.api.v2.ChromeCastException: Remote socket closed
at su.litvak.chromecast.api.v2.Channel.read(Channel.java:417) [268:org.openhab.binding.chromecast:2.4.0.201806241822]
at su.litvak.chromecast.api.v2.Channel.access$200(Channel.java:50) [268:org.openhab.binding.chromecast:2.4.0.201806241822]
at su.litvak.chromecast.api.v2.Channel$ReadThread.run(Channel.java:132) [268:org.openhab.binding.chromecast:2.4.0.201806241822]
19:41:48.610 [WARN ] [su.litvak.chromecast.api.v2.Channel ] - <-- null payload in message
19:41:48.617 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'chromecast:chromecast:2ffc1dff132b09a32720372e56f97a86' changed from ONLINE to OFFLINE
19:41:48.666 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'chromecast:chromecast:LongDogDOTgov' changed from INITIALIZING to ONLINE
19:41:48.669 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'chromecast:chromecast:Doxiecast' changed from UNINITIALIZED to INITIALIZING
19:41:48.696 [WARN ] [su.litvak.chromecast.api.v2.Channel ] - Error while reading
su.litvak.chromecast.api.v2.ChromeCastException: Remote socket closed
at su.litvak.chromecast.api.v2.Channel.read(Channel.java:417) [268:org.openhab.binding.chromecast:2.4.0.201806241822]
at su.litvak.chromecast.api.v2.Channel.access$200(Channel.java:50) [268:org.openhab.binding.chromecast:2.4.0.201806241822]
at su.litvak.chromecast.api.v2.Channel$ReadThread.run(Channel.java:132) [268:org.openhab.binding.chromecast:2.4.0.201806241822]
19:41:48.698 [WARN ] [su.litvak.chromecast.api.v2.Channel ] - <-- null payload in message
19:41:48.706 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'chromecast:chromecast:LongDogDOTgov' changed from ONLINE to OFFLINE
19:41:48.787 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'chromecast:chromecast:Doxiecast' changed from INITIALIZING to ONLINE
19:41:49.004 [DEBUG] [gbee.handler.ZigBeeCoordinatorHandler] - ZigBee network starting
19:41:49.005 [DEBUG] [gbee.handler.ZigBeeCoordinatorHandler] - Initialising ZigBee coordinator
19:41:49.013 [DEBUG] [gbee.handler.ZigBeeCoordinatorHandler] - Key initialise 7E3D10A3DB30AA7CB838F319D87CBF43
19:41:49.016 [DEBUG] [nding.zigbee.handler.ZigBeeSerialPort] - Connecting to serial port [/dev/ttyACM1] at 115200 baud, flow control FLOWCONTROL_OUT_RTSCTS.
19:41:49.019 [ERROR] [nding.zigbee.handler.ZigBeeSerialPort] - Serial Error: Port /dev/ttyACM1 does not exist.
19:41:49.020 [ERROR] [e.cc2531.network.ZigBeeNetworkManager] - Failed to open the dongle.
19:41:49.021 [DEBUG] [rnal.ZigBeeNetworkStateSerializerImpl] - Loading ZigBee network state: Start.
19:41:49.026 [DEBUG] [rnal.ZigBeeNetworkStateSerializerImpl] - Loading ZigBee network state: Done.
19:41:49.031 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'zigbee:coordinator_cc2531:f88421c9' changed from UNKNOWN to OFFLINE: Failed to initialize ZigBee transport layer
and the zwave failing while zigbee is enabled
19:42:53.577 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'zwave:device:512:node12' changed from UNINITIALIZED to UNINITIALIZED (BRIDGE_UNINITIALIZED)
19:42:53.579 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'zwave:device:512:node22' changed from UNINITIALIZED to UNINITIALIZED (BRIDGE_UNINITIALIZED)
19:42:53.582 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'zwave:device:512:node2' changed from UNINITIALIZED to UNINITIALIZED (BRIDGE_UNINITIALIZED)
19:42:53.583 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'zwave:device:512:node18' changed from UNINITIALIZED to UNINITIALIZED (BRIDGE_UNINITIALIZED)
19:42:53.584 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'zwave:device:512:node19' changed from UNINITIALIZED to UNINITIALIZED (BRIDGE_UNINITIALIZED)
19:42:53.585 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'zwave:device:512:node5' changed from UNINITIALIZED to UNINITIALIZED (BRIDGE_UNINITIALIZED)
19:42:53.587 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'zwave:device:512:node4' changed from UNINITIALIZED to UNINITIALIZED (BRIDGE_UNINITIALIZED)
19:42:53.616 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'zwave:serial_zstick:512' changed from UNINITIALIZED to INITIALIZING
19:42:53.620 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'zwave:serial_zstick:512' changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE): Controller is offline
19:42:53.630 [INFO ] [ding.zwave.handler.ZWaveSerialHandler] - Connecting to serial port '/dev/ttyACM0'
19:42:53.640 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'zwave:serial_zstick:512' changed from OFFLINE (BRIDGE_OFFLINE): Controller is offline to OFFLINE (COMMUNICATION_ERROR): Serial Error: Port {0} does not exist
19:42:53.656 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'zwave:device:512:node2' changed from UNINITIALIZED (BRIDGE_UNINITIALIZED) to INITIALIZING
19:42:53.656 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'zwave:device:512:node2' changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE): Controller is offline
19:42:53.681 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'zwave:device:512:node19' changed from UNINITIALIZED (BRIDGE_UNINITIALIZED) to INITIALIZING
19:42:53.681 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'zwave:device:512:node19' changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE): Controller is offline
19:42:53.696 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'zwave:device:512:node5' changed from UNINITIALIZED (BRIDGE_UNINITIALIZED) to INITIALIZING
19:42:53.697 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'zwave:device:512:node5' changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE): Controller is offline
19:42:53.723 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'zwave:device:512:node3' changed from UNINITIALIZED to INITIALIZING
19:42:53.723 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'zwave:device:512:node3' changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE): Controller is offline
19:42:53.723 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'zwave:device:512:node18' changed from UNINITIALIZED (BRIDGE_UNINITIALIZED) to INITIALIZING
19:42:53.724 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'zwave:device:512:node18' changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE): Controller is offline
19:42:53.733 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'zwave:device:512:node12' changed from UNINITIALIZED (BRIDGE_UNINITIALIZED) to INITIALIZING
19:42:53.734 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'zwave:device:512:node12' changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE): Controller is offline
19:42:53.734 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'zwave:device:512:node22' changed from UNINITIALIZED (BRIDGE_UNINITIALIZED) to INITIALIZING
19:42:53.734 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'zwave:device:512:node22' changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE): Controller is offline
19:42:53.737 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'zwave:device:512:node23' changed from UNINITIALIZED to INITIALIZING
19:42:53.738 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'zwave:device:512:node23' changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE): Controller is offline
19:42:53.745 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'zwave:device:512:node25' changed from UNINITIALIZED to INITIALIZING
19:42:53.745 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'zwave:device:512:node27' changed from UNINITIALIZED to INITIALIZING
19:42:53.746 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'zwave:device:512:node25' changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE): Controller is offline
19:42:53.746 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'zwave:device:512:node27' changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE): Controller is offline
19:42:53.749 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'zwave:device:512:node26' changed from UNINITIALIZED to INITIALIZING
19:42:53.749 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'zwave:device:512:node26' changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE): Controller is offline
19:42:53.749 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'zwave:device:512:node4' changed from UNINITIALIZED (BRIDGE_UNINITIALIZED) to INITIALIZING
19:42:53.754 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'zwave:device:512:node4' changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE): Controller is offline
Hey Chris,
Do you have any ideas on this, I just changed all the udev rules and all to make the zigbee port /dev/ttyUSB_cc2531 and the errors stay the same and zwave is knocked offline. The only way I can have zwave is if I have no zigbee coordinator in my things?
Not really - the error is that the binding canât see the port, so itâs likely associated with either permissions (probably the #1 cause of this sort of problem) or udev rules.