jch Posted November 21, 2015 Posted November 21, 2015 Has anyone tried one of these with their ISY? http://www.amazon.com/Remotec-ZTS-110-Z-Wave-Smart-Thermostat/dp/B00KSITI20/ref=pd_sim_60_9?ie=UTF8&dpID=31dIwilE1PL&dpSrc=sims&preST=_AC_UL160_SR131%2C160_&refRID=0Q3K607TY99X6FB9FAMN They are only $63 on Amazon. I have seven zones of baseboard heat so one of my prime requirements is inexpensive. With the intelligence of the ISY, I can't see the need for a very smart thermostat. Basic thermostat functionality , reliable Z-Wave communication and even be a good repeater is all I ask. Plus Xmas is coming and I'd love to put some home automation stuff on my wish list.
danbutter Posted November 21, 2015 Posted November 21, 2015 I have 2 of these and they are great. www.amazon.com/Evolve-T-100R-Residential-Thermostat/dp/B008OF8CKS/ref=sr_1_20?srs=2529402011&ie=UTF8&qid=1448084582&sr=8-20 They need a C wire for power, but then act as a zwave repeater too. They are a clone of the higher end rcs units that have inputs for other temp sensors too! They can fully function as a programmable thermostat if anything ever happened to your ISY too.
Pacificwing Posted November 24, 2015 Posted November 24, 2015 I ordered one of these and was actually coming onto the forum to find support for it when I found this thread. The thermostat works fine, but there is one annoying bug. When you set the thermostat to Celsius, the thermostat performs the unit conversion twice for the Z-wave register for "Heating Setpoint". So, for example, when I manually set the thermostat to 16C, it will report to the ISY that the heating setpoint is -9C. Its doing the conversion to Celsius twice, but only for this particular setpoint. The thermostat operates fine and controls to 16C, but the heating setpoint Z-wave parameters just reports incorrectly when the thermostat is set to metric. It is annoying, but it still functions. The other feature I wish was possible is to have an automatic fallback. I would like to have the ISY control the schedule for most of the time, but if the connection is lost to the ISY, I would like the thermostat to fall back to a specific temperature, rather than the temperature it was last adjusted to. This way if I'm away from home, and the thermostat loses connection to the ISY, then thermostat won't keep running and running and burn through my energy bill. Right now I have it running on its internal schedule, and I use the Z-wave for overrides. Eventually I will put the ISY in charge.
Amigo Posted November 24, 2015 Posted November 24, 2015 @Pacificwing, don't where you are located but I will also be using Celsius and have similar ideas as you. I also wanted to see if ISY can actually read/write the internal schedule. I have ordered a more recent model of RCS and Honeywell z-wave thermostats and will report back my findings of compatibility and functionality with ISY.
fryfrog Posted November 25, 2015 Posted November 25, 2015 I don't think the internal schedule is writable by the ISY for any zwave thermostats, at least I've seen no evidence for this. And I've honestly never seen it mentioned for other controllers or thermostats.
Amigo Posted November 25, 2015 Posted November 25, 2015 yes, that seems to be the common consensus from the experts here. I asked Michel whether it is just lack of documentation from manufacturers or other limitations? Have not heard back. I will mess around with the few z-wave tstats that I ordered and will update everyone if I find something otherwise. cheers.
Michel Kohanim Posted November 25, 2015 Posted November 25, 2015 Hi Amigo, I have not received your email and I respond to all emails. With kind regards, Michel
Amigo Posted November 25, 2015 Posted November 25, 2015 Sorry, it was not an email, I just asked about it in a different thread. Just wanted to know what are the obstacles in supporting the internal schedules of z-wave thermostats, is it just lack of documentation from manufacturers or? For example, If I ask RCS to send you the docs (if there are any) would you be willing to implement and allow read/write from ISY? cheers.
Michel Kohanim Posted November 26, 2015 Posted November 26, 2015 Hi Amigo, With Z-Wave, the device has to support the Schedule command class. It's not a matter of docs from RCS. With kind regards, Michel
Amigo Posted November 27, 2015 Posted November 27, 2015 Ok, thanks. Will try to get in touch and see if any z-wave thermostats support that class. And just be clear, are you referring to COMMAND_CLASS_CLIMATE_CONTROL_SCHEDULE 0x46 ? cheers.
Pacificwing Posted November 27, 2015 Posted November 27, 2015 Okay, Reporting further to my post above. This thermostat has a mind of its own. It does not appear to obey its internal schedule, or when I switch it into "simple" mode, it seems to ignore the ISY intermittently. By that I mean, it works some of the time, but it will often just turn on the heat for no apparent reason. Even when above set-point. I've metered it out as well as checked the logs and confirmed it is the thermostat actually turning on the heating mode. I don't think it is a wiring issue, because it works 80% of the time just as its supposed to. Also, why doesn't the ISY support floating point numbers? I know that Z-wave reports decimal values, so why is the ISY so far behind? There is a big difference between 21C and 21.7C. The ISY doesn't even seem to round up/down properly. Also, this is a little off topic, but what are variables used for? I thought I could assign values to them (like holding a temperature set-point, or a time) but apparently I can only use them for holding a numeric value that I specifically assign. They seem more like adjustable constants than true variables. These limitations make it very difficult to set up more than the most basic thermostat program. Have I got a basic watered-down version of the firmware or something? I'm fairly certain I remember reading somewhere that the ISY had these functions. Floating-point values and context assigned variables is pretty standard stuff for automation these days.
Michel Kohanim Posted November 27, 2015 Posted November 27, 2015 Hi Pacificwing, Variable assignments are supported in 5.0.x branch which is still beta (http://forum.universal-devices.com/forum/108-50/). Will have to investigate further on why you are not getting decimal values because it's supported. With kind regards, Michel
Pacificwing Posted November 27, 2015 Posted November 27, 2015 Perhaps it is the thermostat? Anyone else not getting decimal values reported?
Amigo Posted November 28, 2015 Posted November 28, 2015 I have one of these tstats coming in a couple of weeks, I would be happy to report back my findings. On another note, been doing some research on z-wave basics, and the following couple of links helped me out quite a bit. So if another newbie like me visits this post may be helpful to them as well: list of command classes and how to read device capability: http://wiki.micasaverde.com/index.php/ZWave_Command_Classes a list of z-wave devices where you can filter by command class or frequency,language: http://www.pepper1.net/zwavedb/device?sort=name&sort_type=desc&filter_cmd_class=&filter_frequency=&filter_language=&filter_manufacturer=&filter_generic_class= cheers.
jch Posted January 4, 2016 Author Posted January 4, 2016 Amigo and I discussed this stat on the GoControl stat thread: http://forum.universal-devices.com/topic/17676-gocontrol-gc-tbz48l/?p=160257. I ordered one from Amazon and installed it yesterday. It seems to work just fine, like the GoControl. It paired with the ISY, repeated through a couple of the GoControl stats. If you take it out of Eazy mode, be sure to set it to Permanent Override or the default schedule will take effect. I think it is aesthetically better proportioned than the GoControl stats, although it looks a bit busier with the extra buttons. I'll probably buy four more of these to replace the last of my mechanical thermostats.
Pacificwing Posted January 5, 2016 Posted January 5, 2016 Amigo and I discussed this stat on the GoControl stat thread: http://forum.universal-devices.com/topic/17676-gocontrol-gc-tbz48l/?p=160257. I ordered one from Amazon and installed it yesterday. It seems to work just fine, like the GoControl. It paired with the ISY, repeated through a couple of the GoControl stats. If you take it out of Eazy mode, be sure to set it to Permanent Override or the default schedule will take effect. I think it is aesthetically better proportioned than the GoControl stats, although it looks a bit busier with the extra buttons. I'll probably buy four more of these to replace the last of my mechanical thermostats. Can you try setting it to metric and see if it reports the heating setpoint correctly? Also, keep an eye on it. Mine did strange things, such as randomly turning on the heat when I was at setpoint. It did this intermittently.
Amigo Posted January 5, 2016 Posted January 5, 2016 Good evening, I mentioned in the other thread that it does not work correctly when in Deg C mode. I actually got in touch with Remotec and they said that for their temperature and setpoint reporting they are using "we are using size 2 , precision 1, if temperature is 30, we send out value 0x012C ", in other words they send 300 which means 30.0, so one decimal place. When I look at event viewer, ISY always reports precision of zero for all the analog values out of the tstat?, so I wonder if there is a translation issue possibly in ISY. Below is part of level 3 log, and there is an example of when the thermostat heating setpoint is suppose to be 20 degC, the thermostat's LCD shows it as 20 degC but ISY reports it as -5 degC. Could someone from UDI please look at the log below, at time 06:50:35 PM and confirm that ISY is seeing the heating setpoint correctly? >>Mon 01/04/2016 06:50:34 PM : [ZWAVE-TX ZW009_1] [010C001309054301]...Mon 01/04/2016 06:50:34 PM : [ZWAVE-RX ] ACKMon 01/04/2016 06:50:34 PM : [ZWAVE-RX ] [0104011301E8]Mon 01/04/2016 06:50:34 PM : [ZWAVE-TX ] ACKMon 01/04/2016 06:50:34 PM : [ZWAVE-RX ] [010500133800D1]Mon 01/04/2016 06:50:34 PM : [ZWAVE-TX ] ACKMon 01/04/2016 06:50:34 PM : [ZWAVE-TX ZW009_1] [0109001309023104]...Mon 01/04/2016 06:50:34 PM : [ZWAVE-RX ] ACKMon 01/04/2016 06:50:34 PM : [ZWAVE-RX ] [0104011301E8]Mon 01/04/2016 06:50:34 PM : [ZWAVE-TX ] ACKMon 01/04/2016 06:50:34 PM : [ZWAVE-RX ] [010500133900D0]Mon 01/04/2016 06:50:34 PM : [ZWAVE-TX ] ACKMon 01/04/2016 06:50:34 PM : [ZWAVE-RX ZW009_1] [010C000400090631]...Mon 01/04/2016 06:50:34 PM : [ZWAVE-TX ] ACKMon 01/04/2016 06:50:34 PM : [ZWAVE-PROCESS ] Process value Sensor type=1 uomId=0 prec=2Mon 01/04/2016 06:50:34 PM : [ZWAVE-TX ZW009_1] [0109001309024002]...Mon 01/04/2016 06:50:34 PM : [ZWAVE-RX ] ACKMon 01/04/2016 06:50:34 PM : [ZWAVE-RX ] [0104011301E8]Mon 01/04/2016 06:50:34 PM : [ZWAVE-TX ] ACKMon 01/04/2016 06:50:34 PM : [ZWAVE-RX ] [010500133A00D3]Mon 01/04/2016 06:50:34 PM : [ZWAVE-TX ] ACKMon 01/04/2016 06:50:34 PM : [ZWAVE-RX ZW009_1] [0109000400090340]...Mon 01/04/2016 06:50:34 PM : [ZWAVE-TX ] ACKMon 01/04/2016 06:50:34 PM : [ZWAVE-TX ZW009_1] [0109001309024502]...Mon 01/04/2016 06:50:34 PM : [ZWAVE-RX ] ACKMon 01/04/2016 06:50:34 PM : [ZWAVE-RX ] [0104011301E8]Mon 01/04/2016 06:50:34 PM : [ZWAVE-TX ] ACKMon 01/04/2016 06:50:34 PM : [ZWAVE-RX ] [010500133B00D2]Mon 01/04/2016 06:50:34 PM : [ZWAVE-TX ] ACKMon 01/04/2016 06:50:34 PM : [ZWAVE-RX ZW009_1] [0109000400090345]...Mon 01/04/2016 06:50:34 PM : [ZWAVE-TX ] ACKMon 01/04/2016 06:50:35 PM : [ZWAVE-TX ZW009_1] [0109001309024402]...Mon 01/04/2016 06:50:35 PM : [ZWAVE-RX ] ACKMon 01/04/2016 06:50:35 PM : [ZWAVE-RX ] [0104011301E8]Mon 01/04/2016 06:50:35 PM : [ZWAVE-TX ] ACKMon 01/04/2016 06:50:35 PM : [ZWAVE-RX ] [010500133C00D5]Mon 01/04/2016 06:50:35 PM : [ZWAVE-TX ] ACKMon 01/04/2016 06:50:35 PM : [ZWAVE-RX ZW009_1] [0109000400090344]...Mon 01/04/2016 06:50:35 PM : [ZWAVE-TX ] ACKMon 01/04/2016 06:50:35 PM : [ZWAVE-TX ZW009_1] [0109001309024202]...Mon 01/04/2016 06:50:35 PM : [ZWAVE-RX ] ACKMon 01/04/2016 06:50:35 PM : [ZWAVE-RX ] [0104011301E8]Mon 01/04/2016 06:50:35 PM : [ZWAVE-TX ] ACKMon 01/04/2016 06:50:35 PM : [ZWAVE-RX ] [010500133D00D4]Mon 01/04/2016 06:50:35 PM : [ZWAVE-TX ] ACKMon 01/04/2016 06:50:35 PM : [ZWAVE-RX ZW009_1] [0109000400090342]...Mon 01/04/2016 06:50:35 PM : [ZWAVE-TX ] ACKMon 01/04/2016 06:50:35 PM : [ZWAVE-TX ZW009_1] [010A001309034302]...Mon 01/04/2016 06:50:35 PM : [ZWAVE-RX ] ACKMon 01/04/2016 06:50:35 PM : [ZWAVE-RX ] [0104011301E8]Mon 01/04/2016 06:50:35 PM : [ZWAVE-TX ] ACKMon 01/04/2016 06:50:35 PM : [ZWAVE-RX ] [010500133E00D7]Mon 01/04/2016 06:50:35 PM : [ZWAVE-TX ] ACKMon 01/04/2016 06:50:35 PM : [ZWAVE-RX ZW009_1] [010B000400090543]...Mon 01/04/2016 06:50:35 PM : [ZWAVE-TX ] ACKMon 01/04/2016 06:50:35 PM : [D2D EVENT ] Event [ZW009_1] [CLISPH] [-5] uom=4 prec=0Mon 01/04/2016 06:50:35 PM : [ ZW009_1] CLISPH -5 (uom=4 prec=0)Mon 01/04/2016 06:50:36 PM : [ZWAVE-TX ZW009_1] [010A001309034302]...Mon 01/04/2016 06:50:36 PM : [ZWAVE-RX ] ACKMon 01/04/2016 06:50:36 PM : [ZWAVE-RX ] [0104011301E8]Mon 01/04/2016 06:50:36 PM : [ZWAVE-TX ] ACKMon 01/04/2016 06:50:36 PM : [ZWAVE-RX ] [010500133F00D6]Mon 01/04/2016 06:50:36 PM : [ZWAVE-TX ] ACKMon 01/04/2016 06:50:36 PM : [ZWAVE-RX ZW009_1] [010B000400090543]...Mon 01/04/2016 06:50:36 PM : [ZWAVE-TX ] ACKMon 01/04/2016 06:50:36 PM : [D2D EVENT ] Event [ZW009_1] [CLISPC] [22] uom=4 prec=0Mon 01/04/2016 06:50:36 PM : [ ZW009_1] CLISPC 22 (uom=4 prec=0)Mon 01/04/2016 06:51:44 PM : [ZWAVE-RX ZW009_1] [010B000400090543]...Mon 01/04/2016 06:51:44 PM : [ZWAVE-TX ] ACKMon 01/04/2016 06:51:44 PM : [D2D EVENT ] Event [ZW009_1] [CLISPH] [-4] uom=4 prec=0Mon 01/04/2016 06:51:44 PM : [ ZW009_1] CLISPH -4 (uom=4 prec=0)Mon 01/04/2016 06:51:48 PM : [ZWAVE-RX ZW009_1] [010B000400090543]...Mon 01/04/2016 06:51:48 PM : [ZWAVE-TX ] ACKMon 01/04/2016 06:51:48 PM : [D2D EVENT ] Event [ZW009_1] [CLISPC] [-2] uom=4 prec=0Mon 01/04/2016 06:51:48 PM : [ ZW009_1] CLISPC -2 (uom=4 prec=0)>> cheers.
Pacificwing Posted January 5, 2016 Posted January 5, 2016 Good evening, I mentioned in the other thread that it does not work correctly when in Deg C mode. I actually got in touch with Remotec and they said that for their temperature and setpoint reporting they are using "we are using size 2 , precision 1, if temperature is 30, we send out value 0x012C ", in other words they send 300 which means 30.0, so one decimal place. When I look at event viewer, ISY always reports precision of zero for all the analog values out of the tstat?, so I wonder if there is a translation issue possibly in ISY. Below is part of level 3 log, and there is an example of when the thermostat heating setpoint is suppose to be 20 degC, the thermostat's LCD shows it as 20 degC but ISY reports it as -5 degC. Could someone from UDI please look at the log below, at time 06:50:35 PM and confirm that ISY is seeing the heating setpoint correctly? I don't think it is the ISY. The cooling setpoint, and everything else performs fine. If you convert 68F to Celsius, you get 20C. If you apply the same conversion formula again on the value of 20, you get -6.6 The thermostat is applying the conversion twice before sending it out to the ISY. At least that is what I deduced. I could be wrong.
Amigo Posted January 5, 2016 Posted January 5, 2016 Good morning, I can't say where the issue is. But I can tell you that I also see the issue in the cooling setpoint as well, but it is not in a consistent manner so I don't think it is a simple conversion issue. For example I can send 21 deg heat setpoint and 23 cool setpoint from admin console and all is well, both ISY and thermostat show and work correctly. The thermostat seems to have a setpoint push methodology inside of it to ensure there is a few degrees separation between heat setpoint and cool setpoint. For example if I adjust the heating setpoint up, like say I bump it to 25 degC then thermostat itself forces the active cool setpoint to be 27 deg C. I think the problem happens when this push action happens in the tstat, the z-wave messages received by ISY or given out by the tstat gets screwed up. If I adjust both the setpoints via admin console/z-wave with enough separation between them, then all seems to work fine. If I adjust just one setpoint at a time whether via z-wave or local LCD, if the setpoints overlap the push separation band then I see the problem we are seeing. cheers.
mauricedudeley Posted February 10, 2017 Posted February 10, 2017 I've used this product for almost a year now and I have no regrets! really it works well with smart devices I have in my home. http://www.consumeressentials.com/best-smart-thermostat/
Recommended Posts
Archived
This topic is now archived and is closed to further replies.