oper8

No harm done and sorry for my show of frustration. I might open a ticket with Universal Devices on this. Thanks,

I was referring to the pulldown menus in ISY, not the thermostat. Anyway, never mind. I see nobody does understand my problem. I'll leave it be. Thanks all ! Issue closed.

Thank you for the help. This can be more than just a Z-Wave topic. See attached a screen from the same system but showing a Insteon thermostat mode 2441TH. ISY is reporting the temperature properly, with one decimal, in this case 21.5 C, the thermostat is actually showing the round-up integer temp of 22 C on its display, and on the ISY there is no way to set the thermostat to a temp. with one decimal, the drop down temp scale is only showing integer numbers. Anyway, it's not something very critical, but more of an annoyance for us users outside US not using the USCS measure system. It would be great if these issues could be fixed.

No, this is the temperature reported by a Z-Wave thermostat. Model is GoControl GC-TBZ48. I'm attaching a screen. You see the temperature in Celsius in integer number, but the thermostat can display or set the temp in Celsius with one decimal. I think it can do increments of 0.5 C. I would need the capability to be able to program the thermostat via the ISY in increments of 0.5C for better resolution.

mmb, I highly appreciate your help, can you be more specific ? what "variable row" ?

I'm using ISY version 5.3.4 with Z-wave support and I want to know if I can display my thermostat temperature - and accordingly, use in my programs - in Celsius with one decimal. My z-wave thermostat is reporting the temperature with one decimal, in Celsius, but the ISY console can display only the integer number.

This is extremely helpful ! Thanks wingman1487 ! I did not know I can see the z-wave routes and nodes information. This can explain a lot of issues and can help troubleshoot the z-wave mesh. In my case the Schlage lock connects via 2 other nodes before reaching ISY.

I have only one Lock now, the second was a constant pain and I took it off. As for repeaters, yes I have one Aeotec in between but I presume the lock connects directly to ISY - I have no way to see this with ver. 5.3.0....

This is very helpful. I have over 40 of these z-wave nodes, I placed them in a separate "NOT USED" folder so they don't clog my AC interface. So it's perfectly fine and safe to delete them ?

I had nothing but trouble with the Schlage BE469ZP Lock. Stay away from this version. I also have a BE469NX and it does work perfectly fine.

From my own experience, I don't think this is a broken mesh issue, but rather some sort of "incompatibility" with particular z-wave devices, in special with the (in)famous Schlage BE469ZP Lock. I have two of these locks, one is the older model BE469NX, firmware ver. 0.8.0. This older one responds perfectly fine to query, does also show the complete menu in the AC, zero issues. The newer BE469ZP is responding "UNKNOWN" to query and the menu is missing the "options" tab. I tried everything possible with this lock, installed it at 10 inch distance from ISY, downgraded my ISY firmware, remove it, add it, remove it and add it again.... hours of painful tests.... same result. As such I gave up on it, found an older 469NX on eBay and I hope it will solve this issue. I also forgot to mention, the older one is farther away from ISY. I have a clean network with lots of wired devices (repeaters).

This is a very cool workaround ! I will try it to fix the same problem with reporting the temperature real-time.

I experience the same issue. Running ISY 5.3.3 The thermostat is responding to my programs, I have one that is changing the heat (or cold) setpoint at different times during the day and one that is turning the fan to "on" or "auto". The problem is with the current temperature reporting through ISY. It doesn't update real time. Must do a query to show the current temperature.

I will rather wait. Maybe a new version will fix this. So far everything is working with the "crippled" lock, but working. I have at least a dozen new devices added since 5.0.16 and lots of new programs and scenes. It will be almost like rebuilding my entire network. Note for self: never jump in upgrading to bleeding edge new version until all the bugs are identified and fixed.

Hi lilyoyo1, How did you go back to 5.0.16 ? I installed several new devices since 5.0.16 and my last backup on that version does not have them. Will I have to join them again ? I'm quite nervous about the downgrade, but I would very much want to go back to that version. I really don't like how the z-wave devices are showing with multiple nodes in 5.3.3, lots of things don't make sense, it's all super un-friendly and counter intuitive.