Did you know that you can enjoy many members-only features simply by quickly registering (no CAPTCHA!)?
Registering gives you access to our giveaways, forum features, increased search performance, access to our Download Library, create your own blog & gallery, and more!
Once you have registered, stop by in 'Hello World', and introduce yourself.
RCS TR60 thermostat question
Posted 06 July 2012 - 02:06 PM
Posted 06 July 2012 - 04:50 PM
Posted 07 July 2012 - 10:52 AM
thank you, i guess all thermostat programming would have to ve done locally at the unit
You won't be able to use that... that'd only be if you didn't have the unit connected to your Elk. The IP Address field is likely for cases where you have a Serial to IP converter.
Posted 07 July 2012 - 03:17 PM
I forget people still program their thermostats - I have never programmed one myself in my life - I used to keep the house a permanent 73, but now as power has gotten more expensive, I let the Elk handle the setbacks based on more factors than just time of day.
Posted 07 July 2012 - 07:06 PM
Update, was able to get rules to work, turns out "sent to controls" button in ElkRP doesn't do anything, had to send rules via menu on top. Is there a way to set it to away mode?
Edited by reko19, 07 July 2012 - 09:26 PM.
Posted 08 July 2012 - 03:53 AM
3. RCS Thermostat Mode: Added the ability to send virtually any RCS thermostat command. This is done by creating a M1 text string. The string must start with character ">" followed by the RCS command protocol. Example, to lock the thermostat's display, the text string would be: >A=255,O=00,DL=1^M
Then write a M1 Rule to transmit the text string out the M1XSP’s serial port.
You can find the RCS protocol at http://www.rcstechno...50-00225-43.pdf
In it, if you look at 2.49, you'll find the command to change the setback mode. I've never personally tried this, but it looks like sending:
should activate away mode on all thermostats, and
should turn the system back to normal.
I've considered doing this in the past, but never actually done it. If you try this, please share back your results.
Posted 08 July 2012 - 09:49 AM
Posted 08 July 2012 - 10:16 AM
Edited by reko19, 08 July 2012 - 10:28 AM.
Posted 08 July 2012 - 12:26 PM
To send commands, you have to build the text strings, then select the one to send. Here is an example - I have the following 3 texts set up:
This exact string is used to display the outside temperature on the display - this is from custom setting 1, hence the CS1
>A=255,OT=% CS1 %^M
This one sends a message to the thermostat in the generic messages - I would never actually read the messages, but it's useful because it causes a red light to flash on the display units. Normally I'd use an annoucement, but lately it's not cooling down under 70 degrees until the middle of the night - but we have a newborn baby in the house, so my wife is up every couple hours anyways - when she wakes up and sees the light flashing, she opens a few windows and kicks the whole house fan on
>A=255,TM="Use the House Fan!"^M
And this one clears all the messages, which in turn makes the light stop flashing:
To send these to the thermostat, build up your rules so that WHENEVER action THEN SEND THE FOLLOWING TEXT: [Select a pre-built text string here] THROUGH PORT 1 (whichever XSP your thermostat is connected to).
I'm using an RCS Zone Controller, so I have multiple addresses I can choose from, but so far these actions are global. When I'm doing temperature setbacks, I just have the Elk do them via the simple rules interface.
In looking at this, it looks like it'd be a cool function, but a PITA to set up and maintain - I'd be really tempted to stick my preferred values for each condition into some custom settings, then use Elk rules to completely manage the thermostats - then it's a matter of simple rules via the M1.
That said, try experimenting with these values; your string would be something like >A=1, SB=2^M
Posted 09 July 2012 - 01:41 PM
Posted 11 July 2012 - 04:42 PM
I can also change the setpoints for all the different possible alarm modes via my CQC interface which makes it very easy to tweak the set points based on the season and or personal comfort, although the reality is that this never really needs to be changed.
The hold method really a poor way of accomplishing this IMHO as the desired temp will probably change depending on if you are heating or cooling (ie you might want to set the cool set point to 78 degrees, but would not want to keep the house that hot when heating in the winter, etc, etc, etc). With your current method, you are going to have to keep changing the hold temp based on time of year.
Edited by sic0048, 11 July 2012 - 04:46 PM.
Posted 12 July 2012 - 12:18 AM
In general I think it's sort of a poor way of handling it - you should go all thermostat or all automation programming, not so much of the half and half... if you want to keep your rules clean, the original idea of setting vacation and home via the text string is a good way to go; otherwise if you want total control and a much more intelligent rules-based way of automating the temperature, then put it into your home controller.
It would be nice to see a "best" way of automating your thermostats... someone posted their example a while back here and at first I didn't understand the point - but now I do after going through some season changes. The goal is to eventually get it where you're never messing with the thermostats. I'm not positive I'll ever get there though, because I have a constant internal struggle between being comfortable and getting electric bills that are reasonable, so some days I'll deal with it being a bit hotter than others... and some days I'll use the whole house fan, until my allergies just need a break.
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users