Using the UI5 already were missing the decimal places for the temperature. It is for Celsius users a fundamental feature - here is no more thermometer on the market without it.
(Even HomeSeer, Fibaro etc. support it)
Too big is the difference between 20.6 and 21.4 Celsius (as sample) for automation of room heating.
For Fahrenheit units it may be ok…
We are using for temperature sensors in this time other Z-Wave gateway - a crazy solution…
Somebody know - was this changed for UI7 ?
Thanks.
IMHO no.
I see only integer from my figaro 3in1.
Claas
Official answer from suport:
AUG 20, 2014 | 12:39PM UTC Julian Minut replied:Hi Michael,
Our developers have analyzed this feature request and have decided not to implement this feature because there?s a very high chance to interfere with other z-wave devices that are integrated into Vera. There are over 1000 certified z-wave devices and we try to support as many as possible and sometimes this means we have to do small compromises.
Thank you for your understanding,Thank you,
Julian Minut
Technical Support Team
But I do not have any understanding for this - and send an answer.
Maybe we should all to send them an email - so that they understand that this is a major missing feature?
Hi Julian,sorry, I cannot understand it.
All (not only our) Vera users in Germany (and I think in Europe) are missing this feature.
You understand that this is more a bug as a missing feature?
Other products (HomeSeer, Vera, Fibaro, ?.) use not integer values for temperature - do you know somebody else (major)?You will not find any (digital) temperature measuring device here without decimal places in the value.
This missing feature will make the Vera device unusable for home automation like room heating etc.
For Energy (Aeon HEM series) you are using decimal places - why not for temperature?
Sorry, I cannot understand why you ignore such an important old request.
Do you think that it is better for European users (all Celsius users) to take another product?I really like the Vera concept and we make some projects with it, programming in Lua etc.
And we wanted to expand the business with this units - but - sorry, it’s embarrassing to explain to the user that he cannot properly measure the temperature.Best regards from Germany
Michael Pruefer
Managing Director
…
[quote=“MichaPr, post:4, topic:182569”]But I do not have any understanding for this - and send an answer.
Maybe we should all to send them an email - so that they understand that this is a major missing feature?[/quote]
MichaPr, you’re new here, so you might not be aware of the history of this bug. We’ve been raising the issue of whole-number degrees with MCV since at least UI2. We think it’s only partly MCV’s fault. Way back, we’re guessing that there were some major brands of Z-Wave thermostats that could not handle fractional degrees. Probably they still exist; I can vouch for the RTS thermostat which, even in Celsius mode, operates only in whole degrees. Either MCV tried and failed to convince the manufacturer to fix the problem, or MCV didn’t try. Historically, Z-Wave manufacturers have been both shoddy in their implementation of the standard and unwilling to fix already-released devices, so this isn’t surprising. MCV would have been left with the choice of working around the bug or dropping support for those devices. They opted for the former. It’s probable, as you’ve mentioned, that the decision to do that was made by someone who thinks in (smaller) degrees Fahrenheit, where the problem is 1.8 times smaller.
MCV then compounded the problem by ignoring the UPnP spec and representing the temperature in their Luup engine as a whole number of degrees in the user’s units (Celsius or Fahrenheit). The UPnP spec says that temperature units must be Celsius multiplied by one hundred, equivalent to 0.01 degrees C resolution (and about 0.02 degrees F resolution). So this whole mess has been pushed onto plugin authors too. For MCV to fix this now would require them to make an incompatible change to the Luup data model, which they have been unwilling to do. The Luup engine hasn’t changed its interface since UI2 and I’m not sure that MCV has a plan in place for introducing incompatible changes.
Complaining to support about this bug (yes, you are right, it is a bug) will only get you so far. By suggesting that you will choose a different platform than Vera for your customers, you’ve at least reminded them that there are consequences on their bottom line for not addressing the bug. I hope that this message gets through from MCV support up to management.
Edit: Thanks to the PM sender who corrected my UPnP spec recall: it’s 100ths not 10ths of a degree C.
Every few month this comes up and it’s the new users who raise it, which is important - because the older members, (which I’m fast becoming) - must sound like a broken record now 
Keep up the pressure, I personally hoped their UI7 would address this, so I’m disappointed they’ve not. But to be honest that is nothing new… UI4, UI5, UI6, UI7 → have not had it.
What’s the alternative ? - well it’s not ideal, but under UI5 ditching z-wave temp sensors and going for e.g. netamo, One Wire or 433mhz ones e.g Oregon Scientific (via the RFX Plugin) will provide with the decimal point readings.
I went for the 433mhz option
Hi,
yes, I know about this discussion, even if I’m “new” here - but I had this discussion about 2 years ago too.
Send them the Spec http://upnp.org/specs/ha/UPnP-ha-TemperatureSensor-v1-Service.pdf and was asking about this.
This answer above from support is a standard text - I have got it some months ago too, 100% the same text - so I think many users are asking about this bug, that’s why they have added such a text in CRM.
Maybe we should start here in Forum (at other place) a “Poll” - and ask - Do we need the change in Vera to decimal places in temperature ?
YES, it is a hard work - HomeSeer made this change some time ago too, they have added a second parameter for no integer temperature values - so they are now compatible to all devices.
But - if I know, that something is wrong, I must draw the appropriate consequences and take measures to eliminate the bug - and not ignore it “for ever”.
We will change the rating for Vera at our German review site (www.zwave-review.com) and remove the recommendation for German users.
Device will get the status “partially incompatible” (it is a new one - but we will add it…)
What do you think about a “poll” - will this “message gets through from MCV support up to management” ?
(The power of the users? )
[quote=“parkerc, post:6, topic:182569”]What’s the alternative ? - well it’s not ideal, but under UI5 ditching z-wave temp sensors and going for e.g. netamo, One Wire or 433mhz ones e.g Oregon Scientific (via the RFX Plugin) will provide with the decimal point readings.
I went for the 433mhz option[/quote]
It’s not a real alternative - users are purchasing Fibaro, Aeon, Philio … multi-devices with motion/temperatue, door sensor/temperature etc.
And every time they will have this problem. So Vera is “not compatible” to this multisensors - if say hard …
Hi.
I have been working on a solution to getting decimal places on the temperatures for UI5, it seems to be displaying tenths of a degree for my Secure (Horstmann Controls) thermostat device.
I have another thermostat device but looking at the z-wave data that doesn’t support tenths of a degree.
Under the covers it enables logging of log level 42 which is the raw z-wave data coming back from devices and decodes this data to get the original temperature value before displaying it. It can be set to poll the logs at any interval (default 5 mins) and a device to monitor must be specified.
I’ve published it under apps.mios.com but it doesn’t seem to have appeared yet.
After a bit of effort trying to get it to work with multiple devices the plug-in (for UI5) is available here: MiOS Apps
Best Home Automation shopping experience. Shop at Ezlo!
© 2024 Ezlo Innovation, All Rights Reserved. Terms of Use | Privacy Policy | Forum Rules