Permanent issues with openhab not triggering specific actions after one or two days

  • Platform information:
    • Hardware: Rasperry Pi 4 with 2 GB Ram, formerly 64 GB sd card, now 120GB ssd, 32 bit version
    • OS: latest raspbian build
    • Java Runtime Environment: formerly standard version (Java 11), now 17
    • openHAB version: 3.4.2, currenly OH4 M1

Good morning everybody, I am failing and nearly giving up with my openhab setup, as I just can’t get the system to work longer than some 24h. I hope that someone can guide me better trough what I can try to debug, because as for now, I don’t find the solution.

First of all my current issue:
1.) it seems that sendHttpGetRequest actions fail to work after ~24h.
I have verified that first issue by changing a rule and replacing it as follows:

rule “Lüftung an_aus WC”
when
Channel “deconz:switch:f66d3ff4f6:003c84fffe216342011000:buttonevent” triggered 1002
then
//sendHttpGetRequest(“http://192.168.178.146/relay/0?turn=toggle”)
executeCommandLine(“/home/openhabian/wc-lueftung.sh”)
end

The sh script, that is called, runs a curl command, which is working, while the httpGetRequest isnt.

At the same time, commands linked to the deConz binding stopped working:
As an example, I have a shelly switch, I use as trigger. That even is correclty recognized:

2023-03-23 08:54:38.172 [INFO ] [openhab.event.ItemCommandEvent ] - Item ‘GastezimmerLEDVANCE_Helligkeit’ received command ON
2023-03-23 08:54:38.179 [INFO ] [penhab.event.ItemStatePredictedEvent] - Item ‘GastezimmerLEDVANCE_Helligkeit’ predicted to become ON
2023-03-23 08:54:38.183 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘GastezimmerLEDVANCE_Helligkeit’ changed from 0 to 100
2023-03-23 08:54:39.728 [INFO ] [openhab.event.ItemCommandEvent ] - Item ‘GastezimmerLEDVANCE_Helligkeit’ received command OFF
2023-03-23 08:54:39.730 [INFO ] [penhab.event.ItemStatePredictedEvent] - Item ‘GastezimmerLEDVANCE_Helligkeit’ predicted to become OFF
2023-03-23 08:54:39.732 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘GastezimmerLEDVANCE_Helligkeit’ changed from 100 to 0

The item, GastezimmerLEDVANCE_Helligkeit is directly linked to a deconz channel:
deconz:colortemperaturelight:ee4fb49ab7:f0d1b800001429b101:brightness (Dimmer)

My current logging experience is low. Standard loggings show the events are triggered, but the openhab.log file doesn’t show any issues coming up.

Could you guide me trough what and how excatly I could try next?
I think debugigng the sendHttpGetRequest and/or the deconz binding would make sense, maybe the deconz binding uses same/similiar http actions and I can get closer to the actual issue?

I have little exeperience with the karaf console, read me trough the logging documentation but a bit more assistance, what to try in detail would be very helpful.

PS: several months ago I deactivated the shelly binding for the reason it wasn’t working as expected, may be missing root cause still is the same for all of my issues.

Thank you so much for any hints an advance!
Christian

Focus on one at a time.

The first thing to do is log out what the sendHttpGetRequest is returning both when it succeeds and when it fails. What ever the server is returning is provided as the return value from that call.

The sendHttp actions do not use the HTTP binding so turning up the logging will involve turning up the logging to DEBUG on org.openhab.core.model.script.actions.HTTP instead of org.openhab.binding.HTTP. This is probably easiest to achieve by editing $OH_USERDATA/etc/log4j2.xml. Go to the bottom and copy one of the “Logger” lines and modify it with “DEBUG” as the level and the above as the logger name.

I don’t use deConz so I can only offer generic advice. If it fails at the same time that the HTTP call fails, perhaps the problem is network related or hardware related and not OH specific. Turn up the logging save as for the above. Or, since you are on OH 4M1 you can navigate to Settings → Bindings → deConz and click the little gear icon and change the logger level from there.

In both cases, it’s openhab.log that will have the pertinent log statements.

Does this mean that you were having issues in 3.4.2 and upgraded to OH4 M1 to try and solve them? In general, it’s not recommended to be on a milestone if you want stability.

As OH4 uses Java 17 as standard, I thought giving it a try, but you are right, I’ll see if I revert back.

