At least this shows that the binding is now processing the command and sending a command. I’ve not decoded the command completely, but I think it’s correct (the D7 in the command is 215 which is the temperature you set, the 22 before that I think sets the decimals, and I think the 01 before that says it’s deg C).
The controller didn’t send the command to the device, so I think it’s worth trying again to set the setpoint…
but that could be some missing formatting on my part? This is the first time I use the Number:Temperature.
All my Aeon Multisensor 6s use only Number.
About all my controller errors; they tend to be abundant right after s restart. After that it settles.
I have s spare stick. What do you think about making a backup, restoring to the spare?
I can vaguely remember we have discussed these errors in another thread. They started showing up when my number of nodes reached a high number (>25 or so).
When you do your testing, how many nodes are in your network?
Maybe - I’m also not especially familiar with the new UOM usage, but when I was testing this a couple of weeks back I think it was logging as deg C, so I think the ? does indicate something is wrong somewhere.
For testing normally only a small number as I normally just include the device I’m trying to test with. In my production system though I have around 40 nodes.
habmin also shows duplicates when a channel is assigned to an item name.
Guess that is what it is. Anyway, it shows a value of 22, but clicking on it it changes to an input field showing 21.5 .
Changing the value in paperUI makes the change take (thanks to your latest binding. Didn’t work before), but it is not possible to set the value a second time. No matter how i click, I cannot get the input field back. So it is a once per session setting
habmin does not seems to accept any editing in Description view other than switches ON/OFF.
No, this is not binding related.
Must be a paperUI thing. Cannot provide a log of multiple settings when input field appears only once
Who is maintaining paperUI? Could tip him off (somehow I guess it is not a she?) maybe?
Since it is showing the current value wrong, it is probably type confused in some way.
For what it’s worth, I have updated the same .zip we used yesterday with a debug log of setting the setpoint from paperUI.
only if I insert some trace output in the code and I built it again. My OH2 is running on a RPI2.
My 2 Cents on this change to support UoM:
the binding should be able to interpret all kind of input thrown at it, not only the QunatityType:
+ If only a decimal (23), it should interpret it as a value in the correct Unit being used in the system (Degrees Celsius for example)
+ If a string (like 23 °C), it should be able to interpret it and do the right conversion before sending the value to the device
some devices have their own config parameters to set the desired Unit that is shown on the display of the device. On Z-Wave level, the unit is sent as part of the command (scale parameter). Which scale the binding uses to sent the command? is it always degrees C by default and the conversion takes place in the binding if OH2 system is set to degrees F by default? Or do you set the scale in the binding according to system settings?
Do I take it then that you are not planning to do this? Is it not possible to put the stick in the your PC to debug?
I would agreed - but you are sending a QuantityType, not a Number so this isn’t the binding problem I think - the error shows that the command is received as a QuantityType,.
Firstly, I am not sure why it is not implemented since the latest binding should provide this function - have you deleted the thing and add it back to make sure that you have the latest thing definition?
Please remember that items have types - you can’t just go and use any type that you like - you need to use the right type. For the command, it is possible to write the binding to work with different types, but the update will always be sent in a specific type.
I suggest to resolve the issue here before complicating things
No - the binding will send the value that you provide directly to the device. The binding doesn’t perform scaling.