Currently, I have five Trane Thermostats connected to my Vera2.
Scenario 1: Each thermostat is controlled by various Z-Wave scenes set by time of day.
Examples -
3PM: Thermostat A set to 68 degrees.
11PM: Thermostat A set to 62 degrees. etc.
Scenario 2: Each thermostat is programmed independent of Z-Wave (i.e. set times and temps on the thermostat itself, like a free-standing thermostat).
Now let’s assume that I have activated a scene that puts all thermostats into Energy Saver mode, lowering the heat temp to 58 degrees.
My question: will the thermostats stay in Energy Saver mode under both scenarios? My assumption is that Scenario 2 will indeed stay in ES mode until I tell it otherwise, but I’m less clear about Scenario 1. I am guessing that the scenes (such as 11PM above) will change the settings and it will forget all about ES mode.
@tripletdat,
It will stay in ESM in both scenarios. However, being in ESM suspends the internal schedule, so in scenario 2 it will stay at the pre-set ESM setpoint (as you said). In scenario 1 you’re overriding the setpoint while in ESM; equivalent to making a local setpoint change on the t-stat while in ESM.
I think with a little code you can check the mode of the t-stat and abort the scene when in ESM. (I’d have to test that tonight, before posting it here.)
[quote=“oTi@, post:2, topic:168340”]@tripletdat,
It will stay in ESM in both scenarios. However, being in ESM suspends the internal schedule, so in scenario 2 it will stay at the pre-set ESM setpoint (as you said). In scenario 1 you’re overriding the setpoint while in ESM; equivalent to making a local setpoint change on the t-stat while in ESM.[/quote]
Thanks oTi. I’m not sure I understand your point about scenario 1, however. If a scene puts the thermostat to 68 at 7AM and another scene puts it to 62 at 9AM, what will happen if my “AWAY” scene puts it into ESM at 8AM?
7 AM: Run/Hold mode, setpoint: 68 (i.e. Run or Hold determined by what you set it to on the t-stat. Assume Run)
8 AM: ES mode, setpoint: 58 (i.e. whatever preset is configured on the t-stat.)
9 AM: ES mode, setpoint: 62
I remember when I first set this T-stat up with the built in schedules, when I added it to the Schlage bridge I had to choose which to use, the built in schedule or Z-wave, could not use both. Choosing the built in, nothing displayed on the bridge. Choosing Z-Wave and the schedules were removed from the T-stat.
Question, Do your T-stat schedules run independently while it’s connected to a Z-Wave network?
If you have timed events to interact with the T-stat that fire after you’ve put it into Energy Save mode then the T-Stat will follow the scene and adjust to the new setting.
[quote=“oTi@, post:4, topic:168340”]7 AM: Run/Hold mode, setpoint: 68 (i.e. Run or Hold determined by what you set it to on the t-stat. Assume Run)
8 AM: ES mode, setpoint: 58 (i.e. whatever preset is configured on the t-stat.)
9 AM: ES mode, setpoint: 62[/quote]
So it sounds like the 9AM scene will override the temperature of ESM, sort of negating the whole idea of ESM…
If so, I will probably just program each tstat internally and execute ESM remotely.
@JOD,
The Trane will run from internal schedule whilst included in a Z-Wave network. On the CT-30’s (e.g.) it’s one or the other.[/quote]
I didn’t know that. Seems like such a headache to be using both…
Now all I need is some way to be able to push a button when I leave the house to set it to “away” and a scene to prep the house for me coming home. Too bad this came up when the heating season is no longer in full swing.
[quote=“oTi@, post:9, topic:168340”]
return (luup.variable_get("urn:upnp-org:serviceId:SwitchPower1","Status",<devID>) == "1")
The scene will not run (i.e. the commands won’t be executed) if the t-stat is in ESM.[/quote]
Sorry to ask such a stupid newbie question, but I’ve got 2 thermostats and I only want to keep one event chronology for the pair of them. Can I and the function somehow?
return (luup.variable_get("urn:upnp-org:serviceId:SwitchPower1","Status",<devID1>) and luup.variable_get("urn:upnp-org:serviceId:SwitchPower1","Status",<devID2>) == "1")
That way if both thermostats are in ESM then my morning event that sets temp on both does nothing, but if they are not in ESM the event runs, or if the status is inconsistent (one thermostat is in ESM and the other is not) the event will run.
OK…making progress! I put the LUUP code into each of the tstat scenes, and then created an “AWAY” scene that turned off all the lights and put all tstats into ESM.
When I tested the “AWAY” scene, all the lights went out as expected, but the tstats all show “Waiting for node to reply after 0”.
What does this mean, and do I need to make any changes?
Well, I don’t know what the problem was yesterday. I tried again today and I believe that it is working successfully now.
My “AWAY” scene does two things: it changes the tstats to ESM, and it turns off all the lights. I would like to assign the AWAY scene to an “ON” button on my GE 45631 Z-Wave Wireless Keypad Controller.
When I click the ON button, it should initiate the AWAY scene. My question: will I need to also create a “BACK HOME” scene, and assign it to the “OFF” side of the button? Or will the controller automatically “reverse” the AWAY scene somehow when I click the OFF button (similar to how it turns off lights that were previously turned on with a scene).
Never mind. I realize now that the “ON” and “OFF” are individually programable – I assigned one to my “AWAY” scene, and one to my “HOME” scene. I’ll test it tonight…
[quote=“oTi@, post:9, topic:168340”]Nah. ;D Consider adding this to the Luup tab of the scene that changes the setpoint (change to the Device# of the t-stat):
The scene will not run (i.e. the commands won’t be executed) if the t-stat is in ESM.[/quote]
I’ve got two CA8900 thermostats in the same scenario. They respond correctly to timers for setpoints (cool to 74 at 4PM, then raise cool setpoint to 82 at 6AM when I’m getting ready to leave). I’m trying to create an “AWAY” scene that sets the thermostats to Energy Save mode and overrides these daily setpoints. I tested the code above in MiOS Developers–>Test Luup code (Lua) and it fails every time! Here are some screen shots (testing on t-stat device ID 3):
Assuming the ESM on the CA8900 is controlled through the on/off state (like it is for the Trane), try the following, and leave the “[tt]Device number*[/tt]” field blank:
[quote=“oTi@, post:16, topic:168340”]Assuming the ESM on the CA8900 is controlled through the on/off state (like it is for the Trane), try the following, and leave the “[tt]Device number*[/tt]” field blank:
You will get “[tt]Message sent successful.[/tt]” if the tstat is in normal mode.
You will get “[tt]Code failed[/tt]” if the tstat is in ESM mode.
If that works, you could add the code to a scene and test that.[/quote]
That works! Excellent. I’ll add it to each scene. I assume for both thermostats (device ID’s 3 and 5) I’ll need some ‘or’ logic, such as:
return (luup.variable_get("urn:upnp-org:serviceId:SwitchPower1","Status",3) == "1") or return (luup.variable_get("urn:upnp-org:serviceId:SwitchPower1","Status",5) == "1")
I have posted before and received the advice to use the lump codes to control the Normal and ESM modes via scenes and a virtual switch.
It seems on my last trip away from the house, the initial indications were that the thermostats were all set correctly in ESM, but the next day i noticed through the remote MIOS, the thermostats were back to the internal settings and running the normal schedules. It appears the internal thermostat settings over rode the ESM.
Do we need to use any lump codes to set the Thermostats to ESM? I have an event set up in the Scene’s to run when the virtual switch is activated.
Sounds like the thermostats were set back to Run mode. What was the state of the virtual switch that next day? (Assuming this is a Home/Away virtual switch, and setting it to Home would put the thermostats back in Run mode.)
i don’t think the virtual switch was changed back. I have removed all the lump codes and just use the virtual switch as the event trigger for the scene. Will this work?
