Zigbee binding

zigbee
beginners
Tags: #<Tag:0x00007fd30cec3df8> #<Tag:0x00007fd30cec3cb8>

(Chris Jackson) #944

This means that the binding has not discovered the channels. These devices do not respect the standards and go to sleep very quickly and need to be woken up a lot to allow this to complete.


(Mattwire) #945

Any thoughts on this? It’s a telegesis (Qivicon) dongle on linux and with the latest snapshot (#1251), zigbee binding version 2.3.0.201804060804 it’s failing to initialise the dongle. Specifically it seems to be failing with Error setting Telegesis Prompt 1 register

Logs below:

2018-04-08 18:08:42.001 [DEBUG] [org.openhab.binding.zigbee.telegesis] - BundleEvent STARTING - org.openhab.binding.zigbee.telegesis
2018-04-08 18:08:42.022 [DEBUG] [org.openhab.binding.zigbee.telegesis] - ServiceEvent REGISTERED - {org.eclipse.smarthome.core.thing.binding.ThingHandlerFactory}={service.id=403, service.bundleid=242, service.scope=bundle, component.name=org.openhab.binding.zigbee.telegesis.internal.TelegesisHandlerFactory, component.id=236} - org.openhab.binding.zigbee.telegesis
2018-04-08 18:08:42.044 [DEBUG] [org.openhab.binding.zigbee.telegesis] - BundleEvent STARTED - org.openhab.binding.zigbee.telegesis
2018-04-08 18:08:42.094 [DEBUG] [bee.discovery.ZigBeeDiscoveryService] - Creating ZigBee discovery service for zigbee:coordinator_telegesis:8ffcabae
2018-04-08 18:08:42.099 [DEBUG] [bee.discovery.ZigBeeDiscoveryService] - Activating ZigBee discovery service for zigbee:coordinator_telegesis:8ffcabae
2018-04-08 18:08:42.105 [DEBUG] [org.openhab.binding.zigbee.telegesis] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.discovery.DiscoveryService}={service.id=404, service.bundleid=242, service.scope=singleton} - org.openhab.binding.zigbee.telegesis
2018-04-08 18:08:42.127 [DEBUG] [org.openhab.binding.zigbee.telegesis] - ServiceEvent REGISTERED - {org.eclipse.smarthome.core.thing.binding.firmware.FirmwareUpdateHandler}={service.id=405, service.bundleid=242, service.scope=singleton} - org.openhab.binding.zigbee.telegesis
2018-04-08 18:08:42.170 [DEBUG] [e.telegesis.handler.TelegesisHandler] - Initializing ZigBee Telegesis serial bridge handler.

==> /var/log/openhab2/events.log <==
2018-04-08 18:08:42.175 [hingStatusInfoChangedEvent] - 'zigbee:coordinator_telegesis:8ffcabae' changed from UNINITIALIZED (HANDLER_MISSING_ERROR) to INITIALIZING

==> /var/log/openhab2/openhab.log <==
2018-04-08 18:08:42.173 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Initializing ZigBee network [zigbee:coordinator_telegesis:8ffcabae].
2018-04-08 18:08:42.184 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Channel -1
2018-04-08 18:08:42.187 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - PANID 52217
2018-04-08 18:08:42.190 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - EPANID DFB27E96C13B08C5
2018-04-08 18:08:42.192 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Key null
2018-04-08 18:08:42.195 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Key String 
2018-04-08 18:08:42.199 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Key initialised 56043691D811820755B597DBD1E83B95
2018-04-08 18:08:42.203 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Key final array 56043691D811820755B597DBD1E83B95
2018-04-08 18:08:42.207 [DEBUG] [e.telegesis.handler.TelegesisHandler] - ZigBee Telegesis Coordinator opening Port:'/dev/zigbee' PAN:cbf9, EPAN:DFB27E96C13B08C5, Channel:-1
2018-04-08 18:08:42.211 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Scheduling ZigBee start

==> /var/log/openhab2/events.log <==
2018-04-08 18:08:42.220 [hingStatusInfoChangedEvent] - 'zigbee:coordinator_telegesis:8ffcabae' changed from INITIALIZING to UNKNOWN

