Let me know which one!
I’m running the latest OH version on a RPi 3b+
to rename the tags? just rename it, it’s a textbox.
But it didn’t worked at first too, when the Tag was called “ColorLighting” but I’m gonna try it just to be sure!
As I said, it gets detected but its not controllable like a colorlight …
Thanks for helping.
Do you use a group item for colors?
I have no idea if that works or is even supported by openHAB itself.
Single items work for sure, I have some in my system. You seem to have discovered them with Alexa as well.
Try also some Hue apps out for changing the color.
That’s the thing I’ve also thought about but weirdly it doesn’t work either.
I’ve dispossed a yeelight and one LED strip to alexa but still, can turn it off and send a brightness in percentage but nothing more or less.
The official hue app (for your mobile) does not work to my understanding, because we haven’t reached the state of 100% emulating a hue bridge. But other apps work. Check out if they render the color item correctly and if they allow to change the color. If that works, you need to remove all of your Alexa items unfortunately and rediscover again.
I have the same problem. My color lights are emulated as dimmable lights. Tried an android app as well.
I have both tried adjusting the tagging and completely leaving the tag filters empty. However, I can’t get the lights to show up anything different than as a dimmable light.
download the “amazon echo control” - addon and you will get a channel which parses the last voice command, therefore the last sentence you’ve said to your echo device as a string.
You can compare those within the rules and let some code run:
See my code: (but its jython on the jsr223 api)
if event.itemState.toString().lower() == "pc an" or event.itemState.toString().lower() == "p. c. an":
events.sendCommand(event.itemName.replace("lastVoiceCMD", "TTS"),"Wird gemacht chef")
logVC.info("Jython: PC angeschalten")
events.sendCommand("wol_rechner","ON")
It is not very helpful. Says Openhab should run on port 80 or the emulation will not be discovered. My OH runs on 8080 (default) and is discovered, it just doesn’t see the lights as color lights. I can control and dim the lights, but it won’t control color.
Sorry, but I thought that part of troubleshooting was still about checking whether the right port was set. I get the following representation for a color light from the emulation:
That’s super strange as I’m using the same app for controlling my colour bulbs and the debug output looks good. If you remove the “?debug=true” part, you will see what Alexa sees. And the emulated light should be an extended color light, as stated in the debug out.
I know that Echos might have problems, depending on the firmware. Some devices just don’t have firmware support for colors.
It’s all a bit confusing but the way I understand it is the Hue Emulator does NOT have local Alexa color support. I think the reasoning was that Alexa isn’t suppose to be able to control color bulbs locally, even though it can is a few regions. So you need to use a cloud based app/proxy, so the Alexa can sent the color command on-line to, which would then send a command to the hue emulator. I have all my items exposed to my smartthings hub, so I just added the smartthings app to alexa and now I can control the color.
I don’t think that is how it works, because the android apps don’t know there are echoes in the household, nor do they know how these can be addressed through the cloud. i.e. what my account name is.
I also find it very peculiar, that in spite of using the same app (which is not market specific like alexa), there still is a difference in functionality. Don’t have any explanation for that right now. Even checked Karaf for the bundles, but it only lists one hue emulation, which carries 23rd of january as the version date. The output of the emulation seems ok, but it seems to be something in the interpretation of that output that causes things to not work. As input-wise, it does work with the app that doesn’t care about capabilities. Maybe there is something cached in the echoes? I have deleted and discovered multiple times though, always with the same result.
It works through myopenhab, but I would prefer to use Hue emulation, since that takes one server out of the mix to operate my lights. I do appreciate the efforts in providing myopenhab very much, but compared to the also needed alexa servers, the stability is always going to be a lot less.
The workaround with the echo binding is a neat trick that will probably allow to do almost anything through alexa, but I don’t like that binding because it uses scraping in stead of an API. As I am looking for maximum reliability, I am not too convinced with that.
If I don’t get this to work, I might use some extra items with custom tagging to make sure I can use the emulation for on/off , and use myopenhab for the rest.
Keep in mind that some devices require XY Color Support and that did not make it in 2.4.0 Release unfortunately, it should be in 2.5.0M1 though (I haven’t verified this though, I did not even check the release notes if it’s mentioned there)