I’ll check the advice from you, @rlkoshak later on. Thanks a lot already for your hints.

Will report log entries after testing.

Best,
Christian

Trying to get further:

I changed the log4j2.xml file, which at its end now looks like:

                <Logger level="DEBUG" name="org.openhab.core.model.script.actions.HTTP"/>
		<Logger level="DEBUG" name="org.openhab.binding.HTTP"/>
			</Loggers>

</Configuration>

Pressing the button relevant to trigger the http send request action, I’m getting those warnings, which do end in the logging ~2 or 3 minutes after the action should have been triggered.

2023-03-24 07:03:23.692 [ERROR] [enhab.core.model.script.actions.HTTP] - Fatal transport error: java.lang.InterruptedException
2023-03-24 07:03:24.792 [ERROR] [enhab.core.model.script.actions.HTTP] - Fatal transport error: java.lang.InterruptedException
2023-03-24 07:03:25.210 [ERROR] [enhab.core.model.script.actions.HTTP] - Fatal transport error: java.lang.InterruptedException
2023-03-24 07:03:26.150 [ERROR] [enhab.core.model.script.actions.HTTP] - Fatal transport error: java.lang.InterruptedException

I also enabled to Deconz-Binding DEBUG Logging, but didn’t get any entries.
I had the impression, that my logging was really lagging…

Therefore, I disabled zram (while beeing on ssd) which seems to help regarding the logging but also regarding my issues, which for now are gone.

Now, with a currently working sendHttpGetRequest action, I am not getting any entries in the openhab.log file with logging beeing set to DEBUG.

Despite the “Fatal transport error: java.lang.InterruptedException” I didn’t receive any more statements for now.

I’d meanwhile check whether zram settings might have an effect. Could I be I ran out of memory?

Best regards,
Christian

Hmm…after ~3 hours working, again issues.

Here is a snippet of my openhab.log file (see below).

I am getting only a much delayed log entry, when triggering my rule containing the http send request.

2023-03-24 14:53:34.593 [ERROR] [enhab.core.model.script.actions.HTTP] - Fatal transport error: java.lang.InterruptedException

any idea what to try next?

thanks,
Christian