==> /var/log/openhab2/openhab.log <==
2018-04-08 18:08:43.215 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - ZigBee network starting
2018-04-08 18:08:43.218 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Initialising ZigBee coordinator
2018-04-08 18:08:43.223 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Key initialise 56043691D811820755B597DBD1E83B95
2018-04-08 18:08:43.230 [DEBUG] [ngle.telegesis.ZigBeeDongleTelegesis] - Telegesis dongle initialize.
2018-04-08 18:08:43.232 [DEBUG] [ding.zigbee.handler.ZigBeeSerialPort] - Connecting to serial port [/dev/zigbee] at 19200 baud, flow control FLOWCONTROL_OUT_NONE.
2018-04-08 18:08:43.248 [DEBUG] [ding.zigbee.handler.ZigBeeSerialPort] - Serial port [/dev/zigbee] is initialized.
2018-04-08 18:08:43.251 [DEBUG] [gesis.internal.TelegesisFrameHandler] - TelegesisFrameHandler thread started
2018-04-08 18:08:43.252 [DEBUG] [gesis.internal.TelegesisFrameHandler] - TX Telegesis queue: 1
2018-04-08 18:08:43.255 [DEBUG] [gesis.internal.TelegesisFrameHandler] - TX Telegesis: TelegesisSetPromptEnable1Command [configuration=8804]
2018-04-08 18:08:43.260 [DEBUG] [gesis.internal.TelegesisFrameHandler] - TX Telegesis Data: 41 54 53 30 45 3D 38 38 30 34 0D 0A
2018-04-08 18:08:43.752 [DEBUG] [gesis.internal.TelegesisFrameHandler] - Telegesis interrupted in sendRequest TelegesisSetPromptEnable1Command [configuration=8804]
2018-04-08 18:08:43.755 [DEBUG] [ngle.telegesis.ZigBeeDongleTelegesis] - Error setting Telegesis Prompt 1 register
2018-04-08 18:08:43.757 [DEBUG] [nal.ZigBeeNetworkStateSerializerImpl] - Loading ZigBee network state: Start.
2018-04-08 18:08:43.774 [DEBUG] [nal.ZigBeeNetworkStateSerializerImpl] - Loading ZigBee network state: Done.
2018-04-08 18:08:43.777 [DEBUG] [bee.internal.ZigBeeNetworkDiscoverer] - Network discovery task starting

==> /var/log/openhab2/events.log <==
2018-04-08 18:08:43.784 [hingStatusInfoChangedEvent] - 'zigbee:coordinator_telegesis:8ffcabae' changed from UNKNOWN to OFFLINE: @text/zigbee.status.offline_initializefail

==> /var/log/openhab2/openhab.log <==
2018-04-08 18:08:44.317 [DEBUG] [gesis.internal.TelegesisFrameHandler] - RX Telegesis Data: 4F 4B
2018-04-08 18:08:44.320 [DEBUG] [gesis.internal.TelegesisFrameHandler] - RX Telegesis: TelegesisSetPromptEnable1Command [configuration=8804, status=SUCCESS]


(James Scott Jr) #946

Question: I just read in this thread that there should only be one zigbee coordinator in a home network. I have a Phillips Hue with some devices and I’m waiting on a CC2531EMK dongle to pickup five SengLed bulbs that don’t work with the Hue bridge.

Is the CC2531 going to be considered the second coordinator and therefore force me to turn off the hue bridge?

I’m trying to understand the restriction of Zigbee. Thanks in advance.


(Chris Jackson) #947

It’s a little stronger than that - there CAN ONLY be one coordinator in a network. That doesn’t prevent you having another system doing some controlling, although the ZigBee binding can currently only be configured as the coordinator. More importantly, there can only be one trust centre (which is normally the same as the coordinator). The trust centre does all the network access control, so even if the binding was modified so that it wasn’t a coordinator, you would still need to manage the joining through the single trust centre.

Yes.


(Roshan Milinda) #948

Hi @chris,

Right now what is the best Zigbee dongle to buy? Maybe a link to an online shop?
X Stick or TI2531 or Telegesis ETRX3

can you please point me to a USB dongle that works. Tried with TI2531 with no luck.

In theory, will all the ZigBee Alliance devices should work or only the devices its supported in the binding page?

I am looking at this


(Chris Jackson) #949

It’s a bit hard to answer, but I’ll give a current status…

Ember NCP is my favourite and I believe likely to be the best supported in future. Currently however there aren’t a lot of options for commercial devices - the Linear HUSBZB-1 is available in the US and is therefore currently a good option.

The Digi XStick is newly added - it’s being actively used by at least one person I know of and I’m actively supporting this so it should work ok. It should be easily available online.

The Telegesis is a good option at the moment - it’s well supported and many people are using it. I suspect that it will not be available long term though, and probably won’t support ZB3 features in future.

The TI2531 should also be fine, but currently it’s more of a DIY solution which means you have to program the chip, and it’s normally a bare board so is somewhat fragile.

It’s a bit hard to provide links to online shops without knowing where you are, but you can search I think…

Well, ZigBee is a huge standard with MANY different features. Ultimately the answer should be that any device will work, but without devices to test against, you shouldn’t assume that new devices will necessarily work. Note that I’m talking about new types of device - if you get a new bulb, it will work fine (99.9% anyway) - same with switches, sensors etc.

