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

To add Iris devices did you just simply reset the devices then go to services ->ZHA -> Permit? My HA seems to be able to see them tries to add them then they leave the network

“2017-05-22 22:02:50 INFO (MainThread) [bellows.zigbee.application] Device 0xd549 (00:15:5f:00:b4:4c:e4:84) left the network”

Would like to understand how you add them?

Yep, just reset them (the ones I have blink blue I believe when searching for a network after being reset) and then run the permit service in HA. I had better success doing one sensor at a time.

Visonic MCT-340 E Window/Door Switch: Working

Got them from: https://www.mydigitaldiscount.com/visonic-window-or-door-sensor-for-samsung-smartthings-mct-340e/

Not Working- Bosch Security Motion Sensor PIR Pet Immune for Samsung SmartThings and other Smart Hubs with Zigbee Wireless - ISW-ZPR1-WP13

https://www.mydigitaldiscount.com/bosch-security-motion-sensor-pir-pet-immune-for-samsung-smartthings-and-other-smart-hubs-with-zigbee-wireless/

HA finds it but then leaves the network

484_5, new_state=<state binary_sensor.bosch_iswzpr1wp13_b44ce484_5=off; friendly_name=Bosch ISW-ZPR1-WP13, device_class=motion @ 2017-05-23T17:15:20.478345-04:00>>
2017-05-23 21:15:28 INFO (MainThread) [bellows.zigbee.application] Device 0x3f9f (00:15:5f:00:b4:4c:e4:84) left the network

1 Like

Not working OSRAM SYLVANIA iBR30 Light

“Left the network” similar to bosch motion sensor.

Smartthings Motion Sensor (2015) - working - connected as CentaLite 3325-S.

i can also confirm that Iris Motion V2 is working.

The above ‘working’ means that i see motion and temperature. Unfortunately, there is no Battery status and i get a lot of

2017-05-24 08:58:15 WARNING (MainThread) [bellows.zigbee.application] Unexpected message send notification 2017-05-24 08:58:17 WARNING (MainThread) [bellows.zigbee.zcl] Unknown cluster 64582 2017-05-24 08:59:01 WARNING (MainThread) [bellows.zigbee.zcl] Data remains after deserializing ZCL frame 2017-05-24 08:59:01 WARNING (MainThread) [bellows.zigbee.zcl] [0x0a1d:1:0x0500] No handler for cluster command 1 2017-05-24 08:59:02 WARNING (MainThread) [bellows.zigbee.zcl] [0x0a1d:1:0x0500] No handler for cluster command 0 2017-05-24 08:59:03 WARNING (MainThread) [bellows.zigbee.zcl] [0x0a1d:1:0x0500] No handler for cluster command 0 2017-05-24 08:59:04 WARNING (MainThread) [bellows.zigbee.zcl] [0x0a1d:1:0x0500] No handler for cluster command 0 2017-05-24 08:59:59 WARNING (MainThread) [bellows.zigbee.zcl] [0x0a1d:1:0x0500] No handler for cluster command 0 2017-05-24 09:00:44 WARNING (MainThread) [bellows.zigbee.zcl] [0x0a1d:1:0x0500] No handler for cluster command 0 2017-05-24 09:00:57 WARNING (MainThread) [bellows.zigbee.zcl] [0x0a1d:1:0x0500] No handler for cluster command 0 2017-05-24 09:02:38 WARNING (MainThread) [bellows.zigbee.application] Unexpected message send notification 2017-05-24 09:02:39 WARNING (MainThread) [bellows.zigbee.zcl] Data remains after deserializing ZCL frame 2017-05-24 09:02:39 WARNING (MainThread) [bellows.zigbee.endpoint] [0x0a1d:1] Message on unknown cluster 0x0019 2017-05-24 09:02:42 WARNING (MainThread) [bellows.zigbee.zcl] Data remains after deserializing ZCL frame

GE Link bulbs - 4 connected; first two were recognized immediately, the other two had difficulties (time-out errors) and required HASS restart.

Cree connected bulb…working show’s up as ZHA xx xx xx xxx, how can I rename this to something meaningful?

Lutron Connect Remote–Failed, and incomplete config hangs HASS. Had to remark out ZHA in order to get it to run.

Yes, I tried the Lutron Connected Bulb Remote myself, with similar results. The author of the component says that remotes/buttons aren’t supported yet but that he hopes they will be.

1 Like

Iris Button 3460-L - Failed, only shows Temperature.

BTW, does anybody know how to remove a device from HASS?

The dev says he is looking at a way to allow renaming. In the meantime I installed a sqlite browser on my desktop, shutdown HASS, copied the zigbee.db file and opened in the sqlite app and edited the attributes directly then saved and reuploaded to the HASS location and started HASS back up. Seems to work fine, but probably not the safest/best way :slight_smile:

1 Like

I used customize to rename them in the UI.

1 Like

Makes sense, as it’s an SQ database file used to store the Zigbee config…thanks

@wixoff, thanks for the update–sure hope the Dev can get those Lutron CBR working. I have 5 that I got for $7 each. Work with Wink, but a bit awkward to configure. Nevertheless, mounted on switch box, you get 4 buttons that can trigger anything–pretty sweet :slight_smile:

Guess I’ll have to dive in customize now

You can trash the whole database file but you’ll loose any other zigbee devices that you have paired, otherwise yo can edit that SQL file (zigbee.db) with something like @lordsiris sugguested.

I did that as well, but wanted cleaner/shorter/useful names for the devices to be used in automations.

