CoolMasterNet binding - error when binding starts - SOLVED

I’ve just installed the CoolMasterNet binding for the first time (using the latest OH snapshot).

When the binding starts up, it grabs the correct current state of the devices, but then immediately logs an error, and then the binding doesn’t receive any further updates from the devices. It still successfully control the devices, but communication seems strictly one-way. The error will repeat every time I restart the binding.

Has anyone else seen this? Is it a bug in the binding or OH, or am I doing something stupid?

Log error as follows:

                                 |
20|2018-05-27 09:07:46.248 [WARN ] [mmon.WrappedScheduledExecutorService] - Scheduled runnable ended with an exception                  |
20|java.lang.NullPointerException: null                                                                                                 |
20|        at org.openhab.binding.coolmasternet.handler.HVACHandler.query(HVACHandler.java:117) ~[?:?]                                  |
ja|        at org.openhab.binding.coolmasternet.handler.HVACHandler.refresh(HVACHandler.java:93) ~[?:?]                                 |
  |        at org.openhab.binding.coolmasternet.internal.ControllerHandler.lambda$0(ControllerHandler.java:72) ~[?:?]                   |
  |        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:?]                                             |
  |        at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) [?:?]                                                    |
  |        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) [?:?|
  |        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) [?:?]      |
  |        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:?]                                     |
  |        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:?]                                     |
  |        at java.lang.Thread.run(Thread.java:748) [?:?]                                         

thanks,

Dan

Just noting this was a bug in the binding and has been fixed in the latest snapshot - https://github.com/openhab/openhab2-addons/issues/3644

Hi, I am running the 2.5.0 M1 version of this binding and still have the same problem, see log below.
I also tried the latest Snapshot version of this binding, but found that it is not working at all for me.
All my things go offline with communication error in that version. If I recreate them they show online, but after I try to switch on an aircon they go offline again and the command never makes it through.

I would appreciate some help with this tnx.

2019-06-05 11:57:02.579 [WARN ] [mmon.WrappedScheduledExecutorService] - Scheduled runnable ended with an exception:
java.lang.NumberFormatException: null
    at java.math.BigDecimal.<init>(BigDecimal.java:494) ~[?:?]
    at java.math.BigDecimal.<init>(BigDecimal.java:383) ~[?:?]
    at java.math.BigDecimal.<init>(BigDecimal.java:806) ~[?:?]
    at org.eclipse.smarthome.core.library.types.DecimalType.<init>(DecimalType.java:57) ~[?:?]
    at org.openhab.binding.coolmasternet.internal.handler.HVACHandler.refresh(HVACHandler.java:119) ~[?:?]
    at org.openhab.binding.coolmasternet.internal.ControllerHandler.refreshHVACUnits(ControllerHandler.java:106) ~[?:?]
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) ~[?:?]
    at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) ~[?:?]
    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) ~[?:?]
    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) ~[?:?]
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:?]
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:?]
    at java.lang.Thread.run(Thread.java:748) [?:?]```

An old thread, but for the benefit of the archives I have looked into this exception in detail and you can find further details at https://github.com/openhab/openhab-addons/issues/7333.