Closed mjg59 closed 6 years ago
bellows devices gives:
Device:
NWK: 0x1bc6
IEEE: 00:17:88:01:02:19:57:81
Endpoints:
1: profile=0xc05e, device_type=DeviceType.SCENE_CONTROLLER
Input Clusters:
Basic (0)
2: profile=0x104, device_type=DeviceType.SIMPLE_SENSOR
Input Clusters:
Basic (0)
Power Configuration (1)
Identify (3)
Binary Input (Basic) (15)
Manufacturer Specific (64512)
You may be interested in:
The main thing you missed is the difference between input and output clusters. Those branches include the changes for that (I'm waiting on some other merges to home-assistant before I can request a merge of the input/output cluster split).
The remote works fine when it is first connected. I've presented it as a binary sensor with a level. If you leave the remote for a while without using it, it fails to properly reconnect to the network. I haven't figured out what needs to be done for that to work.
Thanks! I have root on a Hue hub, so I'll see if I can dump the Zigbee traffic there.
That may be useful, but it'll almost certainly use the zll profile, and the differences between zll and zha may be important.
I did some research yesterday, and it looks like it needs some changes in the way that bellows configures the radio to handle rejoins, but I haven't figured out exactly what from the docs yet.
I'm fairly new to zigbee, but I'm not understanding exactly what's missing here... after today's "Smart"things outage, I'm renewing my push to get everything on Home Assistant... and I rely on these Hue buttons a little too much.
So, as above, bellows finds the device, sees that its a "SCENE_CONTROLLER", adds it to the database, and then this is where with my Cree bulbs I saw HASS setting up the device... I see nothing past the Hue buttons joining the network. The device types match the zll.py file, and the output clusters line up as well, so where is the next step taking place beyond it joining the network?
@scottcmace
after today's "Smart"things outage, I'm renewing my push to get everything on Home Assistant...
I don't have Hue buttons, but I'm with you on that push. I just unplugged my SmartThings hub last night. Best feeling ever!
So, is the problem that the device type isn't in the table, or is it that HA doesn't know how to handle a device of this type?
This is my single biggest hurdle at this point... these infernal buttons.
I'm on the same boat with a Lutron Bulb Remote, it get registered on Bellows but after that, buttons events doesn't appear to be registered.
Device: NWK: 0x1e96 IEEE: ff:ff:00:0f:e7:ff:96:dd Endpoints: 1: profile=0xc05e, device_type=DeviceType.CONTROLLER Input Clusters: Basic (0) LightLink (4096) Manufacturer Specific (64580) Manufacturer Specific (65280) Output Clusters: Basic (0) Identify (3) Groups (4) Scenes (5) On/Off (6) Level control (8) LightLink (4096) Manufacturer Specific (65280)
Please re-open in the new zigpy project (https://github.com/zigpy/zigpy) if this is still an issue. There appears to be no way to move issues between projects.
Since these remotes are all implemented differently, I think the only sensible approach is to add proper support for custom device type handlers outside of zigpy, and implement each of them separately.
I'm trying to add support for a Philips Hue dimmer remote to HASS. I've done the following so far:
I then get a binary sensor device in HASS. However, hitting buttons never calls the cluster_command() method and I see no debug output from bellows. zha and bellows debug output: