Openhab3 docker: amazon echo control unstable

I’m trying to running openHAB3 in a Synology Docker and testing some bindings.

  • DSM 7.1-42661 Update 4 on Synology720
  • openhab:latest from Docker Hub
  • Host-Mode is activated

=> most bindings work as expected (KNX, openUV, AirQuality, …meaning bindings with online APIs)

amazonechocontrol does not. I’m getting this error in the logs:

oh - The binding itself seems fine:

  1. installed it
  2. got the amazon account up and running
  3. oh:8080/amazonechocontrol shows all my amazon stuff
  4. I can add every echo/TVStick/Sonos via inbox
  5. at first they’re “online”
  6. after a while they switch to “Unknown” - and back to “Online”

but this error appears regulary

2022-09-26 19:25:41.255 [INFO ] [control.internal.WebSocketConnection] - Web Socket error
java.net.UnknownHostException: openhab: openhab: Name or service not known
	at java.net.InetAddress.getLocalHost(InetAddress.java:1646) ~[?:?]
	at sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:680) ~[?:?]
	at org.eclipse.jetty.client.AbstractConnectorHttpClientTransport.connect(AbstractConnectorHttpClientTransport.java:100) ~[?:?]
	at org.eclipse.jetty.client.HttpClient$1.connect(HttpClient.java:638) ~[?:?]
	at org.eclipse.jetty.client.HttpClient$1.access$100(HttpClient.java:607) ~[?:?]
	at org.eclipse.jetty.client.HttpClient$1$1.failed(HttpClient.java:635) ~[?:?]
	at org.eclipse.jetty.client.AbstractConnectorHttpClientTransport.connectFailed(AbstractConnectorHttpClientTransport.java:138) ~[?:?]
	at org.eclipse.jetty.client.AbstractConnectorHttpClientTransport.connect(AbstractConnectorHttpClientTransport.java:127) ~[?:?]
	at org.eclipse.jetty.client.HttpClient$1.connect(HttpClient.java:638) ~[?:?]
	at org.eclipse.jetty.client.HttpClient$1.succeeded(HttpClient.java:615) ~[?:?]
	at org.eclipse.jetty.client.HttpClient$1.succeeded(HttpClient.java:607) ~[?:?]
	at org.eclipse.jetty.util.SocketAddressResolver$Async.lambda$resolve$1(SocketAddressResolver.java:186) ~[bundleFile:9.4.46.v20220331]
	at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:883) [bundleFile:9.4.46.v20220331]
	at org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.run(QueuedThreadPool.java:1034) [bundleFile:9.4.46.v20220331]
	at java.lang.Thread.run(Thread.java:829) [?:?]
Caused by: java.net.UnknownHostException: openhab: Name or service not known
	at java.net.Inet6AddressImpl.lookupAllHostAddr(Native Method) ~[?:?]
	at java.net.InetAddress$PlatformNameService.lookupAllHostAddr(InetAddress.java:929) ~[?:?]
	at java.net.InetAddress.getAddressesFromNameService(InetAddress.java:1519) ~[?:?]
	at java.net.InetAddress$NameServiceAddresses.get(InetAddress.java:848) ~[?:?]
	at java.net.InetAddress.getAllByName0(InetAddress.java:1509) ~[?:?]
	at java.net.InetAddress.getLocalHost(InetAddress.java:1641) ~[?:?]
	... 14 more

Anyone knows, what to do?

events.log:

2022-09-26 19:32:01.782 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'amazonechocontrol:smartHomeDevice:binder:xxx' changed from UNKNOWN: State not found to ONLINE
2022-09-26 19:32:01.784 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'amazonechocontrol:smartHomeDevice:binder:yyy' changed from UNKNOWN: State not found to ONLINE
2022-09-26 19:32:01.785 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'amazonechocontrol:smartHomeDevice:binder:zzz' changed from UNKNOWN: State not found to ONLINE
2022-09-26 19:32:32.135 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'amazonechocontrol:smartHomeDevice:binder:xxx' changed from ONLINE to UNKNOWN: State not found
2022-09-26 19:32:32.136 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'amazonechocontrol:smartHomeDevice:binder:yyy' changed from ONLINE to UNKNOWN: State not found
2022-09-26 19:32:32.137 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'amazonechocontrol:smartHomeDevice:binder:zzz' changed from ONLINE to UNKNOWN: State not found
...