This is another story… I have no idea what this is as far as ZigBee goes. My guess is it is supporting some of the security or sensor functions in ZigBee, but video is WiFi. If so, then it could work ok, but please don’t blame me if it doesn’t :wink: .

If there are problems, we can look at improving support for any new devices - it is always easier if I have devices on hand, so if anyone is looking at a new device, then please think about sending me one if it doesn’t work so I can add support…

I hope that helps…


(Roshan Milinda) #950

Thank you @chris appreciate the reply. BTW I live in New Zealand :smiley::clinking_glasses:


(Chris Jackson) #951

Nice one :slight_smile: . I’m originally from NZ (Wgtn) but moved to the UK a few years back (I still support the ABs though! :wink: ).


(Daniel) #952

I have 6 Hue bulbs which have only ever been used with openHAB. (I don’t own a bridge or any other Zigbee devices.) They were working flawlessly with openHAB with a CC2531 until I was trying to add them to a group in my .items file and now for some unknown reason only 2 out of the 6 bulbs will connect. I’ve started with a fresh copy of 2.2, of the 2.3 snapshot, tried everything. It seems openHAB just isn’t talking with the others. I even enabled debug logging and it’s not getting any RX from the troublesome lights. I even went and flashed back the sniffer firmware real quick and it does pickup packets when I leave only one of the troublesome lights on so I know the lights are fine and I know the CC2531 is fine. I’m just at my wits end and not sure what to do now. I can try to provide any logs or whatever might help in getting things back working.

Thank you,
Daniel


(Scott Karns) #953

