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

I just ran the permit service and put the device in pairing mode. Most of the time I had to do a HASS restart to get devices to show up. There is 0 feedback on the frontend so not sure if I did anything weird.

Has anyone successfully paired Philips Hue motion sensor with zha? I just tried and I see binary_sensor.philips_hue and sensor.philips_sml001_020054d5_2 showed up.

But binary_sensor.philips_hue always shows state = ‘on’ and sensor.philips_sml001_020054d5_2 which is the temp sensor always has “unknown” value

May I suggest we start using a template for these submissions?

This seems to show up fine, and immediately showed a binary switch on the main page.

Friendly Name: CentraLite 3455-L
Type of Device: Iris Generation 2 - Single Button (Emergency Style)
Entity ID: binary_sensor.centralite_3455l_********_1

Database Values

Attributes

| endpoint_id | cluster | attrid |     value    |
|-------------|---------|--------|--------------|
|      1      |    0    |   4    |  CentraLite  |
|      1      |    0    |   5    |    3455-L    |
|      1      |   1280  |   1    |     44       |

Clusters

| attrid | value  |
|--------|--------|
|   1    |   0    |
|   1    |   1    |
|   1    |   3    |
|   1    |  1280  |
|   1    |   32   |

Devices

|  nwk  | status |
|-------|--------|
| 49853 |    1   |

Endpoints

| endpoint_id | profile_id | device_type | status |
|-------------|------------|-------------|--------|
|      1      |     260    |     1026    |    1   |

For anyone interested in testing the various zigbee sensors/devices, they are back on sale for pretty cheap:
https://www.mydigitaldiscount.com/home.php?cat=621&mode=search&sort=pricelh

got a zig bee fan controller from king of fans… Looks like it pairs and creates a switch… It will turn on light but switch goes off in ui instantly and light stays on… no entitiy for fan at all …this is the entity it creates

switch.king_of_fans__inc_hdc52eastwindfan_0016b720_1

2017-06-18 09:52:36 DEBUG (MainThread) [bellows.ezsp] Send command sendUnicast
2017-06-18 09:52:36 DEBUG (MainThread) [bellows.uart] Sending: b'pM!\x9cT\xbb\xf8\xb6X\x92J$\xab\x15\x93I\x9cO&\xa8\xec\xcff\xc59~'
2017-06-18 09:52:36 DEBUG (MainThread) [bellows.uart] Data frame: b'\x00M\xa1\x9cT\x89mB~'
2017-06-18 09:52:36 DEBUG (MainThread) [bellows.uart] Sending: b'\x81`Y~'
2017-06-18 09:52:36 DEBUG (MainThread) [bellows.ezsp] Application frame 52 (sendUnicast) received
2017-06-18 09:52:36 DEBUG (MainThread) [bellows.uart] Data frame: b'\x10M\xb1\x97T\xbb\xf8\xb6X\x92J$\xab\x15\x93I\x9c\xed&\xab\xedW$~'
2017-06-18 09:52:36 DEBUG (MainThread) [bellows.uart] Sending: b'\x82P:~'
2017-06-18 09:52:36 DEBUG (MainThread) [bellows.ezsp] Application frame 63 (messageSentHandler) received
2017-06-18 09:52:42 DEBUG (Thread-1) [dlipower.dlipower] Response code: 200

output from log

sorry Shabrawy didnt mean that reply to you

after doing a new automation got these errors on restart if it helps any

