Yes, that’s possible: https://hass-apps.readthedocs.io/en/stable/apps/schedy/events.html
Hi all,
Is there anybody wanting to try out the new tutorial?
https://hass-apps.readthedocs.io/en/latest/apps/schedy/tutorial.html
It only works with the development version at the moment (that from master branch), because it relies on a feature which isn’t present in stable yet.
Any feedback from a users perspective is very welcome! Especially for those completely new to Schedy (@thundergreen) the tutorial should be helpful.
Thanks for testing!
Best regards
Robert
I will test it and report… thanks so far! I’ll update to master and try it 
Could you just add on example for Only run schedule if ttemp is either below x or above x
another question is why shedy does not support cooling mode out of the box. i archieve that by changing operation mode to cool and it works ike a charm so far
I am getting errors recently when i have end_plus_days
This line
- { v: “on” , weekdays: “5”, start: “00:30”, end: “15:00” , end_plus_days: 1}
Configuration error: correct format: [HH:MM[:SS]][{±}?d] for dictionary value @ data[‘rooms’][‘Kitchen1’][‘schedule’][1][‘end’]. Got ‘15:00’
I am using development version
This line
@yabuts Hm, that’s weird. I’ll investigate tomorrow. For now, you can switch to the new format for time specifiers and use 15:00+1d for end and omit end_plus_days.
Fixed, the old format works again.
Hi all,
Some of you may already have noticed that Heaty and Schedy stopped working after the upgrade to Home Assistant 0.96. This is due to changes in the climate API. Read the blog post for more information.
The good news is that a new Schedy release is on its way and will probably arrive tonight or tomorrow. You’ll need to make some changes to your Schedy configuration, which will become simpler, and that’s it.
And no, Heaty won’t receive these changes. Please consider it EOL by now and take the chance to switch over to Schedy.
Best regards
Robert
3 Likes
Ok, hass-apps v0.20190720.0 is out. See the docs and contained Changelog for a full list of what has changed. To put it first, Heaty has finally been removed. It wouldn’t make sense to release something that doesn’t work correctly again and again. Those that really want to stick with it simply can’t use Home Assistant 0.96 and the new hass-apps.
As always, feedback is welcome.
Good bloddy job its summer and its broken :). Been putting off updating to Schedy as it was winter and could not live with WAF going down due to no heating
Any tips on migrating to Schedy from Heaty?
I have a very simple config
heaty_minimal:
module: hass_apps_loader
class: HeatyApp
rooms:
lounge:
thermostats:
climate.lounge_heater:
schedule:
# Weekdays
- { temp: 20, start: "16:00", end: "21:00", weekdays: 1-5 }
# Weekends
- { temp: 20, start: "08:30", end: "21:00", weekdays: 6-7 }
# At all other times
- { temp: 17 }
birds:
thermostats:
climate.birds_heater:
schedule:
# Weekdays
- { temp: 20, start: "16:00", end: "21:00", weekdays: 1-5 }
# Weekends
- { temp: 20, start: "08:30", end: "21:00", weekdays: 6-7 }
# At all other times
- { temp: 17 }
studyfront:
thermostats:
climate.study_front_heater:
schedule:
# Weekdays
- { temp: 20, start: "04:00", end: "06:30", weekdays: 1-5 }
- { temp: 20, start: "08:30", end: "16:30", weekdays: 1-5 }
# At all other times
- { temp: 17 }
studyside:
thermostats:
climate.study_side_heater:
schedule:
# Weekdays
- { temp: 20, start: "04:00", end: "06:30", weekdays: 1-5 }
- { temp: 20, start: "08:30", end: "16:30", weekdays: 1-5 }
# At all other times
- { temp: 17 }
kitchen:
thermostats:
climate.kitchen_heater:
schedule:
# At all other times
- { temp: 17 }
entrance:
thermostats:
climate.entrance_heater:
schedule:
# At all other times
- { temp: 17 }
gym:
thermostats:
climate.gym_heater:
schedule:
# At all other times
- { temp: 17 }
masterbedroom:
thermostats:
climate.master_bedroom_heater:
schedule:
# Everyday
- { temp: 17, start: "04:00", end: "07:00", weekdays: 1-5 }
- { temp: 19, start: "20:30", end: "21:30", weekdays: 1-7 }
# At all other times
- { temp: 17 }
guestbedroom:
thermostats:
climate.guest_bedroom_heater:
schedule:
# Everyday
#- { temp: 17, start: "04:00", end: "07:00", weekdays: 1-5 }
#- { temp: 19, start: "20:30", end: "21:30", weekdays: 1-7 }
# At all other times
- { temp: 17 }
gdpbedroom:
thermostats:
climate.gdp_bedroom_heater:
schedule:
# Everyday
- { temp: 17, start: "04:00", end: "07:00", weekdays: 1-5 }
- { temp: 19, start: "20:30", end: "21:30", weekdays: 1-7 }
# At all other times
- { temp: 17 }
bspbedroom:
thermostats:
climate.bsp_bedroom_heater:
schedule:
# Everyday
- { temp: 17, start: "04:00", end: "07:00", weekdays: 1-5 }
- { temp: 19, start: "20:30", end: "21:30", weekdays: 1-7 }
# At all other times
- { temp: 17 }
masterbathroom:
thermostats:
climate.master_bathroom_heater:
schedule:
# At all other times
- { temp: 17 }
guestbathroom:
thermostats:
climate.guest_bathroom_heater:
schedule:
# At all other times
- { temp: 17 }
Good bloddy job its summer and its broken :). Been putting off updating to Schedy as it was winter and could not live with WAF going down due to no heating
Oh yeah, I know 
Any tips on migrating to Schedy from Heaty?
Not really. There isn’t much to do in your case, your best bet would be to have a look at the new tutorial, which may give you some additional inspiration, and then just check unclear points with the docs directly.
Hi @roschi
After long months I was finally forced to move to Schedy with my monster config by the HA 0.96
And I have to say big thanks again. It is working great. The Mark.OVERLAY and rescheduling_delay features saved me tons of automations and artifical sensors in HA 
So please don’t think that below hints are changing anything from above 
-
I found a small bug in documentation. In the Tutorial describing Windows Sensors there is missing
else Skip()at the end of line.In Tips & Tricks section it is correct. -
The only real issue I just found is combination of OVERLAY and rescheduling delay.
If I set manully temperature at thermostat (OVERLAY applies) and then open a window it correctly goes OFF.
a) Then if I close the window inside the resheduling interval it returns fine to the manual value and once rescheduling expires it continues according to schedule. This is correct behavior and absolutely excelent feature.
b) Problem occurs once I open the window for longer time and miss the rescheduling expiration. Then after closure the value is returned to the manual one instead of scheduled one. And durign each evaluation of the schedule it is untouched. In logs it is possible to see conflict (16 vs. 17) but considered as OK.
2019-08-05 14:15:01.356021 INFO schedy_heating: --- [R:bedroom] Final result: 16.0��
2019-08-05 14:15:01.359806 INFO schedy_heating: --- [R:bedroom] Result didn't change, not setting it again.
2019-08-05 14:15:01.362291 INFO schedy_heating: --- [R:bedroom] Unchanged HA state: state='17.0', attributes={'actor_wanted_values': {'climate.eurotronic_eur_spiritz_wall_radiator_thermostat_heat': '17.0'}, 'scheduled_value': '16.0', 'rescheduling_time': None}
TriStone
1 Like
Hi @TriStone
Thanks for the appreciation. It’s great for someone who develops software to see people liking it and the software making lifes easier.
I’ll look into the issue you described, but probably not within the very next weeks due to being quite busy. It would help if you file this problem description as an issue on GitHub.
Thanks. But no hurry, heating season is far ahead
I will add to GitHub.
Yes, there’ll probably be some spare time in September. Docs issue is fixed already.
I don’t know if I have to open a new topic: my problem is, that I can’t get Schedy to initialize.
Here is the related log:
2019-08-11 21:12:43.343344 INFO AppDaemon: Reading config
2019-08-11 21:12:43.373947 INFO AppDaemon: /config/appdaemon/apps/schedy_heating.yaml added or modified
2019-08-11 21:12:43.374509 INFO AppDaemon: App 'schedy_heating' changed
2019-08-11 21:12:43.375367 INFO AppDaemon: Terminating schedy_heating
2019-08-11 21:12:43.376228 INFO AppDaemon: Initializing app schedy_heating using class SchedyApp from module hass_apps_loader
2019-08-11 21:12:43.376739 WARNING AppDaemon: Unable to find module module hass_apps_loader - schedy_heating is not initialized
Can somebody help me please?
Just coming into the Schedy world. Incredibly well architected. Can’t wait to sink my teeth in. Thank you for your time and effort!
1 Like
hello, I’m really inexperienced, I tried schedy by activating a thermostat and I succeeded thanks to the documentation with examples to adapt it in a simple way to what I wanted.
at this point I’m trying to activate a schedule with a switch actor, I should activate a pump for 1 minute every hour, seven days a week, but I can’t, someone who is an expert can give me an example so that he can study us up. thanks
translated with Google
Hi Gionnie
For this regular usecase I would use a normal automation which triggers each hour switches on the pump and after a delay of 1 minute switches it off again.
Schedy is more suited for irregular schedules like 1minute on between 00:00 and 04:00, 5 minutes on between 04:00 and 09:00 rest of the day off.