Zigbee binding

Ahh ofocuse. It was 201…

Guess it helped, even without rebooting.

2018-08-03 19:29:09.870 [hingStatusInfoChangedEvent] - 'zigbee:device:9674089c:001788011032a21b' changed from OFFLINE: Node is not found on network to UNINITIALIZED
2018-08-03 19:29:09.892 [hingStatusInfoChangedEvent] - 'zigbee:device:9674089c:001788011032a21b' changed from UNINITIALIZED to UNINITIALIZED (HANDLER_MISSING_ERROR)
2018-08-03 19:29:09.896 [hingStatusInfoChangedEvent] - 'zigbee:device:9674089c:0017880102139d00' changed from ONLINE to UNINITIALIZED
2018-08-03 19:29:09.902 [hingStatusInfoChangedEvent] - 'zigbee:device:9674089c:0017880102139d00' changed from UNINITIALIZED to UNINITIALIZED (HANDLER_MISSING_ERROR)
2018-08-03 19:29:09.907 [hingStatusInfoChangedEvent] - 'zigbee:device:9674089c:7cb03eaa00a05370' changed from ONLINE to UNINITIALIZED
2018-08-03 19:29:09.910 [hingStatusInfoChangedEvent] - 'zigbee:device:9674089c:7cb03eaa00a05370' changed from UNINITIALIZED to UNINITIALIZED (HANDLER_MISSING_ERROR)
2018-08-03 19:29:09.914 [hingStatusInfoChangedEvent] - 'zigbee:device:9674089c:00158d00022d9e77' changed from OFFLINE: Node has not completed discovery to UNINITIALIZED
2018-08-03 19:29:09.921 [hingStatusInfoChangedEvent] - 'zigbee:device:9674089c:00158d00022d9e77' changed from UNINITIALIZED to UNINITIALIZED (HANDLER_MISSING_ERROR)
2018-08-03 19:29:09.931 [hingStatusInfoChangedEvent] - 'zigbee:coordinator_ember:9674089c' changed from ONLINE to UNINITIALIZED
2018-08-03 19:29:10.288 [hingStatusInfoChangedEvent] - 'zigbee:coordinator_ember:9674089c' changed from UNINITIALIZED to UNINITIALIZED (HANDLER_MISSING_ERROR)
2018-08-03 19:31:46.905 [hingStatusInfoChangedEvent] - 'zigbee:coordinator_ember:9674089c' changed from UNINITIALIZED (HANDLER_MISSING_ERROR) to INITIALIZING
2018-08-03 19:31:47.326 [hingStatusInfoChangedEvent] - 'zigbee:coordinator_ember:9674089c' changed from INITIALIZING to UNKNOWN
2018-08-03 19:31:47.365 [hingStatusInfoChangedEvent] - 'zigbee:device:9674089c:7cb03eaa00a05370' changed from UNINITIALIZED (HANDLER_MISSING_ERROR) to INITIALIZING
2018-08-03 19:31:47.369 [hingStatusInfoChangedEvent] - 'zigbee:device:9674089c:7cb03eaa00a05370' changed from INITIALIZING to OFFLINE
2018-08-03 19:31:47.380 [hingStatusInfoChangedEvent] - 'zigbee:device:9674089c:00158d00022d9e77' changed from UNINITIALIZED (HANDLER_MISSING_ERROR) to INITIALIZING
2018-08-03 19:31:47.386 [hingStatusInfoChangedEvent] - 'zigbee:device:9674089c:00158d00022d9e77' changed from INITIALIZING to OFFLINE
2018-08-03 19:31:47.393 [hingStatusInfoChangedEvent] - 'zigbee:device:9674089c:001788011032a21b' changed from UNINITIALIZED (HANDLER_MISSING_ERROR) to INITIALIZING
2018-08-03 19:31:47.442 [hingStatusInfoChangedEvent] - 'zigbee:device:9674089c:001788011032a21b' changed from INITIALIZING to OFFLINE
2018-08-03 19:31:47.446 [hingStatusInfoChangedEvent] - 'zigbee:device:9674089c:0017880102139d00' changed from UNINITIALIZED (HANDLER_MISSING_ERROR) to INITIALIZING
2018-08-03 19:31:47.452 [hingStatusInfoChangedEvent] - 'zigbee:device:9674089c:0017880102139d00' changed from INITIALIZING to OFFLINE
2018-08-03 19:31:56.431 [hingStatusInfoChangedEvent] - 'zigbee:coordinator_ember:9674089c' changed from UNKNOWN to ONLINE
2018-08-03 19:31:56.438 [nt.FirmwareStatusInfoEvent] - Firmware status of thing zigbee:coordinator_ember:9674089c changed to UNKNOWN.
2018-08-03 19:31:56.465 [hingStatusInfoChangedEvent] - 'zigbee:device:9674089c:0017880102139d00' changed from OFFLINE to OFFLINE: Node is not found on network
2018-08-03 19:31:56.472 [hingStatusInfoChangedEvent] - 'zigbee:device:9674089c:00158d00022d9e77' changed from OFFLINE to OFFLINE: Node is not found on network
2018-08-03 19:31:56.478 [hingStatusInfoChangedEvent] - 'zigbee:device:9674089c:7cb03eaa00a05370' changed from OFFLINE to OFFLINE: Node is not found on network
2018-08-03 19:31:56.485 [hingStatusInfoChangedEvent] - 'zigbee:device:9674089c:001788011032a21b' changed from OFFLINE to OFFLINE: Node is not found on network
2018-08-03 19:31:57.337 [me.event.ThingUpdatedEvent] - Thing 'zigbee:coordinator_ember:9674089c' has been updated.
2018-08-03 19:31:57.499 [me.event.ThingUpdatedEvent] - Thing 'zigbee:device:9674089c:00158d00022d9e77' has been updated.
2018-08-03 19:31:57.511 [hingStatusInfoChangedEvent] - 'zigbee:device:9674089c:00158d00022d9e77' changed from OFFLINE: Node is not found on network to OFFLINE: Node has not completed discovery
2018-08-03 19:31:57.554 [me.event.ThingUpdatedEvent] - Thing 'zigbee:device:9674089c:7cb03eaa00a05370' has been updated.
2018-08-03 19:31:58.356 [me.event.ThingUpdatedEvent] - Thing 'zigbee:coordinator_ember:9674089c' has been updated.
2018-08-03 19:33:09.400 [WARN ] [converter.ZigBeeConverterTemperature] - {}: Failed to bind temperature measurement cluster
2018-08-03 19:33:09.643 [me.event.ThingUpdatedEvent] - Thing 'zigbee:device:9674089c:7cb03eaa00a05370' has been updated.
2018-08-03 19:33:17.655 [hingStatusInfoChangedEvent] - 'zigbee:device:9674089c:7cb03eaa00a05370' changed from OFFLINE: Node is not found on network to ONLINE
2018-08-03 19:33:25.452 [me.event.ThingUpdatedEvent] - Thing 'zigbee:device:9674089c:0017880102139d00' has been updated.
2018-08-03 19:33:33.455 [hingStatusInfoChangedEvent] - 'zigbee:device:9674089c:0017880102139d00' changed from OFFLINE: Node is not found on network to ONLINE

You don’t happen to have a magic script to do this do you, or do you do this by hand? I guess it’s possible - maybe with the library version as an arg as I don’t think there’s a permalink to the latest version.

I just made a last reboote, just to make sure…
It still shows an error, though it seem like the binding is running.