The reason is clear: Java cannot resolve the host name. The question is if something goes wrong with your local DNS or if Amazon sometimes does not provide correct DNS resolution. Since I don‘t see this, I believe it‘s not a general issue.

Maybe you can setup some monitoring for the host the websocket connects to. This is either alexa.Amazon.com or alexa.Amazon.de.

You still use pi-hole ?

Yes, I’m using pihole. But I checked, there wasn’t any blocked queries from the Synology. And also, shouldn’t it be then either on or off the whole time?
The items shouldn’t be changing then, should they?

I’ll deactivated pihole to see what will happen:

2022-09-26 22:50:59.591 [INFO ] [control.internal.WebSocketConnection] - Web Socket error
java.net.ConnectException: Connection refused
	at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) ~[?:?]
	at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:777) ~[?:?]
	at org.eclipse.jetty.io.SelectorManager.doFinishConnect(SelectorManager.java:355) ~[?:?]
	at org.eclipse.jetty.io.ManagedSelector.processConnect(ManagedSelector.java:347) ~[?:?]
	at org.eclipse.jetty.io.ManagedSelector.access$1700(ManagedSelector.java:65) ~[?:?]
	at org.eclipse.jetty.io.ManagedSelector$SelectorProducer.processSelected(ManagedSelector.java:676) ~[?:?]
	at org.eclipse.jetty.io.ManagedSelector$SelectorProducer.produce(ManagedSelector.java:535) ~[?:?]
	at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.produceTask(EatWhatYouKill.java:362) ~[bundleFile:9.4.46.v20220331]
	at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:186) ~[bundleFile:9.4.46.v20220331]
	at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.tryProduce(EatWhatYouKill.java:173) ~[bundleFile:9.4.46.v20220331]
	at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.produce(EatWhatYouKill.java:137) ~[bundleFile:9.4.46.v20220331]
	at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:883) [bundleFile:9.4.46.v20220331]
	at org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.run(QueuedThreadPool.java:1034) [bundleFile:9.4.46.v20220331]
	at java.lang.Thread.run(Thread.java:829) [?:?]
2022-09-26 22:51:06.322 [INFO ] [control.internal.WebSocketConnection] - Web Socket error
java.net.ConnectException: Connection refused
	at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) ~[?:?]
	at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:777) ~[?:?]
	at org.eclipse.jetty.io.SelectorManager.doFinishConnect(SelectorManager.java:355) ~[?:?]
	at org.eclipse.jetty.io.ManagedSelector.processConnect(ManagedSelector.java:347) ~[?:?]
	at org.eclipse.jetty.io.ManagedSelector.access$1700(ManagedSelector.java:65) ~[?:?]
	at org.eclipse.jetty.io.ManagedSelector$SelectorProducer.processSelected(ManagedSelector.java:676) ~[?:?]
	at org.eclipse.jetty.io.ManagedSelector$SelectorProducer.produce(ManagedSelector.java:535) ~[?:?]
	at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.produceTask(EatWhatYouKill.java:362) ~[bundleFile:9.4.46.v20220331]
	at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:186) ~[bundleFile:9.4.46.v20220331]
	at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.tryProduce(EatWhatYouKill.java:173) ~[bundleFile:9.4.46.v20220331]
	at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.produce(EatWhatYouKill.java:137) ~[bundleFile:9.4.46.v20220331]
	at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:883) [bundleFile:9.4.46.v20220331]
	at org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.run(QueuedThreadPool.java:1034) [bundleFile:9.4.46.v20220331]
	at java.lang.Thread.run(Thread.java:829) [?:?]

How would I do that? (It’s alexa.amazon.de which shows up in my Pihole)

Oh. And the domains are still whitelisted, if you’re thinking of

…and on my (to be replaced) Raspberry Pi running OH3 ot works without a flaw.
…I don’t think, it’s because both are running in parallel, is it?

Edit: Perhaps it was parallel running. At least for the ERRORs.
The Echo-Things still change between ONLINE and UNKNOWN state not found , but after deactivating the other Amazon Account bridge, the ERRORs are gone. Perhaps double polling is bad?

