Pacificwing Posted December 31, 2015 Posted December 31, 2015 I don't appear to be having any luck with thermostats. I can't, for the life of me, get any of them to report correctly in metric. This is now the third model I've tried. I purchased a CT-32 thermostat with an RTZW-02 radio. It seems to work okay. I've set the display to metric, and it is displaying temperatures in celsius just fine at the unit. The problem is with how it reports via z-wave. It reports in fahrenheit regardless of what I do. First of all, does the ISY have no ability to convert imperial units to metric within the controller? Seems like (yet another) basic functionality the ISY is missing. I contacted RadioThermostat and they were pretty much clueless and wanted to blame my z-wave controller anyway. I found the manual for the radio. https://www.google.ca/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&ved=0ahUKEwiY6vjgoIXKAhWMSiYKHXUBAP8QFggbMAA&url=http%3A%2F%2Fproducts.z-wavealliance.org%2FMarketCertification%2FFile%3Ffolder%3D%26filename%3DMarketCertificationFiles%2F1046%2FRTZW-02_module_IB_9jun14.pdf&usg=AFQjCNEvNroDf6Sac9BFig8tFHi8cBjxEQ&bvm=bv.110151844,d.eWE&cad=rja On page 11, it lists z-wave parameter 10 as potentially being able to change the temp reporting filter, but their bit table doesn't make much sense. I think their table messed up when they published the manual. Of course, this was total greek to the teir 1 tech support from RadioThermostat I was talking to. Can anyone here make sense of this? Do any of you have any experience with this thermostat, or am I sending yet another one back?
Michel Kohanim Posted December 31, 2015 Posted December 31, 2015 Hi Pacificwing, ISY reports whatever the thermostat sends so it does not do any type of conversion. If setting the parameter does not help, then I would think that this particular firmware version does not allow you to change the unit. With kind regards, Michel
Pacificwing Posted December 31, 2015 Author Posted December 31, 2015 Hi Pacificwing, ISY reports whatever the thermostat sends so it does not do any type of conversion. If setting the parameter does not help, then I would think that this particular firmware version does not allow you to change the unit. With kind regards, Michel That is what I figured. Honestly, I'm not sure how to set the parameter. I'm assuming parameter 10 on this unit is a bit array, but the ISY reports in decimal. I don't know how to do that conversion.
Amigo Posted December 31, 2015 Posted December 31, 2015 That is what I figured. Honestly, I'm not sure how to set the parameter. I'm assuming parameter 10 on this unit is a bit array, but the ISY reports in decimal. I don't know how to do that conversion. Good morning, This may be helpful to you: https://www.mathsisfun.com/binary-decimal-hexadecimal-converter.html type in your decimal value and it will show you the bits set in the box above or vice versa. I believe the left 8 bits are called high byte and the right 8 are what they call low byte. cheers.
Pacificwing Posted January 1, 2016 Author Posted January 1, 2016 I've just had it confirmed from Radio Thermostat that this model does not support switching to metric over Z-wave. Their response below: Hello,Thank you for contacting us about this. It depends on the z wave software you are using. There is nothing that you can change on our end besides what you have already changed on the thermostat itself. We are just on the thermostat side of things so you will need to check with your z wave company about this. If you have any additional questions please don't hesitate to contact us.Regards,Radio Thermostat Support TeamSupport@radiothermostat.com877-602-5028 Buyer beware I guess.
Michel Kohanim Posted January 1, 2016 Posted January 1, 2016 Hi Pacificwing, Thanks so very much for posting and it's quite disappointing: I am not so sure I understand how something can be a thermostat that displays in Metric but sends in English. With kind regards, Michel
Pacificwing Posted January 5, 2016 Author Posted January 5, 2016 Tue 01/05/2016 11:48:59 AM : [ZWAVE-TX ZW006_1] [010C001306054301]... Tue 01/05/2016 11:48:59 AM : [ZWAVE-RX ] ACK Tue 01/05/2016 11:48:59 AM : [ZWAVE-RX ] [0104011301E8] Tue 01/05/2016 11:48:59 AM : [ZWAVE-TX ] ACK Tue 01/05/2016 11:48:59 AM : [ZWAVE-RX ] [010500135400BD] Tue 01/05/2016 11:48:59 AM : [ZWAVE-TX ] ACK Tue 01/05/2016 11:48:59 AM : [ZWAVE-TX ZW006_1] [0109001306028002]... Tue 01/05/2016 11:48:59 AM : [ZWAVE-RX ] ACK Tue 01/05/2016 11:48:59 AM : [ZWAVE-RX ] [0104011301E8] Tue 01/05/2016 11:48:59 AM : [ZWAVE-TX ] ACK Tue 01/05/2016 11:48:59 AM : [ZWAVE-RX ] [010500135500BC] Tue 01/05/2016 11:48:59 AM : [ZWAVE-TX ] ACK Tue 01/05/2016 11:49:00 AM : [ZWAVE-RX ZW006_1] [0109000400060380]... Tue 01/05/2016 11:49:00 AM : [ZWAVE-TX ] ACK Tue 01/05/2016 11:49:00 AM : [ZWAVE-TX ZW006_1] [0109001306024002]... Tue 01/05/2016 11:49:00 AM : [ZWAVE-RX ] ACK Tue 01/05/2016 11:49:00 AM : [ZWAVE-RX ] [0104011301E8] Tue 01/05/2016 11:49:00 AM : [ZWAVE-TX ] ACK Tue 01/05/2016 11:49:00 AM : [ZWAVE-RX ] [010500135600BF] Tue 01/05/2016 11:49:00 AM : [ZWAVE-TX ] ACK Tue 01/05/2016 11:49:00 AM : [ZWAVE-RX ZW006_1] [0109000400060340]... Tue 01/05/2016 11:49:00 AM : [ZWAVE-TX ] ACK Tue 01/05/2016 11:49:00 AM : [ZWAVE-TX ZW006_1] [0109001306024502]... Tue 01/05/2016 11:49:00 AM : [ZWAVE-RX ] ACK Tue 01/05/2016 11:49:00 AM : [ZWAVE-RX ] [0104011301E8] Tue 01/05/2016 11:49:00 AM : [ZWAVE-TX ] ACK Tue 01/05/2016 11:49:00 AM : [ZWAVE-RX ] [010500135700BE] Tue 01/05/2016 11:49:00 AM : [ZWAVE-TX ] ACK Tue 01/05/2016 11:49:01 AM : [ZWAVE-RX ZW006_1] [0109000400060345]... Tue 01/05/2016 11:49:01 AM : [ZWAVE-TX ] ACK Tue 01/05/2016 11:49:01 AM : [ZWAVE-TX ZW006_1] [0109001306024402]... Tue 01/05/2016 11:49:01 AM : [ZWAVE-RX ] ACK Tue 01/05/2016 11:49:01 AM : [ZWAVE-RX ] [0104011301E8] Tue 01/05/2016 11:49:01 AM : [ZWAVE-TX ] ACK Tue 01/05/2016 11:49:01 AM : [ZWAVE-RX ] [010500135800B1] Tue 01/05/2016 11:49:01 AM : [ZWAVE-TX ] ACK Tue 01/05/2016 11:49:01 AM : [ZWAVE-RX ZW006_1] [0109000400060344]... Tue 01/05/2016 11:49:01 AM : [ZWAVE-TX ] ACK Tue 01/05/2016 11:49:01 AM : [ZWAVE-TX ZW006_1] [0109001306024202]... Tue 01/05/2016 11:49:01 AM : [ZWAVE-RX ] ACK Tue 01/05/2016 11:49:01 AM : [ZWAVE-RX ] [0104011301E8] Tue 01/05/2016 11:49:01 AM : [ZWAVE-TX ] ACK Tue 01/05/2016 11:49:01 AM : [ZWAVE-RX ] [010500135900B0] Tue 01/05/2016 11:49:01 AM : [ZWAVE-TX ] ACK Tue 01/05/2016 11:49:01 AM : [ZWAVE-RX ZW006_1] [0109000400060342]... Tue 01/05/2016 11:49:01 AM : [ZWAVE-TX ] ACK Tue 01/05/2016 11:49:01 AM : [ZWAVE-TX ZW006_1] [010A001306034302]... Tue 01/05/2016 11:49:01 AM : [ZWAVE-RX ] ACK Tue 01/05/2016 11:49:01 AM : [ZWAVE-RX ] [0104011301E8] Tue 01/05/2016 11:49:01 AM : [ZWAVE-TX ] ACK Tue 01/05/2016 11:49:01 AM : [ZWAVE-RX ] [010500135A00B3] Tue 01/05/2016 11:49:01 AM : [ZWAVE-TX ] ACK Tue 01/05/2016 11:49:01 AM : [ZWAVE-RX ZW006_1] [010B000400060543]... Tue 01/05/2016 11:49:01 AM : [ZWAVE-TX ] ACK Tue 01/05/2016 11:49:01 AM : [D2D EVENT ] Event [ZW006_1] [CLISPH] [70] uom=17 prec=0 Tue 01/05/2016 11:49:01 AM : [ ZW006_1] CLISPH 70 (uom=17 prec=0) Tue 01/05/2016 11:49:02 AM : [ZWAVE-TX ZW006_1] [010A001306034302]... Tue 01/05/2016 11:49:02 AM : [ZWAVE-RX ] ACK Tue 01/05/2016 11:49:02 AM : [ZWAVE-RX ] [0104011301E8] Tue 01/05/2016 11:49:02 AM : [ZWAVE-TX ] ACK Tue 01/05/2016 11:49:02 AM : [ZWAVE-RX ] [010500135B00B2] Tue 01/05/2016 11:49:02 AM : [ZWAVE-TX ] ACK Tue 01/05/2016 11:49:02 AM : [ZWAVE-RX ZW006_1] [010B000400060543]... Tue 01/05/2016 11:49:02 AM : [ZWAVE-TX ] ACK Tue 01/05/2016 11:49:02 AM : [ZWAVE-TX ZW006_1] [010B001306043104]... Tue 01/05/2016 11:49:02 AM : [ZWAVE-RX ] ACK Tue 01/05/2016 11:49:02 AM : [ZWAVE-RX ] [0104011301E8] Tue 01/05/2016 11:49:02 AM : [ZWAVE-TX ] ACK Tue 01/05/2016 11:49:02 AM : [ZWAVE-RX ] [010500135C00B5] Tue 01/05/2016 11:49:02 AM : [ZWAVE-TX ] ACK Tue 01/05/2016 11:49:02 AM : [ZWAVE-RX ZW006_1] [010C000400060631]... Tue 01/05/2016 11:49:02 AM : [ZWAVE-TX ] ACK Tue 01/05/2016 11:49:02 AM : [ZWAVE-PROCESS ] Process value Sensor type=1 uomId=1 prec=2 Tue 01/05/2016 11:49:02 AM : [ZWAVE-TX ZW006_1] [010B001306043104]... Tue 01/05/2016 11:49:02 AM : [ZWAVE-RX ] ACK Tue 01/05/2016 11:49:02 AM : [ZWAVE-RX ] [0104011301E8] Tue 01/05/2016 11:49:02 AM : [ZWAVE-TX ] ACK Tue 01/05/2016 11:49:02 AM : [ZWAVE-RX ] [010500135D00B4] Tue 01/05/2016 11:49:02 AM : [ZWAVE-TX ] ACK Tue 01/05/2016 11:49:02 AM : [ZWAVE-RX ZW006_1] [010B000400060531]... Tue 01/05/2016 11:49:02 AM : [ZWAVE-TX ] ACK Tue 01/05/2016 11:49:02 AM : [ZWAVE-PROCESS ] Process value Sensor type=5 uomId=0 prec=0 Here is the contents of the event log immediate after I change the heating setpoint from 71 to 70. Some of this makes sense to me, and some of it doesn't. Can anyone with more understanding confirm that this thing is reporting in english units?
Michel Kohanim Posted January 6, 2016 Posted January 6, 2016 Hi Pacificwing, The thermostat does not send any units. It only reports values. AARTech has contacted RTA and they should be in touch with us so that we can get to the bottom of this. With kind regards, Michel
Pacificwing Posted January 14, 2016 Author Posted January 14, 2016 Hi Pacificwing, The thermostat does not send any units. It only reports values. AARTech has contacted RTA and they should be in touch with us so that we can get to the bottom of this. With kind regards, Michel I was surprised to hear this. Did they ever end up reaching out to you?
Michel Kohanim Posted January 15, 2016 Posted January 15, 2016 Hi PacificWing, Not yet. With kind regards, Michel
Pacificwing Posted February 11, 2016 Author Posted February 11, 2016 Well, as a follow up, the moral of this story is that I'm stuck with a thermostat that doesn't work in Celsius....in Canada, which is kind of a big deal. The vendor is not offering a refund (without substantial deductions for shipping and restocking). ISY (as per this thread) seems to have formed the consensus that it is a hardware issue and they should be reporting in Celsius and the controller has no business massaging that information. RTA is holding the position that they send the unconverted values and it is up to the controller to display them correctly. I tend to favour this explanation, since this isn't the only thermostat that reports incorrectly on the ISY, but reports perfectly fine in metric on other controllers. Z-wave has no published information or standard (that I can find) indicating on which end the problem should be solved? Is the hardware manufacturer responsible for converting the values to to correct scale before sending them out, or should the controller provide a way for rescaling when the data is received? I see lots of opinions on the matter, but no hard standards. So I have encountered a endless loop of vender-controller-device manufacturer finger pointing that is going in a circle. I even had the vendor email both an ISY rep AND RTA, but no movement from either side. Bottom line, don't buy this thermostat if you have an ISY and need metric. This will become more of an issue after the Z-wave ISY moves officially into Canada. If you own this thermostat and really like it, but want to use it in metric, then you will need to buy another z-wave controller. I have it on good authority it works on homeseer.
Pacificwing Posted February 11, 2016 Author Posted February 11, 2016 The thermostat does not send any units. It only reports values. This is semantic and a little misleading, if I understand Z-wave correctly. It is true that the thermostat doesn't specifically say which scale to use (farenheight or celcius), but that information has to be stored somewhere. Currently it is 72F in my house. That is about 22C. If the thermostat is sending a basic integer (72 vs 22) it has already made a decision what scale it is using. That information is stored inside the thermostat. The thermostat is reporting a integer of 72, which means it has made the choice to report in Fahrenheit, regardless on whether or not it is actually communicating which units it is using. This was what I was saying above. Currently the ISY accepts this integer as gospel and offers no option to modify it after the fact (this has been discussed on other threads). The only thing you can do is stick the appropriate suffix on it. So if I want my ISY to report 72C, I can do that. I can assure you, it is not 72C in my house. I would be unconscious from heat exhaustion and nearly dead if it was. But, I can make the ISY report that if I want to. What I can't do, is make it report the correct metric value. So right now (as discussed in other threads) the ISY controller will receive an integer from the thermostat and store that value in the thermostat device object, which other GUIs (such as Mobilinc) will use to interface with. RTA says that the controller should allow you to take that integer value, and apply a conversion on the controller side so that the correct value is reported to the end user. They are basing this on the fact that many other controllers do provide this feature. Who is correct? I doubt we will ever get an official answer.
Michel Kohanim Posted February 11, 2016 Posted February 11, 2016 Hello Pacificwing, We have not heard back from RTA. And, we have one of these on order and we'll definitely check it. With kind regards, Michel
Pacificwing Posted February 11, 2016 Author Posted February 11, 2016 Hello Pacificwing, We have not heard back from RTA. And, we have one of these on order and we'll definitely check it. With kind regards, Michel Nice. Thank you for the update.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.