Anyone else having issues with Hue zones and rooms? After upgrading to 2021.12, I have re-enabled the zone entities. But I experience the following behaviour:
When turning on the lights that are grouped as a room or zone in the Hue app (i.e. showing as one entity in HA), sometimes there is a small delay between them turning on: one turns on slightly later than the other, instead of simultaniously.
Sometimes, not all lights in the zone are turned on, only some of them
Sometimes, the brightness of the light is not properly set
I did not experience these issues before upgrading to 2021.12. Issue seems to be still present in 2021.12.1.
123
(Taras)
December 13, 2021, 7:30pm
313
Signify (Philips) eliminated effects from its new API. That’s why they no longer exist in the new Philips Hue integration (which employs the new API).
opened 12:36PM - 12 Dec 21 UTC
integration: hue
### The problem
Since the new release Hue lights won't flash with the `flash` c… ommand. They will just turn on, and stay on.
The previous behaviour when using `flash` is that the light would flash a given number of times – depending on whether `short` or `long` was passed as a parameter – and go back to its previous state (either on or off based on the state of the light when the `flash` command was issued).
### What version of Home Assistant Core has the issue?
2021.12
### What was the last working version of Home Assistant Core?
2021.11.5
### What type of installation are you running?
Home Assistant OS
### Integration causing the issue
Philips Hue
### Link to integration documentation on our website
_No response_
### Example YAML snippet
_No response_
### Anything in the logs that might be useful for us?
_No response_
### Additional information
_No response_
FWIW, there’s an effect that makes a light “breathe” (what you see when the Hue app identifies a light for configuration) and the developer intends to use that for a long flash (there’s nothing natively available to support a short flash).
1 Like
marcelod
(garliclord)
December 13, 2021, 7:41pm
314
I guess if he implements it as an effect you could apply it and then switch it back to no effect quickly so it flashes fewer times. Better than trying to script the flash effect and return original state!
arganto
December 13, 2021, 7:55pm
315
Please read the release notes. Or this Thread. Or both.
2 Likes
cg089
(Cg089)
December 13, 2021, 7:56pm
316
I have different symptoms (still no values after 20 reboots) and also opened an issue tracker meanwhile:
opened 06:17PM - 13 Dec 21 UTC
integration: vallox
### The problem
After updating to 2021.12.x (tried both 2021.12.0 and 2021.12… .1) the vallox integration isn't working anymore.
### What version of Home Assistant Core has the issue?
core-2021.12.1
### What was the last working version of Home Assistant Core?
core-2021.11
### What type of installation are you running?
Home Assistant OS
### Integration causing the issue
Vallox
### Link to integration documentation on our website
https://www.home-assistant.io/integrations/vallox/
### Example YAML snippet
```yaml
vallox:
host: 192.168.12.15
```
### Anything in the logs that might be useful for us?
```txt
Logger: homeassistant.components.fan
Source: components/vallox/fan.py:102
Integration: Ventilator (documentation, issues)
First occurred: 12:22:10 (1 occurrences)
Last logged: 12:22:10
Error while setting up vallox platform for fan
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 249, in _async_setup_platform
await asyncio.shield(task)
File "/usr/src/homeassistant/homeassistant/components/vallox/fan.py", line 77, in async_setup_platform
device = ValloxFan(
File "/usr/src/homeassistant/homeassistant/components/vallox/fan.py", line 102, in __init__
self._attr_unique_id = str(self.coordinator.data.get_uuid())
AttributeError: 'NoneType' object has no attribute 'get_uuid'
Logger: homeassistant.components.sensor
Source: components/vallox/sensor.py:55
Integration: Sensor (documentation, issues)
First occurred: 12:22:09 (1 occurrences)
Last logged: 12:22:09
Error while setting up vallox platform for sensor
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 249, in _async_setup_platform
await asyncio.shield(task)
File "/usr/src/homeassistant/homeassistant/components/vallox/sensor.py", line 238, in async_setup_platform
[
File "/usr/src/homeassistant/homeassistant/components/vallox/sensor.py", line 239, in <listcomp>
description.sensor_type(name, coordinator, description)
File "/usr/src/homeassistant/homeassistant/components/vallox/sensor.py", line 55, in __init__
uuid = self.coordinator.data.get_uuid()
AttributeError: 'NoneType' object has no attribute 'get_uuid'
```
### Additional information
_No response_
claudegel
(Claude Gelinas)
December 13, 2021, 7:59pm
317
Can someone tell me where to find release note concerning the following:
device_state_attributes for custom components
since this last update I get the following in my log:
Entity light.neviweb_light_bureau (<class 'custom_components.neviweb.light.NeviwebLight'>) implements device_state_attributes. Please report it to the custom component author.
As I’m the author can someone tell me where I can get information about the change I need to do ?
Thank you
skynet01
(Alex)
December 13, 2021, 8:03pm
318
I have the same issue when you toggle a group switch instead of toggling the group the info box shows up with group detail
Doh! Mist it the first time. Thanks for taking the time to redirect.
1 Like
uvjim
December 13, 2021, 8:26pm
320
petro
(Petro)
December 13, 2021, 8:31pm
321
can you show me what you mean “in the integration”?
nmsousa76
(nmsousa76)
December 13, 2021, 8:32pm
322
input booleans no longer work as switches in Alexa. They are now showing up as other.
claudegel
(Claude Gelinas)
December 13, 2021, 8:41pm
323
@uvjim ,thank you very much. Now I can update my custom components
123dev
(123dev)
December 13, 2021, 8:43pm
324
@uvjim
Thank you, that did it.
petro
(Petro)
December 13, 2021, 8:47pm
326
That’s a result of the failure. Did you write up an issue on github with the error from your logs?
Migaddo
December 13, 2021, 8:54pm
327
Yes have the same issue, i used the flash optin in an automation, and not working anymore.
Migaddo
December 13, 2021, 9:02pm
329
Thats great news Petro, thank you looking forward for the implementation😀
tom_l
December 13, 2021, 9:03pm
330
It’s a straight name swap see this PR:
bremor:main
← tomlut:patch-1
opened 01:01AM - 05 Dec 21 UTC
device_state_attributes -> extra_state_attributes name change
1 Like
DBM
(Han)
December 13, 2021, 9:41pm
331
Thanks for the update; some nice features to test. But I have a problem as well
I use 2 Hue touch buttons that are build into wall switches. These are the last ones to use my Hue bridge as everything else is migrated to ZHA.
The Hue touch buttons are part of an automation that tests if a specific event comes in via the Hue integration.
alias: Hue Touch Keuken Scenes
description: Process scene commands coming from Hue Touch
id: f00eb98b-a165-4d80-9182-30e2fcdbf26f
trigger:
- platform: event
event_type: hue_event
event_data:
unique_id: 00:00:00:00:00:45:0e:ff-f2
condition: []
action:
- choose:
# switch left top
- conditions:
- condition: template
value_template: "{{trigger.event.data.event == 16}}"
sequence:
- service: scene.turn_on
data_template:
entity_id: scene.woonkamer_cosy
- service: logbook.log
data:
name: Hue Touch
message: Button linksboven
after updating to Home Assistant 2021.12.1 events do not come in any more. Have restarted the system, removed and readded the integration. Not sure what else I can do?
Edit: added correct HA version