Do they still sell the bulb remote? I can’t seem to find it anywhere.
I’ve seen them on amazon for $40 but they go out of stock quickly. Also on Ebay from time to time but it has been a few years I think since it was discontinued. Here is the part number if you care to look around. LZL-4B-WH-L01
Eep, I think I’ll stick with the lightify remotes, only $15.
Anyone Tried this one?
1 Like
yes, support for it to work fully just landed in 0.95 (previously only the on and off buttons worked)
I came across this today… this is almost exactly what I’ve been looking for to control media, scenes, lights, etc.
I wonder if anyone’s tried one of these or if anyone knows of something similar/cheaper?
Settling for IKEA 5 button remotes and ERIA remotes currently.
1 Like
Just to confirm, I switched to 0.95.1 and the Lutron Connected Bulb remotes are still working.
And yes unfortunately they aren’t making the remote anywhere, but I keep an eye out an ebay and have gotten lucky and been able to snap up used ones for $30 a few times over the last year.
the new Lutron Auroa works out of the box with HA. Only issue I’m seeing now is the on off tap doesn’t seem reliable.
the dimmer sends a 2-255 number as you turn it, which I think with some templating can be mapped directly to brightness. need to figure that out!
i can now confirm that the aqara WXKG03LM now has a working quirk as does the ikea 5 button remote this is amazing thanks for all the hard work
2 Likes
Oh, nice, thanks for the heads up. What did you do to get it going? Update HA to the 95.0 version? Or did you have to re-bind the button?
I installed 0.95 yesterday. A few impacts that I have noticed so far
- Original Xiaomi Door/Window sensors (the oval version) appear to have lost their binary sensor. I understand remotes have had this removed, but it seems an oversight for this sensor to not have it. It can be worked around with an automation and an input_boolean, but not ideal. Same behaviour on two different sensors. No improvement on re-pairing
- A number of my Xiaomi motion sensors, the newer ones with the illumination sensors have changed entity_id for the motion entity. Having joined them previously, the IDs ended in “_1” which changed with the new release to “_1280”
- It appears that there is an issue with adding new devices that for some reason they do not get a corresponding entry into the device registry. Ive seen this with 2 different Philips Hue Dimmers. This causes issues like not being able to give them a friendly name in the ZHA config panel or see them in the ZHA integrations list, however they do seem to behave ok as remotes.
I’d be interested if anyone else has experienced these issues?
1 Like
The mija magnet fixed in dev already. Sorry about that!
1 Like
This is concerning… is this 100% repeatable? There shouldn’t have been any changes that affected this…
I joined three Philips remotes before upgrading (0.94.3) and they are in the device registry and can be edited. All my other sensors were also done on < 0.95 and are editable. After the upgrade I joined two more Philips remotes and neither appear in the device registry. If I try to edit their name in the ZHA control panel, I get the following error:
Jun 28 21:37:22 ha hass[10503]: 2019-06-28 21:37:22 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection.140259676281320] Error handling message: required key not provided @ data['device_id']. Got None
Jun 28 21:37:22 ha hass[10503]: Traceback (most recent call last):
Jun 28 21:37:22 ha hass[10503]: File "/home/andrew/.local/lib/python3.7/site-packages/homeassistant/components/websocket_api/connection.py", line 84, in async_handle
Jun 28 21:37:22 ha hass[10503]: handler(self.hass, self, schema(msg))
Jun 28 21:37:22 ha hass[10503]: File "/home/andrew/.local/lib/python3.7/site-packages/voluptuous/schema_builder.py", line 267, in __call__
Jun 28 21:37:22 ha hass[10503]: return self._compiled([], data)
Jun 28 21:37:22 ha hass[10503]: File "/home/andrew/.local/lib/python3.7/site-packages/voluptuous/schema_builder.py", line 589, in validate_dict
Jun 28 21:37:22 ha hass[10503]: return base_validate(path, iteritems(data), out)
Jun 28 21:37:22 ha hass[10503]: File "/home/andrew/.local/lib/python3.7/site-packages/voluptuous/schema_builder.py", line 427, in validate_mapping
Jun 28 21:37:22 ha hass[10503]: raise er.MultipleInvalid(errors)
Jun 28 21:37:22 ha hass[10503]: voluptuous.error.MultipleInvalid: required key not provided @ data['device_id']
Also, thanks for fixing the Mija sensor!!
Also, just want to say a general thanks David! This is my current list of sensors and Im incredibly happy with how reliably this is working across the board.
4 Likes
Which card are you using for displaying attributes across multiple entities?
Looks like it’s this card:
2 Likes
Yes thats the one. Here is my config for it for reference. I really like it because new entities appear automatically.
- clickable: true
columns:
- name: Name
prop: name
- attr: rssi
name: RSSI
- attr: lqi
name: LQI
- name: State
prop: state
entities:
include: zha.*
title: Zigbee Entities
type: 'custom:flex-table-card'
2 Likes
Same here with my door / window sensors. Glad to see a comment saying that a fix is on the way.
Thank you for fixing this. I was at a loss at what to do about it when the binary sensor was removed from the device.
1 Like