2017-06-18 12:06:49 DEBUG (MainThread) [bellows.uart] Data frame: b'\x07L\xb1\xedP*\x15\xb4Y\x94J-\xabU\x92vc\x8d\xb6F\x121n\x96\x009g\x88\xfdg?\xa7~;~'
2017-06-18 12:06:49 DEBUG (MainThread) [bellows.uart] Sending: b'\x81`Y~'
2017-06-18 12:06:49 DEBUG (MainThread) [bellows.ezsp] Application frame 69 (incomingMessageHandler) received
2017-06-18 12:06:49 DEBUG (MainThread) [bellows.zigbee.zdo] [0xed91:zdo] ZDO request 0x0006: [65533, 260, [25], []]
2017-06-18 12:06:49 DEBUG (MainThread) [bellows.ezsp] Send command sendUnicast
2017-06-18 12:06:49 DEBUG (MainThread) [bellows.uart] Sending: b'qM!\x9cT\xbb\xf8\xb2Y\x92\xca%\xaa\x15\x93I\x9cO&\xad\xec\xceg\x8b\xfc\xc7*G~'
2017-06-18 12:06:49 DEBUG (MainThread) [bellows.uart] Data frame: b'\x10M\xa1\x9cT\x82\xc6\xad~'
2017-06-18 12:06:49 DEBUG (MainThread) [bellows.uart] Sending: b'\x82P:~'
2017-06-18 12:06:49 DEBUG (MainThread) [bellows.ezsp] Application frame 52 (sendUnicast) received
2017-06-18 12:06:49 DEBUG (MainThread) [bellows.uart] Data frame: b' M\xb1\x97T\xbb\xf8\xb2Y\x92\xca%\xaa\x15\x93I\x9c\xe6&\xab\xed\x7fG~'
2017-06-18 12:06:49 DEBUG (MainThread) [bellows.uart] Sending: b'\x83@\x1b~'
2017-06-18 12:06:49 DEBUG (MainThread) [bellows.ezsp] Application frame 63 (messageSentHandler) received
2017-06-18 12:06:49 WARNING (MainThread) [bellows.zigbee.application] Unexpected message send notification
2017-06-18 12:06:51 DEBUG (MainThread) [bellows.uart] Data frame: b"0M\xb1\xedT.\x14\xabY\x95Ke\xaaU\x92\tc\x8d\xb6F\x121k\x8a\xfa\xc7c\x8b\xec~?\xa8\xeb\xcd\xde\xed'~"
2017-06-18 12:06:51 DEBUG (MainThread) [bellows.uart] Sending: b'\x840\xfc~'
2017-06-18 12:06:51 DEBUG (MainThread) [bellows.ezsp] Application frame 69 (incomingMessageHandler) received
2017-06-18 12:06:51 WARNING (MainThread) [bellows.zigbee.zcl] Data remains after deserializing ZCL frame
2017-06-18 12:06:51 WARNING (MainThread) [bellows.zigbee.endpoint] [0xed91:1] Message on unknown cluster 0x0019
2017-06-18 12:06:54 DEBUG (MainThread) [bellows.uart] Data frame: b'@M\xb1\xedT.\x14\xabY\x95Ke\xaaU\x92\x08c\x8d\xb6F\x121k\x8a\xf5\xc7c\x8b\xec~?\xa8\xeb\xcd\xde)E~'
2017-06-18 12:06:54 DEBUG (MainThread) [bellows.uart] Sending: b'\x85 \xdd~'
2017-06-18 12:06:54 DEBUG (MainThread) [bellows.ezsp] Application frame 69 (incomingMessageHandler) received
2017-06-18 12:06:54 WARNING (MainThread) [bellows.zigbee.zcl] Data remains after deserializing ZCL frame
2017-06-18 12:06:54 WARNING (MainThread) [bellows.zigbee.endpoint] [0xed91:1] Message on unknown cluster 0x0019
2017-06-18 12:06:57 DEBUG (MainThread) [bellows.uart] Data frame: b'PM\xb1\xedT.\x14\xabY\x95Ke\xaaU\x92\x0bc\xf0\xb6F\x121k\x8a\xf4\xc7c\x8b\xec~?\xa8\xeb\xcd\xde\xb1\t~'
2017-06-18 12:06:57 DEBUG (MainThread) [bellows.uart] Sending: b'\x86\x10\xbe~'
2017-06-18 12:06:57 DEBUG (MainThread) [bellows.ezsp] Application frame 69 (incomingMessageHandler) received
2017-06-18 12:06:57 WARNING (MainThread) [bellows.zigbee.zcl] Data remains after deserializing ZCL frame
2017-06-18 12:06:57 WARNING (MainThread) [bellows.zigbee.endpoint] [0xed91:1] Message on unknown cluster 0x0019
2017-06-18 12:07:00 DEBUG (MainThread) [bellows.uart] Data frame: b'`M\xb1\xedT.\x14\xabY\x95Ke\xaaU\x92\nc\x8c\xb6F\x121k\x8a\xf7\xc7c\x8b\xec~?\xa8\xeb\xcd\xde5\x8d~'
2017-06-18 12:07:00 DEBUG (MainThread) [bellows.uart] Sending: b'\x87\x00\x9f~'
2017-06-18 12:07:00 DEBUG (MainThread) [bellows.ezsp] Application frame 69 (incomingMessageHandler) received
2017-06-18 12:07:00 WARNING (MainThread) [bellows.zigbee.zcl] Data remains after deserializing ZCL frame
2017-06-18 12:07:00 WARNING (MainThread) [bellows.zigbee.endpoint] [0xed91:1] Message on unknown cluster 0x0019
2017-06-18 12:07:03 DEBUG (MainThread) [bellows.uart] Data frame: b'pM\xb1\xedT.\x14\xabY\x95Ke\xaaU\x92\rc\x8d\xb6F\x121k\x8a\xf6\xc7c\x8b\xec~?\xa8\xeb\xcd\xde\x86z~'
2017-06-18 12:07:03 DEBUG (MainThread) [bellows.uart] Sending: b'\x80px~'
2017-06-18 12:07:03 DEBUG (MainThread) [bellows.ezsp] Application frame 69 (incomingMessageHandler) received
2017-06-18 12:07:03 WARNING (MainThread) [bellows.zigbee.zcl] Data remains after deserializing ZCL frame
2017-06-18 12:07:03 WARNING (MainThread) [bellows.zigbee.endpoint] [0xed91:1] Message on unknown cluster 0x0019

More on @Vasiley’s device:

devices

| ieee                    | nwk   | status |
|-------------------------|-------|--------|
| 00:22:a3:00:00:16:b7:20 | 60817 | 1      |

endpoints

| ieee                    | endpoint_id | profile_id | device_type | status |
|-------------------------|-------------|------------|-------------|--------|
| 00:22:a3:00:00:16:b7:20 | 1           | 260        | 14          | 1      |

clusters

| ieee                    | endpoint_id | cluster |
|-------------------------|-------------|---------|
| 00:22:a3:00:00:16:b7:20 | 1           | 0       |
| 00:22:a3:00:00:16:b7:20 | 1           | 514     |
| 00:22:a3:00:00:16:b7:20 | 1           | 3       |
| 00:22:a3:00:00:16:b7:20 | 1           | 4       |
| 00:22:a3:00:00:16:b7:20 | 1           | 5       |
| 00:22:a3:00:00:16:b7:20 | 1           | 6       |
| 00:22:a3:00:00:16:b7:20 | 1           | 8       |

attributes

| ieee                    | endpoint_id | cluster | attrid | value               |
|-------------------------|-------------|---------|--------|---------------------|
| 00:22:a3:00:00:16:b7:20 | 1           | 0       | 4      | King Of Fans,  Inc. |
| 00:22:a3:00:00:16:b7:20 | 1           | 0       | 5      | HDC52EastwindFan    |

My one Osram Lightify RGBW A19 bulb is working now, using HA 0.47 with the latest bellows files installed from github (bellows-master as of June 9, 2017).

I still get a warning in the log:

2017-06-18 17:07:11 WARNING (MainThread) [bellows.zigbee.zcl] Unknown cluster 64527

But all else seems to work – inclusion, on, off, brightness, and color.

I have some other bulbs (GE Link, Osram Lightify Tunable White) I’ll try out soon, but these are all attached to my Lightify hub (and working!) so I might not get around to it for a while.

I’m seeing the leaksmart water sensors register temperature, but no binary report for water.

IRIS keypad doesn’t seem to show up either.

So for my Centralite 3455L (Iris Gen 2 Button) and it seems to work alright.

I created an automation:

- action:
  - data:
      entity_id: group.office_lights
    service: light.toggle
  alias: THE_RED_BUTTON
  id: '1498025574516'
  trigger:
  - entity_id: binary_sensor.centralite_3455l_057bb645_1
    from: 'off'
    platform: state
    to: 'on'

Instantly this pops up

2017-06-24 03:19:59 WARNING (MainThread) [bellows.zigbee.zcl] [0xc2bd:1:0x0500] No handler for cluster command 0

Then this pops up, the script / automation fires.

2017-06-24 03:19:59 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: new_state=<state binary_sensor.centralite_3455l_057bb645_1=on; friendly_name=CentraLite 3455-L @ 2017-06-24T02:19:59.168815-05:00>, old_state=<state binary_sensor.centralite_3455l_057bb645_1=off; friendly_name=CentraLite 3455-L @ 2017-06-24T02:19:51.153957-05:00>, entity_id=binary_sensor.centralite_3455l_057bb645_1>
2017-06-24 03:19:59 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: new_state=<state group.centralite_emergency_button_01=on; order=17, assumed_state=False, friendly_name=Red Button, entity_id=('binary_sensor.centralite_3455l_057bb645_1',) @ 2017-06-24T02:19:59.201451-05:00>, old_state=<state group.centralite_emergency_button_01=off; order=17, assumed_state=False, friendly_name=Red Button, entity_id=('binary_sensor.centralite_3455l_057bb645_1',) @ 2017-06-24T02:19:51.164812-05:00>, entity_id=group.centralite_emergency_button_01>
2017-06-24 03:19:59 INFO (MainThread) [homeassistant.components.automation] Executing THE_RED_BUTTON
2017-06-24 03:19:59 INFO (MainThread) [homeassistant.core] Bus:Handling <Event logbook_entry[L]: entity_id=automation.the_red_button, domain=automation, message=has been triggered, name=THE_RED_BUTTON>
2017-06-24 03:19:59 INFO (MainThread) [homeassistant.helpers.script] Script THE_RED_BUTTON: Running script
2017-06-24 03:19:59 INFO (MainThread) [homeassistant.helpers.script] Script THE_RED_BUTTON: Executing step call service
2017-06-24 03:19:59 INFO (MainThread) [homeassistant.core] Bus:Handling <Event call_service[L]: service=toggle, domain=light, service_call_id=1977792656-21, service_data=entity_id=group.office_lights>
2017-06-24 03:19:59 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: new_state=<state light.office_front_left=on; max_mireds=500, effect_list=['colorloop', 'random'], supported_features=41, min_mireds=154, friendly_name=Office Front Left, brightness=254 @ 2017-06-24T02:19:59.379170-05:00>, old_state=<state light.office_front_left=off; friendly_name=Office Front Left, supported_features=41 @ 2017-06-24T02:19:50.785371-05:00>, entity_id=light.office_front_left>