2018-08-03 19:45:25.848 [.ItemChannelLinkAddedEvent] - Link 'HUE_Temp-zigbee:device:9674089c:0017880102139d00:0017880102139D00_2_measurement_temperature' has been added.
2018-08-03 19:45:25.887 [.ItemChannelLinkAddedEvent] - Link 'HUE_Motion-zigbee:device:9674089c:0017880102139d00:0017880102139D00_1_switch_onoff' has been added.
2018-08-03 19:45:25.988 [.ItemChannelLinkAddedEvent] - Link 'HUE_illumiance-zigbee:device:9674089c:0017880102139d00:0017880102139D00_2_measurement_illuminance' has been added.
2018-08-03 19:45:26.019 [.ItemChannelLinkAddedEvent] - Link 'OsramPlug_OnOff-zigbee:device:9674089c:7cb03eaa00a05370:7CB03EAA00A05370_3_switch_onoff' has been added.
2018-08-03 19:45:26.117 [.ItemChannelLinkAddedEvent] - Link 'HUE_batteryVoltage-zigbee:device:9674089c:0017880102139d00:0017880102139D00_2_battery_voltage' has been added.
2018-08-03 19:45:26.143 [.ItemChannelLinkAddedEvent] - Link 'HUE_Occu-zigbee:device:9674089c:0017880102139d00:0017880102139D00_2_sensor_occupancy' has been added.
2018-08-03 19:45:26.147 [.ItemChannelLinkAddedEvent] - Link 'HueSwitch1_batteryPercent-zigbee:device:9674089c:001788011032a21b:001788011032A21B_2_battery_level' has been added.
2018-08-03 19:45:26.229 [.ItemChannelLinkAddedEvent] - Link 'HueSwitch1_batteryVoltage-zigbee:device:9674089c:001788011032a21b:001788011032A21B_2_battery_voltage' has been added.
2018-08-03 19:45:26.232 [.ItemChannelLinkAddedEvent] - Link 'OsramPlug_TotalPower-zigbee:device:9674089c:7cb03eaa00a05370:7CB03EAA00A05370_3_electrical_activepower' has been added.
2018-08-03 19:45:26.285 [.ItemChannelLinkAddedEvent] - Link 'HUE_batteryPercent-zigbee:device:9674089c:0017880102139d00:0017880102139D00_2_battery_level' has been added.
2018-08-03 19:45:26.421 [.ItemChannelLinkAddedEvent] - Link 'HueSwitch1-zigbee:device:9674089c:001788011032a21b:001788011032A21B_1_switch_onoff' has been added.
2018-08-03 19:45:29.472 [hingStatusInfoChangedEvent] - 'zigbee:device:9674089c:001788011032a21b' changed from UNINITIALIZED to UNINITIALIZED (BRIDGE_UNINITIALIZED)
2018-08-03 19:45:31.119 [hingStatusInfoChangedEvent] - 'zigbee:device:9674089c:0017880102139d00' changed from UNINITIALIZED to UNINITIALIZED (BRIDGE_UNINITIALIZED)
2018-08-03 19:45:31.540 [hingStatusInfoChangedEvent] - 'zigbee:coordinator_ember:9674089c' changed from UNINITIALIZED to INITIALIZING
2018-08-03 19:45:31.656 [hingStatusInfoChangedEvent] - 'zigbee:coordinator_ember:9674089c' changed from INITIALIZING to UNKNOWN
2018-08-03 19:45:31.719 [hingStatusInfoChangedEvent] - 'zigbee:device:9674089c:001788011032a21b' changed from UNINITIALIZED (BRIDGE_UNINITIALIZED) to INITIALIZING
2018-08-03 19:45:31.725 [hingStatusInfoChangedEvent] - 'zigbee:device:9674089c:7cb03eaa00a05370' changed from UNINITIALIZED to INITIALIZING
2018-08-03 19:45:31.727 [hingStatusInfoChangedEvent] - 'zigbee:device:9674089c:0017880102139d00' changed from UNINITIALIZED (BRIDGE_UNINITIALIZED) to INITIALIZING
2018-08-03 19:45:31.744 [hingStatusInfoChangedEvent] - 'zigbee:device:9674089c:001788011032a21b' changed from INITIALIZING to OFFLINE
2018-08-03 19:45:31.748 [hingStatusInfoChangedEvent] - 'zigbee:device:9674089c:7cb03eaa00a05370' changed from INITIALIZING to OFFLINE
2018-08-03 19:45:31.756 [hingStatusInfoChangedEvent] - 'zigbee:device:9674089c:0017880102139d00' changed from INITIALIZING to OFFLINE
2018-08-03 19:45:42.746 [hingStatusInfoChangedEvent] - 'zigbee:coordinator_ember:9674089c' changed from UNKNOWN to ONLINE
2018-08-03 19:45:42.750 [nt.FirmwareStatusInfoEvent] - Firmware status of thing zigbee:coordinator_ember:9674089c changed to UNKNOWN.
2018-08-03 19:45:42.800 [hingStatusInfoChangedEvent] - 'zigbee:device:9674089c:0017880102139d00' changed from OFFLINE to OFFLINE: Node is not found on network
2018-08-03 19:45:42.803 [hingStatusInfoChangedEvent] - 'zigbee:device:9674089c:001788011032a21b' changed from OFFLINE to OFFLINE: Node is not found on network
2018-08-03 19:45:42.806 [hingStatusInfoChangedEvent] - 'zigbee:device:9674089c:7cb03eaa00a05370' changed from OFFLINE to OFFLINE: Node is not found on network
2018-08-03 19:45:42.959 [ERROR] [org.openhab.binding.zigbee          ] - FrameworkEvent ERROR - org.openhab.binding.zigbee
org.osgi.framework.BundleException: Could not resolve module: org.openhab.binding.zigbee [242]
  Another singleton bundle selected: osgi.identity; type="osgi.bundle"; version:Version="2.4.0.201808020834"; osgi.identity="org.openhab.binding.zigbee"; singleton:="true"
2018-08-03 19:45:45.354 [INFO ] [bee.discovery.ZigBeeDiscoveryService] - 00158D00022D9E77: Starting ZigBee device discovery
2018-08-03 19:45:45.426 [me.event.ThingUpdatedEvent] - Thing 'zigbee:coordinator_ember:9674089c' has been updated.
2018-08-03 19:45:45.458 [home.event.InboxAddedEvent] - Discovery Result with UID 'zigbee:device:9674089c:00158d00022d9e77' has been added.
2018-08-03 19:45:45.458 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'zigbee:device:9674089c:00158d00022d9e77' to inbox.
2018-08-03 19:45:45.910 [me.event.ThingUpdatedEvent] - Thing 'zigbee:coordinator_ember:9674089c' has been updated.
2018-08-03 19:45:46.224 [me.event.ThingUpdatedEvent] - Thing 'zigbee:coordinator_ember:9674089c' has been updated.
2018-08-03 19:46:55.631 [WARN ] [converter.ZigBeeConverterTemperature] - {}: Failed to bind temperature measurement cluster
2018-08-03 19:46:55.642 [me.event.ThingUpdatedEvent] - Thing 'zigbee:device:9674089c:7cb03eaa00a05370' has been updated.
2018-08-03 19:47:03.647 [hingStatusInfoChangedEvent] - 'zigbee:device:9674089c:7cb03eaa00a05370' changed from OFFLINE: Node is not found on network to ONLINE
2018-08-03 19:47:03.656 [nt.FirmwareStatusInfoEvent] - Firmware status of thing zigbee:device:9674089c:7cb03eaa00a05370 changed to UNKNOWN.
2018-08-03 19:47:11.719 [me.event.ThingUpdatedEvent] - Thing 'zigbee:device:9674089c:0017880102139d00' has been updated.
2018-08-03 19:47:19.726 [hingStatusInfoChangedEvent] - 'zigbee:device:9674089c:0017880102139d00' changed from OFFLINE: Node is not found on network to ONLINE
2018-08-03 19:47:19.737 [nt.FirmwareStatusInfoEvent] - Firmware status of thing zigbee:device:9674089c:0017880102139d00 changed to UNKNOWN.

My zigbee devices donΒ΄t work though. But that was a problem before I started to update the binding.

