ZHA Zigbee Tested Devices...Please add your device results

andrewpc · September 10, 2017, 1:14pm

Just an update from my previous post. I purchased this stick without knowing whether it was compatible. Its based on the EM357. It turns out the version I purchased does not come with a bootloader and the firmware installed is incompatible.

Not having a bootloader is a problem if you want to change the firmware, via the USB port, to a version supported by bellows. I was going to RMA the stick, however I came across a cheap Insight Adapter (ISA3) device on ebay which can be used to program the stick via its debug port.

Pleased to say that after a bit of mucking around, I was able to program the device with a firmware image that had both a bootloader and supported software flow control (Xon/Xoff). I also needed to set the config via the patch command to enforce a 57600 baud rate. It is now working in Home Assistant 0.53 and currently connected to a Wemo Bulb which seems to be working well. I will connect it to another one tomorrow.

This may not be terribly useful to people that dont have an ISA3, but wanted to point out that the stick is compatible and does work. If you get stuck in the same situation as me, happy to try and help out.

gohassgo · September 15, 2017, 8:03pm

I have some of the same “Centralite” devices as posted earlier. I’m running hass.io 0.53.1 and zha with a HUSBZB-1 USB stick. All sensors report their main purpose in life + temp and do it without delays.

PeQ Door/Window 3300-P, shows as Centralite 3300
PeQ Motion 3305-P, shows as Centralite 3305
PeQ Water/Leak Detector 3315-P, shows as Centralite 3315

All of these devices report four things–their “primary function”, temperature, tamper switch, and battery, but hass.io only shows the primary plus temp. I’m guessing that the “cluster command 0/1” messages in the log are for the battery level and tamper switch.

2017-09-15 14:45:49 WARNING (MainThread) [bellows.zigbee.application] Unexpected message send notification
2017-09-15 14:46:05 WARNING (MainThread) [bellows.zigbee.zcl] Data remains after deserializing ZCL frame
2017-09-15 14:46:05 WARNING (MainThread) [bellows.zigbee.zcl] [0xddcc:1:0x0500] No handler for cluster command 1
2017-09-15 14:46:06 WARNING (MainThread) [bellows.zigbee.zcl] [0xddcc:1:0x0500] No handler for cluster command 0

nichol · September 15, 2017, 9:48pm

Hi,

I am not sure if this is the correct pace to ask this question, however I am trying to get some Osram Lightify RGBW globes working, and from what I can see they should be. Hopefully somebody can point me in the right direction.

I am running the HA 0.53.1 docker image. Firstly bellows was not working so I downloaded the current master from github and replaced the files, and it all seemed good. I sucessfully got a bulb to pair - result of bellows devices is;
bellows -d /zigbeeusbstick devices -D /config/>
Device:
NWK: 0xc8de
IEEE: 84:18:26:00:00:cb:ad:15
Endpoints:
3: profile=0xc05e, device_type=DeviceType.EXTENDED_COLOR_LIGHT
Input Clusters:
Basic (0)
Identify (3)
Groups (4)
Scenes (5)
On/Off (6)
Level control (8)
Color Control (768)
LightLink (4096)
Manufacturer Specific (64516)
Manufacturer Specific (64527)
Output Clusters:
Ota (25)

However problem is that the device will not show up in home assistant.