Nope. Can’t be. I let both openHAB3 bindings run with the same account and the same devices for the night.

  1. works without an Error and without ever-changing states in my Raspberry-Pi based OH3
  2. no errors in docker
  3. ever-changing thing-states in docker

No, I’m completely lost - as I didn’t change anything:

  • no changes in Pi-Hole
  • no changes in raspberry OH3
  • no changes in docker

=> except setting the account-Thing on disabled on both.

very strange…

2022-09-27 07:32:14.536 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'amazonechocontrol:smartHomeDevice:binder:xxx' changed from UNKNOWN: State not found to ONLINE
2022-09-27 07:32:14.537 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'amazonechocontrol:smartHomeDevice:binder:yyy' changed from UNKNOWN: State not found to ONLINE
2022-09-27 07:32:14.537 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'amazonechocontrol:smartHomeDevice:binder:zzz' changed from UNKNOWN: State not found to ONLINE
2022-09-27 07:32:44.784 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'amazonechocontrol:smartHomeDevice:binder:xxx' changed from ONLINE to UNKNOWN: State not found
2022-09-27 07:32:44.785 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'amazonechocontrol:smartHomeDevice:binder:yyy' changed from ONLINE to UNKNOWN: State not found
2022-09-27 07:32:44.785 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'amazonechocontrol:smartHomeDevice:binder:zzz' changed from ONLINE to UNKNOWN: State not found
2022-09-27 07:34:15.665 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'amazonechocontrol:smartHomeDevice:binder:xxx' changed from UNKNOWN: State not found to ONLINE
2022-09-27 07:34:15.666 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'amazonechocontrol:smartHomeDevice:binder:yyy' changed from UNKNOWN: State not found to ONLINE
2022-09-27 07:34:15.666 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'amazonechocontrol:smartHomeDevice:binder:zzz' changed from UNKNOWN: State not found to ONLINE
2022-09-27 07:34:45.902 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'amazonechocontrol:smartHomeDevice:binder:xxx' changed from ONLINE to UNKNOWN: State not found
2022-09-27 07:34:45.903 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'amazonechocontrol:smartHomeDevice:binder:yyy' changed from ONLINE to UNKNOWN: State not found
2022-09-27 07:34:45.903 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'amazonechocontrol:smartHomeDevice:binder:zzz' changed from ONLINE to UNKNOWN: State not found
2022-09-27 07:36:16.842 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'amazonechocontrol:smartHomeDevice:binder:xxx' changed from UNKNOWN: State not found to ONLINE
2022-09-27 07:36:16.842 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'amazonechocontrol:smartHomeDevice:binder:yyy' changed from UNKNOWN: State not found to ONLINE
2022-09-27 07:36:16.843 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'amazonechocontrol:smartHomeDevice:binder:zzz' changed from UNKNOWN: State not found to ONLINE
2022-09-27 07:36:47.083 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'amazonechocontrol:smartHomeDevice:binder:xxx' changed from ONLINE to UNKNOWN: State not found
2022-09-27 07:36:47.083 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'amazonechocontrol:smartHomeDevice:binder:yyy' changed from ONLINE to UNKNOWN: State not found
2022-09-27 07:36:47.083 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'amazonechocontrol:smartHomeDevice:binder:zzz' changed from ONLINE to UNKNOWN: State not found
2022-09-27 07:38:18.025 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'amazonechocontrol:smartHomeDevice:binder:xxx' changed from UNKNOWN: State not found to ONLINE
2022-09-27 07:38:18.025 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'amazonechocontrol:smartHomeDevice:binder:yyy' changed from UNKNOWN: State not found to ONLINE
2022-09-27 07:38:18.026 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'amazonechocontrol:smartHomeDevice:binder:zzz' changed from UNKNOWN: State not found to ONLINE
2022-09-27 07:38:48.270 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'amazonechocontrol:smartHomeDevice:binder:xxx' changed from ONLINE to UNKNOWN: State not found
2022-09-27 07:38:48.270 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'amazonechocontrol:smartHomeDevice:binder:yyy' changed from ONLINE to UNKNOWN: State not found
2022-09-27 07:38:48.270 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'amazonechocontrol:smartHomeDevice:binder:zzz' changed from ONLINE to UNKNOWN: State not found
2022-09-27 07:40:06.990 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'amazonechocontrol:echo:binder:xxx' changed from OFFLINE to UNINITIALIZED
2022-09-27 07:40:06.996 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'amazonechocontrol:echo:binder:xxx' changed from UNINITIALIZED to UNINITIALIZED (HANDLER_MISSING_ERROR)
2022-09-27 07:40:06.997 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'amazonechocontrol:echo:binder:yyy' changed from ONLINE to UNINITIALIZED
2022-09-27 07:40:07.001 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'amazonechocontrol:echo:binder:yyy' changed from UNINITIALIZED to UNINITIALIZED (HANDLER_MISSING_ERROR)
2022-09-27 07:40:07.001 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'amazonechocontrol:echo:binder:zzz' changed from ONLINE to UNINITIALIZED
2022-09-27 07:40:07.008 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'amazonechocontrol:echo:binder:zzz' changed from UNINITIALIZED to UNINITIALIZED (HANDLER_MISSING_ERROR)
2022-09-27 07:40:07.008 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'amazonechocontrol:echo:binder:sonos' changed from ONLINE to UNINITIALIZED
2022-09-27 07:40:07.012 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'amazonechocontrol:echo:binder:sonos' changed from UNINITIALIZED to UNINITIALIZED (HANDLER_MISSING_ERROR)
2022-09-27 07:40:07.012 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'amazonechocontrol:flashbriefingprofile:binder:-xxx' changed from ONLINE to UNINITIALIZED
2022-09-27 07:40:07.016 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'amazonechocontrol:flashbriefingprofile:binder:-xxx' changed from UNINITIALIZED to UNINITIALIZED (HANDLER_MISSING_ERROR)
2022-09-27 07:40:07.017 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'amazonechocontrol:echo:binder:www' changed from ONLINE to UNINITIALIZED
2022-09-27 07:40:07.021 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'amazonechocontrol:echo:binder:www' changed from UNINITIALIZED to UNINITIALIZED (HANDLER_MISSING_ERROR)
2022-09-27 07:40:07.021 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'amazonechocontrol:echo:binder:vvv' changed from ONLINE to UNINITIALIZED
2022-09-27 07:40:07.025 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'amazonechocontrol:echo:binder:vvv' changed from UNINITIALIZED to UNINITIALIZED (HANDLER_MISSING_ERROR)
2022-09-27 07:40:07.027 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'amazonechocontrol:smartHomeDevice:binder:xxx' changed from UNKNOWN: State not found to UNINITIALIZED
2022-09-27 07:40:07.030 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'amazonechocontrol:smartHomeDevice:binder:xxx' changed from UNINITIALIZED to UNINITIALIZED (HANDLER_MISSING_ERROR)
2022-09-27 07:40:07.031 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'amazonechocontrol:smartHomeDevice:binder:yyy' changed from UNKNOWN: State not found to UNINITIALIZED
2022-09-27 07:40:07.035 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'amazonechocontrol:smartHomeDevice:binder:yyy' changed from UNINITIALIZED to UNINITIALIZED (HANDLER_MISSING_ERROR)
2022-09-27 07:40:07.035 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'amazonechocontrol:smartHomeDevice:binder:www' changed from UNKNOWN: State not found to UNINITIALIZED
2022-09-27 07:40:07.040 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'amazonechocontrol:smartHomeDevice:binder:www' changed from UNINITIALIZED to UNINITIALIZED (HANDLER_MISSING_ERROR)
2022-09-27 07:40:07.041 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'amazonechocontrol:smartHomeDevice:binder:zzz' changed from UNKNOWN: State not found to UNINITIALIZED
2022-09-27 07:40:07.046 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'amazonechocontrol:smartHomeDevice:binder:zzz' changed from UNINITIALIZED to UNINITIALIZED (HANDLER_MISSING_ERROR)
2022-09-27 07:40:07.046 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'amazonechocontrol:account:binder' changed from ONLINE to UNINITIALIZED
2022-09-27 07:40:07.063 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'amazonechocontrol:account:binder' changed from UNINITIALIZED to UNINITIALIZED (DISABLED)
2022-09-27 07:40:07.064 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'amazonechocontrol:echo:binder:xxx' changed from UNINITIALIZED (HANDLER_MISSING_ERROR) to UNINITIALIZED (BRIDGE_UNINITIALIZED)
2022-09-27 07:40:07.064 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'amazonechocontrol:echo:binder:yyy' changed from UNINITIALIZED (HANDLER_MISSING_ERROR) to UNINITIALIZED (BRIDGE_UNINITIALIZED)
2022-09-27 07:40:07.065 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'amazonechocontrol:echo:binder:zzz' changed from UNINITIALIZED (HANDLER_MISSING_ERROR) to UNINITIALIZED (BRIDGE_UNINITIALIZED)
2022-09-27 07:40:07.067 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'amazonechocontrol:echo:binder:sonos' changed from UNINITIALIZED (HANDLER_MISSING_ERROR) to UNINITIALIZED (BRIDGE_UNINITIALIZED)
2022-09-27 07:40:07.068 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'amazonechocontrol:flashbriefingprofile:binder:-xxx' changed from UNINITIALIZED (HANDLER_MISSING_ERROR) to UNINITIALIZED (BRIDGE_UNINITIALIZED)
2022-09-27 07:40:07.068 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'amazonechocontrol:echo:binder:www' changed from UNINITIALIZED (HANDLER_MISSING_ERROR) to UNINITIALIZED (BRIDGE_UNINITIALIZED)
2022-09-27 07:40:07.069 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'amazonechocontrol:echo:binder:vvv' changed from UNINITIALIZED (HANDLER_MISSING_ERROR) to UNINITIALIZED (BRIDGE_UNINITIALIZED)
2022-09-27 07:40:07.069 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'amazonechocontrol:smartHomeDevice:binder:xxx' changed from UNINITIALIZED (HANDLER_MISSING_ERROR) to UNINITIALIZED (BRIDGE_UNINITIALIZED)
2022-09-27 07:40:07.069 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'amazonechocontrol:smartHomeDevice:binder:yyy' changed from UNINITIALIZED (HANDLER_MISSING_ERROR) to UNINITIALIZED (BRIDGE_UNINITIALIZED)
2022-09-27 07:40:07.069 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'amazonechocontrol:smartHomeDevice:binder:www' changed from UNINITIALIZED (HANDLER_MISSING_ERROR) to UNINITIALIZED (BRIDGE_UNINITIALIZED)
2022-09-27 07:40:07.070 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'amazonechocontrol:smartHomeDevice:binder:zzz' changed from UNINITIALIZED (HANDLER_MISSING_ERROR) to UNINITIALIZED (BRIDGE_UNINITIALIZED)

