Re: [mh] Alexa woes (again)
Wayne Gatlin <[email protected]> Wed, 7 Feb 2024 19:32:33 -0600
| Newsgroups | gmane.comp.misc.misterhouse.user |
|---|---|
| Message-ID | <CA+E=prxtF67h_GZifV9WjJ4DY3Gzmc+rxCYdJkTEXHWvLFf00A@mail.gmail.com> |
--===============5378446125260101522== Content-Type: multipart/alternative; boundary="000000000000c62ea60610d4c91d" --000000000000c62ea60610d4c91d Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable If you aren't seeing any debug messages then it's probably an issue with multicast on the machine or permissions with port 80 which need elevated access. Make sure you see it listening on port 80 with net stat. If ssdp was working you would be seeing messages from all kinds of things on your network on the same subnet in addition to Alexa -Wayne On Wed, Dec 13, 2023, 12:35=E2=80=AFPM Paul Onley via misterhouse-users < [email protected]> wrote: > I have had similar experiences with alexa and what has worked for me is t= o > shut down all alexa devices. Use the phone app to delete all home > automation devices. Do a factory reset on one alexa device and use it to > "Discover new devices". It's a pain but has worked for me in the past. Be > aware that if this fixes it for you that you may have to repeat the proce= ss > EACH TIME you want to add a new device so I recommend making sure you hav= e > all your devices defined the way you want them in the .mht file before > doing this. > > my current settings are the same as your but I have debug remarked and do > not have the alexaHttpPortCount =3D 0 setting. > > > > On 12/12/23 15:14, Giles Godart-Brown wrote: > > All > I've just received my new Raspberry Pi5 and thought I would do a straight > install from scratch of the latest Master release. > All is well, apart from Alexa which wont discover any of my MH devices. > I've tried removing them all in the app and rebooting alexas but still no > good. > The relevant part of my ini file is > <snip> > alexa_enable =3D 1 > alexaEnableChunked =3D 1 > alexaHttpIp =3D 192.168.100.57 > alexaHttpPortCount =3D 0 > alexaHttpPort =3D 80 > debug=3Dalexa:5 > alexaForceLongFormat=3D1 > </snip> > I haven't changed my items.mht file from the version that worked on my ol= d > Pi4 > Oddly I don't seem to be getting any alexa log messages during discovery, > just a couple during initialise viz; > <snip> > 12/12/2023 20:59:02 Alexa open_port: p=3D50000 pn=3DalexaSsdpNotification > s=3DSocket_Item=3DHASH(0x5555705140a8) > > 12/12/2023 20:59:02 Alexa open_port: p=3D pn=3DalexaSsdpListen > s=3DSocket_Item=3DHASH(0x5555705143d8) > </snip> > Anyone got any ideas? > THX > Giles > > > ________________________________________________________ > 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 > > --000000000000c62ea60610d4c91d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"auto"><div>If you aren't seeing any debug messages then it&= #39;s probably an issue with multicast on the machine or permissions with p= ort 80 which need elevated access. Make sure you see it listening on port 8= 0 with net stat.</div><div dir=3D"auto"><br></div><div dir=3D"auto">If ssdp= was working you would be seeing messages from all kinds of things on your = network on the same subnet in addition to Alexa=C2=A0</div><div dir=3D"auto= "><br></div><div dir=3D"auto">-Wayne<br><br><div class=3D"gmail_quote" dir= =3D"auto"><div dir=3D"ltr" class=3D"gmail_attr">On Wed, Dec 13, 2023, 12:35= =E2=80=AFPM Paul Onley via misterhouse-users <<a href=3D"mailto:misterho= [email protected]">[email protected]</a= >> wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0= 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><u></u> =20 =20 =20 <div> <div>I have had similar experiences with alexa and what has worked for me is to shut down all alexa devices. Use the phone app to delete all home automation devices. Do a factory reset on one alexa device and use it to "Discover n= ew devices". It's a pain but has worked for me in the past. Be = aware that if this fixes it for you that you may have to repeat the process EACH TIME you want to add a new device so I recommend making sure you have all your devices defined the way you want them in the .mht file before doing this.<br> </div> <div><br> </div> <div>my current settings are the same as your but I have debug remarked and do not have the <font size=3D"4" f= ace=3D"Calibri"> alexaHttpPortCount =3D 0 setting.</font><br> <span style=3D"font-family:monospace"><br> </span></div> <div><br> </div> <div><br> </div> <div>On 12/12/23 15:14, Giles Godart-Brown wrote:<br> </div> <blockquote type=3D"cite"> =20 <font size=3D"4" face=3D"Calibri">All<br> I've just received my new Raspberry Pi5 and thought I would do = a straight install from scratch of the latest Master release.<br> All is well, apart from Alexa which wont discover any of my MH devices.<br> I've tried removing them all in the app and rebooting alexas bu= t still no good.<br> The relevant part of my ini file is <br> <snip><br> alexa_enable=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0 =3D 1<br> alexaEnableChunked=C2=A0=C2=A0=C2=A0=C2=A0 =3D 1<br> alexaHttpIp=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0 =3D 192.168.100.57<br> alexaHttpPortCount =3D 0<br> alexaHttpPort =3D 80<br> debug=3Dalexa:5<br> alexaForceLongFormat=3D1<br> </snip><br> I haven't changed my items.mht file from the version that worke= d on my old Pi4<br> Oddly I don't seem to be getting any alexa log messages during discovery, just a couple during initialise viz;<br> <snip><br> 12/12/2023 20:59:02 Alexa open_port: p=3D50000 pn=3DalexaSsdpNotification s=3DSocket_Item=3DHASH(0x5555705140a8)<b= r> <br> 12/12/2023 20:59:02 Alexa open_port: p=3D pn=3DalexaSsdpListen s=3DSocket_Item=3DHASH(0x5555705143d8)<br> </snip><br> Anyone got any ideas?<br> THX<br> Giles<br> </font> <br> <fieldset></fieldset> <br> <fieldset></fieldset> <pre>________________________________________________________ To unsubscribe from this list, go to: <a href=3D"https://lists.sourceforge.= net/lists/listinfo/misterhouse-users" target=3D"_blank" rel=3D"noreferrer">= https://lists.sourceforge.net/lists/listinfo/misterhouse-users</a> </pre> </blockquote> <p><br> </p> </div> ________________________________________________________<br> To unsubscribe from this list, go to: <a href=3D"https://lists.sourceforge.= net/lists/listinfo/misterhouse-users" rel=3D"noreferrer noreferrer" target= =3D"_blank">https://lists.sourceforge.net/lists/listinfo/misterhouse-users<= /a><br> <br> </blockquote></div></div></div> --000000000000c62ea60610d4c91d-- --===============5378446125260101522== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline --===============5378446125260101522== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline ________________________________________________________ To unsubscribe from this list, go to: https://lists.sourceforge.net/lists/listinfo/misterhouse-users --===============5378446125260101522==--