mksway
commented
1 year ago Hi,
I am currently checking what might be the cause. Do you have a battery connected to your powerrouter? Do you see the new channels introduced in the newer version (and configuration parameters)? If not openhab maybe somehow stored old values. According to the stacktrace it fails reading the safetysoc data for some reason :( Though this should not be the case since it was present in 3.1.0 already.
I have reuploaded the bundle where this message is only visible @ debug level in order to get rid of the annoying message...
If you would be so kind and use the new .jar (https://github.com/mksway/openhab-lgessenervu-dist/blob/main/org.openhab.binding.lgessenervu-3.4.3-SNAPSHOT.jar) and turn the loglevel for this plugin to debug and post me the json response from the webservice it would be great.
Best
meschmesch
I run openhab 3.4.4 and just installed the latest openhab-lgessenervu-dist-binding (3.4.3-SNAPSHOT). I get the following errors every 20 seconds:
2023-06-23 10:03:23.943 [ERROR] [ssenervu.internal.LGEssenervuHandler] - getNumericValueOfString empty String java.lang.NumberFormatException: empty String at jdk.internal.math.FloatingDecimal.readJavaFormatString(FloatingDecimal.java:1842) ~[?:?] at jdk.internal.math.FloatingDecimal.parseDouble(FloatingDecimal.java:110) ~[?:?] at java.lang.Double.parseDouble(Double.java:543) ~[?:?] at org.openhab.binding.lgessenervu.internal.LGEssenervuHandler.getNumericValueOfString(LGEssenervuHandler.java:322) [bundleFile:?] at org.openhab.binding.lgessenervu.internal.LGEssenervuHandler.responseCallbackCurrentData(LGEssenervuHandler.java:483) [bundleFile:?] at org.openhab.binding.lgessenervu.internal.client.LGLanClient.getCurrentData(LGLanClient.java:174) [bundleFile:?] at org.openhab.binding.lgessenervu.internal.job.SnapshotJob.run(SnapshotJob.java:35) [bundleFile:?] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) [?:?] 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:1128) [?:?] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:?] at java.lang.Thread.run(Thread.java:829) [?:?]Uninstalling the binding and using the old version 3.1.0 solves the problem, there I have no errors.