Btw… I canΒ΄t add tis new Trust Zigbee motion sensor ZPIR-8000. ItΒ΄s recognized as an unknown device.

All in one place (for Ember)…
https://openhab.ci.cloudbees.com/job/openHAB2-Bundles/lastSuccessfulBuild/org.openhab.binding$org.openhab.binding.zigbee/
https://openhab.ci.cloudbees.com/job/openHAB2-Bundles/lastSuccessfulBuild/org.openhab.binding$org.openhab.binding.zigbee.ember/

No, I do this by hand. But a script would be easy to do. The links do contain the version numbers, at least for the libraries. So, a shell script for OH 2.3 release or 2.4 snapshot to update to the latest zigbee binding and libraries through a manual install?

Do a list -s |grep -i zig. OH must have chosen one of the older ones. I would uninstall and leave all for files in addons.

openhab> bundle:list -s |grep -i zig
191 β”‚ Active    β”‚  80 β”‚ 1.0.14                 β”‚ com.zsmartsystems.zigbee
196 β”‚ Active    β”‚  80 β”‚ 2.4.0.201808020834     β”‚ org.openhab.binding.zigbee
200 β”‚ Active    β”‚  80 β”‚ 1.0.11                 β”‚ com.zsmartsystems.zigbee.dongle.cc2531
202 β”‚ Active    β”‚  80 β”‚ 1.0.11                 β”‚ com.zsmartsystems.zigbee.dongle.telegesis
203 β”‚ Active    β”‚  80 β”‚ 1.0.11                 β”‚ com.zsmartsystems.zigbee.dongle.xbee
242 β”‚ Installed β”‚  80 β”‚ 2.3.0                  β”‚ org.openhab.binding.zigbee
243 β”‚ Active    β”‚  80 β”‚ 2.3.0                  β”‚ org.openhab.binding.zigbee.cc2531
245 β”‚ Active    β”‚  80 β”‚ 2.3.0                  β”‚ org.openhab.binding.zigbee.telegesis
246 β”‚ Active    β”‚  80 β”‚ 2.3.0                  β”‚ org.openhab.binding.zigbee.xbee
256 β”‚ Active    β”‚  80 β”‚ 1.0.14                 β”‚ com.zsmartsystems.zigbee.dongle.ember
257 β”‚ Active    β”‚  80 β”‚ 2.4.0.201808020834     β”‚ org.openhab.binding.zigbee.ember
openhab>

I dont think it will change anything. Chris mentioned that this is a problem somewhere. It happened as well with the 2.3.0 binding.

Somehow I just managed to add the Trust Zigbee motion sensor ZPIR-8000. And itΒ΄s name is ADUROLIGHT VMS_ADUROLIGHT

But I see no channels for the device?

This is the properties of the device:

zigbee_logicaltype END_DEVICE
zigbee_powerlevel FULL
modelId VMS_ADUROLIGHT
vendor ADUROLIGHT
zigbee_networkaddress 34210
zigbee_powermode RECEIVER_ON_IDLE
zigbee_powersources [DISPOSABLE_BATTERY]
zigbee_powersource DISPOSABLE_BATTERY
hardwareVersion 1
zigbee_stkversion 2
zigbee_datecode 2017-08-04

Seems like this is the real product of the device, and Trust is just a brand.
http://adurosmart.com/product/81823/

In your userdata/zigbee folder will be an XML file - can you send this to me please? It might be too big to attach here, so it might be easier to email (chris -at- cd-jackson.com).

Done…
I had two xlm files. I have send you both.

@chris I wonder if my problems could be due to not running OH 2.4 ? IΒ΄m still running 2.3.0 stable.

Unfortunately these don’t seem to contain the device you showed above :confused:. One of the two files should be updated recently and I would have expected to contain the device information…

Which problem do you mean - the error on startup? This error is caused by trying to start a second ZigBee bundle (bundle 242) which is the 2.3 ZigBee bundle, as well as bundle 196 which is the 2.4 ZigBee bundle.

Huh?? How is that possible? ItΒ΄s the only files IΒ΄ve got in that folder /srv/openhab2-userdata/zigbee/

Okay I was just guessing.

A small status:
The problem with my Zigbee devices is a bit strange.
I can tell from the led on the Hue motion sensor, as well as this new Trust motion sensor, that theyΒ΄re registrering motion fine. But nothing get through to the binding, since I canΒ΄t see any update state changes in OpenHab.
Osram Plug doesnΒ΄t work again.
All these devices are stated ONLINE in Openhab.

I have given up totally on the Hue dimmer switch. It tend to work for a few hours (max one day) and then itΒ΄s offline. When pushed on one of the buttons, it gives a red long light and then goes off. I guess it no longer has a connection to the coordinator.

I have not tried with any Xiaomi devices again, yet.

As I said a few days ago, I believe that this is a problem with the trust centre configuration. Unfortunately the Silabs documentation is very poor, and their support staff also don’t know the answer, so they are trying to find out what the options do. Until I hear back, there is very little I can do - sorry.

Yeah it was mainly just to give you an status. Perhaps it could be usefull information.

Yes my EXTRA_JAVA_OPTS has all three ports, mysensors ttyUSB0, zwave ttyACM0, and zigbee ttyACM1. I now have zwave working with the zigbee installed, however I still only get the error that the serial port does not exist for the zigbee. Everything else works, kinda sucks. :frowning:

In your EXTRA_JAVA_OPTS, you need to use the names you created in your udev rules. These need to be the full path too (/dev/ttyUSB_cc2531, etc.). You wouldn’t need the EXTRA_JAVA_OPTS if you used a standard Linux naming convention (ref: check the note at the bottom).

Here are my udev rules for an HUSBZB-1 (no EXTRA_JAVA_OPTS required)…

# cat /etc/udev/rules.d/99-server.rules 
KERNEL=="ttyUSB[0-9]*", ATTRS{interface}=="HubZ Z-Wave Com Port", SYMLINK+="ttyUSB-5", GROUP="dialout", MODE="0666"
KERNEL=="ttyUSB[0-9]*", ATTRS{interface}=="HubZ ZigBee Com Port", SYMLINK+="ttyUSB-55", GROUP="dialout", MODE="0666"

So here are my settings and my logs:

/etc/default/openhab2

EXTRA_JAVA_OPTS="-Dgnu.io.rxtx.SerialPorts=/dev/ttyACM0:/dev/ttyACM1:/dev/ttyUSB0:/dev/ttyUSB_cc2531"


udev rule

SUBSYSTEM=="tty", ATTRS{idVendor}=="0451", ATTRS{idProduct}=="16a8", ATTRS{serial}=="__0X00124B000E896C97", SYMLINK+="ttyUSB_cc2531"


gundark@doghouse:/var/lib/openhab2/jsondb$ ls -la /dev/
drwxr-xr-x 22 root root          4400 Aug 12 14:12 .
drwxr-xr-x 24 root root          4096 Aug  7 06:04 ..
crw-rw----  1 root dialout   166,   0 Aug 12 14:08 ttyACM0
crw-rw----  1 root dialout   166,   1 Aug 12 14:12 ttyACM1
crw-rw----  1 root dialout   188,   0 Aug 12 14:14 ttyUSB0
lrwxrwxrwx  1 root root             7 Aug 12 14:12 ttyUSB_cc2531 -> ttyACM1

