Alexa can't find more new hue devices

Setup, Configuration and Use Beginners
1
  • Platform information:
    • Hardware: X64 / RAM 4Gb / 64 Gb eMMC
    • OS: Ubuntu 20.04
    • Java Runtime Environment: Zulu11.54+25-CA (build 11.0.14.1+1-LTS)
    • openHAB version: 3.4.2
      The Hue emulation works with my Alexa devices but starting from today it is impossible to detect new devices.
  • Nginix is working and configured according this file:
server {
  listen 80;
  location / {
    proxy_pass                              http://localhost:8080/;
    proxy_set_header Host                   $http_host;
    proxy_set_header X-Real-IP              $remote_addr;
    proxy_set_header X-Forwarded-For        $proxy_add_x_forwarded_for;
    proxy_set_header X-Forwarded-Proto      $scheme;
  }

  location /api {
    proxy_pass http://localhost:8080/api/;
  }
}
  • Here is the iptables configuration (iptables -S):
-P INPUT ACCEPT
-P FORWARD ACCEPT
-P OUTPUT ACCEPT
  • The self test is ok (http://MY_IP_ADDRESS/api/status).
  • Both http://MY_IP_ADDRESS:8080/description.xml and http://MY_IP_ADDRESS/description.xml show the description file.
  • Both curl http://MY_IP_ADDRESS:8080/api and curl http://MY_IP_ADDRESS:8080/api/ give:
    [{“error”:{“address”:“/”,“description”:“Not Authorized”,“type”:4}}]
  • When I start the pairing the log shows:
023-03-19 21:55:25.805 [INFO ] [ueemulation.internal.upnp.UpnpServer] - Hue Emulation UPNP server started on 192.168.1.5:8080
2023-03-19 21:57:13.619 [INFO ] [io.hueemulation.internal.ConfigStore] - Hue Emulation pairing enabled for 180s
2023-03-19 22:00:13.621 [INFO ] [io.hueemulation.internal.ConfigStore] - Hue Emulation disable pairing
  • The the item to be recognized is a dmmer tagged with Lighting label.

To start the detection, I set the hue emulation in this way:

  • Device Pairing: on
  • Pairing: Add Unknown User-Keys: on
  • Optional Discovery Web Port: 8080

With these settings, the other five items were correctly detected by Alexa, but now I’m unable to understand where the problem is.
I will be grateful to anyone who can give me some suggestion to fix this issue.
Thank you

Alessandro

2

This issue should be fixed in OH 4.0.

3

Dear Mike,
you are right: the ID of the the new exposed item is 479.
Thanks a lot!

Alessandro

4

Dear Mike,
I’m sorry to bother you again, but it seems there are another limiti in the HUE ID. In detail, it seems that ID >= 900 are not longer discovered by Alexa. My latest detected ID is 889.
Do you know the way to assign manually the IDs? If I change the HUEEMU tag value don’t have any effect in the real ID attribution (see http://myIP:8080/api/testuser/lights).
My openHAB version is 4.2.2.
Thank you in advance

Alessandro

5

There are 2 other recent posts about Alexa no longer discovering new devices correctly and in those posts the IDs are less than 255.

I don’t think your issue is due to the id being greater than 899. It uses the HUEEMU metadata to generate the id, so it should change if you update the metadata for an item.

6

Dear Mike,
Thanks a lot for the very quick answer. I added the Switchable tag to an item with 123 as ID and it was detected by Alexa while the ID >= 900 remains not recognized.

Alessandro