I have created lots of automation’s via the Alexa routines feature, which then switches input boolean components in HA to action the request.
This is getting cumbersome using one input boolean for each routine. I would like to create a virtual dimmer in HA then expose this entity to Alexa. This would give me a 100 different responses via the dimmer, using just one entity, is this possible?
Hi @lonebaggie
Would it be possible for you to detail how this integrates in the Alexa app ?
Currently, I use the alexa-local node wich is very unstable for me.
In the alexa app I use for creating routines (on adroid), I only see my hue lights and (sometimes) the lights I have created with alexa-local.
If I understand correctly, creating a light template should make the entity discoverable by Alexa ?
I use dummy bulb for triggering event in HA see the following
basically create a routine in the alexa app to change the dummy bulb brightness . Then use the brightness level in ha to trigger anything you want . One bulb 100 different triggers
the light template is just a light created in HA .
Dont use alexa-local-node ? node-red ? . I use alexa cloud and before that emulated hue in HA worked fine. Emulated hue will present the bulb to alexa without any problems
Confirm this is now in HA. You will need to confirm configuration and restart HA . You can turn it off and on in the UI wont do anything except change colour
Once you have the virtual bulb. Expose it with emulated hue
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?