[del.core.internal.ModelRepositoryImpl] - Loading model 'home.rules'
[del.core.internal.ModelRepositoryImpl] - Loading model 'time.rules'
[del.core.internal.ModelRepositoryImpl] - Loading model 'guest.sitemap'
[del.core.internal.ModelRepositoryImpl] - Loading model 'home.sitemap'
[del.core.internal.ModelRepositoryImpl] - Loading model 'seanphone.sitemap'
[del.core.internal.ModelRepositoryImpl] - Loading model 'master.sitemap'
[del.core.internal.ModelRepositoryImpl] - Loading model 'home.things'
12.733[org.openhab.binding.mysensors        ] - BundleEvent STARTING - org.openhab.binding.mysensors
12.746[org.openhab.binding.mysensors        ] - BundleEvent STARTED - org.openhab.binding.mysensors
12.759[org.openhab.binding.mysensors        ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.core.thing.binding.ThingHandlerFactory}={service.id=323, service.bundleid=196, service.scope=bundle, component.name=org.openhab.binding.mysensors.factory.MySensorsHandlerFactory, component.id=207} - org.openhab.binding.mysensors
12.971[ome.event.ThingStatusInfoChangedEvent] - 'mysensors:bridge-ser:gateway' changed from UNINITIALIZED to INITIALIZING
12.972[ensors.handler.MySensorsBridgeHandler] - Initialization of the MySensors bridge
12.978[ome.event.ThingStatusInfoChangedEvent] - 'weatherunderground:weather:denver' changed from UNINITIALIZED to INITIALIZING
12.986 [WARN ] [e.core.thing.binding.BaseThingHandler] - BaseThingHandler.initialize() will be removed soon, ThingStatus can be set manually via updateStatus(ThingStatus.ONLINE)
12.988[ome.event.ThingStatusInfoChangedEvent] - 'weatherunderground:weather:denver' changed from INITIALIZING to ONLINE
12.992[sensors.factory.MySensorsCacheFactory] - Cache file: given_ids.cached exist.
12.994[sensors.factory.MySensorsCacheFactory] - Cache (given_ids) content: [0, 1, 2, 130, 4, 6, 8, 9, 10, 138, 11, 12, 140, 13, 14, 142, 15, 144, 16, 17, 18, 146, 19, 20, 148, 21, 149, 22, 150, 23, 151, 24, 152, 25, 26, 27, 28, 29, 30, 31, 34, 36, 39, 40, 42, 43, 44, 45, 46, 174, 47, 48, 50, 51, 52, 53, 54, 55, 56, 57, 66, 74, 75, 77, 78, 79, 81, 82, 83, 84, 85, 86, 87, 88, 89, 90, 91, 93]
13.002[ocol.serial.MySensorsSerialConnection] - Set skip check on startup to: false
13.006[ocol.serial.MySensorsSerialConnection] - Enabling connection watchdog
13.039[org.openhab.binding.mysensors        ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.discovery.DiscoveryService}={service.id=325, service.bundleid=196, service.scope=singleton} - org.openhab.binding.mysensors
13.043[s.discovery.MySensorsDiscoveryService] - Starting MySensors discovery scan
13.047[ensors.handler.MySensorsBridgeHandler] - Initialization of the MySensors bridge DONE!
13.072[ocol.serial.MySensorsSerialConnection] - Connecting to /dev/ttyUSB0 [baudRate:115200]
13.412[ocol.serial.MySensorsSerialConnection] - Final port list: /dev/ttyACM0:/dev/ttyACM1:/dev/ttyUSB0:/dev/ttyUSB_cc2531
13.443[ocol.serial.MySensorsSerialConnection] - Successfully connected to serial port.
13.444[ocol.serial.MySensorsSerialConnection] - Waiting 3 seconds to allow correct reset trigger on serial connection opening
16.458[orsAbstractConnection$MySensorsWriter] - Sending to MySensors: 0;0;3;0;2;
16.476[orsAbstractConnection$MySensorsReader] - 0;255;3;0;2;2.3.0
16.478[orsAbstractConnection$MySensorsReader] - Good,Gateway is up and running! (Ver:2.3.0)
16.482[ome.event.ThingStatusInfoChangedEvent] - 'mysensors:bridge-ser:gateway' changed from INITIALIZING to ONLINE
16.502[sensors.factory.MySensorsCacheFactory] - Writing on cache given_ids, content: [0,1,2,130,4,6,8,9,10,138,11,12,140,13,14,142,15,144,16,17,18,146,19,20,148,21,149,22,150,23,151,24,152,25,26,27,28,29,30,31,34,36,39,40,42,43,44,45,46,174,47,48,50,51,52,53,54,55,56,57,66,74,75,77,78,79,81,82,83,84,85,86,87,88,89,90,91,93]
16.820[sensors.handler.MySensorsThingHandler] - Event listener for node 25-1 not registered yet, registering...
20.139[.basic.internal.servlet.WebAppServlet] - Started Basic UI at /basicui/app
20.370[lassic.internal.servlet.WebAppServlet] - Started Classic UI at /classicui/app
20.421[marthome.ui.paper.internal.PaperUIApp] - Started Paper UI at /paperui
22.247 [ERROR] [ipse.smarthome.core.items.GenericItem] - Tried to set invalid state 90 (DecimalType) on item HotTubReturn of type StringItem, ignoring it
22.414[.ui.habmin.internal.servlet.HABminApp] - Started HABmin servlet at /habmin
22.458[bpanel.internal.HABPanelDashboardTile] - Started HABPanel at /habpanel
22.668[org.openhab.binding.zigbee.cc2531    ] - BundleEvent STARTING - org.openhab.binding.zigbee.cc2531
22.671[org.openhab.binding.zigbee.cc2531    ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.core.thing.binding.ThingHandlerFactory}={service.id=430, service.bundleid=320, service.scope=bundle, component.name=org.openhab.binding.zigbee.cc2531.internal.CC2531HandlerFactory, component.id=297} - org.openhab.binding.zigbee.cc2531
22.683[org.openhab.binding.zigbee.cc2531    ] - BundleEvent STARTED - org.openhab.binding.zigbee.cc2531
24.478[smarthome.event.ItemStateChangedEvent] - PhotoTrip changed from NULL to 0
24.480[gbee.discovery.ZigBeeDiscoveryService] - Creating ZigBee discovery service for zigbee:coordinator_cc2531:f88421c9
24.481[gbee.discovery.ZigBeeDiscoveryService] - Activating ZigBee discovery service for zigbee:coordinator_cc2531:f88421c9
24.482[org.openhab.binding.zigbee.cc2531    ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.discovery.DiscoveryService}={service.id=433, service.bundleid=320, service.scope=singleton} - org.openhab.binding.zigbee.cc2531
24.510[ome.event.ThingStatusInfoChangedEvent] - 'zigbee:coordinator_cc2531:f88421c9' changed from UNINITIALIZED to INITIALIZING
24.515[g.zigbee.cc2531.handler.CC2531Handler] - Initializing ZigBee CC2531 serial bridge handler.
24.516[gbee.handler.ZigBeeCoordinatorHandler] - Initializing ZigBee network [zigbee:coordinator_cc2531:f88421c9].
24.517[gbee.handler.ZigBeeCoordinatorHandler] - Channel 11
24.518[gbee.handler.ZigBeeCoordinatorHandler] - PANID -26867
24.518[gbee.handler.ZigBeeCoordinatorHandler] - EPANID 00124B000E896C97
24.520[gbee.handler.ZigBeeCoordinatorHandler] - Key 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
24.520[gbee.handler.ZigBeeCoordinatorHandler] - Key String 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
24.524[gbee.handler.ZigBeeCoordinatorHandler] - Key initialised 3D6688D09EDF4D1FA1E763CC288C1413
24.534[gbee.handler.ZigBeeCoordinatorHandler] - Key final array 3D6688D09EDF4D1FA1E763CC288C1413
24.560[g.zigbee.cc2531.handler.CC2531Handler] - ZigBee CC2531 Coordinator opening Port:'/dev/ttyUSB_cc2531' PAN:ffff970d, EPAN:00124B000E896C97, Channel:11
24.620[gbee.handler.ZigBeeCoordinatorHandler] - Scheduling ZigBee start
24.621[ome.event.ThingStatusInfoChangedEvent] - 'zigbee:coordinator_cc2531:f88421c9' changed from INITIALIZING to UNKNOWN
24.633[ome.event.ThingStatusInfoChangedEvent] - 'chromecast:chromecast:LongDogDOTgov' changed from UNINITIALIZED to INITIALIZING
25.208 [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) [286:org.openhab.binding.chromecast:2.4.0.201806241822]
	at su.litvak.chromecast.api.v2.Channel.access$200(Channel.java:50) [286:org.openhab.binding.chromecast:2.4.0.201806241822]
	at su.litvak.chromecast.api.v2.Channel$ReadThread.run(Channel.java:132) [286:org.openhab.binding.chromecast:2.4.0.201806241822]