After upgrading my openhab2 install to openHAB 2.3.0~20180414125243-1 (Build #1257), I can no longer start the zigbee binding due to coordinator startup failures. I am running openHABian on a raspberry pi 3, which has been running solidly since I last updated openhab2 on January 4 this year.

Checking the installed zigbee related bundles shows:

openhab> bundle:list | grep -i zigbee                                                                                                                                                                                                                                                                                                                                                         
199 │ Active   │  80 │ 1.0.8                  │ com.zsmartsystems.zigbee
200 │ Active   │  80 │ 1.0.8                  │ com.zsmartsystems.zigbee.dongle.cc2531
201 │ Active   │  80 │ 1.0.8                  │ com.zsmartsystems.zigbee.dongle.ember
202 │ Active   │  80 │ 1.0.8                  │ com.zsmartsystems.zigbee.dongle.telegesis
203 │ Active   │  80 │ 1.0.8                  │ com.zsmartsystems.zigbee.dongle.xbee
234 │ Active   │  80 │ 2.3.0.201804141026     │ ZigBee Binding
235 │ Active   │  80 │ 2.3.0.201804141026     │ ZigBee CC2531 Binding
236 │ Active   │  80 │ 2.3.0.201804141026     │ ZigBee Ember Binding
237 │ Active   │  80 │ 2.3.0.201804141026     │ ZigBee Telegesis Binding
238 │ Active   │  80 │ 2.3.0.201804141026     │ ZigBee XBee Binding

The zigbee log (logging set to DEBUG level):

2018-04-16 08:40:15.289 [DEBUG] [org.openhab.binding.zigbee          ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.core.thing.binding.ThingHandlerFactory}={service.id=122, service.bundleid=234, service.scope=bundle, component.name=org.openhab.binding.zigbee.internal.ZigBeeHandlerFactory, component.id=18} - org.openhab.binding.zigbee
2018-04-16 08:40:15.295 [DEBUG] [org.openhab.binding.zigbee          ] - BundleEvent STARTING - org.openhab.binding.zigbee
2018-04-16 08:40:15.298 [DEBUG] [org.openhab.binding.zigbee          ] - BundleEvent STARTED - org.openhab.binding.zigbee
2018-04-16 08:40:15.307 [DEBUG] [org.openhab.binding.zigbee          ] - BundleEvent [unknown:512] - org.openhab.binding.zigbee
2018-04-16 08:40:15.318 [DEBUG] [org.openhab.binding.zigbee.cc2531   ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.core.thing.binding.ThingHandlerFactory}={service.id=123, service.bundleid=235, service.scope=bundle, component.name=org.openhab.binding.zigbee.cc2531.internal.CC2531HandlerFactory, component.id=19} - org.openhab.binding.zigbee.cc2531
2018-04-16 08:40:15.322 [DEBUG] [org.openhab.binding.zigbee.cc2531   ] - BundleEvent STARTING - org.openhab.binding.zigbee.cc2531
2018-04-16 08:40:15.325 [DEBUG] [org.openhab.binding.zigbee.cc2531   ] - BundleEvent STARTED - org.openhab.binding.zigbee.cc2531
2018-04-16 08:40:15.335 [DEBUG] [org.openhab.binding.zigbee.cc2531   ] - BundleEvent [unknown:512] - org.openhab.binding.zigbee.cc2531
2018-04-16 08:40:15.345 [DEBUG] [org.openhab.binding.zigbee.ember    ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.core.thing.binding.ThingHandlerFactory}={service.id=124, service.bundleid=236, service.scope=bundle, component.name=org.openhab.binding.zigbee.ember.internal.EmberHandlerFactory, component.id=20} - org.openhab.binding.zigbee.ember
2018-04-16 08:40:15.349 [DEBUG] [org.openhab.binding.zigbee.ember    ] - BundleEvent STARTING - org.openhab.binding.zigbee.ember
2018-04-16 08:40:15.351 [DEBUG] [org.openhab.binding.zigbee.ember    ] - BundleEvent STARTED - org.openhab.binding.zigbee.ember
2018-04-16 08:40:15.358 [DEBUG] [org.openhab.binding.zigbee.ember    ] - BundleEvent [unknown:512] - org.openhab.binding.zigbee.ember
2018-04-16 08:40:15.368 [DEBUG] [org.openhab.binding.zigbee.telegesis] - ServiceEvent REGISTERED - {org.eclipse.smarthome.core.thing.binding.ThingHandlerFactory}={service.id=125, service.bundleid=237, service.scope=bundle, component.name=org.openhab.binding.zigbee.telegesis.internal.TelegesisHandlerFactory, component.id=21} - org.openhab.binding.zigbee.telegesis
2018-04-16 08:40:15.372 [DEBUG] [org.openhab.binding.zigbee.telegesis] - BundleEvent STARTING - org.openhab.binding.zigbee.telegesis
2018-04-16 08:40:15.375 [DEBUG] [org.openhab.binding.zigbee.telegesis] - BundleEvent STARTED - org.openhab.binding.zigbee.telegesis
2018-04-16 08:40:15.382 [DEBUG] [org.openhab.binding.zigbee.telegesis] - BundleEvent [unknown:512] - org.openhab.binding.zigbee.telegesis
2018-04-16 08:40:15.392 [DEBUG] [org.openhab.binding.zigbee.xbee     ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.core.thing.binding.ThingHandlerFactory}={service.id=126, service.bundleid=238, service.scope=bundle, component.name=org.openhab.binding.zigbee.xbee.internal.XBeeHandlerFactory, component.id=22} - org.openhab.binding.zigbee.xbee
2018-04-16 08:40:15.396 [DEBUG] [org.openhab.binding.zigbee.xbee     ] - BundleEvent STARTING - org.openhab.binding.zigbee.xbee
2018-04-16 08:40:15.398 [DEBUG] [org.openhab.binding.zigbee.xbee     ] - BundleEvent STARTED - org.openhab.binding.zigbee.xbee
2018-04-16 08:40:15.405 [DEBUG] [org.openhab.binding.zigbee.xbee     ] - BundleEvent [unknown:512] - org.openhab.binding.zigbee.xbee
2018-04-16 08:40:47.882 [DEBUG] [bee.discovery.ZigBeeDiscoveryService] - Creating ZigBee discovery service for zigbee:coordinator_cc2531:b0ec0a7d
2018-04-16 08:40:47.885 [DEBUG] [bee.discovery.ZigBeeDiscoveryService] - Activating ZigBee discovery service for zigbee:coordinator_cc2531:b0ec0a7d
2018-04-16 08:40:47.896 [DEBUG] [org.openhab.binding.zigbee.cc2531   ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.discovery.DiscoveryService}={service.id=286, service.bundleid=235, service.scope=singleton} - org.openhab.binding.zigbee.cc2531
2018-04-16 08:40:47.981 [DEBUG] [.zigbee.cc2531.handler.CC2531Handler] - Initializing ZigBee CC2531 serial bridge handler.
2018-04-16 08:40:47.985 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Initializing ZigBee network [zigbee:coordinator_cc2531:b0ec0a7d].
2018-04-16 08:40:47.988 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Channel 11
2018-04-16 08:40:47.989 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - PANID -11488
2018-04-16 08:40:47.991 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - EPANID C744DE63C7028774
2018-04-16 08:40:47.995 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Key 8A D4 C4 18 A1 77 08 1C F8 54 6B 80 23 B3 86 AF
2018-04-16 08:40:47.996 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Key String 8A D4 C4 18 A1 77 08 1C F8 54 6B 80 23 B3 86 AF
2018-04-16 08:40:48.001 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Key final array 8AD4C418A177081CF8546B8023B386AF
2018-04-16 08:40:48.045 [DEBUG] [.zigbee.cc2531.handler.CC2531Handler] - ZigBee CC2531 Coordinator opening Port:'/dev/ttyUSBzigbee' PAN:ffffd320, EPAN:C744DE63C7028774, Channel:11
2018-04-16 08:40:48.053 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Scheduling ZigBee start
2018-04-16 08:40:48.085 [DEBUG] [org.openhab.binding.zigbee          ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.core.ConfigDescriptionProvider}={service.id=287, service.bundleid=234, service.scope=singleton} - org.openhab.binding.zigbee
2018-04-16 08:40:48.090 [DEBUG] [org.openhab.binding.zigbee          ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.core.ConfigDescriptionProvider}={service.id=288, service.bundleid=234, service.scope=singleton} - org.openhab.binding.zigbee
2018-04-16 08:40:48.105 [DEBUG] [org.openhab.binding.zigbee          ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.core.thing.binding.firmware.FirmwareUpdateHandler}={service.id=289, service.bundleid=234, service.scope=singleton} - org.openhab.binding.zigbee
2018-04-16 08:40:48.224 [DEBUG] [org.openhab.binding.zigbee          ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.core.thing.binding.firmware.FirmwareUpdateHandler}={service.id=290, service.bundleid=234, service.scope=singleton} - org.openhab.binding.zigbee
2018-04-16 08:40:48.256 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - B0CE18140306E556: Initializing ZigBee thing handler zigbee:device:b0ec0a7d:b0ce18140306e556
2018-04-16 08:40:48.256 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - B0CE1814030107C6: Initializing ZigBee thing handler zigbee:device:b0ec0a7d:b0ce1814030107c6
2018-04-16 08:40:48.262 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - B0CE1814030107C6: Coordinator status changed to UNKNOWN.
2018-04-16 08:40:48.264 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - B0CE1814030107C6: Coordinator is unknown or not online.
2018-04-16 08:40:48.262 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - B0CE18140306E556: Coordinator status changed to UNKNOWN.
2018-04-16 08:40:48.268 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - B0CE18140306E556: Coordinator is unknown or not online.
2018-04-16 08:40:48.286 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - B0CE1814030107C6: Channel zigbee:device:b0ec0a7d:b0ce1814030107c6:B0CE1814030107C6_1_switch_level linked - polling started.
2018-04-16 08:40:48.286 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - B0CE18140306E556: Channel zigbee:device:b0ec0a7d:b0ce18140306e556:B0CE18140306E556_1_switch_level linked - polling started.
2018-04-16 08:40:48.287 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - B0CE1814030107C6: Channel zigbee:device:b0ec0a7d:b0ce1814030107c6:B0CE1814030107C6_1_color_temperature linked - polling started.
2018-04-16 08:40:48.723 [DEBUG] [org.openhab.binding.zigbee          ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.core.ConfigDescriptionProvider}={service.id=295, service.bundleid=234, service.scope=singleton} - org.openhab.binding.zigbee
2018-04-16 08:40:48.738 [DEBUG] [org.openhab.binding.zigbee          ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.core.thing.binding.firmware.FirmwareUpdateHandler}={service.id=296, service.bundleid=234, service.scope=singleton} - org.openhab.binding.zigbee
2018-04-16 08:40:48.776 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 000B57FFFE2EFE6A: Initializing ZigBee thing handler zigbee:device:b0ec0a7d:000b57fffe2efe6a
2018-04-16 08:40:48.779 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 000B57FFFE2EFE6A: Coordinator status changed to UNKNOWN.
2018-04-16 08:40:48.781 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 000B57FFFE2EFE6A: Channel zigbee:device:b0ec0a7d:000b57fffe2efe6a:000B57FFFE2EFE6A_1_switch_level linked - polling started.
2018-04-16 08:40:48.784 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 000B57FFFE2EFE6A: Coordinator is unknown or not online.
2018-04-16 08:40:48.870 [DEBUG] [org.openhab.binding.zigbee          ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.core.ConfigDescriptionProvider}={service.id=299, service.bundleid=234, service.scope=singleton} - org.openhab.binding.zigbee
2018-04-16 08:40:48.884 [DEBUG] [org.openhab.binding.zigbee          ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.core.thing.binding.firmware.FirmwareUpdateHandler}={service.id=300, service.bundleid=234, service.scope=singleton} - org.openhab.binding.zigbee
2018-04-16 08:40:48.901 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 001788010211ECB8: Initializing ZigBee thing handler zigbee:device:b0ec0a7d:001788010211ecb8
2018-04-16 08:40:48.904 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 001788010211ECB8: Coordinator status changed to UNKNOWN.
2018-04-16 08:40:48.906 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 001788010211ECB8: Coordinator is unknown or not online.
2018-04-16 08:40:48.919 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 001788010211ECB8: Channel zigbee:device:b0ec0a7d:001788010211ecb8:001788010211ECB8_1_switch_onoff linked - polling started.
2018-04-16 08:40:48.921 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 001788010211ECB8: Channel zigbee:device:b0ec0a7d:001788010211ecb8:001788010211ECB8_2_battery_level linked - polling started.
2018-04-16 08:40:48.922 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 001788010211ECB8: Channel zigbee:device:b0ec0a7d:001788010211ecb8:001788010211ECB8_2_measurement_illuminance linked - polling started.
2018-04-16 08:40:48.923 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 001788010211ECB8: Channel zigbee:device:b0ec0a7d:001788010211ecb8:001788010211ECB8_2_sensor_occupancy linked - polling started.
2018-04-16 08:40:48.926 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 001788010211ECB8: Channel zigbee:device:b0ec0a7d:001788010211ecb8:001788010211ECB8_2_measurement_temperature linked - polling started.
2018-04-16 08:40:48.922 [DEBUG] [org.openhab.binding.zigbee          ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.core.ConfigDescriptionProvider}={service.id=301, service.bundleid=234, service.scope=singleton} - org.openhab.binding.zigbee
2018-04-16 08:40:48.938 [DEBUG] [org.openhab.binding.zigbee          ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.core.thing.binding.firmware.FirmwareUpdateHandler}={service.id=302, service.bundleid=234, service.scope=singleton} - org.openhab.binding.zigbee
2018-04-16 08:40:48.952 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - B0CE181403019F87: Initializing ZigBee thing handler zigbee:device:b0ec0a7d:b0ce181403019f87
2018-04-16 08:40:48.955 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - B0CE181403019F87: Coordinator status changed to UNKNOWN.
2018-04-16 08:40:48.966 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - B0CE181403019F87: Channel zigbee:device:b0ec0a7d:b0ce181403019f87:B0CE181403019F87_1_switch_level linked - polling started.
2018-04-16 08:40:48.965 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - B0CE181403019F87: Channel zigbee:device:b0ec0a7d:b0ce181403019f87:B0CE181403019F87_1_color_temperature linked - polling started.
2018-04-16 08:40:48.968 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - B0CE181403019F87: Coordinator is unknown or not online.
2018-04-16 08:40:49.057 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - ZigBee network starting
2018-04-16 08:40:49.060 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Initialising ZigBee coordinator
2018-04-16 08:40:49.121 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Key initialise 8AD4C418A177081CF8546B8023B386AF
2018-04-16 08:40:49.135 [DEBUG] [e.dongle.cc2531.ZigBeeDongleTiCc2531] - CC2531 transport initialize
2018-04-16 08:40:49.143 [DEBUG] [ding.zigbee.handler.ZigBeeSerialPort] - Connecting to serial port [/dev/ttyUSBzigbee] at 115200 baud, flow control FLOWCONTROL_OUT_RTSCTS.
2018-04-16 08:40:49.159 [DEBUG] [ding.zigbee.handler.ZigBeeSerialPort] - Serial port [/dev/ttyUSBzigbee] is initialized.
2018-04-16 08:40:49.174 [DEBUG] [31.network.impl.CommandInterfaceImpl] - ->  SYS_RESET (Packet: subsystem=null, length=1, apiId=41 00, data=FE 01 41 00 01 41, checksum=41, error=false) 
2018-04-16 08:40:50.784 [DEBUG] [com.zsmartsystems.zigbee            ] - BundleEvent STARTING - com.zsmartsystems.zigbee
2018-04-16 08:40:50.805 [DEBUG] [com.zsmartsystems.zigbee            ] - BundleEvent STARTED - com.zsmartsystems.zigbee
2018-04-16 08:40:50.886 [DEBUG] [m.zsmartsystems.zigbee.dongle.cc2531] - BundleEvent STARTING - com.zsmartsystems.zigbee.dongle.cc2531
2018-04-16 08:40:50.915 [DEBUG] [m.zsmartsystems.zigbee.dongle.cc2531] - BundleEvent STARTED - com.zsmartsystems.zigbee.dongle.cc2531
2018-04-16 08:40:50.964 [DEBUG] [om.zsmartsystems.zigbee.dongle.ember] - BundleEvent STARTING - com.zsmartsystems.zigbee.dongle.ember
2018-04-16 08:40:51.025 [DEBUG] [om.zsmartsystems.zigbee.dongle.ember] - BundleEvent STARTED - com.zsmartsystems.zigbee.dongle.ember
2018-04-16 08:40:51.069 [DEBUG] [smartsystems.zigbee.dongle.telegesis] - BundleEvent STARTING - com.zsmartsystems.zigbee.dongle.telegesis
2018-04-16 08:40:51.107 [DEBUG] [smartsystems.zigbee.dongle.telegesis] - BundleEvent STARTED - com.zsmartsystems.zigbee.dongle.telegesis
2018-04-16 08:40:51.116 [DEBUG] [com.zsmartsystems.zigbee.dongle.xbee] - BundleEvent STARTING - com.zsmartsystems.zigbee.dongle.xbee
2018-04-16 08:40:51.135 [DEBUG] [com.zsmartsystems.zigbee.dongle.xbee] - BundleEvent STARTED - com.zsmartsystems.zigbee.dongle.xbee
2018-04-16 08:40:54.864 [WARN ] [.cc2531.network.ZigBeeNetworkManager] - Dongle reset failed. Assuming bootloader is running and sending magic byte 0xef.
2018-04-16 08:40:59.868 [WARN ] [.cc2531.network.ZigBeeNetworkManager] - Attempt to get out from bootloader failed.
2018-04-16 08:40:59.901 [DEBUG] [ding.zigbee.handler.ZigBeeSerialPort] - Serial port '/dev/ttyUSBzigbee' closed.

I cleared /var/lib/openhab2/cache and /var/lib/openhab2/tmp before starting openhab2 after upgrading. I had experienced no problems starting openhab and more specifically, the zigbee binding since my previous update.

Any ideas @chris?

I may be able to revert to the previously installed version of openhab2 and capture the zigbee startup log for comparison.


(Chris Jackson) #954

The reported error is that the dongle can’t communicate with your dongle. I would double check the serial options, and reset the stick.

I don’t think reverting to an old version to grab the log will help at all. Nothing has changed with the TI driver, and the issue is a low level communication issue.


(Scott Karns) #955

I Performed a binary search and have determined that the last Zigbee binding that successfully works with my CC2531 coordinator is 2.4.0.201712240351. The next version after that one, 2.4.0-20171225.035150, fails. It is not the serial port, as version 2.4.0.201712240351 of the zigbee binding is running without error:

openhab> things list | sort
tradfri:0820:tradfrigw:65536 (Type=Thing, Status=UNINITIALIZED, Label=Trådfri Dimmer, Bridge=tradfri:gateway:tradfrigw)
unifi:client:CasaKarns:ritaipad (Type=Thing, Status=ONLINE, Label=Unifi: Rita's iPad, Bridge=unifi:controller:CasaKarns)
unifi:client:CasaKarns:ritakindle (Type=Thing, Status=ONLINE, Label=Unifi: Rita's Kindle, Bridge=unifi:controller:CasaKarns)
unifi:client:CasaKarns:ritaphone (Type=Thing, Status=ONLINE, Label=Unifi: Rita's S5, Bridge=unifi:controller:CasaKarns)
unifi:client:CasaKarns:scottphone (Type=Thing, Status=ONLINE, Label=Unifi: Scott's Note 4, Bridge=unifi:controller:CasaKarns)
unifi:controller:CasaKarns (Type=Bridge, Status=ONLINE, Label=Unifi Controller: #1, Bridge=null)
yamahareceiver:yamahaAV:5f9ec1b3_ed59_1900_4530_00a0de1b0fff (Type=Bridge, Status=UNINITIALIZED, Label=Yamaha Receiver HTR-4065, Bridge=null)
yamahareceiver:zone:5f9ec1b3_ed59_1900_4530_00a0de1b0fff:Main_Zone (Type=Thing, Status=UNINITIALIZED, Label=HTR-4065 Main_Zone, Bridge=yamahareceiver:yamahaAV:5f9ec1b3_ed59_1900_4530_00a0de1b0fff)
zigbee:coordinator_cc2531:b0ec0a7d (Type=Bridge, Status=ONLINE, Label=CC2531EMK Coordinator, Bridge=null)
zigbee:device:b0ec0a7d:000b57fffe2efe6a (Type=Thing, Status=ONLINE, Label=Tradfri Bulb1, Bridge=zigbee:coordinator_cc2531:b0ec0a7d)
zigbee:device:b0ec0a7d:001788010211ecb8 (Type=Thing, Status=ONLINE, Label=Philips SML001 Motion Detector, Bridge=zigbee:coordinator_cc2531:b0ec0a7d)
zigbee:device:b0ec0a7d:b0ce1814030107c6 (Type=Thing, Status=ONLINE, Label=SengLED CT Bulb2, Bridge=zigbee:coordinator_cc2531:b0ec0a7d)
zigbee:device:b0ec0a7d:b0ce181403019f87 (Type=Thing, Status=ONLINE, Label=SengLED CT Bulb1, Bridge=zigbee:coordinator_cc2531:b0ec0a7d)
zigbee:device:b0ec0a7d:b0ce18140306e556 (Type=Thing, Status=ONLINE, Label=SengLED Bulb1, Bridge=zigbee:coordinator_cc2531:b0ec0a7d)
zwave:device:zstickgen5:node2 (Type=Thing, Status=ONLINE, Label=Wall Dimmer, Bridge=zwave:serial_zstick:zstickgen5)
zwave:device:zstickgen5:node3 (Type=Thing, Status=OFFLINE (COMMUNICATION_ERROR): Node is not communicating with controller, Label=Keypad, Bridge=zwave:serial_zstick:zstickgen5)
zwave:device:zstickgen5:node4 (Type=Thing, Status=ONLINE, Label=Node 4, Bridge=zwave:serial_zstick:zstickgen5)
zwave:serial_zstick:zstickgen5 (Type=Bridge, Status=ONLINE, Label=Z-Wave Serial Controller, Bridge=null)

I suppose I can take a look at the changes introduced with the commits following the 2018-12-24 version.


(Chris Jackson) #956

What do you mean by a binary search?

There were absolutely no changes between these versions!

Ok, I’m only going on the error return which states that the dongle is not responding.

I don’t think we’ve got to that version yet :wink: . There have been some changes to the binding, but I believe none to the TI driver.


(Scott Karns) #957

I reverted to several snapshots within the time period of interest until I found the last snapshot that runs without error, as well as the following snapshot that does not, splitting the time intervals between test snapshots in half at each stage of my search.

I do see that that there were no changes to the binding bundle between 2017-12-17 and 2018-01-01, commits 13495d8 and fb60579 respectively. Hmmm, I’ll experiment some more, but I am able to run the 20171224 zigbee binding snapshot without errors.

Oops, obviously my typo. I should have typed 2017-12-24.

[Update 1: 2018-04-16]

In addition to openhab2/unstable, I tried installing the additional packages openhab2-addons/unstable and openhab2-addons-legacy, with the idea that perhaps there is some startup timing issue related to the time it takes to download bindings versus installing them from the .kar archives in /usr/share/openhab2/addons/. With only those changes, my zigbee coordinator is now working with the current openhab2/unstable snapshots – 2.3.0~20180414125243-1.

That’s not proof that my theory is correct, but at least all of my zigbee devices are online again.


(Benoit LORAND) #958

Hi all,

I’m new user of openhab. I will try to control Ikea Tradfri with my Qivicon funkstick (10c4:89fb).
I will use the method here https://github.com/openhab/zigbee for my device get /dev/ttyUSB0
I think the device is correctly recognise by openhab :


But it can’t detect anything :cry:

I have enable debug and get this :

https://pastebin.com/ekzwcnyW

I have read in this topic that the Qivicon firmware should be different from the original telegesis one. So i try to use minicom but it fail. minicom stay disconnected. I don’t understand why, i use minicom -D /dev/ttyUSB0 -b 19200… Openhab can see the firmware version, so it should be possible

Can you help me ?


(Chris Jackson) #959

There is no sign of any devices joining the network in the log.

The baud rate is wrong - it should be 57600.


(orzech) #960

Hi,

After snapshot update from 20180331 to 20180421 I’m getting an error:

2018-04-21 20:45:54.340 [ERROR] [core.karaf.internal.FeatureInstaller] - Failed installing 'openhab-persistence-mapdb, openhab-binding-exec, openhab-action-xmpp, openhab-misc-restdocs, openhab-ui-habpanel, openhab-binding-zigbee, openhab-transformation-map, openhab-ui-classic, openhab-binding-kodi, openhab-ui-habmin, openhab-transformation-xslt, openhab-transformation-exec, openhab-ui-paper, openhab-transformation-scale, openhab-binding-samsungtv, openhab-binding-milight, openhab-misc-market, openhab-transformation-javascript, openhab-binding-weather1, openhab-transformation-regex, openhab-transformation-jsonpath, openhab-binding-zwave, openhab-binding-mihome, openhab-transformation-xpath, openhab-persistence-rrd4j, openhab-ui-basic, openhab-action-mail, openhab-binding-astro': Unable to resolve root: missing requirement [root] osgi.identity; osgi.identity=openhab-binding-zigbee; type=karaf.feature; version="[2.3.0.SNAPSHOT,2.3.0.SNAPSHOT]"; filter:="(&(osgi.identity=openhab-binding-zigbee)(type=karaf.feature)(version>=2.3.0.SNAPSHOT)(version<=2.3.0.SNAPSHOT))" [caused by: Unable to resolve openhab-binding-zigbee/2.3.0.SNAPSHOT: missing requirement [openhab-binding-zigbee/2.3.0.SNAPSHOT] osgi.identity; osgi.identity=org.openhab.binding.zigbee.cc2531; type=osgi.bundle; version="[2.3.0.201804202151,2.3.0.201804202151]"; resolution:=mandatory [caused by: Unable to resolve org.openhab.binding.zigbee.cc2531/2.3.0.201804202151: missing requirement [org.openhab.binding.zigbee.cc2531/2.3.0.201804202151] osgi.wiring.package; filter:="(osgi.wiring.package=org.openhab.binding.zigbee.discovery)"]]

Does anybody have similar issue?


(Chris Jackson) #961

This is a known issue and should be fixed soon.


(orzech) #962

Is there any workaround?


(Chris Jackson) #963

I’ve not tried this, but you could try the following command -:

feature:install esh-config-discovery-usbserial