Re: [mh] Alexa bridge suddenly stopped working

I have not run into the issue your guys are experiencing, maybe my echos
have not been updated to that version yet. But if the port is the issue
(Google Home has always been limited to port 80) then all you have to do it
change the port that the MH web server is running on because the Alexa
Bridge module advertises/uses the MH built in web server.

Once you change the MisterHouse web server port to 80, all you should need
in your mh.private.ini is:
alexa_enable=1
alexaEnableChunked=1

To change the MH web server port use (the Alexa Bridge code uses this
config for the SSDP messages) :
http_port=80


Ron,

I wrote a Misterhouse module that emulates a Hue bridge like the external
java app you are running but its integrated into MH. You can see the
documentation in the local MH docs @
http://HM-IP:port/docs/lib/AlexaBridge.html#AlexaBridge


_Wayne


On Fri, Sep 20, 2019 at 1:39 PM Ron Fleming <[email protected]> wrote:

> Paul,
>
>
>
> Perhaps my setup is a bit different.   I am using bwssystem’s  ha-bridge
> Java program to provide the bridge emulation :
>
>
>
> https://github.com/armzilla/amazon-echo-ha-bridge
>
>
>
> It has an habridge.config file that stores the bridge configuration
> including the Port.  It can also be changed from the habridge web interface.
>
>
>
> You may be using a different bridge emulator, but I’ll bet the issue is
> the same.   I am running an old version of mh and have my echo integration
> running outside of misterhouse.
>
> I hope that helps!
>
>
>
> Ron
>
>
>
> *From:* Paul Onley <[email protected]>
> *Sent:* Friday, September 20, 2019 11:44 AM
> *To:* [email protected]
> *Subject:* Re: [mh] Alexa bridge suddenly stopped working
>
>
>
> Ron,
>
> What did you have to do to configure for port 80? I have included
>
>
>
> mh.private.ini:alexaHttpPort = 80
>
>
>
> in my mh.private.ini but still see
>
>
>
> 09/20/19 10:42:34 AM [Alexa] Debug: Configured for port 8080
>
>
>
> during startup and am still unable to discover any devices.
>
>
>
> Thanks
>
> Paul
>
>
>
>
>
> On 9/20/19 8:35 AM, Ron Fleming wrote:
>
> 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]> <[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
>
>
>
>
> ________________________________________________________
> To unsubscribe from this list, go to:
> https://lists.sourceforge.net/lists/listinfo/misterhouse-users
>
>

________________________________________________________
To unsubscribe from this list, go to: https://lists.sourceforge.net/lists/listinfo/misterhouse-users