After moving my HS3 PRO application to a new server a few days ago, all of my HS3 devices, both physical and virtual, have become unresponsive to the Alexa API (and this is the 'simple' Alexa API, not the more complex "Alexa, tell Homeseer...." version).
Does the Alexa HomeSeer skill use myHS in some fashion? One thing I have noticed is that trying to reach myhs.homeseer.com/Login from any system in my house is redirecting me to the wrong IP address (it's one that's within my home network, and it's one that my 'old' HS3 server was assigned as I copied stuff from the old server to a new one. The 'new' one has the IP address of the 'old' one, the 'old' HS3 server is powered off, and everything inside the house is happy.
When I try to connect to myhs.homeseer.com from OUTSIDE of my home network, I get a 'too many redirects' error.
Any suggestions as to what might be going on?
-M.
Does the Alexa HomeSeer skill use myHS in some fashion? One thing I have noticed is that trying to reach myhs.homeseer.com/Login from any system in my house is redirecting me to the wrong IP address (it's one that's within my home network, and it's one that my 'old' HS3 server was assigned as I copied stuff from the old server to a new one. The 'new' one has the IP address of the 'old' one, the 'old' HS3 server is powered off, and everything inside the house is happy.
When I try to connect to myhs.homeseer.com from OUTSIDE of my home network, I get a 'too many redirects' error.
Any suggestions as to what might be going on?
-M.
Comment