25.213 [WARN ] [su.litvak.chromecast.api.v2.Channel  ] -  <--  null payload in message 
25.219[ome.event.ThingStatusInfoChangedEvent] - 'chromecast:chromecast:LongDogDOTgov' changed from ONLINE to OFFLINE
25.625[gbee.handler.ZigBeeCoordinatorHandler] - ZigBee network starting
25.626[gbee.handler.ZigBeeCoordinatorHandler] - Initialising ZigBee coordinator
25.634[gbee.handler.ZigBeeCoordinatorHandler] - Key initialise 3D6688D09EDF4D1FA1E763CC288C1413
25.637[nding.zigbee.handler.ZigBeeSerialPort] - Connecting to serial port [/dev/ttyUSB_cc2531] at 115200 baud, flow control FLOWCONTROL_OUT_RTSCTS.
25.642 [ERROR] [nding.zigbee.handler.ZigBeeSerialPort] - Serial Error: Port /dev/ttyUSB_cc2531 does not exist.
25.643 [ERROR] [e.cc2531.network.ZigBeeNetworkManager] - Failed to open the dongle.
25.644[rnal.ZigBeeNetworkStateSerializerImpl] - Loading ZigBee network state: Start.
25.656[rnal.ZigBeeNetworkStateSerializerImpl] - Loading ZigBee network state: Done.
25.659[ome.event.ThingStatusInfoChangedEvent] - 'zigbee:coordinator_cc2531:f88421c9' changed from UNKNOWN to OFFLINE: Failed to initialize ZigBee transport layer
26.633[ome.event.ThingStatusInfoChangedEvent] - 'chromecast:chromecast:Doxiecast' changed from INITIALIZING to ONLINE

openhab-cli console

 15 β”‚ Active   β”‚  80 β”‚ 5.3.1.201602281253     β”‚ OSGi JAX-RS Connector
 16 β”‚ Active   β”‚  80 β”‚ 2.4.5                  β”‚ Jackson-annotations
 17 β”‚ Active   β”‚  80 β”‚ 2.4.5                  β”‚ Jackson-core
 18 β”‚ Active   β”‚  80 β”‚ 2.4.5                  β”‚ jackson-databind
 19 β”‚ Active   β”‚  80 β”‚ 2.4.5                  β”‚ Jackson-dataformat-XML
 20 β”‚ Active   β”‚  80 β”‚ 2.4.5                  β”‚ Jackson-dataformat-YAML
 21 β”‚ Active   β”‚  80 β”‚ 2.4.5                  β”‚ Jackson-module-JAXB-annotations
 22 β”‚ Active   β”‚  80 β”‚ 2.7.0                  β”‚ Gson
 23 β”‚ Active   β”‚  80 β”‚ 18.0.0                 β”‚ Guava: Google Core Libraries for Java
 24 β”‚ Active   β”‚  80 β”‚ 3.0.0.v201312141243    β”‚ Google Guice (No AOP)
 25 β”‚ Active   β”‚  80 β”‚ 1.5.8                  β”‚ swagger-annotations
 26 β”‚ Active   β”‚  80 β”‚ 3.19.0.GA              β”‚ Javassist
 28 β”‚ Active   β”‚  80 β”‚ 3.5.2                  β”‚ JmDNS
 30 β”‚ Active   β”‚  80 β”‚ 1.0.0                  β”‚ Units of Measurement API
 32 β”‚ Active   β”‚  80 β”‚ 1.1.0.Final            β”‚ Bean Validation API
 33 β”‚ Active   β”‚  80 β”‚ 2.0.1                  β”‚ javax.ws.rs-api
 34 β”‚ Active   β”‚  80 β”‚ 3.2.0.v201101311130    β”‚ ANTLR Runtime
 35 β”‚ Active   β”‚  80 β”‚ 3.2.1                  β”‚ Commons Collections
 36 β”‚ Active   β”‚  80 β”‚ 1.1                    β”‚ Commons Exec
 37 β”‚ Active   β”‚  80 β”‚ 2.2.0                  β”‚ Commons IO
 38 β”‚ Active   β”‚  80 β”‚ 2.6                    β”‚ Commons Lang
 48 β”‚ Active   β”‚  80 β”‚ 4.1.5                  β”‚ Apache Karaf :: OSGi Services :: Event
 67 β”‚ Active   β”‚  80 β”‚ 2.11.0.v20150805-0538  β”‚ EMF Common
 68 β”‚ Active   β”‚  80 β”‚ 2.11.1.v20150805-0538  β”‚ EMF Ecore
 69 β”‚ Active   β”‚  80 β”‚ 2.11.1.v20150805-0538  β”‚ EMF XML/XMI Persistence
 70 β”‚ Active   β”‚  80 β”‚ 3.8.0.v20160509-1230   β”‚ Common Eclipse Runtime
 71 β”‚ Active   β”‚  80 β”‚ 3.6.100.v20160223-2218 β”‚ Extension Registry Support
 80 β”‚ Active   β”‚  80 β”‚ 9.3.21.v20170918       β”‚ Jetty :: Proxy
 94 β”‚ Active   β”‚  80 β”‚ 0.2.1.v20170706-0855   β”‚ org.eclipse.lsp4j
 95 β”‚ Active   β”‚  80 β”‚ 0.2.1.v20170706-0855   β”‚ org.eclipse.lsp4j.jsonrpc
 96 β”‚ Active   β”‚  80 β”‚ 0.10.0.oh230           β”‚ Eclipse SmartHome Config Core
 97 β”‚ Active   β”‚  80 β”‚ 0.10.0.oh230           β”‚ Eclipse SmartHome Configuration Discovery
 98 β”‚ Active   β”‚  80 β”‚ 0.10.0.oh230           β”‚ Eclipse SmartHome Configuration mDNS Discovery
 99 β”‚ Active   β”‚  80 β”‚ 0.10.0.oh230           β”‚ Eclipse SmartHome Config Dispatcher
