Hello!
So I had a virtual light for Alexa TTS functionality for years and at some point with an update it stopped working. There were instructions on how to do this in the custom alexa integration oce but I cant find it anymore. I read the documentation on templates and lights and all but I cant figure out what is wrong and if I need scripts for the turn_on and off and dim functions now.
So I had this now for years in my configuration.yaml, but it now gives me errors in code if I dont add anything behind turn_on etc.:
So I changed it to this, but now when I want to switch it off I get an error that the service call must contain at least an entity ID. And if I click on settings of the entity I get a message that light.alexa_virtual does not have a clear entity ID.
lights:
brasseur_bureau_led_remote:
friendly_name: "Brasseur Bureau Led Remote"
unique_id: "brasseur bureau led Remote"
turn_on:
- condition: state
entity_id: light.brasseur_bureau_led_remote
state: "off"
turn_off:
- condition: state
entity_id: light.brasseur_bureau_led_remote
state: "on"
Any chance you are having issues with your virtual light after latest update to 2025.4.0 ? I came home this morning to the wife saying some stuff wasn’t working, and I ultimately realized that brightness was no longer exposed to the Alexa app… for now I just restored backup and ran discovery on Alexa and all is back to normal.
I am going to try the change that was suggested to you up there later and update again, but I just worked all night, so hoping to wake up to a little insight if it’s just me, the Alexa discovery, or HA update. Thanks.
I will also check the pull-requests to see if something got changed that could have caused the exposure of brightness to change in update.