had this nifty little Hue scene selector working with the hue.hue_activate_scene
service.
Updating Hassio from 065.1 broke that in my settings (adding to several other Hue issues), first, 0.68.1 didn’t bring it back.
Is there any hope we get the hue.hue_activate_scene back, as basic functionality, using the regular scenes built into Hue ?
script:
set_hue_scene:
alias: Set Hue scene
sequence:
- service: hue.hue_activate_scene
data_template:
group_name: '{{ states.input_select.hue_groups.state }}'
scene_name: '{{ states.input_select.hue_scenes.state }}'
This is working fine for me, do you have any errors?
yes, nothing happening except for 1 hue-group… all others do nothing any more with the scenes that worked just fine before.
im not the only one: "hue.hue_activate_scene" not working consistently since 0.66 · Issue #13685 · home-assistant/core · GitHub
Have you changed the name of the group? The group and scene name must match exactly the ones on the hub.
no i have done nothing but update from 0.65.1 to 68.0 and 68.1…
resulting in many Hue issues, this being one of them
anon43302295:
No idea then, sorry.
which version Hassio do you run? Maybe I have to go back…
Not hassio. Homeassistant, 0.68.1 at the moment.
ok cool, im on Hassio, also .68.1
just for reference:
opened 05:53PM - 08 May 18 UTC
closed 11:01PM - 25 May 18 UTC
Can you please include the lights property in the group class? Understanding which lights are in a group will be required...
home-assistant:dev
← home-assistant:hue-bridge-availability
opened 07:29AM - 12 Mar 18 UTC
home-assistant:dev
← home-assistant:philips-hue-available
opened 07:36AM - 06 Mar 18 UTC
opened 07:56AM - 31 Mar 18 UTC
closed 11:11PM - 01 Apr 18 UTC
Home Assistant release with the issue:
0.66.0
Last working Home Assistant release (if known):
0.65.6
Operating environment (Hass.io/Docker/Windows/etc.):
HA running in official docker container for Raspberry...
opened 07:45AM - 28 Mar 18 UTC
closed 07:43PM - 29 Mar 18 UTC
Home Assistant release with the issue:
0.66beta (tried with beta1 and beta2)
Last working Home Assistant release (if known):
0.65.6
Operating environment (Hass.io/Docker/Windows/etc.):
Docker on Synology...
opened 09:44AM - 17 Apr 18 UTC
closed 02:51PM - 19 Jun 18 UTC
Home Assistant release with the issue:
0.67.0
but also reports from version 0.66
Last working Home Assistant release (if known):
0.65.6
Operating environment (Hass.io/Docker/Windows/etc.):
Linux virtualenv
Component/platform:
hue
Description of...
as said, hope its gets solved any time soon…
1 Like
I have changed my hue scenes so they are all unique & they work fine. For example previously I had…
group_name: 'Outside'
scene_name: 'Full'
group_name: "Living Room"
scene_name: 'Full'
Now…
group_name: 'Outside'
scene_name: "Outside Full"
group_name: "Living Room"
scene_name: "Living Room Full"
Also by doing this I realized that I can template the automation a step further to only use one input_select for all scenes…
- service: hue.hue_activate_scene
data_template:
group_name: >
{% if states.input_select.hue_select_scene_test.state|first == "L" %}
Living Room
{% elif states.input_select.hue_select_scene_test.state|first == "O" %}
Outside
{% endif %}
scene_name: >
{{ states.input_select.hue_select_scene_test.state }}`
2 Likes
jimbob1001:
changed my hue scenes
that is certainly valuable, but I was simply looking to implement the standard Hue scenes, that are still there. It is because of the new Hue implementation in Hassio (asyncio) this doesn’t work anymore, and it should be reinstalled soon, i hope.
Besides that, I will have a deeper look at what you suggest here, might indeed be very nice for the adjusted user scenes.
Thanks,
Marius
cryptyk
(Ryan)
February 5, 2019, 4:53am
12
Sorry to raise this from the dead, but I’ve noticed that hue_activate_scene works when group_name is a Hue Room or an HA light group. But it does not work if the group_name is a Hue LightGroup.