Hi I’m looking at doing something similar but for exposure to Nodered instead of Alexa.
The above works fine, it gives me a lightbulb in the GUI and the toggle switch and when switching on and off it changes colour in the GUI and NodeRed gets the values. So on/off works perfect.
What I was actually hoping to achieve was getting a dummy light in the GUI that I can also dim. So it’s not just on/off but also a slider to set value between 0-255 or 0-100.
Can anyone help in how I turn the below which gives a light bulb passing on on/off into a light that passes on on/off and %
I expected the set_level line to take care of that but for some reason it doesn’t.
Ok @lonebaggie , I already had the virtual light template as I mentioned in the other thread. But I had limited the emulated_hue to just scripts like this:
I saw only 2 of my scripts which worked fine from Alexa. It did not find the Alexa Virtual light.
I then tried using the emulated_hue as above with just the one entity listed and Alexa found every HA device I had plus scripts and automations - 43 new devices! All of them were emulated hue lights and contained duplicates of devices I had already plus the Alexa Virtual Light. So I had to delete them all from Alexa App and change my config to:
Trouble with HUE Emulated Lights in Hassio 98.5 anyone?
My Emulated hue was working great as mentioned above until I had to rebuild my system. I used the latest version at the time 2.12 (Hassio 98.5). Funny thing is that
my Alexa app now says “device doesn’t support requested data”
I can see the brightness value change in HA using the “States” page. But,…
when Alexa sets it to 1% brightness, HA States show it to be 4
Alexa shows a status of “device malfunction”
My Configuration.yaml looks like this (used to work):
I’m thinking about doing the opposite of what the OP did. I have a ton of input_booleans in HA that I use to trigger infrared transmissions in Node-RED using node-red-contrib-broadlink-control.
Does anyone know a way to encode these input_booleans in groups of 16 inside words (or 8/byte) and expose those words/bytes to Node-RED for later decoding?
So as said in the other post, I have 2 Tuya door sensor that they are not accessed in Smart Life app from HA, and I’m unable to find their IP, as they connect only for 1 second when door opens and closes, so manual IP configuration for them it’s imposible. The workaround that I found is, as Alexa recognize it, is to have a smartplug to be turned on when the door is open. The issue of this system is that I have to have a smart plug (well, two as they are two sensors) only used of this.
The idea, to solve this issue, is to have a virtual small plug/light/other device that Alexa con turn on and so HA will recognize it. This is usefull for a Home Made alarm system.
So following yout steps, I created a light, but of course I’m doing something bad, because the virtua light is not turning on and off and neither Alexa finds it. The current configuration is the one that I added in the previous post.
I have several Alexa, a Nest Mini and a Hue Bridge with some lights.
OK . small steps .First you have to get Emulated hue , or Nabu Casa working. see
You must able to get a device from HA to be recognised by Alexa , otherwise you have nothing to trigger.
Once you have a device from HA in Alexa . You can create a routine in Alexa that when the motion detector is activated you get alexa to trigger that HA device (switch, bulb , script , etc). That’s the idea for the virtual bulb its just a trigger for HA to react too.
Thanks for this links. I managed to create following the instructions the virtual light, but I have 2 problems now with it.
Problem 1: It duplicated all the lights, don’t know if you know a way to undo this and only to have the new lights.
Problem 2: HA and Alexa are unable to turn on and off the light created that I named “Alexa Luz Sim Entrada”. Here I think the issue is #Luz Falsa# that script “script.theater_lights_on” doesn’t exist in my HA, but when creating it, I don’t know what to do with or activate.
If you can help, (another time) I really apreciate it a lot.
Thanks again for the reply. So I’ll remove that and manually delete it.
The script " script.theater_lights_on" I have not created anything, only added that commanad. You think that a script inside HA with the same name has to be created?
If not, I’ll raise a thread with it. Thanks again (a 1000) for your help!
If I removed the "expose_by_default: true" it will cause that all the devices are detected. So I keep it. Manually I can remove the other devices, but they do not disturb right now, also if they are duplicated. The expose to false maybe I can do it once I want to add more lights or things to HUE, or if removing the rest and doing a future manual check.
To solve the issue with the light on/off I removed the script part and is working, so I left it as:
Just had another issue after one of the last updates, and the turn_on and turn_off gives an error “Inccorct type. Expected “object””. But I’m unable how to solve it.
light:
- platform: template
lights:
theater_lights:
friendly_name: "Alexa Sensor Sim Entrada"
turn_on: *Here is the error code*
turn_off: *Here is the error code*