Using Alexa and Hue in a Sense Network

Scholar

Using Alexa and Hue in a Sense Network

Hi, 

I'm using an Echo Plus and a Hue Bridge inside a Sense Network (Echo connected via WiFi, Bridge directly plugged into the LAN socket of my Sense router). As soon as I activate Device Protection on the Sense, Alexa aka the Echo Plus is no longer able to reach the Hue Bridge. If I switch Device Protection off, everything is working as usual.

Any ideas on how to fix this?

Thanks in advance! 

3 REPLIES 3
FormerMember
Not applicable

Re: Using Alexa and Hue in a Sense Network

I woukd also like to report an issue with my Hue bridge v1.

If it is connected to Sense via lan, it doesn't connect to internet as in updates don't work and the hue page just show [] in browser.

Still I can control the lights without issue.

 

Then if plug Hue via lan to my zte mf286 4g modem, it works normally and connects to the Internet.

 

I have tried turning off all protections from Sense but no help.

Scholar

Re: Using Alexa and Hue in a Sense Network

After investigating the issues a bit further I can add some additional comments:

-the Hue bridge does also not respond from commands send via the Android Hue App from outside the network (remote connection). Thus Alexa/the Echo is not the issue, but the connection to the bridge from the outside.

-port forwarding of ports 80 and 3000 as found in some solutions on other router platforms doesn't change anything, the ports are however not visible from the outside, which seems wierd

-taking a look at the log file obtained from sense.router/diag.log, the port seems to be going up and down quite a lot. Here's a short snapshot:

[  720.900000] RTL: Link Status Changed - Port2 Link DOWN
[  722.900000] RTL: Link Status Changed - Port2 Link UP
[  730.900000] RTL: Link Status Changed - Port2 Link DOWN
[  733.900000] RTL: Link Status Changed - Port2 Link UP
[ 1059.900000] RTL: Link Status Changed - Port2 Link DOWN
[ 2318.900000] RTL: Link Status Changed - Port2 Link UP
[ 4235.900000] RTL: Link Status Changed - Port2 Link DOWN
[ 4250.900000] RTL: Link Status Changed - Port2 Link UP
[ 4756.900000] RTL: Link Status Changed - Port2 Link DOWN
[73326.900000] RTL: Link Status Changed - Port2 Link UP
[73330.900000] RTL: Link Status Changed - Port2 Link DOWN
[73845.900000] RTL: Link Status Changed - Port2 Link UP
[73848.900000] RTL: Link Status Changed - Port2 Link DOWN
[73849.900000] RTL: Link Status Changed - Port2 Link UP
[73857.900000] RTL: Link Status Changed - Port2 Link DOWN
[73860.900000] RTL: Link Status Changed - Port2 Link UP
[73898.900000] RTL: Link Status Changed - Port2 Link DOWN

-After switching the device protection on, it takes roughly 15-30 minutes until the bridge "vanishes". During that time frame, full communication and functionality is available.

-Switching the Tracking protection off and leaving everything else on, doesn't change anything. My guess would be that the firewall is somehow blocking the connection. 

Scholar

Re: Using Alexa and Hue in a Sense Network

Last update for today: switching browsing protection on and off is sufficient to allow or block access to the bridge both from the outside and from the echo (which thanks to the hue skill is virtually the same).