In the Log Viewer I receive on going the following message:
2024-12-15 13:11:09.145 [WARN ] [mmon.WrappedScheduledExecutorService] - Scheduled runnable ended with an exception:
java.lang.IllegalArgumentException: Invalid URI host: null (authority: hereisaIPv6address)
at org.eclipse.jetty.client.HttpClient.checkHost(HttpClient.java:541) ~[?:?]
at org.eclipse.jetty.client.HttpClient.newHttpRequest(HttpClient.java:526) ~[?:?]
at org.eclipse.jetty.client.HttpClient.newRequest(HttpClient.java:484) ~[?:?]
at org.eclipse.jetty.client.HttpClient.newRequest(HttpClient.java:473) ~[?:?]
at org.openhab.binding.hpprinter.internal.api.HPWebServerClient.fetchData(HPWebServerClient.java:105) ~[?:?]
at org.openhab.binding.hpprinter.internal.api.HPWebServerClient.getProductUsageFeatures(HPWebServerClient.java:78) ~[?:?]
at org.openhab.binding.hpprinter.internal.HPPrinterBinder.dynamicallyAddChannels(HPPrinterBinder.java:124) ~[?:?]
at org.openhab.binding.hpprinter.internal.HPPrinterHandler.initializeScheduled(HPPrinterHandler.java:80) ~[?:?]
at org.openhab.binding.hpprinter.internal.HPPrinterHandler.lambda$0(HPPrinterHandler.java:68) ~[?:?]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539) ~[?:?]
at java.util.concurrent.FutureTask.run(FutureTask.java:264) ~[?:?]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304) ~[?:?]
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:840) [?:?]
In the Thing configuration there you can see a switch between IPv4 and a IPv6 address. I thought to use the hostname. But the offered hostname of my CM1415fn is not valid in the configuration of the thing.
I can solve the problem with deactivating IPv6 on the Webinterface of the printer but then I run into a bigger problem with my wife - she can not print anymore. So another issue came up: Why cannot MacOS print with IPv4??? But that should not be the problem here.