Ok, do you recognize it yourself? 
Yes. I set three statistics and all three show in the default home view.
Hmmm, not sure actually what you mean 
That you can’t tell because I have manually changed it in between?
No.
2018-12-14 15:13:25.009964 INFO schedy_heating: --- [R:kid] ������ <<Schedule 'kid'>/1:<Rule x='Abort() if is_off("input_boolean.schedy"'...>>
2018-12-14 15:13:25.011931 INFO schedy_heating: --- [R:kid] ������ => Abort()
2018-12-14 15:13:25.013977 INFO schedy_heating: --- [R:kid] Found no result.
2018-12-14 15:13:25.014884 INFO schedy_heating: --- [R:kid] No suitable value found in schedule.
Congratulations, you successfully implemented the schedule killswitch!
1 Like
So I think that’s a bug right? 4 other rooms use exactly the same schedule expression, but this one is the only with allow_manual_changes.
Would you show me the schedule of that room please?
EDIT: No bug for sure.
EDIT 2: And the schedule_prepend section as well, please.
And what do you expect the first rule in schedule_prepend to do?
To not schedule anything, any rule, if this switch is off. And it is on.
The rule evaluates to Abort(), as your logs say. Are you sure that it’s on?
OK, I’m really a piece of…
This schedy switch was off and no target temperature has been set.
Please be gentle with me, do not blame me too much (if I wasted your time).
Yes, such things happen…
You could look at the logs from time to time to learn reading and interpreting them correctly, then you can solve such things yourself in no time.
You’re completely right. And I looked to the logs before writing. Once again, I’m sorry.
Not too bad, was funny after all
@radar Ah, what I wanted to say about the way you wrote the schedules… There’s a lot of boilerplate code involved, you could use sub-schedules and simplify it greatly like so:
- v: 20
rules:
- { start: "06:00", end: "07:30", weekdays: "2-3"} #mardi et mercredi matin
- { start: "17:00", end: "20:30", weekdays: "1-2"} #lundi et mardi soir
- x: None if is_on('input_boolean.kids') else Skip()
rules:
-,{ start: "06:00", end: "07:30", weekdays: 1} #un lundi matin sur deux
- { start: "17:00", end: "21:00", weekdays: 5} #un vendredi soir sur deux
- weekdays: 6-7
rules:
- { start: "07:00", end: "09:30" } #un week-end matin sur deux
- { start: "18:00", end: "21:00" } #un week-end soir sur deux
- v: 19
rules:
- { start: "07:30", end: "18:00", weekdays: 3} #mercredi dans la journée
- x: None if is_on('input_boolean.kids') else Skip()
rules:
- { start: "09:30", end: "18:00", weekdays: "6-7"} #un week-end journée sur deux
- { v: 16 } #reste du temps
Just a hint though.
EDIT: Ah, these 16’s can be removed as well, will do that after dinner.
EDIT 2: Should be equivalent to what you had before. Maybe I’ll use something like that snippet as an example.
2 Likes
Oh. Seems like a nightmare to setup because I don’t have hass.io. I use hassbian. Sorry but this seems like very mysterious app. No demo, no screens?
@Jiran Since you decided for hassbian, I suppose you have had a reason to do so. But if you struggle with executing the 3 commands required for installing, you’ll probably have much more difficulties with the configuration and Schedy just isn’t for you.
I have hassbian because of RF script which is able to receive data from RF receiver on raspberry gpio. I’m not sure if this is possible in hass.io. I think only via rflink. I’m sure I can run 3 commands I made many custom settings… But this installation is difficult or very bad described. I am not sure what is worst.
@Jiran Usually, people succeed with installing hass-apps. If you have concrete questions, I’m willing to help, but these not constructive statements won’t get us any further.