f cree bulbs. I can’t bind to it anymore. I had a hue and cree bind perfectly after I updated the bindings. I have been messing with my system and cant bind to the cree anymore. I reset it (off 3 on 1 is easiest) and still no luck. It’s going back. Ill try another hue.
*I’m day 3 noob so take this with a grain of salt
Anyways just trying to help out and increase documentation of zigbee. Seems its limited.
Hi all,
Is the Phillips hue tap recogniced by the binding?
Thanks
chris
January 25, 2018, 7:48am
765
No - these use ZGP which isn’t supported at the moment at least.
ok. thanks.
chris
January 25, 2018, 7:57am
767
Will do. I did buy one a while ago with a view to testing it, but I was unable to get it to work. Newer stacks in theory should support it (but no the Telegesis, or the TI firmware that most people are using).
Are any locks supported by the TI firmware? Is there going to be any?
chris
January 25, 2018, 5:21pm
769
I don’t think that the TI firmware will specifically support any particular devices (not that I’m aware). Currently locks are not supported within the binding though (for any coordinator).
jjmeseguer
January 25, 2018, 11:21pm
770
Hi @chris ,
If not, can the dongle work with the binding and with that at the same time? Can I have two dongles, one for each?
The setting for high priority is on the VM Server configuration within the VMWare Host dashboard, though it’s not specific to the USB. Apologies for misrepresenting the configuration item!
If you’re on ESXI 6.5:
Go to “Virtual Machines”
Select your VM, press “Actions”, then “Edit Settings”
Click “VM Options” in the top, then expand “Advanced”
Set Latency Sensitivity to “High”
Note that my most current setup has the sensitivity set to normal and my system is working as expected, so this may not be required anymore.
chris
January 26, 2018, 7:51am
772
It’s still unclear to me if they are ZigBee compliant. If so, then they should work as the manufacturer generally should not matter. From what I’ve read on other forums, they do not comply with ZigBee and this causes problems.
My focus at this stage is on getting the system stable and adding support for different types of ZigBee devices. If you can get the devices to join the network, and they comply with the ZCL, then they should work. If there are issues with the ZCL implementation then I’m happy to look at a log to see what is happening and try and improve the support in this area, but if there are more fundamental issues relating to joining and rejoining (which is what I recall reading on the SmartThings forum) then it’s likely to be difficult to support them.
@chris , did you see my latest mail? The latest addon seams to solve the problem that the Hue lamps did not switch to online. If I add only a few lamps I can also control them, but if I add all my 32 lamps nothing happens when switching a lamp on or off. Also this TX queue in the log does not seam to be empty at any time. There is also a lot of activity in the log when all lamps are added. Do you habe any idea what could cause this?
trumee
January 26, 2018, 10:27am
774
I updated the binding to 2.3.0, and got
2018-01-26 04:24:40.114 [hingStatusInfoChangedEvent] - 'zigbee:coordinator_ember:3e00fd97' changed from UNKNOWN to UNINITIALIZED
2018-01-26 04:24:40.175 [hingStatusInfoChangedEvent] - 'zigbee:coordinator_ember:3e00fd97' changed from UNINITIALIZED to UNINITIALIZED (HANDLER_MISSING_ERROR)
2018-01-26 04:24:40.699 [hingStatusInfoChangedEvent] - 'zigbee:coordinator_ember:3e00fd97' changed from UNINITIALIZED (HANDLER_MISSING_ERROR) to INITIALIZING
2018-01-26 04:24:40.704 [hingStatusInfoChangedEvent] - 'zigbee:coordinator_ember:3e00fd97' changed from INITIALIZING to UNKNOWN
2018-01-26 04:24:40.733 [hingStatusInfoChangedEvent] - 'zigbee:device:3e00fd97:7ce5240000077666' changed from UNINITIALIZED (HANDLER_MISSING_ERROR) to INITIALIZING
2018-01-26 04:24:40.740 [hingStatusInfoChangedEvent] - 'zigbee:device:3e00fd97:7ce5240000077666' changed from INITIALIZING to OFFLINE
2018-01-26 04:24:40.751 [hingStatusInfoChangedEvent] - 'zigbee:device:3e00fd97:7ce524000001c4d3' changed from UNINITIALIZED (HANDLER_MISSING_ERROR) to INITIALIZING
2018-01-26 04:24:40.760 [hingStatusInfoChangedEvent] - 'zigbee:device:3e00fd97:7ce524000001c4d3' changed from INITIALIZING to OFFLINE
openhab> bundle:list
247 ��� Active ��� 80 ��� 2.3.0.201801252322 ��� ZigBee Binding
openhab> log:tail
04:30:23.769 [DEBUG] [org.openhab.binding.zigbee ] - ServiceEvent UNREGISTERING - {org.eclipse.smarthome.core.thing.binding.firmware.FirmwareUpdateHandler}={service.id=1563, service.bundleid=247, service.scope=singleton} - org.openhab.binding.zigbee
04:30:23.777 [DEBUG] [org.openhab.binding.zigbee ] - ServiceEvent UNREGISTERING - {org.eclipse.smarthome.core.thing.binding.ThingHandlerFactory}={component.name=org.openhab.binding.zigbee.internal.ZigBeeHandlerFactory, component.id=464, service.id=1561, service.bundleid=247, service.scope=bundle} - org.openhab.binding.zigbee
04:30:23.781 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'zigbee:coordinator_ember:3e00fd97' changed from UNINITIALIZED to UNINITIALIZED (HANDLER_MISSING_ERROR)
04:30:23.912 [DEBUG] [org.openhab.binding.zigbee ] - BundleEvent STOPPING - org.openhab.binding.zigbee
04:30:23.914 [DEBUG] [nding.zigbee.internal.ZigBeeActivator] - ZigBee binding stopped.
04:30:23.919 [DEBUG] [org.openhab.binding.zigbee ] - ServiceEvent UNREGISTERING - {org.eclipse.smarthome.config.core.ConfigDescriptionProvider}={service.id=1564, service.bundleid=247, service.scope=singleton} - org.openhab.binding.zigbee
04:30:23.928 [DEBUG] [org.openhab.binding.zigbee ] - ServiceEvent UNREGISTERING - {org.eclipse.smarthome.config.core.ConfigDescriptionProvider}={service.id=1565, service.bundleid=247, service.scope=singleton} - org.openhab.binding.zigbee
04:30:23.938 [DEBUG] [org.openhab.binding.zigbee ] - BundleEvent STOPPED - org.openhab.binding.zigbee
04:30:23.977 [DEBUG] [org.openhab.binding.zigbee ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.core.thing.binding.ThingHandlerFactory}={component.name=org.openhab.binding.zigbee.internal.ZigBeeHandlerFactory, component.id=465, service.id=1568, service.bundleid=247, service.scope=bundle} - org.openhab.binding.zigbee
04:30:23.986 [DEBUG] [org.openhab.binding.zigbee ] - BundleEvent STARTING - org.openhab.binding.zigbee
04:30:23.990 [DEBUG] [nding.zigbee.internal.ZigBeeActivator] - ZigBee binding started. Version 2.3.0.201801252322
04:30:24.019 [DEBUG] [org.openhab.binding.zigbee ] - BundleEvent STARTED - org.openhab.binding.zigbee
04:30:24.178 [DEBUG] [.zigbee.internal.ZigBeeHandlerFactory] - Creating coordinator handler for org.eclipse.smarthome.core.thing.internal.BridgeImpl@f7183ddd
04:30:24.183 [DEBUG] [gbee.discovery.ZigBeeDiscoveryService] - Creating ZigBee discovery service for zigbee:coordinator_ember:3e00fd97
04:30:24.186 [DEBUG] [gbee.discovery.ZigBeeDiscoveryService] - Activating ZigBee discovery service for zigbee:coordinator_ember:3e00fd97
04:30:24.195 [DEBUG] [org.openhab.binding.zigbee ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.discovery.DiscoveryService}={service.id=1569, service.bundleid=247, service.scope=singleton} - org.openhab.binding.zigbee
04:30:24.214 [DEBUG] [org.openhab.binding.zigbee ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.core.thing.binding.firmware.FirmwareUpdateHandler}={service.id=1570, service.bundleid=247, service.scope=singleton} - org.openhab.binding.zigbee
04:30:24.273 [DEBUG] [handler.ZigBeeCoordinatorEmberHandler] - Initializing ZigBee Ember serial bridge handler.
04:30:24.275 [DEBUG] [gbee.handler.ZigBeeCoordinatorHandler] - Initializing ZigBee network [zigbee:coordinator_ember:3e00fd97].
04:30:24.276 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'zigbee:coordinator_ember:3e00fd97' changed from UNINITIALIZED (HANDLER_MISSING_ERROR) to INITIALIZING
04:30:24.277 [DEBUG] [gbee.handler.ZigBeeCoordinatorHandler] - Channel 26
04:30:24.278 [DEBUG] [gbee.handler.ZigBeeCoordinatorHandler] - PANID 59XXX
04:30:24.283 [DEBUG] [gbee.handler.ZigBeeCoordinatorHandler] - EPANID C502C01B0C32XXXX
04:30:24.285 [DEBUG] [gbee.handler.ZigBeeCoordinatorHandler] - Key 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
04:30:24.287 [DEBUG] [gbee.handler.ZigBeeCoordinatorHandler] - Key String 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
04:30:24.291 [DEBUG] [gbee.handler.ZigBeeCoordinatorHandler] - Key initialised FE7FC7BB555CE0BC6C73A3E0CF2274E3
04:30:24.294 [DEBUG] [gbee.handler.ZigBeeCoordinatorHandler] - Key final array FE7FC7BB555CE0BC6C73A3E0CF2274E3
04:30:24.297 [DEBUG] [handler.ZigBeeCoordinatorEmberHandler] - ZigBee Coordinator Ember opening Port:'/dev/ttyUSB1' PAN:e915, EPAN:C502C01B0C32BD9B, Channel:26
04:30:24.302 [DEBUG] [.zigbee.internal.ZigBeeHandlerFactory] - Creating coordinator handler for org.eclipse.smarthome.core.thing.internal.ThingImpl@c14bee1
04:30:24.303 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'zigbee:coordinator_ember:3e00fd97' changed from INITIALIZING to UNKNOWN
04:30:24.307 [DEBUG] [org.openhab.binding.zigbee ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.core.ConfigDescriptionProvider}={service.id=1571, service.bundleid=247, service.scope=singleton} - org.openhab.binding.zigbee
04:30:24.324 [DEBUG] [.zigbee.internal.ZigBeeHandlerFactory] - Creating coordinator handler for org.eclipse.smarthome.core.thing.internal.ThingImpl@bd4303c
04:30:24.324 [DEBUG] [gbee.handler.ZigBeeCoordinatorHandler] - Scheduling ZigBee start
04:30:24.335 [DEBUG] [org.openhab.binding.zigbee ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.core.ConfigDescriptionProvider}={service.id=1572, service.bundleid=247, service.scope=singleton} - org.openhab.binding.zigbee
04:30:24.337 [DEBUG] [org.openhab.binding.zigbee ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.core.thing.binding.firmware.FirmwareUpdateHandler}={service.id=1573, service.bundleid=247, service.scope=singleton} - org.openhab.binding.zigbee
04:30:24.342 [DEBUG] [org.openhab.binding.zigbee ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.core.thing.binding.firmware.FirmwareUpdateHandler}={service.id=1574, service.bundleid=247, service.scope=singleton} - org.openhab.binding.zigbee
04:30:24.348 [DEBUG] [ing.zigbee.handler.ZigBeeThingHandler] - 7CE524000001C4D3: Initializing ZigBee thing handler zigbee:device:3e00fd97:7ce524000001c4d3
04:30:24.349 [DEBUG] [ing.zigbee.handler.ZigBeeThingHandler] - 7CE5240000077666: Initializing ZigBee thing handler zigbee:device:3e00fd97:7ce5240000077666
04:30:24.354 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'zigbee:device:3e00fd97:7ce5240000077666' changed from UNINITIALIZED (HANDLER_MISSING_ERROR) to INITIALIZING
04:30:24.355 [DEBUG] [ing.zigbee.handler.ZigBeeThingHandler] - 7CE5240000077666: Coordinator status changed to UNKNOWN.
04:30:24.357 [DEBUG] [ing.zigbee.handler.ZigBeeThingHandler] - 7CE5240000077666: Coordinator is unknown or not online.
04:30:24.358 [DEBUG] [ing.zigbee.handler.ZigBeeThingHandler] - 7CE524000001C4D3: Coordinator status changed to UNKNOWN.
04:30:24.360 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'zigbee:device:3e00fd97:7ce524000001c4d3' changed from UNINITIALIZED (HANDLER_MISSING_ERROR) to INITIALIZING
04:30:24.361 [DEBUG] [ing.zigbee.handler.ZigBeeThingHandler] - 7CE524000001C4D3: Coordinator is unknown or not online.
04:30:24.363 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'zigbee:device:3e00fd97:7ce5240000077666' changed from INITIALIZING to OFFLINE
04:30:24.367 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'zigbee:device:3e00fd97:7ce524000001c4d3' changed from INITIALIZING to OFFLINE
04:30:24.368 [DEBUG] [ing.zigbee.handler.ZigBeeThingHandler] - 7CE5240000077666: Channel zigbee:device:3e00fd97:7ce5240000077666:7CE5240000077666_1_switch_level linked - polling started.
04:30:24.371 [DEBUG] [ing.zigbee.handler.ZigBeeThingHandler] - 7CE5240000077666: Channel zigbee:device:3e00fd97:7ce5240000077666:7CE5240000077666_1_switch_onoff linked - polling started.
04:30:24.373 [DEBUG] [ing.zigbee.handler.ZigBeeThingHandler] - 7CE524000001C4D3: Channel zigbee:device:3e00fd97:7ce524000001c4d3:7CE524000001C4D3_1_switch_level linked - polling started.
04:30:24.377 [DEBUG] [ing.zigbee.handler.ZigBeeThingHandler] - 7CE524000001C4D3: Channel zigbee:device:3e00fd97:7ce524000001c4d3:7CE524000001C4D3_1_switch_onoff linked - polling started.
My GE bulbs no longer work.
chris
January 26, 2018, 10:43am
775
I don’t know what the “latest” is -I thought I’d replied to the last email I received from you, but maybe not. The issue I saw in the last log I looked at was simply down to loading - the network was still heavily loaded after 10 or 15 minutes of the log.
I will look more at improving this by saving more data to local storage to avoid having to request it again on startup. I have a couple of issues open to track this - quite a lot has been done to improve it already, but there are still things that are planned.
Yes - there is a lot to do when a device gets added - this is of course normal and unavoidable.We need to find out what the device supports, what model, manufacturer, supported features etc so that we can work out what channels to support.
trumee
January 26, 2018, 10:58am
776
@chris , It seems version 2.3.0 no longer exposes the Switch for the GE bulb. The only property i get is switch_level.
jjmeseguer
January 26, 2018, 10:59am
777
Hi,@AndrewL did it with zigbee-shepherd and explains it here:
opened 10:55PM - 26 Sep 17 UTC
TL;DR
Zigbee-shepherd now supports Xiaomi zigbee devices. Here is my zigbee to … MQTT bridge based on zigbee-shepherd: https://github.com/AndrewLinden/xiaomi-zb2mqtt
Here is how I got Xiaomi Zigbee switches (WXKG01LM and WXKG02LM) working with zigbee-shepherd:
1. Flash your CC2531 with CC2531ZNP-Pro-Secure_LinkKeyJoin.hex from here: https://github.com/mtornblad/zstack-1.2.2a.44539/tree/master/CC2531
2. Xiaomi devices send predetermined attribute reports to coordinator endpoint 1 with profile id 0x0104 (Zigbee Home Automation profile). Zigbee-shepherd at the moment registers the 0x0104 profile to endpoint 2. So to get Xiaomi attribute reports working we need to swap the profile id-s of endpoints 1 and 2 in zigbee-shepherd. That can be done in lib/initializers/init_controller.js on line 64:
```
dlgInfos = [
{ profId: 0x0104, epId: 1 }, { profId: 0x0101, epId: 2 }, { profId: 0x0105, epId: 3 },
{ profId: 0x0107, epId: 4 }, { profId: 0x0108, epId: 5 }, { profId: 0x0109, epId: 6 }
];
```
3. Pair your switches. The WXKG01LM can be paired when after reseting the switch you keep toggling the reset for some time to prevent the switch to go to sleep mode before pairing process for zigbee-shepherd is complete. When you don't succees at first, simply try again. You can also try this fork https://github.com/HollyAssistTeam/zigbee-shepherd which has some patches to make pairing more forgiving if the new device does not answer.
One must note that when pairing fails it is usually because shepherd fails to interrogate the device about its properties because the switch or sensor goes to sleep. But on the CC2531 ZNP pairing is done instantly when you reset your device https://github.com/zigbeer/zigbee-shepherd/issues/19
Such is the case with WXKG02LM too. This switch has no separate reset button and I could not keep it awake so shepherd would think pairing succeeded. But as the pairing on ZNP succeeds you can simply gather the neccessary info ieeeAddr and nwkAddr from the debug log and carefully craft a entry in lib/database/dev.db yourself. Then shepherd thinks it is paired and happily fires events based on the attribute reports sent by the switch.
I’m still investigating and don’t have any Zigbee equipment, hopefully he can answer to you.@AndrewL ’s tool, or would I need two of them (if they can coexist)?
chris
January 26, 2018, 12:53pm
778
Correct - this was an enhancement added recently.
trumee
January 27, 2018, 12:27am
779
I have the Linear Zigbee/Zwave stick. After running for sometime, i get
[ 78.830729] cp210x ttyUSB1: failed set request 0x7 status: -32
[ 78.841347] cp210x ttyUSB1: failed set request 0x7 status: -32
[ 199.922884] cp210x ttyUSB1: failed set request 0x7 status: -32
[ 199.950839] cp210x ttyUSB1: failed set request 0x7 status: -32
[ 199.959840] cp210x ttyUSB1: failed set request 0x7 status: -32
[ 200.017209] cp210x ttyUSB1: failed set request 0x7 status: -32
[ 200.018363] cp210x ttyUSB1: failed set request 0x7 status: -32
Is there any fix for this?
5iver
January 27, 2018, 1:45am
780
I have the same controller and dmesg --time-format iso|grep tty shows me these too…
2018-01-25T13:56:43,398480-0500 cp210x ttyUSB1: failed set request 0x7 status: -32
It looks like they come up after an OH or binding restart, but doesn’t seem to be an issue.
chris
January 27, 2018, 8:37am
781
This log isn’t from the binding - it’s coming from a system log I guess, so there’s not a lot that the binding can do I think? Maybe there’s a driver issue - I’m really not sure what this means.
trumee
January 27, 2018, 1:36pm
782
Pairing a new device doesnt work unless the zigbee stick is power-cycled.
