Vera - Smarter Home Control Forum

General => Temperature Monitoring & HVAC Control => Topic started by: wilme2 on January 11, 2018, 05:50:19 pm

Title: Honeywell YTH8320ZW - ModeStatus when HeatOn and EngerySavingsMode
Post by: wilme2 on January 11, 2018, 05:50:19 pm
In UI5, the Honeywell YTH8320ZW - ModeStatus was what the documentation said it was supposed to be - a single variable to indicate whether the thermostat was set to Heat, Cool, Auto, or Off.  There was a separate variable for EnergyModeStatus.

http://wiki.micasaverde.com/index.php/Luup_UPnP_Variables_and_Actions#HVAC_UserOperatingMode1 (http://wiki.micasaverde.com/index.php/Luup_UPnP_Variables_and_Actions#HVAC_UserOperatingMode1)
http://wiki.micasaverde.com/index.php/Luup_Devices#urn:upnp-org:serviceId:HVAC_UserOperatingMode1_--_ModeStatus (http://wiki.micasaverde.com/index.php/Luup_Devices#urn:upnp-org:serviceId:HVAC_UserOperatingMode1_--_ModeStatus)

Unforunately in UI7, if while in Heat you also set to Energy Saving, the ModeStatus returns "EconomyHeatOn" instead of "HeatOn"  The funny thing is if you do this in the GUI - set to Heat first, then Energy, the GUI then stops showing the thermostat in Heat  - no mode is selected since the ModeStatus isn't one of the items in the GUI.

Has anyone found a way around this?  I need the ModeStatus variable without the "Economy" so I can keep thermostats on a zoned system in sync.  I need to make sure one can't be set to Heat while the other is set to Cool.   One might legitimately be in Energy while the other one isn't, so I don't want to effectively sync both ModeStatus and EnergyModeStatus when I should not have to do so.

Here is my UI5 PLEG logic:  http://forum.micasaverde.com/index.php/topic,30792.msg221170.html#msg221170 (http://forum.micasaverde.com/index.php/topic,30792.msg221170.html#msg221170)
Title: Re: Honeywell YTH8320ZW - ModeStatus when HeatOn and EngerySavingsMode
Post by: wilme2 on January 26, 2018, 11:49:19 am
I attempted to eliminate the EconomyHeatOn option from the S_HVAC_UserOperatingMode1.xml file, but no impact...
Title: Re: Honeywell YTH8320ZW - ModeStatus when HeatOn and EngerySavingsMode
Post by: wilme2 on February 08, 2018, 10:47:52 am
Vera support tells me to just deal with it...

Very frustrating we don't have more control over the function of devices like this...
Title: Re: Honeywell YTH8320ZW - ModeStatus when HeatOn and EngerySavingsMode
Post by: rigpapa on February 08, 2018, 02:37:45 pm
Can you not just add another set of conditions in PLEG to distinguish between the modes and set the correct available mode whether the Honeywell says HeatOn or EconomyHeatOn? This makes for a few more conditions, but I think it's well within PLEG's capability to do this. Perhaps @RichardTSchaefer or another lurking PLEGspertTM could chime in on specific syntax.
Title: Re: Honeywell YTH8320ZW - ModeStatus when HeatOn and EngerySavingsMode
Post by: wilme2 on February 09, 2018, 11:00:23 am
Can you not just add another set of conditions in PLEG to distinguish between the modes and set the correct available mode whether the Honeywell says HeatOn or EconomyHeatOn? This makes for a few more conditions, but I think it's well within PLEG's capability to do this. Perhaps @RichardTSchaefer or another lurking PLEGspertTM could chime in on specific syntax.

Yeah...  I just hate how Vera can't do the same thing the same way twice, ever.

I will post my PLEG logic here when finished in case it saves time for someone else...
Title: Re: Honeywell YTH8320ZW - ModeStatus when HeatOn and EngerySavingsMode
Post by: rigpapa on February 09, 2018, 12:46:30 pm
Thermostats in particular are a bit of nightmare (I maintain two thermostat plugins, so I have lots of desk-shaped flat spots on my forehead). UPnP has one set of ideas about how they should work, which Vera loosely follows, but the implementation specifics vary widely as Vera's own interpretation vs that of the many plugins shows. The UI7 interface code itself is littered with exceptions and inconsistent tests for device types and capabilities. It looks like a series of kludges to get specific things working, and no apparent effort to step back and look at the 50,000ft view and refactor. I hope they straighten it out in UI8.
Title: Re: Honeywell YTH8320ZW - ModeStatus when HeatOn and EngerySavingsMode
Post by: wilme2 on March 08, 2018, 02:32:42 pm
Can you not just add another set of conditions in PLEG to distinguish between the modes and set the correct available mode whether the Honeywell says HeatOn or EconomyHeatOn? This makes for a few more conditions, but I think it's well within PLEG's capability to do this. Perhaps @RichardTSchaefer or another lurking PLEGspertTM could chime in on specific syntax.

So I finally wrote the PLEG yesterday that allows me to keep the Thermostats synced, essentially ignoring "EconomyHeatOn".  I turned to PLEG Basics for inspiration, and realized I could use the if-then-else functionality.  So in ModeStatus as SecondFloorModeStatusRaw, then update to a clean SecondFloorModeStatus via the condition:

      (SecondFloorModeStatusRaw eq "EconomyHeatOn") ? "HeatOn" : SecondFloorModeStatusRaw