I have noticed some strange behavior of the setpoint in the android app
My recuperator has 7 gears for the ventilator, and I have a setpoint defined for that and put it into the sitemap.
Number B_Provent_gear_selected "Ventilation Gear [%d]" <fan> (gVentilation) { mqtt="<[olmo:provent/gear_selected:state:default]" }
Setpoint item=B_Provent_gear_selected minValue=1 maxValue=7 step=1
It works great from the BasicUI but when used from the android APP the setpoint sent to the script contains a decimal point. notice in the debug it is sending 6.0 instead of 6.
2017-05-30 11:26:07.573 [DEBUG] [eclipse.smarthome.model.script.TERMO] - --------- Send ventilation gear command kicked in set to:5
2017-05-30 11:26:07.580 [INFO ] [lipse.smarthome.io.net.exec.ExecUtil] - executed commandLine '/home/pi/curl_provent_put_gear.sh 5'
2017-05-30 11:26:37.233 [DEBUG] [eclipse.smarthome.model.script.TERMO] - --------- Send ventilation gear command kicked in set to:6.0
2017-05-30 11:26:37.255 [INFO ] [lipse.smarthome.io.net.exec.ExecUtil] - executed commandLine '/home/pi/curl_provent_put_gear.sh 6.0'
2017-05-30 11:26:47.643 [DEBUG] [eclipse.smarthome.model.script.TERMO] - --------- Send ventilation gear command kicked in set to:7
2017-05-30 11:26:47.653 [INFO ] [lipse.smarthome.io.net.exec.ExecUtil] - executed commandLine '/home/pi/curl_provent_put_gear.sh 7'
An I doing something wrong or that is a bug? I know I could sort it out in a script but that a patch to a problem that should not exist IMHO