Zigbee binding

Mike_Bagdanoff · January 8, 2018, 5:37am

I have the same issue with the 1/7 binding and my husbzb-1. My zigbee devices stop responding after a few hours (ST plugs) . I just moved back to a PI3 and a fresh install of 2.2 release (with the 1/7 zigbee binding) and it still happens.

AFromD · January 8, 2018, 7:03am

And it is pretty much what I was reporting here and seems similar to what weakfl and BClark have logged here.

Commands to lamps are not getting through, but I can still see lamps go offline when I remove power, and my Hue motion sensor keeps working perfectly. So Zigbee seems to be working for incoming status updates, but no commands seem to be getting out any more.

I am on the Husbzb, so is Mike_Bagdanoff, weakfl is using Telegesis, and ScottKinSF is using a TI dongle. I am running Windows 10, the others Raspi and maybe linux. So it is not dependent on hardware or OS. It seems to resolve for a while after restarting the binding and the java serial component. So something is amiss there, which causes messages not to get sent.

Thanks for the ST Motion sensors, I just bought 3 on my last visit to the US!

chris · January 8, 2018, 7:47am

Sorry, but without looking at real data, you simply can not say they are the same. I can say 100% for sure that the issue reported by @scottk is totally different to what is reported by @weakfl which is an issue with the Telegesis driver, and is also different to the issue you have reported.

Or just maybe, as above, they are all totally different issues (this is the case). This is why I prefer people to report the problem they have, rather than just to say “I have the same problem” - often issues are not the same even if outwardly they might look the same (in this case, the outward sign is just that devices stop working…).

weakfl · January 8, 2018, 8:42am

That was my fault, sorry. I just saw a growing queue in @AFromD’s log an thought it must be the same issue.
On closer examination, the log messages are different:

chris · January 8, 2018, 9:46am

It’s not a problem - and I know it’s very easy to do . It’s one of my little niggles when people send a “I have the same problem” email, or “I changed X and it stopped everything working” (or that sort of thing) - often without any information to back up the issue.

Logs are my friend - they only supply the facts (even if not all of them sometimes)

Benjy · January 8, 2018, 2:22pm

Looking much more stable in my system now! Thanks! I have full control over all my bulbs for a few hours at a time now, after then it’s back to no response until I restart openHAB (I can’t seem to reset the binding on it’s own as the Telegesis thing doesn’t come back online). Will try to get some more logs for you when I can!

Mike_Bagdanoff · January 8, 2018, 9:53pm

I fully reset my zigbee stick (husbzb-1) and re-paired my 3 ST outlets. I then was able to pair one of my ST motion sensors and one of my ST contact sensors. Everything seems to be working fine as of this moment but I have turned debug logging on and I’ll see if it all fails after a few hours then I can send the logs.

Some observations:

The “Contact Portal 1” channel of the ST Contact sensor is defined as a Switch and should probably be defined as a Contact
The Temperature channels are hard-coded to celsius, so adding a configuration like zwave devices would be nice
Motion Presence and Motion Intrusion are both switches, and half of my Zwave Motion sensors are Switches for the sensor_binary channel and half are Contacts so I’m not sure which is right.
Battery Level reports would be nice as well

Thanks for getting this working! I have a bunch of these sensors that are no longer a waste of money

imagio · January 9, 2018, 6:01am

Just got a Telegesis stick. When I add it as a thing it seems to initialize correctly but I see no output when trying to connect a zigbee device. Just a “starting zigbee scan” and nothing further.

2018-01-09 00:55:42.294 [DEBUG] [zigbee.internal.ZigBeeHandlerFactory] - Creating coordinator handler for org.eclipse.smarthome.core.thing.internal.BridgeImpl@6556d3c7

2018-01-09 00:55:42.299 [DEBUG] [bee.discovery.ZigBeeDiscoveryService] - Creating ZigBee discovery service for zigbee:coordinator_telegesis:05be6620

2018-01-09 00:55:42.305 [DEBUG] [bee.discovery.ZigBeeDiscoveryService] - Activating ZigBee discovery service for zigbee:coordinator_telegesis:05be6620

2018-01-09 00:55:42.317 [DEBUG] [org.openhab.binding.zigbee ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.discovery.DiscoveryService}={service.id=406, service.bundleid=254, service.scope=singleton} - org.openhab.binding.zigbee

2018-01-09 00:55:42.338 [DEBUG] [org.openhab.binding.zigbee ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.core.thing.binding.firmware.FirmwareUpdateHandler}={service.id=407, service.bundleid=254, service.scope=singleton} - org.openhab.binding.zigbee

