Signal channel in TP-Link Kasa binding generates a log warning

@hilbrand, I noticed just now when updating to the August 2019 beta of the TP-Link binding that the Signal channel is no longer working, and is generating a warning in the log:

2019-11-15 22:24:02.742 [WARN ] [mmon.WrappedScheduledExecutorService] - Scheduled runnable ended with an exception: java.lang.NoSuchFieldError: DECIBEL_MILLIWATTS
	at org.openhab.binding.tplinksmarthome.internal.handler.SmartHomeHandler.updateChannelState( ~[?:?]
	at org.openhab.binding.tplinksmarthome.internal.handler.SmartHomeHandler.lambda$3( ~[?:?]
	at java.util.ArrayList.forEach( ~[?:?]
	at java.util.Collections$UnmodifiableCollection.forEach( ~[?:?]
	at org.openhab.binding.tplinksmarthome.internal.handler.SmartHomeHandler.refreshChannels( ~[?:?]
	at java.util.concurrent.Executors$ ~[?:?]
	at java.util.concurrent.FutureTask.runAndReset( ~[?:?]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301( ~[?:?]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ ~[?:?]
	at java.util.concurrent.ThreadPoolExecutor.runWorker( [?:?]
	at java.util.concurrent.ThreadPoolExecutor$ [?:?]
	at [?:?]

I noticed before updating to the latest build that signal strengths weren’t showing up in PaperUI, but didn’t give it any thought. My guess is that TP-Link changed the “DECIBEL_MILLIWATTS” field to a different name in a recent firmware update.

That is related to the change to UoM types in the binding. I guess the UoM decibel miniwatt is not available in 2.4 and causing this error :slightly_frowning_face:

Ah, I see. Guess I’ll need to update to 2.5M2. Thanks!