Alexa does not find Hue Emulation Items (despite having OpenHab running on Port 80)

I just recongized that I do not discover any devices with the web (alexa.amazon.com), but after trying:
“Alexa, discover devices” all devices have been disovered.

Shouldn’t a rollershutter be another type?
I don’t see Information about how to expose rollershutters checking openHAB Hue Emulation - System Integrations | openHAB

Ehm. You know Philips Hue do you? They have no ZigBee based rollershutters so their protocol also doesn’t support it so Alexa doesn’t support it, via The local Hue protocol at least.

I emulate the rollershutters as dimmable lights and that’s what they show up as. You can then move the rollershutters all the way down by saying “set xyz to 99%”. When using 0% or 100% it’s going to be translated to OFF/ON somewhere along the way which causes my Homematics to not react at all. While this can probably be fixed with a rule I never bothered to. You should also be able to use Alexa routines to make “her” act on more natural sounding commands, like “move xyz up/down”.

Thanks.
I thought, that the 2.5 binding supports „real“ Rolleshutter items.
I will try it your way instead.

I tried another round of getting Hue emulation to work (like months before).
I started with the official doc and set the iptables according to the docs (port 80).
After enabling the device pairing, all my items have been discovered.

When I open the descriptions.xml, I get:
grafik

…/api/status returns:

Reachability test

|URL|Responds?|Ours?|
| --- | --- | --- |
|http://192.168.68.28:8080/description.xml|no|no|
|http://192.168.68.28/description.xml|no|no|

When starting discovery:

2020-04-20 19:53:45.950 [INFO ] [io.hueemulation.internal.ConfigStore] - Using discovery ip 192.168.68.28
2020-04-20 19:53:45.955 [INFO ] [io.hueemulation.internal.ConfigStore] - Hue Emulation pairing enabled for 60s
2020-04-20 19:53:46.296 [DEBUG] [ueemulation.internal.upnp.UpnpServer] - Self test fail on http://192.168.68.28/description.xml: java.net.ConnectException: Connection refused (Conne$
2020-04-20 19:53:46.330 [DEBUG] [l.upnp.HueEmulationConfigWithRuntime] - Cannot restart thread

But I can discover all Switch items.
Unfortunately they do not respond to Alexa.
AND:
http://192.168.68.28:8080/api/testuser/lights
does not return any lights.

It doesn’t seem the Hue Emulation binding is receiving your http requests. I suspect that may be because of your configuration. I use the following in /etc/rc.local (my OpenHAB server is running CentoOS 7):

/sbin/iptables -t nat -A PREROUTING -p tcp -m tcp --dport 80 -j REDIRECT --to-ports 8080

I haven’t changed any of the “standard” ports used by OpenHAB, it still listens on TCP port 8080 for incoming http requests. As I noted above, I configure the Hue Emulation binding through the PaperUI:


Note that I set the Optional Discovery Web Port to 80.

I had some problems with the Hue Emulation binding a few months back, but now that I’m running a 2.5.x-SNAPSHOT, I haven’t experienced any problems. I have not been successful using the Switchable tag for my switch-only (non-dimmer) items.

Thanks, Scott.

I did not change any of the standard ports either and use the same routing stuff from the docs:
sudo iptables -t nat -A PREROUTING -p tcp -m tcp --dport 80 -j REDIRECT --to-ports 8080
(sorry, I forgot to mention this).

Is that how it’s supposed to be? I would like to actually use just switched from hue emulation
(Coffee machine, Car Heater, Irrigation, …) :frowning:

I was running into a very similar situation where I could not get Alexa to see any of my tagged devices. I had put off the port redirection as I had read both positive and negative reviews of implementing it. I can tell you that once I enabled the port redirection, deleted my items from alexa.amazon.com then put the binding in discovery mode, and finally I clicked on the big blue discover button on the alexa website…after discovery was complete…like magic Alexa was back controlling the house.