Is the Homeseeer server down at the moment ?

[JMarias]

I checked all the servers and the logs and could not see anything obvious. I restarted the service on the connection server. Let me know if anyone is still seeing an issue.

As mentioned above, all is well now. Symptoms were...
Alexa Basic commands resulted in "I'm having trouble reaching "xxx". Device page on Amazon showed all devices os "Offline".

HSTouch returned "Unable to Connect"

What I did find interesting was that events could be triggered via the Alexa -> IFTTT->HomeSeer. Not sure how the communications differ between Alexa and HS VS IFTTT and HS. But am mentioning it in case it helps.

[rjh]

Very odd for sure as IFTTT and Alexa use the same method for communications. Did you happen to try to log into your system from myhs.homeseer.com? Did that work?

As mentioned above, all is well now. Symptoms were...
Alexa Basic commands resulted in "I'm having trouble reaching "xxx". Device page on Amazon showed all devices os "Offline".

HSTouch returned "Unable to Connect"

What I did find interesting was that events could be triggered via the Alexa -> IFTTT->HomeSeer. Not sure how the communications differ between Alexa and HS VS IFTTT and HS. But am mentioning it in case it helps.

[aptalca]

In my case, myhs.homeseer.com remote access was working, but alexa voice commands resulted in the error.

As of last night, everything is working again.

Thanks

[ewkearns]

Very odd for sure as IFTTT and Alexa use the same method for communications. Did you happen to try to log into your system from myhs.homeseer.com? Did that work?

If this helps any.... my Alexa stopped working... at least partially. Some events wouldn't work at all, for example, "Alexa, turn on the fan" returned an error something to the effect that the device wasn't responding." Alexa, Tell Homeseer to turn on the fan," also, failed.

However, another device failed with "Alexa, turn on the light," but worked with "Alexa, Tell Homeseer to turn on the light."

I "fixed" the issue with a network wide reboot. My suspicion is that this problem either was an Amazon update and/or related to an HS3 update.