[tacmi] TA CMI Binding - NPE when 4th parameter not set #4515
Comments
Could you turn on TRACE level debugging for the TA CMI binding, like: <logger name="org.openhab.binding.tacmi" level="TRACE"/> in your logback.xml file? This should add verbose logging for when the binding receives a command. |
Here is the log extract:
|
Thank you, @Sineos. It looks like the 1.8.3 TACmi binding has a bug here, where the code assumes you've specified a fourth part of the binding config string, the measureType. If this analysis is correct, then you can either add a fourth part to the binding config string (it looks like |
Thank you for your support. I currently have no access to my system but I will report back once back home. |
Your analysis is correct, it does in fact expect a fourth config item. Also The issue with the fourth config item is still present in the snapshot:
With the fourth config item added:
Knowing this, it is not a real issue anymore. Thanks a lot |
@Sineos thanks for reporting this bug, and that it is still present in the 1.9 snapshot. @Wolfgang1966, would you be able to take a look at fixing this? |
Good morning everybody, @Sineos, please find attached a new version of the binding, which should fix the NPE when using three parameters. Would you please be so kind and test it? By the way, I'm glad to read that somebody except me uses the TA-CMI binding. :-) |
@Wolfgang1966 actually your CMI binding made me dig into OH in the first place. I wanted to integrate my UVR into NodeRed and was totally frustrated with this $%&§ CoE interface. So many thanks for providing this binding. I have tested your latest snapshot and it works like intended. Again thanks a lot for this fast and dedicated support. |
My Environment
Issue
Generally the binding is working, I'm able to receive analog values and digital values, even toggling digital inputs works. Still the log frequently shows following line:
2016-07-03 19:37:28.918 [WARN ] [.b.tacmi.internal.TACmiBinding] - Error in execute: java.net.SocketTimeoutException, Message: Receive timed out
This is my CoE Setting
Also the UVR is showing a improperly configured Node 2 in the CAN topology
Issue 2
I'm an absolute beginner with OH so please bear with me, if I'm completely stupid but I can't manage to get the CMI playing nicely with MQTT / NodeRed. This is what I got:
Item:
mqttToOnOff.map
Switching the digital IO manually to ON in the UVR16x2 results in:
2016-07-03 21:34:58.155 [INFO ] [runtime.busevents ] - Brenner state updated to ON
also "1" is published to
uvr/digital/test/bla
. The same is true for OFF, so I guess this is the expected behavior.Injecting a "1" from NodeRed to the MQTT Topic uvr/digital/test results in:
2016-07-03 21:39:05.801 [INFO ] [runtime.busevents ] - Brenner received command ON
and the UVR's digital input toggles.
My expected behavior would have been:
uvr/digital/test/bla
The text was updated successfully, but these errors were encountered: