Amazon Echo Binding offline

Add-ons Bindings
21

Facing the same issue - the Alexa Bridge stays offline with the error GET url 'https://alexa.amazon.in/api/phoenix' failed: null.

22

Just to be clear for future readers, there are at least two issues with the Amazon Echo Control binding right now.

One is relatively minor and it’s a parsing exception thrown into the logs with some regularity. This is only a warning, and it doesn’t seem to impact functionality at all. At least for me it doesn’t. See post #5 for an example of that error.

The second and more serious problem is for some users (but not all it seems, maybe there is a commonality in region?) the bridge Thing is in an error state but the other Things seems to still work.

A third problem which might be related to the second is recreating the bridge Thing is failing.

It’s probably best to no include the first problem on this thread.

I am seeing the first problem but not the second and third one for what it’s worth.

Apparently not. At least not yet.

3 Likes
23

Hey @Chad_Hadsell, exactly the same here. I am using Smarthome/J and air quality measurement devices, all these devices do not show channels anymore. Let’s see what the next days bring…

24

Hi All
I have two separate (both logical and physical i.e. different houses and different accounts for alexa) OH4.3 systems .5 and .6 and both are showing the same error as below

Seems that alexa can control the things (Smart Kettle)but via the OH integration the control it is not available.

I am in Europe/Spain fwiw.
Error:
GET url ‘https://alexa.amazon.com/api/phoenix’ failed: null

25

[amazonechocontrol.internal.Connection] - getSmartHomeDevices fails: GET url 'https://alexa.amazon.de/api/phoenix' failed: null for me (OH 4.3.5), too.

27

FWIW - I get the same errors filling my logs, although it seems everything is working with Amazon Echo Control.

Hope a fix can be found soon.

EDIT: It seems that the “Smarthome” controls are not working - eg temperature sensor readings from my echo devices.

28

Following a bit of testing - I cannot get the smarthome features to work.

Within the item I get the error:

Invalid Link

amazonechocontrol:smartHomeDevice:myamazonaccount:echosmartdevice:temperature

I have tried older (and newer eg snapshot) versions of the binding, but to avail.

It was all working fine until the upgrade to V5.

I use the temp sensors on my Alexas quite extensively, so I hope this can be worked around.

The fact that it worked up until the upgrade would suggest this isn’t specifically an Amazon thing.

29

After installing OpenHAB Version 5 the issue seems to have vanished :-). I am running OpenHAB in docker and have another issue now: avmfritz:energy channel does no longer exist :frowning:

30

I can not confirm this.

In my OH 5 environment the amazonechocontrol binding is going offline every 5 minutes.

There seems to be a fixed interval, which is trying to update the smarthomeDeviceStates. This Query causes the null error that the binding cannot handle.

31

Same here.

32

Yes it does seem that it is the smarthome devices that is the issue.

If I set discoverSmartHome=0 in my things

Bridge amazonechocontrol:account:amazon “email@domain.com” [discoverSmartHome=0, pollingIntervalSmartHomeAlexa=30, pollingIntervalSmartSkills=120]

Then I don’t get the error in the log (as obviously it is not attempting to look for smarthome devices)

However, as noted as well, I am unable to retrieve any smarthome info either - which in my case is the temperature sensor value.

So I would conclude that it is the smart home discover / devices etc which is the issue.

I am able to use the rest of the binding OK - so TTS, changing volume on the echos etc and other “standard” echo functions are working fine.

EDIT: You also need to remove the actual defined thing or things in the .thing file as well to prevent the logs - i.e.

Thing smartHomeDevice myshdevice "Alexa Guard - Room 1" @ "echoserialnumber" [id="AAA_SonarCloudService_smarthomedeviceid"]
33

Hi,

well, I did not make any changes other than to upgrade to OH% (via new docker image, apt-get update + apt-get install ffmpeg, which both should not have any impact). The error is gone, confirmed for me, just checked again. You could try to flush cache and restart . no other idea.

Cheers
P.

34

This was the case with me, bidge showed error but items were still online and working (checked with several echos). After upfating to latest docker image OH5.0 everything is green

Cheers

P.

35

Are you using any SmartHomeDevices?

For me the issue wasn’t the binding going offline - but that SmartHomeDevices not working - described very well in this post…

I assume this issue is still present?

36

Yes I am using DECT 2000 plug in devices from AVM (8 pieces) and 2 DEC Repeater

37

So you have

discoverSmartHome=1 (or 2 or 3)

In your amazonechocontrol.things file?

And you are getting channels linked correctly with your items without any errors like the one below?

31e12c5dd01ecafee7eeba021753ef724238b88d_2_682x500

And you don’t get any errors in the log?

If this is the case, you say you only did an update and installed ffmepg (which unlikley to be the reason for the fix).

Did you do anything else? You suggested clearing cache - but I get the impression you didn’t do this…?

Is anybody else able to confirm if the smarthomedevice detection and linking is now working again?

Cheers

38

It’s not on OH5 in Europe.

39

i can confirm it is working on OH5 :slight_smile: – sorry i need to correct me, the thing is green but it doenst work.

40

I have 2 separate RPi running 4.3.5 and 4.3.6

Both RPi are Rpi 5’swith 8Gb Ram

I am in Spain, so europe

Amazon Account fails with this error on both

Status:
OFFLINE
COMMUNICATION_ERROR
GET url ‘h ttps://alexa.amazon.co.uk/api/phoenix’failed: null

Note i inserted the space after the h so the forum would not try to resolve the url.

41

The binding is not more working under OH 4.x

You need to update to 5.0.0