2023-03-24 07:41:49.554 [WARN ] [mazonechocontrol.internal.Connection] - Smart home device command failed. The request '{"controlRequests":[{"entityId":"335f80d2-4a9f-4fd1-b318-66957c2f5959","entityType":"APPLIANCE","parameters":{"action":"turnOff"}}]}' resulted in error(s): {"entity":{"entityId":"335f80d2-4a9f-4fd1-b318-66957c2f5959","entityType":"APPLIANCE"},"code":"TargetApplianceUnreachableException","message":"ENDPOINT_UNREACHABLE","data":null}
2023-03-24 08:11:48.783 [WARN ] [mazonechocontrol.internal.Connection] - Smart home device command failed. The request '{"controlRequests":[{"entityId":"335f80d2-4a9f-4fd1-b318-66957c2f5959","entityType":"APPLIANCE","parameters":{"action":"turnOff"}}]}' resulted in error(s): {"entity":{"entityId":"335f80d2-4a9f-4fd1-b318-66957c2f5959","entityType":"APPLIANCE"},"code":"TargetApplianceUnreachableException","message":"ENDPOINT_UNREACHABLE","data":null}
2023-03-24 08:41:48.492 [WARN ] [mazonechocontrol.internal.Connection] - Smart home device command failed. The request '{"controlRequests":[{"entityId":"335f80d2-4a9f-4fd1-b318-66957c2f5959","entityType":"APPLIANCE","parameters":{"action":"turnOff"}}]}' resulted in error(s): {"entity":{"entityId":"335f80d2-4a9f-4fd1-b318-66957c2f5959","entityType":"APPLIANCE"},"code":"TargetApplianceUnreachableException","message":"ENDPOINT_UNREACHABLE","data":null}
2023-03-24 09:11:48.196 [WARN ] [mazonechocontrol.internal.Connection] - Smart home device command failed. The request '{"controlRequests":[{"entityId":"335f80d2-4a9f-4fd1-b318-66957c2f5959","entityType":"APPLIANCE","parameters":{"action":"turnOff"}}]}' resulted in error(s): {"entity":{"entityId":"335f80d2-4a9f-4fd1-b318-66957c2f5959","entityType":"APPLIANCE"},"code":"TargetApplianceUnreachableException","message":"ENDPOINT_UNREACHABLE","data":null}
2023-03-24 09:41:47.674 [WARN ] [mazonechocontrol.internal.Connection] - Smart home device command failed. The request '{"controlRequests":[{"entityId":"335f80d2-4a9f-4fd1-b318-66957c2f5959","entityType":"APPLIANCE","parameters":{"action":"turnOff"}}]}' resulted in error(s): {"entity":{"entityId":"335f80d2-4a9f-4fd1-b318-66957c2f5959","entityType":"APPLIANCE"},"code":"TargetApplianceUnreachableException","message":"ENDPOINT_UNREACHABLE","data":null}
2023-03-24 10:11:48.453 [WARN ] [mazonechocontrol.internal.Connection] - Smart home device command failed. The request '{"controlRequests":[{"entityId":"335f80d2-4a9f-4fd1-b318-66957c2f5959","entityType":"APPLIANCE","parameters":{"action":"turnOff"}}]}' resulted in error(s): {"entity":{"entityId":"335f80d2-4a9f-4fd1-b318-66957c2f5959","entityType":"APPLIANCE"},"code":"TargetApplianceUnreachableException","message":"ENDPOINT_UNREACHABLE","data":null}
2023-03-24 10:41:46.858 [WARN ] [mazonechocontrol.internal.Connection] - Smart home device command failed. The request '{"controlRequests":[{"entityId":"335f80d2-4a9f-4fd1-b318-66957c2f5959","entityType":"APPLIANCE","parameters":{"action":"turnOff"}}]}' resulted in error(s): {"entity":{"entityId":"335f80d2-4a9f-4fd1-b318-66957c2f5959","entityType":"APPLIANCE"},"code":"TargetApplianceUnreachableException","message":"ENDPOINT_UNREACHABLE","data":null}
2023-03-24 10:47:35.532 [ERROR] [enhab.core.model.script.actions.HTTP] - Fatal transport error: java.util.concurrent.TimeoutException: Total timeout 5000 ms elapsed
2023-03-24 10:47:50.412 [WARN ] [p.internal.http.HttpResponseListener] - Requesting 'http://192.168.178.166:8080/list?nukiId=******&token=*******' (method='GET', content='null') failed: java.util.concurrent.TimeoutException: Total timeout 3000 ms elapsed
2023-03-24 10:47:50.420 [WARN ] [io.openhabcloud.internal.CloudClient] - Socket.IO disconnected: ping timeout
2023-03-24 10:47:50.422 [INFO ] [io.openhabcloud.internal.CloudClient] - Disconnected from the openHAB Cloud service (UUID = 82...55, base URL = http://localhost:8080)
2023-03-24 10:48:20.411 [WARN ] [p.internal.http.HttpResponseListener] - Requesting 'http://192.168.178.166:8080/list?nukiId=*****&token=*****' (method='GET', content='null') failed: java.util.concurrent.TimeoutException: Total timeout 3000 ms elapsed
2023-03-24 10:48:41.073 [ERROR] [enhab.core.model.script.actions.HTTP] - Fatal transport error: java.util.concurrent.ExecutionException: java.net.UnknownHostException: api.huum.eu: Temporärer Fehler bei der Namensauflösung
2023-03-24 10:48:41.084 [ERROR] [enhab.core.model.script.actions.HTTP] - Fatal transport error: java.util.concurrent.ExecutionException: java.net.UnknownHostException: api.huum.eu
2023-03-24 10:48:50.412 [WARN ] [p.internal.http.HttpResponseListener] - Requesting 'http://192.168.178.166:8080/list?nukiId=****&token=******' (method='GET', content='null') failed: java.util.concurrent.TimeoutException: Total timeout 3000 ms elapsed
2023-03-24 10:49:20.413 [WARN ] [p.internal.http.HttpResponseListener] - Requesting 'http://192.168.178.166:8080/list?nukiId=****&token=*******' (method='GET', content='null') failed: java.util.concurrent.TimeoutException: Total timeout 3000 ms elapsed
2023-03-24 10:49:37.000 [WARN ] [mazonechocontrol.internal.Connection] - Request to url 'https://alexa.amazon.de/api/phoenix/state' fails with unknown error
java.net.UnknownHostException: alexa.amazon.de
	at sun.nio.ch.NioSocketImpl.connect(NioSocketImpl.java:567) ~[?:?]
	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:327) ~[?:?]
	at java.net.Socket.connect(Socket.java:633) ~[?:?]
	at sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:304) ~[?:?]
	at sun.security.ssl.BaseSSLSocketImpl.connect(BaseSSLSocketImpl.java:174) ~[?:?]
	at sun.net.NetworkClient.doConnect(NetworkClient.java:183) ~[?:?]
	at sun.net.www.http.HttpClient.openServer(HttpClient.java:531) ~[?:?]
	at sun.net.www.http.HttpClient.openServer(HttpClient.java:636) ~[?:?]
	at sun.net.www.protocol.https.HttpsClient.<init>(HttpsClient.java:266) ~[?:?]
	at sun.net.www.protocol.https.HttpsClient.New(HttpsClient.java:380) ~[?:?]
	at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNewHttpClient(AbstractDelegateHttpsURLConnection.java:193) ~[?:?]
	at sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1242) ~[?:?]
	at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:1128) ~[?:?]
	at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:179) ~[?:?]
	at sun.net.www.protocol.http.HttpURLConnection.getOutputStream0(HttpURLConnection.java:1430) ~[?:?]
	at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:1401) ~[?:?]
	at sun.net.www.protocol.https.HttpsURLConnectionImpl.getOutputStream(HttpsURLConnectionImpl.java:220) ~[?:?]
	at org.openhab.binding.amazonechocontrol.internal.Connection.makeRequest(Connection.java:640) ~[?:?]
	at org.openhab.binding.amazonechocontrol.internal.Connection.makeRequestAndReturnString(Connection.java:561) ~[?:?]
	at org.openhab.binding.amazonechocontrol.internal.Connection.getSmartHomeDeviceStatesJson(Connection.java:1082) ~[?:?]
	at org.openhab.binding.amazonechocontrol.internal.handler.AccountHandler.updateSmartHomeState(AccountHandler.java:911) ~[?:?]
	at org.openhab.binding.amazonechocontrol.internal.handler.AccountHandler.lambda$2(AccountHandler.java:167) ~[?:?]
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539) ~[?:?]
	at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305) ~[?:?]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305) ~[?:?]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) ~[?:?]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) ~[?:?]
	at java.lang.Thread.run(Thread.java:833) ~[?:?]
