Re: [mh] Alexa bridge suddenly stopped working
"Ron Fleming" <[email protected]>
| Newsgroups | gmane.comp.misc.misterhouse.user |
|---|---|
| Message-ID | <[email protected]> |
Dan, I had the same issue. I think Amazon may have pushed changed out to the Echo devices. It would appear that they require the bridge to be on port 80. I had mh on 80 and the bridge on 8080. I started seeing unusually request in the mh http server log that I think were meant for the bridge. The quick fix for me was to put mh on 8080 and the bridge on 80. Hopefully Amazon will correct this and I can go back to my default configuration. Hope this helps. Ron From: [email protected] <[email protected]> Sent: Monday, September 16, 2019 7:58 AM To: [email protected] Subject: [mh] Alexa bridge suddenly stopped working Been using the Alexa bridge to MH for well over a year without issues. It was the last piece I needed to complete my HA integration. Tuesday of last week, 9/10, it suddenly stopped working. A request is answered with "Devicename is not responding, please check its network connection..." I tried debugging, but so far have not found a reason. It seems like Echo/Alexa does not even attempt to connect the the bridge. I did add a bogus device and asked Echo to discover devices, I do see traffic to MH at that point, but Echo comes back with"No new devices". Alexa app on my Android phone shows "Server is unresponsive". Has anyone else experienced this? Thanks Dan ________________________________________________________ To unsubscribe from this list, go to: https://lists.sourceforge.net/lists/listinfo/misterhouse-users