jay (support) wrote:Ah, I see. In Alexa, any device that is dimmable is considered a light, others that only support on/off are considered switches (at least in terms of their UI apparently). In Indigo, we have a similar construct: DimmerDevice and RelayDevice respectively. We publish those devices to Alexa based on their definitions. DimmerDevices support both PowerController and BrightnessController Alexa interfaces. RelayDevices only support the PowerController interface since you can't send dim commands to them.
Apparently, Alexa assumes that only the former is a light. I'm not sure that changing the subtype of a RelayDevice to be "LIGHT" will solve the issue or if Alexa is looking specifically at whether the device has the BrightnessController interface. If it's the former, and I'll try testing that, then we can most likely make that work. If, however, it's the latter, then I'm not sure we can do anything about it (since a RelayDevice in Indigo will throw an error if you try to set the brightness on it).
Hey Jay,
Firstly, a huge thank you for getting the native Alexa integration implemented. I've ditched the Alexa Hue Bridge and taken the plunge and all appears to work OK after making virtual devices to accommodate a few actions I needed.
However, I had bother with Alexa Groups and lights too. In the old Hue based plugin, everything was a light whereas now, my dimmable lights (Aeon) are 'dimmers' whereas non-dimmable light switches and lamps on a plug-in switch are not considered lights.
Let's say I'm in the bedroom and say 'Alexa, turn the lights off', with the old plug in it just worked. Now, it replies 'A few things share the name lights, which one did you want'?.
I'm guessing it was because there are switches and plugins called '<room name> lights'.
Although the solution above worked for me, it would be good if one could override the device type from switch or plugin and change it to bulb in Indigo so Alexa picked it up as a light. I'm guessing this would then work OK?
Cheers,
Chris
--