2018-01-09 00:55:42.441 [DEBUG] [er.ZigBeeCoordinatorTelegesisHandler] - Initializing ZigBee Telegesis serial bridge handler.

2018-01-09 00:55:42.444 [hingStatusInfoChangedEvent] - ‘zigbee:coordinator_telegesis:05be6620’ changed from UNINITIALIZED to INITIALIZING

2018-01-09 00:55:42.446 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Initializing ZigBee network [zigbee:coordinator_telegesis:05be6620].

2018-01-09 00:55:42.450 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Channel -1

2018-01-09 00:55:42.454 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - PANID 0

2018-01-09 00:55:42.458 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - EPANID 0000000000000000

2018-01-09 00:55:42.461 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Key null

2018-01-09 00:55:42.465 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Initialising network

2018-01-09 00:55:42.470 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Created random ZigBee PAN ID [F8CC].

2018-01-09 00:55:42.557 [me.event.ThingUpdatedEvent] - Thing ‘zigbee:coordinator_telegesis:05be6620’ has been updated.

2018-01-09 00:55:42.559 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Created random ZigBee extended PAN ID [93636C7FAAFE233F].

2018-01-09 00:55:42.645 [me.event.ThingUpdatedEvent] - Thing ‘zigbee:coordinator_telegesis:05be6620’ has been updated.

2018-01-09 00:55:44.528 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Key String

2018-01-09 00:55:44.527 [me.event.ThingUpdatedEvent] - Thing ‘zigbee:coordinator_telegesis:05be6620’ has been updated.

2018-01-09 00:55:44.533 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Key initialised 380F0CF53891D68D96EE13CB7684133E

2018-01-09 00:55:44.539 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Key final array 380F0CF53891D68D96EE13CB7684133E

2018-01-09 00:55:44.545 [DEBUG] [er.ZigBeeCoordinatorTelegesisHandler] - ZigBee Coordinator Telegesis opening Port:‘/dev/ttyUSB1’ PAN:f8cc, EPAN:93636C7FAAFE233F, Channel:-1

2018-01-09 00:55:44.555 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Scheduling ZigBee start

2018-01-09 00:55:44.567 [hingStatusInfoChangedEvent] - ‘zigbee:coordinator_telegesis:05be6620’ changed from INITIALIZING to UNKNOWN

2018-01-09 00:55:44.577 [nt.FirmwareStatusInfoEvent] - Firmware status of thing zigbee:coordinator_telegesis:05be6620 changed to UNKNOWN.

2018-01-09 00:55:45.558 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - ZigBee network starting

2018-01-09 00:55:45.562 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Initialising ZigBee coordinator

2018-01-09 00:55:45.567 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Key initialise 380F0CF53891D68D96EE13CB7684133E

2018-01-09 00:55:45.576 [DEBUG] [ing.zigbee.internal.ZigBeeSerialPort] - Connecting to serial port [/dev/ttyUSB1] at 19200 baud, flow control FLOWCONTROL_OUT_NONE.

2018-01-09 00:55:45.593 [DEBUG] [ing.zigbee.internal.ZigBeeSerialPort] - Serial port [/dev/ttyUSB1] is initialized.

2018-01-09 00:55:46.651 [DEBUG] [nal.ZigBeeNetworkStateSerializerImpl] - Saving ZigBee network state: done.

2018-01-09 00:55:46.654 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - initResponse is JOINED

2018-01-09 00:55:46.659 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - initializeNetwork is true

2018-01-09 00:55:48.219 [hingStatusInfoChangedEvent] - ‘zigbee:coordinator_telegesis:05be6620’ changed from UNKNOWN to OFFLINE: zigbee.status.offline_startupfail

2018-01-09 00:55:51.415 [hingStatusInfoChangedEvent] - ‘zigbee:coordinator_telegesis:05be6620’ changed from OFFLINE: zigbee.status.offline_startupfail to ONLINE

2018-01-09 00:55:53.239 [me.event.ThingUpdatedEvent] - Thing ‘zigbee:coordinator_telegesis:05be6620’ has been updated.

2018-01-09 00:55:53.250 [DEBUG] [nal.ZigBeeNetworkStateSerializerImpl] - Saving ZigBee network state: done.

2018-01-09 00:55:53.340 [me.event.ThingUpdatedEvent] - Thing ‘zigbee:coordinator_telegesis:05be6620’ has been updated.

2018-01-09 00:58:40.430 [DEBUG] [bee.discovery.ZigBeeDiscoveryService] - Starting ZigBee scan for zigbee:coordinator_telegesis:05be6620

AFromD · January 9, 2018, 5:52pm

