This has been going on for quite a while and over a number of versions of openHAB. Currently running on 2.5.0 Release Build. Not sure if this is showing up now due to the heat here in Oz.
Z-Wave Stick = Aoetec Gen 5
2019-12-31 15:08:34.108 [vent.ItemStateChangedEvent] - KitchenMultisensor_SensorTemperature changed from 31.9 °C to 3E+1 °C
That’s a curiousity, isn’t it? I wonder what causes the difference in the logged format. In both cases, the number will be held as BigDecimal, so it’s just a format-to-string oddity. Noting that 30.00000 is actually stored differently from 30 or 30.0, I expect that it’s something to do with that, the way it gets updated by binding.
Might be specific to QuantityType (with units)
Why, what are you doing with it in a rule? Comparisons etc. should function just the same.
Or do you mean it displays in E style in your UI?
What display format have you specified (in Item label, or sitemap)?
The first entry was from my openHab logs so I’m thinking that removes the issue of pulling them from the nodeRed node as it is only getting the value stored by openHab. That leaves the question as to why OpenHab is showing temperatures in certain ways.
I’m going to step very gently here as @chris has done an amazing job of the Zwave interface and there have been alot of issues with the upgrade to 2.5 which he has done a very diligent on fixing.
I can confirm that this issue is way back in time and I just adjusted to it. As we are now on a stable release and well it’s hot down under I thought time to ask.
Some have suggested a conversion issue which I can understand. However to be a stable consumer platform we need to move beyond temp below 30c being in one format and above being in another format.
Back to Chris.
Let me find at time when it occurs again and I’ll send over the logs and take your guidance on log levels. Now is a good time as temps here are well above 30c each day.