„Unknown state“ und das switchen zwischen online/offline ist ein Bug in der openHAB Version des bindings. Die smarthome devices sind da nur sehr eingeschränkt nutzbar.

Englisch please :smile:

1 Like

english: “Unknown state” and switching between online/offline is a bug in the openHAB version of the binding. The smarthome devices can only be used to a very limited extent.

hmm… I don’t get that in my raspberry pi OH3… should be same version. are both 3.3.0 release build?

I think, I’m a small step further.
on my “legacy” openHAB3 (still running) - there’s

  • two echos
  • six WiFi-smartplugs

and it’s running flawless.

on my “new” docker openHAB3 - there’s

  • four echos
  • two WiFi-smartplugs

and it’s running without status switches.

As soon, as I add another device → there’s status switching. So I guess, it’s a matter of number of devices!
7 devices:

6 devices:

I must confess, I’m totally confused right now.
on my RPi-installation I could add all there is, and never experienced a problem - even more than 6 devices in my tests.
After removing all items in my docker-installation and adding them one by one in a different order, I never experienced a problem. And even after I added more than 6 devices.

But! What seemingly is the solution to all this: I accidentially added my “Samsung TV”, which somehow managed to get into my Alexa installation. It doesn’t really fit any purpose and even isn’t available on my RPi-installation “Scan”. But somehow was in the docker-installation. It was called “Fernseher”, which I confused with my smartplug to my TV. So, after not adding it to the docker, I now can easily add as many devices as I like - and there’s no more state switching…