Some Zigbee devices can be quite picky to connect. You usually have to reset them in some way, and make sure the scan is active before you actually do it. I have an osram socket that will only associate right when connecting it to power, and hue lamps that had been connected before need to be reset with the dimmer remote before they will connect with something else.

imagio · January 9, 2018, 8:34pm

I reset my device (Lowes Iris motion sensor v2) and expected to see at least some output. Is there a way to enable deeper logging? I set org.openhab.bindings.zigbee to DEBUG but I’m not sure what else to do.

5iver · January 9, 2018, 8:50pm

But be prepared for massive amounts of data… and set them back to WARN when your done debugging.

This has a typo, so may explain not getting anything in the log.

imagio · January 9, 2018, 9:28pm

Ah I didn’t know to enable com.zsmartsystems.zigbee for debug logging. I already had the zigbee binding debug working. I get some more info now when starting discovery but no apparent communication with my device. I tried both the a SmartThings motion sensor and a Lowes Iris v2 motion sensor. The logging from discovery is always the same, apparently no communication. Both were fully reset when trying to pair. (I am on the 2.3 snapshot build btw)

018-01-09 16:25:35.961 [DEBUG] [bee.discovery.ZigBeeDiscoveryService] - Starting ZigBee scan for zigbee:coordinator_telegesis:05be6620

2018-01-09 16:25:35.968 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - Permit join to 65532/0 for 60 seconds.

2018-01-09 16:25:35.974 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - TX CMD: ManagementPermitJoiningRequest [0/0 -> 65532/0, cluster=0036, TID=73, permitDuration=60, tcSignificance=true]

2018-01-09 16:25:35.980 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - TX APS: ZigBeeApsFrame [sourceAddress=0/0, destinationAddress=65532/0, profile=0000, cluster=54, addressMode=DEVICE, radius=31, sequence=115, payload=00 3C 01]

2018-01-09 16:25:35.986 [DEBUG] [ngle.telegesis.ZigBeeDongleTelegesis] - Telegesis send: TelegesisSendMulticastCommand [radius=31, address=65532, sourceEp=0, destEp=0, profileId=0, clusterId=54, messageData=00 3C 01]

2018-01-09 16:25:35.992 [DEBUG] [gesis.internal.TelegesisFrameHandler] - TX Telegesis queue: 1164

2018-01-09 16:25:35.998 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - TX CMD: ManagementPermitJoiningRequest [0/0 -> 0/0, cluster=0036, TID=74, permitDuration=60, tcSignificance=true]

2018-01-09 16:25:36.003 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - TX APS: ZigBeeApsFrame [sourceAddress=0/0, destinationAddress=0/0, profile=0000, cluster=54, addressMode=DEVICE, radius=31, sequence=116, payload=00 3C 01]

2018-01-09 16:25:36.008 [DEBUG] [ngle.telegesis.ZigBeeDongleTelegesis] - Telegesis send: TelegesisSendUnicastCommand [address=0, sourceEp=0, destEp=0, profileId=0, clusterId=54, messageData=00 3C 01, messageId=null]

2018-01-09 16:25:36.012 [DEBUG] [gesis.internal.TelegesisFrameHandler] - TX Telegesis queue: 1165

Sergi_Suarez · January 10, 2018, 10:20am

Hi Chris,

Just wondering of there was any update on adding support to Conbee/Raspbee

Thanks

BR

Sergi

chris · January 10, 2018, 10:49am

@imagio please use code fences when pasting logs into the forum so they are readable.

No - typically if the join doesn’t work, then there is no information coming from the stick, so there is simply nothing to log.

No - recently. I’ve been busy working on the other coordinators and general binding issues/improvements. If someone wants to look at it then please feel free

Sergi_Suarez · January 10, 2018, 11:10am

That’s unfortunate. I can’t found any telegesis ETRX3 on sale. Only with a developer kit that costs more than 300€. Unfortunately my programing skills are not really good and Java was one of my most hated languages. I always prefered assembler.

I think I will stay with the deconz softwware that at least works.

chris · January 10, 2018, 11:13am

They are reasonably easily available in most countries (but not all). Where are you located?

Sergi_Suarez · January 10, 2018, 11:16am

Spain. I was searching telegesis etrx3 and only found the kit. Now I’m searching for etrx3 usb and I have found more options.

Is this one working? ETRX357USB+8M

chris · January 10, 2018, 11:46am

Yes - should be fine.

imagio · January 10, 2018, 1:23pm

@chris Does that mean that my devices (Iris motion v2 and SmartThings motion) can’t work with the telegesis stick or is more data about the devices needed to get them to communicate?

chris · January 10, 2018, 2:37pm

What do you mean specifically? I don’t know quite what you’re referring to, but I think it should be fine. It certainly works fine with an ST motion sensor.