Angry ZigBee messages?

2017-06-24 03:20:04 WARNING (MainThread) [bellows.zigbee.zcl] [0xc2bd:1:0x0500] No handler for cluster command 0
2017-06-24 03:20:04 WARNING (MainThread) [bellows.zigbee.zcl] [0xc2bd:1:0x0500] No handler for cluster command 0
2017-06-24 03:20:04 WARNING (MainThread) [bellows.zigbee.zcl] [0xc2bd:1:0x0500] No handler for cluster command 0

Grumpy HomeAssistant is grumpy (large recorder DB)

2017-06-24 03:20:04 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting

More state change data

2017-06-24 03:20:04 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: new_state=<state light.office_rear_right=off; friendly_name=Office Rear Right, supported_features=41 @ 2017-06-24T02:20:04.564760-05:00>, old_state=<state light.office_rear_right=on; max_mireds=500, effect_list=['colorloop', 'random'], supported_features=41, min_mireds=154, friendly_name=Office Rear Right, brightness=252 @ 2017-06-24T02:19:50.796452-05:00>, entity_id=light.office_rear_right>
2017-06-24 03:20:04 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: new_state=<state light.office_front_right=off; friendly_name=Office Front Right, supported_features=41 @ 2017-06-24T02:20:04.578908-05:00>, old_state=<state light.office_front_right=on; max_mireds=500, effect_list=['colorloop', 'random'], supported_features=41, min_mireds=154, friendly_name=Office Front Right, brightness=254 @ 2017-06-24T02:19:50.813930-05:00>, entity_id=light.office_front_right>
2017-06-24 03:20:04 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: new_state=<state light.office_hallway=off; friendly_name=Office Hallway, supported_features=41 @ 2017-06-24T02:20:04.592734-05:00>, old_state=<state light.office_hallway=on; max_mireds=500, effect_list=['colorloop', 'random'], supported_features=41, min_mireds=154, friendly_name=Office Hallway, brightness=76 @ 2017-06-24T02:19:50.842817-05:00>, entity_id=light.office_hallway>

Visonic MCT-340 E Door/Window Sensor

  • Open/Close: Working
  • Temperature: Not Working

Bosch ISW-ZPR1-WP13 Motion Sensor:

  • Motion: Not Working
  • Temperature: Working

I have the same door sensor reporting temperature, just very infrequently

Centralite 3450L (Iris Gen 2 Keyfob) - Not Working, not seen by ZHA at all as far as I can tell.

WEMO light bulbs work great. Fully dimmable, no issues.

Just purchased some Philips Hue White and Color ambiance bulbs. Brand new so set up was easy, turned on zha permit, turned on the bulbs and bang they are connected. In the front-end I can easily turn on/off/dim AND change color! I grouped the two lights together since they are in a double bulb standing light and I can even coordinate the color changes via the front-end.

The question I have is that I have some automations that turn the lights on/off based on sunlight. How do I specify the color I want it to go too? Can I default it to the ‘white’ it began with?
Thanks
Norm

Hi

When I follow your instructions my bulb loose the connection to HA in step 5. Is it not possible to have the dimmer and HA working at the same time?

RStanley,

In HA version 49.0, the ZHA component addresses the temperature issue regarding the Visonic MCT-340 E Door/Window Sensor. I confirmed that all three of my sensors are displaying temperature consistently for the last 4 hours. I simply performed the upgrade and 30 minutes later all three sensors were reporting temperature.

In regards to the Bosch ISW-ZPR1-WP13 Motion Sensor, I am unable to view the temperature and motion values. I paired this device a few weeks ago.
I am having a tough time trying to remove the Bosch sensor from HA so I can try to pair it again.

The bulb should not be paired with anything (dimmer or HA) prior to step 5. It should be completely reset (step 3). Assuming the dimmer properly paired with HA in step 4, performing step 5 should pair the bulb with both the dimmer and HA and allow it to be controlled by both.