1 Like

So interesting enough, with Cree Connect bulbs, they show up in HASS even before a restart (after pairing). Then after restart, they get renamed to Cree Connected A-19 60W Equivalent , I guess so kind of further detection get the name from the device… It actually adds a second record to the DB, under Attributes. If I rename the value field, it lets allows me to change the name within HASS (shutdown HASS etc. as explained by @lordsiris

The Lutron Connect bulb remote is great for resetting bulbs, BTW, when testing etc., bottom and second button, hold close to lights, wait for the light to blink and the bulb it reset :slight_smile:

i spent the past few days migrating my Zigbee devices from ST to Hass (using Zha component)

after many trials i managed to to get 13 devices up and running successfully, but suddenly i cannot include more devices event from the same types i managed to add before, the log as below

2017-06-02 01:32:45 INFO (MainThread) [homeassistant.components.zha] Permitting joins for 60s
2017-06-02 01:32:45 DEBUG (MainThread) [bellows.ezsp] Send command permitJoining
2017-06-02 01:32:45 DEBUG (MainThread) [bellows.uart] Sending: b’\x00R!\x8ah!T~’
2017-06-02 01:32:45 DEBUG (MainThread) [bellows.uart] Data frame: b’\x01R\xa1\x8aTG\x80~’
2017-06-02 01:32:45 DEBUG (MainThread) [bellows.uart] Sending: b’\x81`Y~’
2017-06-02 01:32:45 DEBUG (MainThread) [bellows.ezsp] Application frame 34 (permitJoining) received
2017-06-02 01:32:45 INFO (MainThread) [homeassistant.core] Bus:Handling <Event service_executed[L]: service_call_id=1978375536-1>
2017-06-02 01:32:48 DEBUG (MainThread) [bellows.uart] Data frame: b’\x11R\xb1\xedT.\x14\xabY\x95Ke\xabU\x92\xaac\xf30w\x121k\x8a\xef\xc7cV>^?\xb7\xb8\xcd\xcf\x0cJ~’
2017-06-02 01:32:48 DEBUG (MainThread) [bellows.uart] Sending: b’\x82P:~’
2017-06-02 01:32:48 DEBUG (MainThread) [bellows.ezsp] Application frame 69 (incomingMessageHandler) received
2017-06-02 01:32:48 WARNING (MainThread) [bellows.zigbee.zcl] Data remains after deserializing ZCL frame
2017-06-02 01:32:48 WARNING (MainThread) [bellows.zigbee.endpoint] [0xdc17:1] Message on unknown cluster 0x0019
2017-06-02 01:32:51 DEBUG (MainThread) [bellows.uart] Data frame: b’!R\xb1\xedT.\x14\xabY\x95Ke\xabU\x92\xadc\xf30w\x121k\x8a\xee\xc7cV>^?\xb7\xb8\xcd\xcfh\xa0~’
2017-06-02 01:32:51 DEBUG (MainThread) [bellows.uart] Sending: b’\x83@\x1b~’
2017-06-02 01:32:51 DEBUG (MainThread) [bellows.ezsp] Application frame 69 (incomingMessageHandler) received
2017-06-02 01:32:51 WARNING (MainThread) [bellows.zigbee.zcl] Data remains after deserializing ZCL frame
2017-06-02 01:32:51 WARNING (MainThread) [bellows.zigbee.endpoint] [0xdc17:1] Message on unknown cluster 0x0019
2017-06-02 01:32:53 DEBUG (MainThread) [bellows.uart] Data frame: b’1R\xb1\xedT.\x14\xabY\x95Ke\xabU\x92\xacc\xf00w\x121k\x8a\xe9\xc7cV>^?\xb7\xb8\xcd\xcfgJ~’
2017-06-02 01:32:53 DEBUG (MainThread) [bellows.uart] Sending: b’\x840\xfc~’
2017-06-02 01:32:53 DEBUG (MainThread) [bellows.ezsp] Application frame 69 (incomingMessageHandler) received
2017-06-02 01:32:53 WARNING (MainThread) [bellows.zigbee.zcl] Data remains after deserializing ZCL frame
2017-06-02 01:32:53 WARNING (MainThread) [bellows.zigbee.endpoint] [0xdc17:1] Message on unknown cluster 0x0019

any one can help with this issue ?

Can confirm the same behavior with the Bosch Motion Sensor. I have extras if a dev needs a sample to get working. This is a cheap and readily available option, I’m sure many folks picked them up for 12.50/ea a few weeks ago.

For the time being these will remain connected through my Vera, but that’s the last bit to get me moving totally to HA.

1 Like

I moved all my zigbee devices back to SmartThings and pull in the states via MQTT. Half are locally controlled and half require the cloud on SmartThings so I’m not too happy about that but its way more reliable at this point. Really happy to see that the ZHA protocol is being built and improved, but not ready for prime time yet.

On a few occasions, I randomly couldn’t get HASS to restart. No log entries, nothing. Finally commented out ZHA and it worked. Rolled back to an old database and it worked again, but quit a few days later. At one point I deleted the data base and factory reset all devices, re-added them, etc. Worked for a few days then randomly quit again. Some window sensors would say open when they were open, but then go back to closed for no reason. Works fine on Smartthings.

Again, thanks for all the effort put in to date. Not trying to discourage the devs at all. Worst part is that when it just quits on me for no reason (no new devices or anything crazy), there are no logs to show anything. It just shows the old log as if I never restarted, but nothing loads.

1 Like