2023-03-24 10:49:37.018 [WARN ] [trol.internal.handler.AccountHandler] - updateSmartHomeState fails with unexpected error
java.net.UnknownHostException: alexa.amazon.de
	at sun.nio.ch.NioSocketImpl.connect(NioSocketImpl.java:567) ~[?:?]
	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:327) ~[?:?]
	at java.net.Socket.connect(Socket.java:633) ~[?:?]
	at sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:304) ~[?:?]
	at sun.security.ssl.BaseSSLSocketImpl.connect(BaseSSLSocketImpl.java:174) ~[?:?]
	at sun.net.NetworkClient.doConnect(NetworkClient.java:183) ~[?:?]
	at sun.net.www.http.HttpClient.openServer(HttpClient.java:531) ~[?:?]
	at sun.net.www.http.HttpClient.openServer(HttpClient.java:636) ~[?:?]
	at sun.net.www.protocol.https.HttpsClient.<init>(HttpsClient.java:266) ~[?:?]
	at sun.net.www.protocol.https.HttpsClient.New(HttpsClient.java:380) ~[?:?]
	at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNewHttpClient(AbstractDelegateHttpsURLConnection.java:193) ~[?:?]
	at sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1242) ~[?:?]
	at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:1128) ~[?:?]
	at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:179) ~[?:?]
	at sun.net.www.protocol.http.HttpURLConnection.getOutputStream0(HttpURLConnection.java:1430) ~[?:?]
	at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:1401) ~[?:?]
	at sun.net.www.protocol.https.HttpsURLConnectionImpl.getOutputStream(HttpsURLConnectionImpl.java:220) ~[?:?]
	at org.openhab.binding.amazonechocontrol.internal.Connection.makeRequest(Connection.java:640) ~[?:?]
	at org.openhab.binding.amazonechocontrol.internal.Connection.makeRequestAndReturnString(Connection.java:561) ~[?:?]
	at org.openhab.binding.amazonechocontrol.internal.Connection.getSmartHomeDeviceStatesJson(Connection.java:1082) ~[?:?]
	at org.openhab.binding.amazonechocontrol.internal.handler.AccountHandler.updateSmartHomeState(AccountHandler.java:911) ~[?:?]
	at org.openhab.binding.amazonechocontrol.internal.handler.AccountHandler.lambda$2(AccountHandler.java:167) ~[?:?]
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539) ~[?:?]
	at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305) ~[?:?]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305) ~[?:?]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) ~[?:?]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) ~[?:?]
	at java.lang.Thread.run(Thread.java:833) ~[?:?]
