Hey @J-N-K
Amazon Air Quality integration has also stopped working that we worked together on a few years ago to integrate. It’s showing NULL now for everything.
I’m running org.smarthomej.binding.amazonechocontrol-4.3.2.jar
Best, Jay
My understanding is that the latest version of the binding is the official one now and not the smarthomej verison. But regardless, there seems to be a lot of problems related to Amazon Echo Control and the timing of these problems point to Amazon changing their APIs to support their AI offering. There are several threads about but the main issues seem to be:
- cannot authenticate to Amazon any more when creating a new bridge Thing
- the bridge Thing going offline and nothing works
- the bridge Thing intermittently going offline but everything appears to continue working
- warnings in the logs about empty JSON strings
Try with the latest binding from the official repos instead of the smarthome/j version and if this problem persists, check for some of these other errors.
I don’t know if anyone is working on a fix.
wasn’t that not just for OH5? When I tested it it with 4.3.5 it was not included, in 5.0 I can confirm that it’s the newest.
And yes, there’s something happening within the amazon API and it seems that the amazon servers are rolling out differently. For me everything still works fine except that the lastVoiveCommand cannot be received reliably.
Could be. I thought it was released in 4.3 but it has been awhile.
@jwiseman I am trying to get the air quality sensor running in OH5 and having issues too.
Looking at Amazon documentation, I don’t see an endpoint to query anything else but the temperature
Do you recall, what was used to get the Air quality?
It looks like Amazon either addressed the API changes or reverted them back. The Air Quality of their own units started to work again this morning.
I’m still running the same binding as before.
I’m in the US.
Best, Jay
I can confirm. I was surprised that my outdoor lights came on yesterday evening. These lights are controlled through the echo control binding (no other way to integrate them with OH have I found).
I still have the binding’s log level set to 0 so I don’t know if I’ve still seeing the empty JSON exception or not but it appears to be working now.
Thanks i now consider this specific issue as fixed and will not further investigate this
If the binding does indeed still use an API that Amazon has marked as deprecated, there might still be some work to do eventually.
Sure, and that is still something i will attempt to fix. We identified 5 potential problems, some of them still need work.
This is broken again with the API changes rolling out again this week.
Best, Jay
Looking at what homeassistent did is they just ignore this http status 299. Still trying to understand it all, but it looks like this is returned when no sensor is found. I don;t have a sensor, can you confirm you do not get the JsonParseException in your logs ?