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).
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).
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!
Please read the release notes. Or this Thread. Or both.
I have different symptoms (still no values after 20 reboots) and also opened an issue tracker meanwhile:
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
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.
Relates back to 2021.4 I believe. 2021.4: For our advanced users ❤️ - Home Assistant
This pull specifically (according to the release notes): Replace Entity.device_state_attributes with Entity.extra_state_attributes by emontnemery · Pull Request #47304 · home-assistant/core · GitHub
can you show me what you mean “in the integration”?
input booleans no longer work as switches in Alexa. They are now showing up as other.
That’s a result of the failure. Did you write up an issue on github with the error from your logs?
Yes have the same issue, i used the flash optin in an automation, and not working anymore.
Thats great news Petro, thank you looking forward for the implementation😀
It’s a straight name swap see this PR:
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
We’ll it showed that I had to
change the unique_id to device_id
change “trigger.event.data.event == 16” to “trigger.event.data.subtype == 2”
So probably something changed to the unique_id (no longer unique) and the trigger events changed label and number.
Hue_event output:
Event 18 fired 23:00:
{
"event_type": "hue_event",
"data": {
"id": "hue_tap_switch_2_button",
"device_id": "25ee5fa89a0b3476e093c87eb6f12741",
"unique_id": "479d9056-f300-474e-b618-d7f15f82b81c",
"type": "initial_press",
"subtype": 2
},
"origin": "LOCAL",
"time_fired": "2021-12-13T22:00:28.562153+00:00",
"context": {
"id": "69919057de08fe1fa0eedad2a9c4bd5a",
"parent_id": null,
"user_id": null
}
}
The subtype numbers now are 1, 2, 3 and 4. They used the be the event numbers 16, 17, 34 and 18. Probably missed all of that in the breaking changes.