2023-03-24 10:49:49.158 [ERROR] [enhab.core.model.script.actions.HTTP] - Fatal transport error: java.util.concurrent.ExecutionException: java.net.UnknownHostException: api.huum.eu: Temporärer Fehler bei der Namensauflösung
2023-03-24 10:49:49.175 [ERROR] [enhab.core.model.script.actions.HTTP] - Fatal transport error: java.util.concurrent.ExecutionException: java.net.UnknownHostException: api.huum.eu
2023-03-24 10:49:50.413 [WARN ] [p.internal.http.HttpResponseListener] - Requesting 'http://192.168.178.166:8080/list?nukiId=*******&token=***********' (method='GET', content='null') failed: java.util.concurrent.TimeoutException: Total timeout 3000 ms elapsed
2023-03-24 10:50:13.615 [INFO ] [io.openhabcloud.internal.CloudClient] - Connected to the openHAB Cloud service (UUID = 82...55, base URL = http://localhost:8080)
2023-03-24 11:11:47.466 [WARN ] [mazonechocontrol.internal.Connection] - Smart home device command failed. The request '{"controlRequests":[{"entityId":"335f80d2-4a9f-4fd1-b318-66957c2f5959","entityType":"APPLIANCE","parameters":{"action":"turnOff"}}]}' resulted in error(s): {"entity":{"entityId":"335f80d2-4a9f-4fd1-b318-66957c2f5959","entityType":"APPLIANCE"},"code":"TargetApplianceUnreachableException","message":"ENDPOINT_UNREACHABLE","data":null}
2023-03-24 11:41:46.268 [WARN ] [mazonechocontrol.internal.Connection] - Smart home device command failed. The request '{"controlRequests":[{"entityId":"335f80d2-4a9f-4fd1-b318-66957c2f5959","entityType":"APPLIANCE","parameters":{"action":"turnOff"}}]}' resulted in error(s): {"entity":{"entityId":"335f80d2-4a9f-4fd1-b318-66957c2f5959","entityType":"APPLIANCE"},"code":"TargetApplianceUnreachableException","message":"ENDPOINT_UNREACHABLE","data":null}
2023-03-24 12:11:45.852 [WARN ] [mazonechocontrol.internal.Connection] - Smart home device command failed. The request '{"controlRequests":[{"entityId":"335f80d2-4a9f-4fd1-b318-66957c2f5959","entityType":"APPLIANCE","parameters":{"action":"turnOff"}}]}' resulted in error(s): {"entity":{"entityId":"335f80d2-4a9f-4fd1-b318-66957c2f5959","entityType":"APPLIANCE"},"code":"TargetApplianceUnreachableException","message":"ENDPOINT_UNREACHABLE","data":null}
2023-03-24 12:41:45.531 [WARN ] [mazonechocontrol.internal.Connection] - Smart home device command failed. The request '{"controlRequests":[{"entityId":"335f80d2-4a9f-4fd1-b318-66957c2f5959","entityType":"APPLIANCE","parameters":{"action":"turnOff"}}]}' resulted in error(s): {"entity":{"entityId":"335f80d2-4a9f-4fd1-b318-66957c2f5959","entityType":"APPLIANCE"},"code":"TargetApplianceUnreachableException","message":"ENDPOINT_UNREACHABLE","data":null}
2023-03-24 13:02:08.878 [WARN ] [mazonechocontrol.internal.Connection] - Smart home device command failed. The request '{"controlRequests":[{"entityId":"335f80d2-4a9f-4fd1-b318-66957c2f5959","entityType":"APPLIANCE","parameters":{"action":"turnOff"}}]}' resulted in error(s): {"entity":{"entityId":"335f80d2-4a9f-4fd1-b318-66957c2f5959","entityType":"APPLIANCE"},"code":"TargetApplianceUnreachableException","message":"ENDPOINT_UNREACHABLE","data":null}
2023-03-24 13:11:45.397 [WARN ] [mazonechocontrol.internal.Connection] - Smart home device command failed. The request '{"controlRequests":[{"entityId":"335f80d2-4a9f-4fd1-b318-66957c2f5959","entityType":"APPLIANCE","parameters":{"action":"turnOff"}}]}' resulted in error(s): {"entity":{"entityId":"335f80d2-4a9f-4fd1-b318-66957c2f5959","entityType":"APPLIANCE"},"code":"TargetApplianceUnreachableException","message":"ENDPOINT_UNREACHABLE","data":null}
2023-03-24 13:41:44.613 [WARN ] [mazonechocontrol.internal.Connection] - Smart home device command failed. The request '{"controlRequests":[{"entityId":"335f80d2-4a9f-4fd1-b318-66957c2f5959","entityType":"APPLIANCE","parameters":{"action":"turnOff"}}]}' resulted in error(s): {"entity":{"entityId":"335f80d2-4a9f-4fd1-b318-66957c2f5959","entityType":"APPLIANCE"},"code":"TargetApplianceUnreachableException","message":"ENDPOINT_UNREACHABLE","data":null}
2023-03-24 14:11:44.297 [WARN ] [mazonechocontrol.internal.Connection] - Smart home device command failed. The request '{"controlRequests":[{"entityId":"335f80d2-4a9f-4fd1-b318-66957c2f5959","entityType":"APPLIANCE","parameters":{"action":"turnOff"}}]}' resulted in error(s): {"entity":{"entityId":"335f80d2-4a9f-4fd1-b318-66957c2f5959","entityType":"APPLIANCE"},"code":"TargetApplianceUnreachableException","message":"ENDPOINT_UNREACHABLE","data":null}
2023-03-24 14:41:43.929 [WARN ] [mazonechocontrol.internal.Connection] - Smart home device command failed. The request '{"controlRequests":[{"entityId":"335f80d2-4a9f-4fd1-b318-66957c2f5959","entityType":"APPLIANCE","parameters":{"action":"turnOff"}}]}' resulted in error(s): {"entity":{"entityId":"335f80d2-4a9f-4fd1-b318-66957c2f5959","entityType":"APPLIANCE"},"code":"TargetApplianceUnreachableException","message":"ENDPOINT_UNREACHABLE","data":null}

Sure that you don’t have a network problem ?
It looks like there are

  • timeouts
  • myopenhab.org seems not to be reachable
  • there are messages about DNS problems ( Temporärer Fehler bei der Namensauflösung )

Thanks Wolfgang,

this is what the log suggests…however while having those issues, I can permanently access the raspberry via SSH, SFTP, I can use the web frontend from openhab and phoscon and rules, using for example “curl” are working without issues.

Therefore having network issues doesn’t sound suitable for me…?

Still I am currenlty giving it a try having ip v6 disabled and I already organized a LAN cable to have a next try connecting to my router directly.

Figure out why the HTTP address doesn’t respond when the sendHttpGetRequest is made. If the HTTP server doesn’t reply within five seconds the request times out with an error.

The problem may be in your network or the server itself. I can’t rule out OH as the problem but the root cause right now is the time from OH making the request and the server responding is exceeding five seconds.

All of these have a much more generous timeout.

thanks @rlkoshak and @Wolfgang_S

Thats helpful and good to know. So my next steps will be checking wifi vs. lan connection and/or replacing the rasperry. will keep that thread updated with information on my progress.

Its a pleasure having such a good community. thanks again!

Edit / 31st of march:
No more warnings at all while having connected my raspberry to LAN instead of using Wifi.
For all users having similiar issues than I had, maybe that’s a good hint to start. For now I’ll let the system run as it is, but maybe in future try to more figure out what is causing the troubles. Maybe I’ll start with a separate wifi dongle, let’s see…

As I didn’t find more hints related OH + raspberry Wifi issues, it even might be related to my home network situation / wifi channels / inteferences whatever.

Finally wanted to thank you for hinting me there. I was struggling for months with openhab, set it new op with new SD card, now with an SSD (which is still nice as beeing super fast!) and it cost me many of my nerves.

/ original post /

Hi guys,

After switching to LAN, no warnings and issues since more than two days. Looks very promising!
Didn’t figure out yet what’s causing the wifi trouble, but should the raspberry keep working for the next several days with lan connected, I am already more than happy.

Will update in a week or two, but thanks already now for hinting me to where I am now.

Best, Christian

1 Like