Place the custom_components folder in your configuration directory (or add its contents to an existing custom_components folder). You need to set up your Hue bridge first. TODO Alternatively install via HACS.
you need to install a new integration in HACS
1 Like
My remote stopped working with hue advanced sensors 3.0.
It took me some time to figure out that the component got split into two components (sensor and remote).
What’s the reason for splitting the component? Did not find some information about that on github.
Also I didn’t find release notes about 3.0 and this breaking change.
@robmarkcole would it be possible to add breaking changes like that to the readme in future? Or are they already somewhere and I did not find them? It would be great if breaking changes would show up in hacs too (if possible).
Yes remotes are in their own repo now, which can be installed via HACS. Couple of technical reasons, but mostly this is to help out the maintainers. As this is a custom integration the release process is not as managed as HA. I am dealing with a newborn baby and fitting in coding when windows of opportunity pop up. Frankly it puts a lot of pressure on open source maintainers to expect a professional service for something we are doing in our spare time
Thanks for your reply, I totally understand. I think just adding something like “Breaking change: component splitted” would already help to avoid too many questions form users.
I just noticed that my remote got unavailable after a restart of ha core. It already worked yesterday and I don’t see an error in the logs. Any suggestions how I could fix this. The component worked fine for months when it was in hue advanced sensors.
Well the release notes do discuss this:
I think they could be clearer with hindsight, but when you’ve only had a couple of hours sleep a day for several weeks this is what you get
1 Like
Update on the Hue sensors repo (doesn’t affect Hue remotes repo):
PLEASE BE ADVISED: you are strongly encouraged to use the official Hue sensor integration, and cease using this custom integration.
Longer explanation: sensor support in the official hue integration is more feature-complete than this custom integration, and if you’re already using Hue-remotes-HASS, then the refresh rate for sensors in the official integration will be automatically the fastest possible. Since we want to migrate users to the official integration, please do not open feature request issues or create PR adding new functionality to this custom integration, as they will not be considered. This custom integration will remain available until the next breaking change with Home Assistant, at which point this repo will be archived.
After restarting ha core a few times the component works again. The thing is if I restart there is a big chance that it’s gets unavailable again. Also I noticed that it’s like a 100% chance to get the state unavailable, when I’m restartig home assistant (hassio). Is this a known issue? Have to say that I didn’t track the state of this entity before (with hue sensor advanced) so I can’t see if this was there earlier. The thing is I never had issues with the remote, so I guess it was fine. Now it seems like I have to remember to check the state of the entity after each restart and restart again if unavailable.
@robmarkcole, could you elaborate on this? The reason this custom component had been so appealing is that the official Hue integration’s refresh rate was painfully slow (which I understand is due to Hue’s API), at least up until the time I had installed my first Hue Motion Sensor. Is that refresh rate improved through the use of Hue-remotes-HASS?
TLDR use the remotes CC for fast motion sensors. The long explanation is too technical for this forum. Enjoy
Ok, that makes the remotes CC fairly valuable, thank you.
Hey guys, how does everyone do automations with theses?
I have a Hue Tap switch linked. But when trying to do automations in Node-Red using the “State_Changed” home asssitant node. it doesn’t detect the same button pressed twice.
What I mean is,
If I press. Button 1 then button 2. All works.
If I press Button 1, then again Button 1. It doesn’t send the second signal, since there wasn’t a “change”.
Anyone got a work around?
Thanks!
I don’t use Node-Red for automations but the if you hit the same button two times in a row the state isn’t changing so it stands to reason that “State_Changed” wouldn’t work. I’m guessing that you need to use an events node.
For regular HA automations using a to: in the trigger won’t work because the state isn’t changing, but if you just have platform: state and entity_id: in the trigger and then put to: as a condition it will work.
I tried figuring this out with the Home-Assistant automations (Which I’ve barely used) and am having a lot of trouble finding “platform” under Trigger Type. Could you perhaps give me a quick screenshot of how you created an automation with a hue button? 
I have the FOH switches, not the tap…but same idea.
- id: dinette_light_switch_control
alias: "Dinette Light Switch Control"
trigger:
- platform: state
entity_id: remote.dinette_switch
condition:
- condition: state
entity_id: remote.dinette_switch
state: 'left_upper_press'
action:
...
That worked! Thanks a lot man! Have a great weekend!
Hey guys,
is it OK that after installing Hue-remotes-HASS I can see the Entity of my Hue Dimmer Switch, but there is no Device? With Official Hue Integration, I have both Devices and Entities.
Btw, everything works as expected, I can use Dimmer Switch Entities in Home Assistant Automations using the State “1_click_up” or similar.
Thank you.
Hi,
Trying to add my hue remotes with the Hue-remotes-HASS integration v0.1.
Config:
hue:
bridges:
- host: 192.168.x.x
allow_unreachable: true
allow_hue_groups: true
remote:
- platform: hueremote
Gettings this error:
Log Details (ERROR)
Tue Mar 31 2020 15:02:33 GMT+0200 (Central European Summer Time)
Error while setting up platform hueremote
Traceback (most recent call last):
File “/srv/homeassistant/lib/python3.6/site-packages/homeassistant/helpers/entity_platform.py”, line 150, in _async_setup_platform
await asyncio.wait_for(asyncio.shield(task), SLOW_SETUP_MAX_WAIT)
File “/usr/lib/python3.6/asyncio/tasks.py”, line 358, in wait_for
return fut.result()
File “/home/homeassistant/.homeassistant/custom_components/hueremote/remote.py”, line 40, in async_setup_platform
config.get(CONF_SCAN_INTERVAL, DEFAULT_SCAN_INTERVAL),
File “/home/homeassistant/.homeassistant/custom_components/hueremote/data_manager.py”, line 159, in async_add_platform_entities
async for is_new, model, dev_id, _ in self._iter_data(platform_models):
File “/home/homeassistant/.homeassistant/custom_components/hueremote/data_manager.py”, line 56, in _iter_data
await bridge.sensor_manager.coordinator.async_request_refresh()
AttributeError: ‘HueBridge’ object has no attribute ‘sensor_manager’
HA info:
python_version 3.6.9
version 0.103.6
Any tips?
After upgrading HASS to 0.107 and “Hue sensor advanced” to V3.0, my Hue Smart Buttons are gone.
E.g. “remote.hue_smart_button_1” is “unavailable”, and I cannot find it under another name. What can I do to make them work again?
Had the same issue. See #1150
You will need to install a new component because sensors and remotes got split. See #1153