1) I don’t recommend to get rid of any of your ecobee schedules. In many posts I’ve done in the past, I reiterated that ST users should not get rid of their ecobee schedules as ecobee scheduling is more reliable than ST scheduling (at the moment). For more details about the ST scheduling issues, see this thread:
2) The MonitorAndSetEcobeeTemp smartapp relies on ecobee scheduling for its processing. It combines ecobeeChangeMode and ecobeeResumeProg in one smartapp with some added features : it also monitors the outdoor temperature (you need to input your weather station or outdoor temp sensor) and adjusts your heating/cooling setpoints based on some thresholds that you provide (more/less heat, more/less cool based on some outdoor temp settings).
3) Based on the use case that you provided in your post, you may want to look into ecobeeSetZoneWithSchedule instead of MonitorAndSetEcobeeTemp. This smartapp is a bit more complex to set up, but it does everything MonitorAndSetEcobeeTemp does plus it gives you a room by room configuration through the definition of zones.
The zone settings can be “virtual” or “physical” as smart vents are coming to the market to control the airflow and create physical zones inside your home (ex. at nights, the ‘upstairs’ zone set for my house will ensure that only the bedrooms will be cooled or heated to avoid energy costs).
FYI, I’m currently testing ecobeeSetZoneWithSchedule with a smart vent manufacturer and it really provides some added value in terms of comfort and energy savings. The smart vents’ level settings (% open or close) is then reevaluated every 5 minutes according to the desired heating/cooling setpoints and the current temperature inside the zone(s) scheduled at a given time.
For more details about ecobeeSetZoneWithSchedule and ScheduleTstatZones, pleaser refer to this thread:
4) To update MyEcobee device type, you usually just need to copy and paste the code within the IDE and publish it (unless specified otherwise, that should be sufficient).
The same thing for MyEcobeeInit smartapp or any other smartapps.
If you update MyEcobee device, please make sure to have the latest version of MyEcobeeInit as the 2 work together for better exception handling.
5) I’m glad that you have less exceptions and errors in the past weeks….
I’ve noticed that same behavior at my home since the last ST platform update.
Cross your fingers, we may enjoy the platform stability that we had before all the platforms changes introduced for Hub V2
Before those platform changes, MyEcobee Device would run for months without any intervention.
Regards.
P.S. I don’t quite understand your following statements below. If the 2 smartapps are configured correctly based on your ST hello modes, they should be quite effficient to set the right ecobee climate/program and they should not conflict with your sleep schedule. You would then need to create several ecobeeChangeMode instances for each ST hello mode used as input.
Depending on your use case and lifestyle, you may also want to set your holdType input parameter to indefinite instead of nextTransition for the described scenario as the away ‘hold’ will then last as long as required till you come back to the house. If you are really a doctor then your schedule may be quite different from mine as I usually work 9-5.