100 β”‚ Active   β”‚  75 β”‚ 0.10.0.oh230           β”‚ Eclipse SmartHome Config XML
101 β”‚ Active   β”‚  80 β”‚ 0.10.0.oh230           β”‚ Eclipse SmartHome Core
102 β”‚ Active   β”‚  80 β”‚ 0.10.0.oh230           β”‚ Eclipse SmartHome Core Audio
103 β”‚ Active   β”‚  80 β”‚ 0.10.0.oh230           β”‚ Eclipse SmartHome AutoUpdate Binding
104 β”‚ Active   β”‚  80 β”‚ 0.10.0.oh230           β”‚ Eclipse SmartHome Core Binding XML
105 β”‚ Active   β”‚  80 β”‚ 0.10.0.oh230           β”‚ Eclipse SmartHome Core ID
106 β”‚ Active   β”‚  80 β”‚ 0.10.0.oh230           β”‚ Eclipse SmartHome Core Persistence
107 β”‚ Active   β”‚  80 β”‚ 0.10.0.oh230           β”‚ Eclipse SmartHome Scheduler Service
108 β”‚ Active   β”‚  80 β”‚ 0.10.0.oh230           β”‚ Eclipse SmartHome Core Thing
109 β”‚ Active   β”‚  75 β”‚ 0.10.0.oh230           β”‚ Eclipse SmartHome Core Thing XML
110 β”‚ Active   β”‚  80 β”‚ 0.10.0.oh230           β”‚ Eclipse SmartHome Transformation Service
111 β”‚ Active   β”‚  80 β”‚ 0.10.0.oh230           β”‚ Eclipse SmartHome Core Voice
112 β”‚ Active   β”‚  80 β”‚ 0.10.0.oh230           β”‚ Eclipse SmartHome Console
113 β”‚ Active   β”‚  80 β”‚ 0.10.0.oh230           β”‚ Eclipse SmartHome Console for OSGi runtime Karaf
114 β”‚ Active   β”‚  80 β”‚ 0.10.0.oh230           β”‚ Eclipse SmartHome JavaSound I/O, Fragments: 180
115 β”‚ Active   β”‚  80 β”‚ 0.10.0.oh230           β”‚ Eclipse SmartHome Monitor
116 β”‚ Active   β”‚  80 β”‚ 0.10.0.oh230           β”‚ Eclipse SmartHome Net I/O Bundle
117 β”‚ Active   β”‚  80 β”‚ 0.10.0.oh230           β”‚ Eclipse SmartHome REST Interface Bundle
118 β”‚ Active   β”‚  80 β”‚ 0.10.0.oh230           β”‚ Eclipse SmartHome Core REST API
119 β”‚ Active   β”‚  80 β”‚ 0.10.0.oh230           β”‚ Eclipse SmartHome REST mDNS Announcer
120 β”‚ Active   β”‚  80 β”‚ 0.10.0.oh230           β”‚ Eclipse SmartHome REST Interface JAX-RS optimization Bundle
121 β”‚ Active   β”‚  80 β”‚ 0.10.0.oh230           β”‚ Eclipse SmartHome Sitemap REST API
122 β”‚ Active   β”‚  80 β”‚ 0.10.0.oh230           β”‚ Eclipse SmartHome SSE REST API
123 β”‚ Active   β”‚  80 β”‚ 0.10.0.oh230           β”‚ Eclipse SmartHome Voice REST API
124 β”‚ Active   β”‚  80 β”‚ 0.10.0.oh230           β”‚ Eclipse SmartHome Bonjour/MDS Service Discovery Bundle
125 β”‚ Active   β”‚  80 β”‚ 0.10.0.oh230           β”‚ Eclipse SmartHome Web Audio Support
126 β”‚ Active   β”‚  80 β”‚ 0.10.0.oh230           β”‚ Eclipse SmartHome Model Core
127 β”‚ Active   β”‚  80 β”‚ 0.10.0.oh230           β”‚ Eclipse SmartHome Item Model
128 β”‚ Active   β”‚  80 β”‚ 0.10.0.oh230           β”‚ Eclipse SmartHome Item Model IDE
129 β”‚ Active   β”‚  80 β”‚ 0.10.0.oh230           β”‚ Eclipse SmartHome Item Model Runtime
130 β”‚ Active   β”‚  80 β”‚ 0.10.0.oh230           β”‚ Eclipse SmartHome Language Server
131 β”‚ Active   β”‚  80 β”‚ 0.10.0.oh230           β”‚ Eclipse SmartHome Persistence Model
132 β”‚ Active   β”‚  80 β”‚ 0.10.0.oh230           β”‚ Eclipse SmartHome Persistence Model IDE
133 β”‚ Active   β”‚  80 β”‚ 0.10.0.oh230           β”‚ Eclipse SmartHome Persistence Runtime
134 β”‚ Active   β”‚  80 β”‚ 0.10.0.oh230           β”‚ Eclipse SmartHome Rule Model
135 β”‚ Active   β”‚  80 β”‚ 0.10.0.oh230           β”‚ Eclipse SmartHome Rule Model IDE
136 β”‚ Active   β”‚  80 β”‚ 0.10.0.oh230           β”‚ Eclipse SmartHome Rule Runtime
137 β”‚ Active   β”‚  80 β”‚ 0.10.0.oh230           β”‚ Eclipse SmartHome Script
138 β”‚ Active   β”‚  80 β”‚ 0.10.0.oh230           β”‚ Eclipse SmartHome Script Model IDE
139 β”‚ Active   β”‚  80 β”‚ 0.10.0.oh230           β”‚ Eclipse SmartHome Script Runtime
140 β”‚ Active   β”‚  80 β”‚ 0.10.0.oh230           β”‚ Eclipse SmartHome Sitemap Model
141 β”‚ Active   β”‚  80 β”‚ 0.10.0.oh230           β”‚ Eclipse SmartHome Sitemap Model IDE
142 β”‚ Active   β”‚  80 β”‚ 0.10.0.oh230           β”‚ Eclipse SmartHome Sitemap Runtime
143 β”‚ Active   β”‚  80 β”‚ 0.10.0.oh230           β”‚ Eclipse SmartHome Thing Model
144 β”‚ Active   β”‚  80 β”‚ 0.10.0.oh230           β”‚ Eclipse SmartHome Thing Model IDE
145 β”‚ Active   β”‚  80 β”‚ 0.10.0.oh230           β”‚ Eclipse SmartHome Thing Model Runtime
146 β”‚ Active   β”‚  80 β”‚ 0.10.0.oh230           β”‚ Eclipse SmartHome Json Storage Service
147 β”‚ Active   β”‚  80 β”‚ 0.10.0.oh230           β”‚ Eclipse SmartHome UI
148 β”‚ Active   β”‚  80 β”‚ 0.10.0.oh230           β”‚ Eclipse SmartHome UI Icons
149 β”‚ Active   β”‚  80 β”‚ 0.10.0.oh230           β”‚ Eclipse SmartHome Classic IconSet
150 β”‚ Active   β”‚  80 β”‚ 2.12.0.v20170518-0757  β”‚ Xtend Runtime Library
151 β”‚ Active   β”‚  80 β”‚ 2.12.0.v20170518-0757  β”‚ Xtend Macro Interfaces
152 β”‚ Active   β”‚  80 β”‚ 2.12.0.v20170518-0959  β”‚ Xtext
153 β”‚ Active   β”‚  80 β”‚ 2.12.0.v20170519-0752  β”‚ Xtext Common Types
154 β”‚ Active   β”‚  80 β”‚ 2.12.0.v20171017-1700  β”‚ Xtext IDE Core
155 β”‚ Active   β”‚  80 β”‚ 2.12.0.v20170518-0959  β”‚ Xtext Utility
156 β”‚ Active   β”‚  80 β”‚ 2.12.0.v20170519-0752  β”‚ Xbase Model
157 β”‚ Active   β”‚  80 β”‚ 2.12.0.v20170519-0752  β”‚ Xbase Generic IDE Services
158 β”‚ Active   β”‚  80 β”‚ 2.12.0.v20170518-0757  β”‚ Xbase Runtime Library
173 β”‚ Active   β”‚  80 β”‚ 2.3.0                  β”‚ JUPnP Library
174 β”‚ Active   β”‚  80 β”‚ 1.9.6                  β”‚ MIME streaming extension
175 β”‚ Active   β”‚  80 β”‚ 5.0.2                  β”‚ Require-Bundle Fix :: org.objectweb.asm
177 β”‚ Active   β”‚  90 β”‚ 2.3.0                  β”‚ openHAB Core
178 β”‚ Active   β”‚  80 β”‚ 2.3.0                  β”‚ openHAB Karaf Integration
180 β”‚ Resolved β”‚  80 β”‚ 2.3.0                  β”‚ openHAB Sound Support, Hosts: 114
181 β”‚ Active   β”‚  80 β”‚ 2.3.0                  β”‚ openHAB Dashboard UI
186 β”‚ Active   β”‚  80 β”‚ 3.1.4                  β”‚ Stax2 API
187 β”‚ Active   β”‚  80 β”‚ 1.0.2                  β”‚ Units of Measurement Common Library
188 β”‚ Active   β”‚  80 β”‚ 1.0.8                  β”‚ Units of Measurement Implementation for Java SE
189 β”‚ Active   β”‚  80 β”‚ 1.6.0                  β”‚ Commons Codec
190 β”‚ Active   β”‚  80 β”‚ 3.2.0                  β”‚ Commons Net
191 β”‚ Active   β”‚  80 β”‚ 4.2.3                  β”‚ Apache HttpClient OSGi bundle
192 β”‚ Active   β”‚  80 β”‚ 4.2.3                  β”‚ Apache HttpCore OSGi bundle
193 β”‚ Active   β”‚  80 β”‚ 3.1.0.7                β”‚ Apache ServiceMix :: Bundles :: commons-httpclient
194 β”‚ Active   β”‚  80 β”‚ 2.3.0                  β”‚ openHAB 1.x Compatibility Layer
196 β”‚ Active   β”‚  80 β”‚ 2.1.0.201706190930     β”‚ MySensors Binding
197 β”‚ Active   β”‚  80 β”‚ 0.9.0.201701210957     β”‚ WeatherUnderground Binding
198 β”‚ Active   β”‚  80 β”‚ 1.1.1.201605111122     β”‚ Swagger Provider
199 β”‚ Active   β”‚  80 β”‚ 2.3.1                  β”‚ Gson
200 β”‚ Active   β”‚  80 β”‚ 2.1.0                  β”‚ json-path
201 β”‚ Active   β”‚  80 β”‚ 3.12.0.OH              β”‚ nrjavaserial
207 β”‚ Active   β”‚  80 β”‚ 1.5.8                  β”‚ swagger-core
208 β”‚ Active   β”‚  80 β”‚ 1.5.8                  β”‚ swagger-jaxrs
209 β”‚ Active   β”‚  80 β”‚ 1.5.8                  β”‚ swagger-models
210 β”‚ Active   β”‚  80 β”‚ 2.2                    β”‚ json-smart
211 β”‚ Active   β”‚  80 β”‚ 3.4.0                  β”‚ Apache Commons Lang
212 β”‚ Active   β”‚  80 β”‚ 0.10.0.oh230           β”‚ Eclipse SmartHome Automation API
213 β”‚ Active   β”‚  80 β”‚ 0.10.0.oh230           β”‚ Eclipse SmartHome Automation commands
214 β”‚ Active   β”‚  80 β”‚ 0.10.0.oh230           β”‚ Eclipse SmartHome Automation Core
215 β”‚ Active   β”‚  80 β”‚ 0.10.0.oh230           β”‚ Eclipse SmartHome Automation Module Core
216 β”‚ Active   β”‚  80 β”‚ 0.10.0.oh230           β”‚ Eclipse SmartHome Automation Media Modules
217 β”‚ Active   β”‚  80 β”‚ 0.10.0.oh230           β”‚ Eclipse SmartHome Automation Module Script
218 β”‚ Active   β”‚  80 β”‚ 0.10.0.oh230           β”‚ Eclipse SmartHome Automation Script Globals
219 β”‚ Active   β”‚  80 β”‚ 0.10.0.oh230           β”‚ Eclipse SmartHome Automation Script RuleSupport
220 β”‚ Active   β”‚  80 β”‚ 0.10.0.oh230           β”‚ Eclipse SmartHome Automation Module Timer
221 β”‚ Active   β”‚  80 β”‚ 0.10.0.oh230           β”‚ Eclipse SmartHome Automation GSON Parser
222 β”‚ Active   β”‚  80 β”‚ 0.10.0.oh230           β”‚ Eclipse SmartHome Automation Providers
223 β”‚ Active   β”‚  80 β”‚ 0.10.0.oh230           β”‚ Eclipse SmartHome Automation REST API
224 β”‚ Active   β”‚  80 β”‚ 0.10.0.oh230           β”‚ Astro Binding
225 β”‚ Active   β”‚  80 β”‚ 0.10.0.oh230           β”‚ ntp Binding
226 β”‚ Active   β”‚  80 β”‚ 0.10.0.oh230           β”‚ YahooWeather Binding
227 β”‚ Active   β”‚  80 β”‚ 0.10.0.oh230           β”‚ Eclipse SmartHome Configuration USB-Serial Discovery
228 β”‚ Active   β”‚  80 β”‚ 0.10.0.oh230           β”‚ Eclipse SmartHome Configuration USB-Serial Discovery Linux sysf Scanning
229 β”‚ Active   β”‚  80 β”‚ 0.10.0.oh230           β”‚ Eclipse SmartHome Config Serial
230 β”‚ Active   β”‚  80 β”‚ 0.10.0.oh230           β”‚ Eclipse SmartHome IoT Marketplace Extension Service
231 β”‚ Active   β”‚  80 β”‚ 0.10.0.oh230           β”‚ Eclipse SmartHome Serial Transport
232 β”‚ Active   β”‚  80 β”‚ 0.10.0.oh230           β”‚ Eclipse SmartHome Serial Transport for RXTX
233 β”‚ Active   β”‚  75 β”‚ 0.10.0.oh230           β”‚ Eclipse SmartHome Exec Transformation Service
234 β”‚ Active   β”‚  75 β”‚ 0.10.0.oh230           β”‚ Eclipse SmartHome JavaScript Transformation Service
235 β”‚ Active   β”‚  75 β”‚ 0.10.0.oh230           β”‚ Eclipse SmartHome JSonPath Transformation Service
236 β”‚ Active   β”‚  75 β”‚ 0.10.0.oh230           β”‚ Eclipse SmartHome Map Transformation Service
237 β”‚ Active   β”‚  75 β”‚ 0.10.0.oh230           β”‚ Eclipse SmartHome RegEx Transformation Service
238 β”‚ Active   β”‚  75 β”‚ 0.10.0.oh230           β”‚ Eclipse SmartHome Scale Transformation Service
239 β”‚ Active   β”‚  75 β”‚ 0.10.0.oh230           β”‚ Eclipse SmartHome XPath Transformation Service
240 β”‚ Active   β”‚  75 β”‚ 0.10.0.oh230           β”‚ Eclipse SmartHome Xslt Transformation Service
241 β”‚ Active   β”‚  80 β”‚ 0.10.0.oh230           β”‚ Eclipse SmartHome Basic UI, Fragments: 257
242 β”‚ Active   β”‚  80 β”‚ 0.10.0.oh230           β”‚ Eclipse SmartHome WebApp UI, Fragments: 258
243 β”‚ Active   β”‚  80 β”‚ 0.10.0.oh230           β”‚ Eclipse SmartHome Paper UI, Fragments: 261
245 β”‚ Active   β”‚  80 β”‚ 1.12.0                 β”‚ openHAB MQTT Binding
247 β”‚ Active   β”‚  80 β”‚ 1.12.0                 β”‚ openHAB Weather Binding
253 β”‚ Active   β”‚  80 β”‚ 2.3.0                  β”‚ ZoneMinder Binding
254 β”‚ Active   β”‚  80 β”‚ 2.3.0                  β”‚ openHAB REST Documentation
255 β”‚ Active   β”‚  80 β”‚ 1.12.0                 β”‚ openHAB MQTT Transport Bundle
256 β”‚ Active   β”‚  80 β”‚ 1.12.0                 β”‚ openHAB RRD4j Persistence Bundle
257 β”‚ Resolved β”‚  75 β”‚ 2.3.0                  β”‚ openHAB Basic UI Fragment, Hosts: 241
258 β”‚ Resolved β”‚  75 β”‚ 2.3.0                  β”‚ openHAB Classic UI Fragment, Hosts: 242
259 β”‚ Active   β”‚  80 β”‚ 2.3.0                  β”‚ HABmin User Interface
260 β”‚ Active   β”‚  80 β”‚ 2.3.0                  β”‚ HABPanel User Interface
261 β”‚ Resolved β”‚  75 β”‚ 2.3.0                  β”‚ openHAB Paper UI Theme Fragment, Hosts: 243
262 β”‚ Active   β”‚  80 β”‚ 0.9.10.v20160429-1435  β”‚ reflections (wrap)
263 β”‚ Active   β”‚  80 β”‚ 1.5.8.v20160511-1038   β”‚ swagger-jersey2-jaxrs (wrap)
274 β”‚ Active   β”‚  80 β”‚ 2.4.0.201807242215     β”‚ ZWave Binding
284 β”‚ Active   β”‚  80 β”‚ 1.12.0                 β”‚ openHAB Serial Binding
286 β”‚ Active   β”‚  80 β”‚ 2.4.0.201806241822     β”‚ Chromecast Binding
314 β”‚ Active   β”‚  80 β”‚ 1.0.11                 β”‚ com.zsmartsystems.zigbee
315 β”‚ Active   β”‚  80 β”‚ 1.0.11                 β”‚ com.zsmartsystems.zigbee.dongle.cc2531
316 β”‚ Active   β”‚  80 β”‚ 1.0.11                 β”‚ com.zsmartsystems.zigbee.dongle.ember
317 β”‚ Active   β”‚  80 β”‚ 1.0.11                 β”‚ com.zsmartsystems.zigbee.dongle.telegesis
318 β”‚ Active   β”‚  80 β”‚ 1.0.11                 β”‚ com.zsmartsystems.zigbee.dongle.xbee
319 β”‚ Active   β”‚  80 β”‚ 2.3.0                  β”‚ ZigBee Binding
320 β”‚ Active   β”‚  80 β”‚ 2.3.0                  β”‚ ZigBee CC2531 Binding
321 β”‚ Active   β”‚  80 β”‚ 2.3.0                  β”‚ ZigBee Ember Binding
322 β”‚ Active   β”‚  80 β”‚ 2.3.0                  β”‚ ZigBee Telegesis Binding
323 β”‚ Active   β”‚  80 β”‚ 2.3.0                  β”‚ ZigBee XBee Binding
openhab>                                                            