I thought that there might be a problem with HA 0.53.1 talking to bellows as the included version had issue. I then ran HA 0.49.1 (from what I can see people are having success with lightify on this version. bellows worked correctly out of the box, I deleted the zigbee.db file, reset my bulb and tried again. Same issue as before, the bulb seems to add ok, however does not show up in the interface.

Hoping somebody can point me in the right direction.

Logs included below (I hope I have captured all the relevant ones)

2017-09-16 07:03:20 INFO (MainThread) [homeassistant.setup] Setting up zha
2017-09-16 07:03:20 DEBUG (MainThread) [bellows.zigbee.appdb] Loading application state from /config/zigbee.db
2017-09-16 07:03:20 DEBUG (MainThread) [bellows.uart] Sending: b’1ac038bc7e’
2017-09-16 07:03:20 DEBUG (MainThread) [bellows.uart] RSTACK Version: 2 Reason: RESET_SOFTWARE frame: b’c1020b0a527e’
2017-09-16 07:03:20 DEBUG (MainThread) [bellows.ezsp] Send command version
2017-09-16 07:03:20 DEBUG (MainThread) [bellows.uart] Sending: b’004221a850ed2c7e’
2017-09-16 07:03:20 DEBUG (MainThread) [bellows.uart] Data frame: b’0142a1a8502815e23c957e’
2017-09-16 07:03:20 DEBUG (MainThread) [bellows.uart] Sending: b’8160597e’
2017-09-16 07:03:20 DEBUG (MainThread) [bellows.ezsp] Application frame 0 (version) received
2017-09-16 07:03:20 DEBUG (MainThread) [bellows.ezsp] Send command setConfigurationValue
2017-09-16 07:03:20 DEBUG (MainThread) [bellows.uart] Sending: b’7d314321fb582815c3277e’
2017-09-16 07:03:20 DEBUG (MainThread) [bellows.uart] Data frame: b’1243a1fb54fb737e’
2017-09-16 07:03:20 DEBUG (MainThread) [bellows.uart] Sending: b’82503a7e’
2017-09-16 07:03:20 DEBUG (MainThread) [bellows.ezsp] Application frame 83 (setConfigurationValue) received
2017-09-16 07:03:20 DEBUG (MainThread) [bellows.ezsp] Send command setConfigurationValue
2017-09-16 07:03:20 DEBUG (MainThread) [bellows.uart] Sending: b’224021fb592f15226f7e’
2017-09-16 07:03:20 DEBUG (MainThread) [bellows.uart] Data frame: b’2340a1fb54c6107e’
2017-09-16 07:03:20 DEBUG (MainThread) [bellows.uart] Sending: b’83401b7e’
2017-09-16 07:03:20 DEBUG (MainThread) [bellows.ezsp] Application frame 83 (setConfigurationValue) received
2017-09-16 07:03:20 DEBUG (MainThread) [bellows.ezsp] Send command setConfigurationValue
2017-09-16 07:03:20 DEBUG (MainThread) [bellows.uart] Sending: b’334121fb792b15a2d77e’
2017-09-16 07:03:20 DEBUG (MainThread) [bellows.uart] Data frame: b’3441a1fb54d32a7e’
2017-09-16 07:03:20 DEBUG (MainThread) [bellows.uart] Sending: b’8430fc7e’
2017-09-16 07:03:20 DEBUG (MainThread) [bellows.ezsp] Application frame 83 (setConfigurationValue) received
2017-09-16 07:03:20 DEBUG (MainThread) [bellows.ezsp] Send command setConfigurationValue
2017-09-16 07:03:20 DEBUG (MainThread) [bellows.uart] Sending: b’444621fb7d5e291514417e’
2017-09-16 07:03:20 DEBUG (MainThread) [bellows.uart] Data frame: b’4546a1fb5435d07e’
2017-09-16 07:03:20 DEBUG (MainThread) [bellows.uart] Sending: b’8520dd7e’
2017-09-16 07:03:20 DEBUG (MainThread) [bellows.ezsp] Application frame 83 (setConfigurationValue) received
2017-09-16 07:03:20 DEBUG (MainThread) [bellows.ezsp] Send command setConfigurationValue
2017-09-16 07:03:20 DEBUG (MainThread) [bellows.uart] Sending: b’554721fb4d2815713f7e’
2017-09-16 07:03:20 DEBUG (MainThread) [bellows.uart] Data frame: b’5647a1fb54a9ec7e’
2017-09-16 07:03:20 DEBUG (MainThread) [bellows.uart] Sending: b’8610be7e’
2017-09-16 07:03:20 DEBUG (MainThread) [bellows.ezsp] Application frame 83 (setConfigurationValue) received
2017-09-16 07:03:20 DEBUG (MainThread) [bellows.ezsp] Send command setConfigurationValue
2017-09-16 07:03:20 DEBUG (MainThread) [bellows.uart] Sending: b’664421fb55d515b18f7e’
2017-09-16 07:03:20 DEBUG (MainThread) [bellows.uart] Data frame: b’6744a1fb54948f7e’
2017-09-16 07:03:20 DEBUG (MainThread) [bellows.uart] Sending: b’87009f7e’
2017-09-16 07:03:20 DEBUG (MainThread) [bellows.ezsp] Application frame 83 (setConfigurationValue) received
2017-09-16 07:03:20 DEBUG (MainThread) [bellows.ezsp] Send command networkInit
2017-09-16 07:03:20 DEBUG (MainThread) [bellows.uart] Sending: b’774521bf02267e’
2017-09-16 07:03:20 DEBUG (MainThread) [bellows.uart] Data frame: b’7045a5bf549c7d7e’
2017-09-16 07:03:20 DEBUG (MainThread) [bellows.uart] Sending: b’8070787e’
2017-09-16 07:03:20 DEBUG (MainThread) [bellows.ezsp] Application frame 23 (networkInit) received
2017-09-16 07:03:20 DEBUG (MainThread) [bellows.uart] Data frame: b’0045b1b1c4beee7e’
2017-09-16 07:03:20 DEBUG (MainThread) [bellows.uart] Sending: b’8160597e’
2017-09-16 07:03:20 DEBUG (MainThread) [bellows.ezsp] Application frame 25 (stackStatusHandler) received
2017-09-16 07:03:20 DEBUG (MainThread) [bellows.ezsp] Send command getNetworkParameters
2017-09-16 07:03:20 DEBUG (MainThread) [bellows.uart] Sending: b’014a21808c477e’
2017-09-16 07:03:20 DEBUG (MainThread) [bellows.uart] Data frame: b’114aa180542b7a13e897f33cc1f3259b944127abedce677302c13ff17e’
2017-09-16 07:03:20 DEBUG (MainThread) [bellows.uart] Sending: b’82503a7e’
2017-09-16 07:03:20 DEBUG (MainThread) [bellows.ezsp] Application frame 40 (getNetworkParameters) received
2017-09-16 07:03:20 DEBUG (MainThread) [bellows.ezsp] Send command setPolicy
2017-09-16 07:03:20 DEBUG (MainThread) [bellows.uart] Sending: b’124b21fd517a60e97e’
2017-09-16 07:03:20 DEBUG (MainThread) [bellows.uart] Data frame: b’224ba1fd54d8f87e’
2017-09-16 07:03:20 DEBUG (MainThread) [bellows.uart] Sending: b’83401b7e’
2017-09-16 07:03:20 DEBUG (MainThread) [bellows.ezsp] Application frame 85 (setPolicy) received
2017-09-16 07:03:20 DEBUG (MainThread) [bellows.ezsp] Send command setPolicy
2017-09-16 07:03:20 DEBUG (MainThread) [bellows.uart] Sending: b’234821fd524b97367e’
2017-09-16 07:03:20 DEBUG (MainThread) [bellows.uart] Data frame: b’3348a1fd54ed2f7e’
2017-09-16 07:03:20 DEBUG (MainThread) [bellows.uart] Sending: b’8430fc7e’
2017-09-16 07:03:20 DEBUG (MainThread) [bellows.ezsp] Application frame 85 (setPolicy) received
2017-09-16 07:03:20 DEBUG (MainThread) [bellows.ezsp] Send command setPolicy
2017-09-16 07:03:20 DEBUG (MainThread) [bellows.uart] Sending: b’344921fd542b29a27e’
2017-09-16 07:03:20 DEBUG (MainThread) [bellows.uart] Data frame: b’4449a1fd54e1c97e’
2017-09-16 07:03:20 DEBUG (MainThread) [bellows.uart] Sending: b’8520dd7e’
2017-09-16 07:03:20 DEBUG (MainThread) [bellows.ezsp] Application frame 85 (setPolicy) received
2017-09-16 07:03:20 DEBUG (MainThread) [bellows.ezsp] Send command getNodeId
2017-09-16 07:03:20 DEBUG (MainThread) [bellows.uart] Sending: b’454e218f05057e’
2017-09-16 07:03:20 DEBUG (MainThread) [bellows.uart] Data frame: b’554ea18f542a2fbf7e’
2017-09-16 07:03:20 DEBUG (MainThread) [bellows.uart] Sending: b’8610be7e’
2017-09-16 07:03:20 DEBUG (MainThread) [bellows.ezsp] Application frame 39 (getNodeId) received
2017-09-16 07:03:20 DEBUG (MainThread) [bellows.ezsp] Send command getEui64
2017-09-16 07:03:20 DEBUG (MainThread) [bellows.uart] Sending: b’564f218ea26f7e’
2017-09-16 07:03:20 DEBUG (MainThread) [bellows.uart] Data frame: b’664fa18ec4b381bf59fb47250c867e’
2017-09-16 07:03:20 DEBUG (MainThread) [bellows.uart] Sending: b’87009f7e’
2017-09-16 07:03:20 DEBUG (MainThread) [bellows.ezsp] Application frame 38 (getEui64) received
2017-09-16 07:03:20 INFO (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=zha, service=permit>
2017-09-16 07:03:20 INFO (MainThread) [homeassistant.setup] Setup of domain zha took 0.8 seconds.
2017-09-16 07:03:20 INFO (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=zha>
2017-09-16 07:03:20 DEBUG (MainThread) [bellows.ezsp] Send command sendUnicast
2017-09-16 07:03:20 DEBUG (MainThread) [bellows.uart] Sending: b’674c219c54f4ddec99944a26a91593499c4f26acedcf678ffdc363dbbc7e’
2017-09-16 07:03:20 DEBUG (MainThread) [bellows.uart] Data frame: b’774ca19c54224e4f7e’
2017-09-16 07:03:20 DEBUG (MainThread) [bellows.uart] Sending: b’8070787e’
2017-09-16 07:03:20 DEBUG (MainThread) [bellows.ezsp] Application frame 52 (sendUnicast) received
2017-09-16 07:03:21 DEBUG (MainThread) [bellows.uart] Data frame: b’074cb19754f4ddec99944a26a91592499c4626abedbd9b7e’
2017-09-16 07:03:21 DEBUG (MainThread) [bellows.uart] Sending: b’8160597e’
2017-09-16 07:03:21 DEBUG (MainThread) [bellows.ezsp] Application frame 63 (messageSentHandler) received

2017-09-16 07:03:31 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File “/usr/local/lib/python3.6/asyncio/tasks.py”, line 180, in _step
result = coro.send(None)
File “/usr/src/app/homeassistant/components/zha/init.py”, line 146, in async_device_initialized
discovered_info = yield from _discover_endpoint_info(endpoint)
File “/usr/src/app/homeassistant/components/zha/init.py”, line 290, in _discover_endpoint_info
yield from read([‘manufacturer’, ‘model’])
File “/usr/src/app/homeassistant/components/zha/init.py”, line 286, in read
allow_cache=True,
File “/usr/local/lib/python3.6/site-packages/bellows/zigbee/zcl/init.py”, line 192, in read_attributes
result = yield from self.read_attributes_raw(to_read)
File “/usr/local/lib/python3.6/site-packages/bellows/zigbee/zcl/init.py”, line 159, in read_attributes_raw
v = yield from self.request(True, 0x00, schema, attributes)
File “/usr/local/lib/python3.6/site-packages/bellows/zigbee/application.py”, line 283, in request
v = yield from asyncio.wait_for(reply_fut, timeout)
File “/usr/local/lib/python3.6/asyncio/tasks.py”, line 362, in wait_for
raise futures.TimeoutError()
concurrent.futures._base.TimeoutError

gohassgo · September 15, 2017, 11:45pm

I’m running hass.io 0.53.1 and zha with a HUSBZB-1 USB stick.

Also paired were a couple of Quirky + GE “Tripper” Smart Window/Door Sensors. They are also pretty snappy responders. They show as “Sercomm Corp. Tripper” and only successfully report an open/closed state.These are reset and paired by holding the button down while inserting the battery and continue holding the button for a couple of seconds.

A few GE Link dimmable lights are working as well. They show up as “GE_Appliances ZLL Light” and have both the on/off switch and a brightness slider on the device card. These take five one-second on/off cycles to reset and join.

Paul_M · September 23, 2017, 4:51pm

@gregg098 I’m trying to get the Smartthings / Centralite 3305-S Motion Sensor to pair but cannot. You mentioned you got this to work? Do you remember doing anything special?

I’ve removed the sensor from my smart things hub. I did a factory reset on the motion sensor. I’ve done a zha permit and northing. I tried putting the battery in right after calling zha permit, and the motion sensor green light comes on for a few seconds but it does not pair. Additionally I have the sensor directly next to the my GoControl HUSBZB-1 stick.

I was able to pair the lower iris sensors fine.

Any ideas?

Paul_M · September 23, 2017, 5:15pm

@gregg098 Nevermind as I figured it out. I was not doing a proper factory reset.

For anyone else trying to figure this out, the proper steps to factory reset the Centralite 3305-S Motion Sensor (SmartThings) motion sensor and add to home assistant is:

Take the cover off the motion sensor and remove the battery
Find something that can push the reset button the motion sensor
Call the zha permit service in HA
Hold the reset button down on then motion and put the battery back in
A red light should appear on the motion sensor, release the reset button BEFORE the red light goes off on its own.
It should now pair automatically with HA after performing step #5. I believe a blue light will appear on the motion sensor when this is happening.

My issue was step #5, I was waiting for the red light to go off on its own.

Paul

gohassgo · September 24, 2017, 12:57am

All of my PeQ branded Centralite sensors pair in this way–holding the reset button while popping in the battery and then let go of the button.

sephtin · September 25, 2017, 4:56am

NYCE NCZ-3010-HA (Zigbee) Door Hinge Sensor. I bought mine at Lowes.

Result: Fails to pair, I’m using HUSBZB-1 with HS-zha. Other devices are fine, but the door hinge pairs, then “leaves”.

hass logs for trying to pair:

2017-09-24 21:09:14 INFO (MainThread) [homeassistant.core] Bus:Handling <Event call_service[L]: domain=zha, service_data=, service=permit, service_call_id=139808344413296-16>
2017-09-24 21:09:14 INFO (MainThread) [homeassistant.components.zha] Permitting joins for 60s
2017-09-24 21:09:14 INFO (MainThread) [homeassistant.core] Bus:Handling <Event service_executed[L]: service_call_id=139808344413296-16>
...
2017-09-24 21:09:35 INFO (MainThread) [bellows.zigbee.application] Device 0x9b9a (00:0d:6f:00:0b:1f:26:66) joined the network
2017-09-24 21:09:35 INFO (MainThread) [bellows.zigbee.device] [0x9b9a] Discovering endpoints
2017-09-24 21:09:35 INFO (MainThread) [bellows.zigbee.device] [0x9b9a] Discovered endpoints: [1]
2017-09-24 21:09:35 INFO (MainThread) [bellows.zigbee.endpoint] [0x9b9a:1] Discovering endpoint information
2017-09-24 21:09:36 INFO (MainThread) [bellows.zigbee.endpoint] [0x9b9a:1] Discovered endpoint information: <SimpleDescriptor endpoint=1 profile=260 device_type=1026 device_version=0 input_clusters=[0, 1, 3, 1280, 32] output_clusters=[]>
2017-09-24 21:09:36 INFO (MainThread) [homeassistant.core] Bus:Handling <Event platform_discovered[L]: platform=zha, discovered=discovery_key=00:0d:6f:00:0b:1f:26:66-1-1280, service=load_platform.binary_sensor>
2017-09-24 21:09:36 INFO (MainThread) [homeassistant.components.binary_sensor] Setting up binary_sensor.zha
2017-09-24 21:09:38 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: new_state=<state binary_sensor.nyce_3010_0b1f2666_1=off; friendly_name=NYCE 3010, device_class=opening @ 2017-09-24T21:09:38.102357-05:00>, entity_id=binary_sensor.nyce_3010_0b1f2666_1, old_state=None>
2017-09-24 21:09:38 INFO (MainThread) [bellows.zigbee.application] Device 0x9b9a (00:0d:6f:00:0b:1f:26:66) left the network

The reviews for the sensor have been mixed, but as they don’t work with hass, I have several paired to SmartThings through MQTT with good luck so far. I’d much rather they were working natively.

If I can provide additional details to help get these working, please feel free to contact me!

christheradioguy · September 26, 2017, 3:07pm

Out of curiosity has anyone been able to pair the Lutron Connected Bulb remote with HASS? Got a couple of these currently paired to a Wink Hub and would love to have them natively paired to Home Assistant.

nichol · September 30, 2017, 12:56am

Hi,

I am just wondering if anybody has managed to get the hue dimmer to work with ZHA, acting as a trigger in HA.

Bellows is able to see the remote, however I am unable to see it in HA.

Thanks,
Nichol

Bellows devices output below:
Device:
NWK: 0xb151
IEEE: 00:17:88:01:02:0f:71:f0
Endpoints:
1: profile=0xc05e, device_type=DeviceType.SCENE_CONTROLLER
Input Clusters:
Basic (0)
Output Clusters:
Basic (0)
Identify (3)
Groups (4)
Scenes (5)
On/Off (6)
Level control (8)
2: profile=0x104, device_type=DeviceType.SIMPLE_SENSOR
Input Clusters:
Basic (0)
Power Configuration (1)
Identify (3)
Binary Input (Basic) (15)
Manufacturer Specific (64512)
Output Clusters:
Ota (25)

gazoscalvertos · October 1, 2017, 8:44pm

What different did you do to get these to pair initially?

traslin · October 2, 2017, 2:19pm

From what I could tell, you just had to get the timing perfect. So I just tried different counts for when to start the ZHA pairing on the HA side when resetting the bulbs, including starting the pairing before the bulbs reset. I can’t remember the exact timing when it finally worked though.

JackieBrown · October 3, 2017, 12:48am

Any tricks for that Mike. I have a ton of those bulbs but can’t get them to pair at all

gazoscalvertos · October 3, 2017, 10:27am

Thanks, I shall give this a shot.

Paul_M · October 8, 2017, 12:10pm

I’m having issues getting a third 3326-L motion sensor to pair in HA 0.54/0.55. I have two previous 3326-L motion sensors I had no issues pairing, and continue to work fine in HA to this day. I’m using the GoControl HUSBZB-1 stick. Any ideas?

mike1237 · October 16, 2017, 5:10pm

@roothorick is right, Iris v1 devices don’t speak Zigbee Home Automation (ZHA) protocol.

They speak “AlertMe” which is a custom protocol built ontop of Zigbee stack.

Someone wrote a python library to speak this protocol, but it’s not integrated into Hass (yet).

mike1237 · October 16, 2017, 5:13pm

Someone did reverse engineer the protocol and made a python wrapper for it.

Now we just need to create a Hass component to tie the two together.

wixoff · October 17, 2017, 1:00am

I don’t know if it’s just me, but zha doesn’t seem to be working as well as it did before:

My GE Link bulbs used to work flawlessly, and now they all disappear from HASS when restarting (and have to be reset and re-added each time).

My Sylvania Lightify RGBW bulbs have lost their RGB functionality, and are now only white and color temperature adjustable.

My IKEA Tradfri plain-white bulb (1000lm) won’t join the network anymore.

Weird. Anyone else seeing these problems?

wakeskate · October 18, 2017, 6:58am

Visonic MCT-340 E Wireless Door Window Sensor 2.4ghz ZigBee
This sensor has been working great but after upgrading to 0.54
the temp sensor now just has a dash and does not show temp.
Upgraded to 0.55.2 and still the same issue.

Anyone have this working?

garn · October 22, 2017, 3:18pm

On earlier versions temperature (on the MCT-340E) was sporadically working, getting ready to upgrade now and will let you know.

Any more word on the Bosch motion sensors as far as getting those to work?

ETA: Under states in developer tools for one of the sensors I’m getting the temperature and for the other I’m getting “Unknown” for now…