Alexa playing hard to get

[gbCambridge]

Big mistake...I went on holiday about a month ago, for three weeks. When I returned, Alexa would not recognise a single device. "Not recognised" was the message. I could claim that I changed nothing...true...but of course, the entire system could have changed around me.

So, I upgraded HAB to the latest version. It appears to work. I can control all my devices from the Bridge Devices page. But the process which builds the devices to allow Alexa to discover them just does not work. Alexa finds a lot of devices (both from the app and from the PC)...all now marked as Hue type, but none of them work from the Alexa voice control or the Alexa app. Habridge Devices continues to work, all devices can be fired on and off from the on-screen buttons, so something is failing between HAbridge and he Alexa discovery. So given that I have definitely NOT changed anything on my side (other than the upgrade of HaBridge) can anyone indicate where I should start looking for the fix?

<< I should add that I also followed the advice and changed the Habridge Web Server port to 80 via the config file. However, it still shows as 8080 in the Bridge Control..perhaps not working either.

Thanks for the help

[gbCambridge]

Got the port changed by changing java parameter! Device recognition is confused... I am getting up to three entries per device. a Philips Hue Light and one or more Royal Philips Electronics smart device, for each device! Nothing with a dimmer appears to work at all.

[bwssytems]

This is the same issue as #1133

Please delete your devices in the echo app or web page, renumber devices on the ha-bridge and do a discovery after that.

[gbCambridge]

Hi ,

I shall certainly try that …again. But today I started getting an object error on a couple of device entries in ha-bridge. Also random failures to connect …about 80% of my devices are working through Alexa. All work via Domoticz. The communication seems to be getting flaky. But after I forced port 80 to be used the flakiness reduced to about 10%.

I would say that performance has degraded over the last few weeks…and I have no idea whey

Thanks for the help

George

From: BWS Systems notifications@github.com Sent: 14 October 2019 15:08 To: bwssytems/ha-bridge ha-bridge@noreply.github.com Cc: gbCambridge george.m.brooke@gmail.com; Author author@noreply.github.com Subject: Re: [bwssytems/ha-bridge] Alexa playing hard to get (#1141)

This is the same issue as #1133 https://github.com/bwssytems/ha-bridge/issues/1133

Please delete your devices in the echo app or web page, renumber devices on the ha-bridge and do a discovery after that.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/bwssytems/ha-bridge/issues/1141?email_source=notifications&email_token=AH2Y2FGGMDETDTSQ2DAMREDQOR4L5A5CNFSM4JAHB6OKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBE25FQ#issuecomment-541699734 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AH2Y2FFGWCEW7AZ527KTMHLQOR4L5ANCNFSM4JAHB6OA . https://github.com/notifications/beacon/AH2Y2FCI3RDQP7PZBAYILDDQOR4L5A5CNFSM4JAHB6OKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBE25FQ.gif

[gbCambridge]

Hi,

I did exactly as you said.

The result is that most devices have two identical entries, as Royal Philips Electronics smart device in the Alexa device table. I have deleted the second of each duplication. When I activate (some) of them by voice I get told that there is a difficulty in communicating with the provider. Some work but certain devices (which work via Domoticz) always fail on the communication.

Is there a test mode where I can check the communication? I cannot see why some would work and some not, given they are all from the same communicating devices.

I think we are getting nearer.

Thanks for the help

George

From: BWS Systems notifications@github.com Sent: 14 October 2019 15:08 To: bwssytems/ha-bridge ha-bridge@noreply.github.com Cc: gbCambridge george.m.brooke@gmail.com; Author author@noreply.github.com Subject: Re: [bwssytems/ha-bridge] Alexa playing hard to get (#1141)

This is the same issue as #1133 https://github.com/bwssytems/ha-bridge/issues/1133

Please delete your devices in the echo app or web page, renumber devices on the ha-bridge and do a discovery after that.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/bwssytems/ha-bridge/issues/1141?email_source=notifications&email_token=AH2Y2FGGMDETDTSQ2DAMREDQOR4L5A5CNFSM4JAHB6OKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBE25FQ#issuecomment-541699734 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AH2Y2FFGWCEW7AZ527KTMHLQOR4L5ANCNFSM4JAHB6OA . https://github.com/notifications/beacon/AH2Y2FCI3RDQP7PZBAYILDDQOR4L5A5CNFSM4JAHB6OKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBE25FQ.gif

[andrewborrill]

Had ha-bridge working on port 82 to avoid port 80 as this was in use by another application. Have discovered ha-bridge no longer working on port 82 as no devices can be found by Alexa. Have setup a test Raspberry Pi to run ha-bridge on port 80 and ha-bridge is now working as expected. So something has changed! with regards to port usage. I guess I must be one of many having this issue as either Alexa or ha-bridge have changed something. Hope someone can sort the mess.

[bwssytems]

@andrewborrill It is Amazon that has changed the requirement for port 80. It is unfortunate.