@ReneTode read what I wrote. I too have respect to his work. Thi smeans I can´t say any critics? Great 
This is the reason why some thing never become popular. Tesla was the greatest genius (in my opinion) but died poor and alone. Edison is famous and died very rich. Only because people better understood to his thoughts… (just better PR)
there is a difference between say some critics and stating that something is bad and useless (which is what you did)
i did, that why i say that you shouldnt write it but show it.
i said what i had to say so i leave it by that and i wont disturb this topic any more then this.
OK so here is a criticism. As we can read Schedy is “next level” of HA automation. Sorry it is not. If it would be some GUI based tool which is able to talk to HA entities then OK. But now it is much more complicated thing without added value. You can use MQTT GUI based dashboard and tools to create schedules and you will reach the same functions but in much easy way.
Sorry if you think I´m an idiot. Maybe I´m but HA is not created for profi programmers. It is (and HASS.IO popularity is the proof) for people somewhere in the middle between an APE and SKILLED PROGRAMMER. This is me.
This project is on opposite way. Complicated tools for complicated results. Something like “framework” better than “usable tool”.
I will also stop talking about it even this topic name sound very poetic.
@ReneTode Thanks for pointing that out. My thoughts tend to be quite similar…
@Jiran There are reasons why I don’t give you complete configurations:
Users are supposed to work through the documentation and then be able to express their own needs in own schedules, like saying something in your own words instead of just repeating what you once heard without understanding it fully.
You claim that there are other tools available to achieve the same that Schedy does, just much simpler. Then well, go and use them. Even though I don’t believe there’s anything giving you the same flexibility with less effort. You’re instead just not seeming to want to understand what Schedy does. BTW, it’s not “the next level of automation” - never said that. It’s a really convenient way to do scheduling, both in a simple and an advanced way. And my goal isn’t to reinvent automations.
So to conclude this. I develop this software this way because I need it to work this way and find it quite useful. I don’t really mind whether you find it useful as well. If you want me to develop something you see lots of value in, then pay me for it.
Cheers, and enjoy that beautiful winter day.
P.S.: It’s nice and warm in here, thanks to Schedy.
Hmm, seems like @baz123 wrote almost the same like me…
You are a developer. You made your work public.
Here is a word of public (mine).
“After I installed and used HAdashboard, created own RFgpio to mqtt script, now playing with Lovelace - I´m unable to use your product.”
Take from it what you want.
@baz123 is using Schedy with success, if I’m right.
@Jiran And that’s the difference: Schedy is no product. I’m not selling it nor do I sell the promise that everybody is able to use it.
And, to be fair, most of that discussion here took place before Schedy was released as stable and there was some confusion about the version of documentation to use. That has been sorted out now as it’s now officially released.
You forgot that “copying” is one of the best way of learning. Children does it. All creatures in nature does it.
Maybe medicine doctors (volunteer, non paid) could give scalpel to their patient hands and say “try it” and after ask me what was wrong 
Oh dear, we won’t make any new progress I fear. Either copy the numerous examples provided in the docs and learn from them, or go and use one of these graphical tools you mentioned. Should be sufficient for turning your light off after all and you’ll probably be happier in the short-run.
This is it 
lol, try to get that working with you beloved hassio!
I use hassbian 
For what it’s worth: yeah, super nice for what it’s built for, but nowhere near Schedy’s capabilities. And a nightmare to maintain, keep secure and compatible with Google’s APIs… even seems to pull in mosquitto at it’s own.
As I said, go and use it. You’ll probably be happy in the short-run and as long as you don’t feel like having smarter scheduling, you don’t want more than this.
Good luck.
Hello,
I got some error messages in the log like
Thermostat doesn't seem to support the operation mode heat, supported modes are: ['auto', 'boost', 'manual', 'lowering', 'comfort']. Please check your config!
Is it possible to “deactivate” not supported operation modes?
@dnuc Well, that thermostat doesn’t seem to have an operation mode for turning it off. You should rather disable operation mode support for the actor completely. Have a look at the actor documentation for this, especially for supports_opmodes.
@roschi do you notice when you get PM?
or is there another way i can contact you outside this (none shedy related)
@ReneTode Sure, either by PM or mail (see the git commit history or here: https://pypi.org/project/hass_apps/) and click on the author name.
i did send you a PM here 2 days ago.
Ok, responded
Hi,
I coulnd’t figure that out 100% from the documentation. I need a configuration where I have a normal schedule set and, depending on the state of a switch, another schedule is used. My scenario is having a weekly schedule depending on default home/absence times. Wit a swicht “Vacation” I override the schedule and use another schedule as long as the switch is active. My approach would be the same as in the example with the bath-switch. My question is: Does this system also support sub-schedules? Like that:
schedule:
- x: 21 if is_on("switch.vacation") else Skip()
rules:
- { start: "05:00", end: "08:00" }
- x: 19 if is_on("switch.vacation") else Skip()
rules:
- { start: "08:00", end: "22:00" }
- x: 17.5 if is_on("switch.vacation") else Skip()
- v: 21
rules:
- { start: "04:30", end: "07:00", weekdays: "1-2" }
- { start: "05:00", end: "07:00", weekdays: "3-5" }
- { start: "05:00", end: "08:00", weekdays: "6-7" }
- { v: 18, start: "07:00", end: "22:00", weekdays: "1-5" }
- { v: 19, start: "08:00", end: "22:00", weekdays: "6-7" }
- { v: 17.5 }
Would something like that work? Can it even be combined in a one-liner?
Of course combined with the re-scheduling automation…