NGINX problem die to hue emulation

Setup, Configuration and Use Beginners
,
7

Seems as I’ve been able to fix the fragile system.

  1. use in section 80 no 301 forward, but only the sections from hue emulation manual.
    → 
server {
    listen 80;

location /api {
      proxy_pass http://192.168.0.10:8080/api/;
    }

location / {
    proxy_pass                              http://192.168.0.10: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;
  }
}
  1. in 443 section all the stuff can be as desired (I think)
  2. set in hue emulation settings page port to 80 (IP I kept empty, and hue v1 emulation I also left deactivated)
  3. remove from alexa-homepage all smart home devices and search again
  4. call page http://192.168.0.10:8080/api/status/link (or however the IP of the Raspi is) to activate device pairing
  5. all devices were found on my side.

By the way: all entries in http://192.168.0.10/api/status were “no” but pairing still succeeded fine, and
Hue Pages with :80 are still forwarded to https://localhost by chrome (and :8443 by opera) but anyhow all seems to work is fine.

1 Like