I’d like to do something like
"is_on(this button press event) ..."in a schedule
Ah, right. That’s not possible since an event is something that happens and is then gone, it has no state. You’ll need to create an input_boolean or something similar and then toggle it via an automation whenever the event happens.
Hi all,
I’m running Schedy from few months now and I’m still trying to add features. One that I’m missing is adding a particular preset that my climate component.
This is what I want to achieve:
If my input select change from not_home to home switch on schedules with preset “boost” for 2h. It this possible?
Thank you in advance
If my input select change from not_home to home switch on schedules with preset “boost” for 2h. It this possible?
You’ll need to create a HA sensor which is on for two hours after the state changed to “Home” and then add a schedule rule in Schedy that adds 2 to the value while that sensor is on. See the docs about Result Postprocessors and the related examples for how to do this in an elegant way.
EDIT: Or use an input_boolean instead of the sensor and switch it via an automation with delay, probably easier to accomplish.
If I have understood correctly this will add 2 degress on my normal schedule for a determined period of time.
This could be certainly a workaround. My main goal was to use valve capability to “boost” heat.
If I have understood correctly this will add 2 degress on my normal schedule for a determined period of time.
This could be certainly a workaround. My main goal was to use valve capability to “boost” heat.
Oh, somehow got that wrong. I guess the boost mode you mentioned would involve switching to another HVAC mode, right? This is something Schedy’s thermostat actor doesn’t support at all.
Well I don’t know exactly.
It’s not a pure HVAC mode.
It’s called a “preset”.
Here’s the specifics inside dev panel:
hvac_modes:
- auto
- heat
- 'off'
current_temperature: 18.5
min_temp: 4.5
max_temp: 30.5
target_temp_step: 0.5
temperature: 5
preset_mode: null
preset_modes:
- boost
battery: High
valve: 4
level: 0
mode: null
voltage: 2.8
id: 002018A99D1262
interface: ip
friendly_name: Termosifone Soggiorno
supported_features: 17
Maybe also this field is not supported right?
Have you tried just switching that preset on (however that’s done) via an automation for two hours after you get home? What does Schedy tell you when you do so?
Hi all,
Schedy 0.7.0 has just been released with no new features, but a small bugfix and improvements in logging and the docs. As announced in the previous release, the old result type Skip() is now gone in favor of its new name Next().
As always, the full patch notes can be found here.
Let me know if you’re facing any issue.
Enjoy the new release.
Best regards
Robert
I didn’t try with an automation (that’s a good tip btw).
Schedy is not aware of this preset. If I manually change it to “boost” nothing happens in logs.
Schedy is not aware of this preset. If I manually change it to “boost” nothing happens in logs.
That sounds good, then simply try out an automation.
Thank you 
Hi Robert,
Trying to get Schedy working but I’m having trouble with the instructions. I have a working AppDaemon install, but the final Schedy config is probably not right and I don’t totally understand your configuration instructions:
From the docs, with my notes in >>>:
Configuration
When you followed the above steps for installing hass-apps, you automatically installed AppDaemon as well. Configuring AppDaemon is out of the scope of this tutorial, but there is a Configuration Section in the AppDaemon Documentation which describes what to do. We assume that you’ve got a working AppDaemon 3.x for now.
Several cups of tea - didn’t help.
apps directory. This is just a stub which imports the real app’s code.Done.
I want to use Schedy.
apps directory and start editing it. Adapt the sample configuration as necessary. Documentary comments explaining what the different settings mean are included. The sample configurations can also be found in the GitHub repository under docs/apps/<app_name>/sample-apps.yaml .I created a “coffee_schedule.yaml” file with the config for it, adapted from your heating tutorial, saved in the appdaemon/apps folder.
apps.yaml and restart its apps automatically.Er…what changes to the apps.yaml file? This is the first time this file is mentioned and there are no instructions on what it should contain to run Schedy?
Are you able to help?
Thanks,
Andy.
Er…what changes to the apps.yaml file? This is the first time this file is mentioned and there are no instructions on what it should contain to run Schedy?
Oh, this is a leftover from AppDaemon 2.x where there could only be a single apps.yaml file containing definitions for all apps, it actually means the YAML file you just created. Will fix it.
EDIT: Fixed in latest docs
Ok, thanks. In that case I have done everything required and it’s not doing anything. How do I actually test that Schedy is installed and working?
How do I actually test that Schedy is installed and working?
Since you said you used the tutorial, that tells you to check AppDaemon’s logs for feedback on what’s going on…
Hi,
I like what Schedy gives but I see it lacks user interface as you would expect in XXI centaury. There is no UI but I wonder if there is a way to CRUD schedules via REST or any other way that a custom web page can edit schedules file that is integrated within HA ?
Fair enough. I can’t seem to get it to generate a log for some reason, even though I’ve added the log settings in the config file. However, after clearing out the unnecessary config files, it appears my schedule is now working. Very nice. I also have the schedule state changes being announced by Alexa.
Fair enough. I can’t seem to get it to generate a log for some reason, even though I’ve added the log settings in the config file.
Hmm, in the simplest case, it logs to stdout (or stderr, I don’t know for sure). Without a working logging it’s almost impossible to debug things, so better get this to work for the future.
However, after clearing out the unnecessary config files, it appears my schedule is now working. Very nice. I also have the schedule state changes being announced by Alexa.
Interesting! How exactly did you implement the notifications?
I like what Schedy gives but I see it lacks user interface as you would expect in XXI centaury. There is no UI but I wonder if there is a way to CRUD schedules via REST or any other way that a custom web page can edit schedules file that is integrated within HA ?
Simple answer: No.
I don’t like GUIs very much and since I started writing Schedy primarily for myself, there is no GUI.
However, you can let your schedules depend on arbitrary entities in Home Assistant, such as sensors, input_booleans or input_selects and make them very dynamic that way. The docs are full of examples and this thread gives lots of them as well.
I added Alexia Media Player as a custom component using HACS. This integrates the media player functions which also includes a TTS capability. Then it’s a case of using automations to detect the state changes and call alexa’s notification service using a TTS command. The automation is triggered by the input select states. You can also have a simple on/off automated notification associated with the actor to announce the start and end of each schedule if you like.