I just feel kind of lost.

@5iver

I don’t know how to modify your udev rule to work with my hardware, adding group and mode like you have accomplishes nothing, IE it doesn’t change the way the device is listed when I β€œls -la”

Thanks though

Did you reboot or rerun the udev rules? This should work…

SUBSYSTEM=="tty", ATTRS{idVendor}=="0451", ATTRS{idProduct}=="16a8", ATTRS{serial}=="__0X00124B000E896C97", SYMLINK+="ttyUSB_cc2531", GROUP="dialout", MODE="0666"

You can test your udev rules running against a specific device, before actually running them, by using…

udevadm test `udevadm info -a /dev/ttyUSB_cc2531| grep "looking at device"| sed "s/looking at device '//"| sed "s/'://"`

The symlink won’t be put into the group, but the target of the symlink will be…

[root@fedora01 /]# ls -la /dev/ |grep ttyUSB
crw-rw-rw-   1 root dialout 188,   0 Aug 12 17:44 ttyUSB0
crw-rw-rw-   1 root dialout 188,   1 Aug 12 17:44 ttyUSB1
lrwxrwxrwx   1 root root           7 Aug 10 15:30 ttyUSB-5 -> ttyUSB0
lrwxrwxrwx   1 root root           7 Aug 10 15:30 ttyUSB-55 -> ttyUSB1

