search

sidoh / esp8266_milight_hub

Replacement for a Milight/LimitlessLED hub hosted on an ESP8266
MIT License
947 stars 220 forks source link

Improve behavior of websocket connection in UI #189

Open sidoh opened 6 years ago

sidoh commented 6 years ago

This should involve two things:

ccutrer commented 3 years ago

oh my gosh, yes please! I have all my IoT devices on a separate VLAN too. it's not even routable from my main VLAN - my HA Hub is dual-homed. And headless. So to try out the web UI and verify connectivity, I was ssh'ing in and port forwarding. I was so confused if my antenna wasn't working, or what else it could be, because the sniffer wasn't seeing anything, even for sending packets. An "unable to connect to port 81" would have instantly clued me in as to what was going on.

Related, why are you using a separate port for the web socket connection? If you ran over the same port, this wouldn't be a problem. WebSocket was designed to do this, using the UPGRADE method (which it looks like you're frontend is doing anyway. I'm guessing it's just not as easy with the Arduino sdk to hook up the web sockets server to the regular web server?)