Heaty will die, Schedy be born!

i dont know what docs you did read, but in the section manual installation you see that if you already got appdaemon installed its nothing more then

activate your appdaemon venv
pip install --upgrade hass-apps

whats difficult about that???

1 Like

Thanks @roschi.

Thank you. But I have appdaemon installed in /home/homeassistant/appdaemon (there is apps.yaml appdaemon.yaml and apps directory) using

sudo pip3 install appdaemon

after

pip3 install --upgrade hass-apps

and now…? How can I start hass apps to configure schedy?

Oh, now I can see I installed appdaemon before using:

sudo hassbian-config install appdaemon

but now when I run:

appdaemon -c /home/homeassistant/appdaemon/

it shows error:

ERROR no ‘appdaemon’ section in /home/homeassistant/appdaemon/appdaemon.yaml

there is this text in appdaemon.yaml:

AppDaemon:
logfile: STDOUT
errorfile: STDERR
log_generations: 3
threads: 10
HASS:
ha_url: http://127.0.0.1:8123
ha_key: test123

Any idea?

OK using this article: https://github.com/home-assistant/hassbian-scripts/blob/dev/docs/appdaemon.md

appdaemon repaired and running

now via virtualenv:

pip install --upgrade hass-apps

is finished.

Next step is to configure schedy using some yaml or activate it somehow?

@Jiran Really, read the documentation from the getting started chapter onwards. I wrote this for you, not me.

This is a full configuration example with comments on each available setting. Copy it to a .yaml file in your apps directory and adapt it to your needs.
Which .yaml?

Sorry. I really apreciate your effort. You have my respect for this work. BUT. This manual is not well written. It is for experts only. Sorry. Good manual is almost for everybody…

What I want to say is tha good written manual doesn´t create other questions…

Doesn’t matter.

OH my… now a real hell comes :slight_smile:

And I just want to schedule heating pump switch on / off. Maybe it will be better to do this via automation :frowning:

No real usability description. No examples. No final home assistant screenshot…

Really. After few days I just don´t know why should I use Schedy and what it brings. Will there be some graphical interface on switch? Or is this just a kind of automation (but why)?

Well, writing to the HA configuration manually isn’t straightforward as well, but you do it if you need automations etc.

If you have concrete suggestions for improving the documentation, you’re very welcome to file a pull request and help others that way.

There are quite some examples for writing schedules included in the docs. Even the difference to just using plain automations is explained a bit. You just have to read it. Schedy is far, far superior to using automations for scheduling things.

And no, there won’t be any graphical UI. That’s not feasible with the complexity that Schedy schedules can have.

I think best manuals are the ones using step by step images. I could create such (for hassbian).

Anyway…before I will start wasting time with configuration. What is real goal of schedy? What is it? Will there be graphical interface on switch in HA allowing me to set time and/or date? Or is this just a config based tool to create…something (what)? Sorry. I don´t want to upset you but could you give me answer how to imagine schedy?
Thank you?

Hm, I’m not sure how images could help with executing the commands needed for installation. They are just something to be maintained and kept up to date - additional effort for no real value IMHO.

And: Have you read the chapter about the concept of Schedy?

Well, my suggestion is this: Read the documentation completely. Start - as suggested on the main page - with the concept chapter and then go on. And then you’re welcome to ask for things still unclear.

OK this make sense…thank you.

Fine. We’ll see how we can help you after you read through it.

Well I want only to schedule single switch (heating pump) and turn off lights (philips hue) after midnight if I forget to.

Will try to set it :slight_smile:

Are there some complete config examples somewhere?

Schedules heavily depend on the usecase, so there’s no general one. And schedules are independent of the actor type used.

You find both simple and more custom examples along the Writing Schedules and Expressions chapters. And finally, there’s the Tips and Tricks chapter for help with some common scenarios.

Thanks. I mean some complete config. Do you have one? It will tell more than separated pieces…

i think you should be glad that it is @roschi that created this for free with a documentation that is usefull for most people, because if it was me i wouldnt have responded anymore after the negative way you talk about his work.

you install a program and dont even know what that program does or how it can be used, and after that you go ask the creator what you need to do and rant about his docs again??

i am sorry but i think your behaviour is way below every level, and i must say that i have high respect for @roschi that he still takes time for you.
instead of saying that you have respect for his work you might want to think about being a bit more respectfull towards him.

maybe it would be better if i didnt write this, but i think sometimes things need to be said.

1 Like