What do you see when you run (making sure you openhab account is in dialout and tty)…

# id openhab
uid=964(openhab) gid=963(openhab) groups=963(openhab),5(tty),18(dialout)

If you want to keep the nonstandard name, you may also want to try putting the EXTRA_JAVA_OPTS at the top of start.sh, in case the way you are doing it isnt working. This is what I have for setting up JSR223…

export EXTRA_JAVA_OPTS="-Xbootclasspath/a:/opt/openhab2/conf/jython/jython-standalone-2.7.0.jar -Dpython.home=/opt/openhab2/conf/jython -Dpython.path=/opt/openhab2/conf/lib"

A random thing to check when this is happening, is to look into /var/lock and see if you have a LCK..ttyUSB_cc2531 file. You should, if everything is working OK. I had been running OH as root, but when I changed it to an openhab account, I found that directory did not have permissions to allow the openhab account to write the lock file, and found errors showing this in journalctl…

Aug 12 18:35:15 fedora01 start.sh[7448]: Launching the openHAB runtime...
Aug 12 18:36:17 fedora01 start.sh[7448]: check_group_uucp(): error testing lock file creation Error details:Permission deniedcheck_lock_status: No permission to create lock file.
Aug 12 18:36:17 fedora01 start.sh[7448]: RXTX fhs_lock() Error: opening lock file: /var/lock/LCK..ttyUSB-55: Permission denied. FAILED TO OPEN: No such file or directory

This is a complete mystery that I’m currently looking into, but I’ve temporarily given rwx to everyone until I can figure it out. I’m also using snapshot 1325, so it may be related to some of the recent ESH changes or an updated nrjavaserial.

Hey everyone,

sorry for the wall of text.

I acquired a Elelabs ZigBee USB stick (uses a EM358) a while ago and have been using it for a few weeks without any big issues.

However, after I was done with testing I added the rest of my ZigBee devices and suddenly after a restart all of my ZigBee nodes are offline and won’t come back. I even reverted to an older config and yet the nodes are still not coming back.

So I reset the controller, removed all nodes and added them again just for it to happen again yesterday, all nodes were freshly added and are now dead again.

Since it ran for weeks without issues I assume one of the new devices messed up the network but I’m not sure which and I’m not sure if I can recover from this without having to add all nodes every time this happens. So before readding all nodes again I thought I would ask here.

I’m was using the Docker image 2.3.0-amd64-debian when it happened. When starting with this image the controller will come online but only 1-4 random nodes will come online with it, none of these are controllable however.

I also tried 2.4.0-snapshot-amd64-debian which handles things slightly differently. Now OpenHAB is stuck in a endless discovery loop at startup and the ZigBee log just keeps flowing forever. After like 10 minutes it will have discovered all nodes one by one (even ones that aren’t even powered) but none of them will be controllable.

Adding a fresh device will work and the controller can talk to it just fine. Until this happens again that is.
Actually, I can’t add a new node until I cleanup manually.

I’m seriously confused as to why this keeps happening and since the config rollback doesn’t help I assume something at the network level gets messed up with one of the devices I added? Does the Ember stick keep its own config like the Z-wave sticks do or has the controller simply removed all nodes from the network (for whatever reason)?

I took a debug log with 2.3.0 on startup after the issue occurred and I can post it (assuming it contains no sensitive info?). Not sure if it’s of any help though since the network is already messed up at this point.

Just for reference, these are the devices I added a day before the network died:

  • 1x Innr RB 185 C (RGBW E27 bulb)
  • 5x Philips LCT003 (RGBW GU10 spot)
  • 2x Philips LTW012 (W E14 bulb)
  • 1x Philips LST002 (RGBW LED strip)
  • 1x Philips RWL021 (Dimmer switch)
  • 1x Philips SML001 (Motion sensor)

That makes for a total of ~24 devices on this network (including the existing).

Everything kept working for a full day, at night I noticed that the motion sensor stopped reporting its luminance, the next morning the network was unresponsive, after a restart it was dead. Controller comes up with a few random nodes, nothing responds.

I’m assuming the issue lies with one of the battery powered ones or the LED strip since I added plenty of bulbs and spots before that and they all worked fine. Still, I hope this issue can be diagnosed before continuing, it sucks that one device can take your whole network down like this.

So, anybody experienced this before? Any idea how to get the network back without pairing everything again? Any idea what could cause this?

Exactly the same issue I had. Untill @chris has changed the Zigbee binding, I have given up on Zigbee.
Lucky for me, my Zigbee devices are all just test devices.

1 Like