I’ve created a graphical scheduler where you can easily schedule things to be turned on or off, or values (e.g. temperatures) change at a certain time and not via other triggers. I wanted to make it simple so users don’t need to be tech savvy but could still adjust the schedule in the frontend. So, now it’s here hb9hkn/weekly_scheduler_card: – it can be installed through HACS (you have to add a custom resource) by downloading the integration and the card.
The frontend has 30 min slots, however using the services you can choose any time you want via yaml.
1 Like
Hi,
I tried to install it using hacs (version 2.0.5) but I got this error:
In the hacs debug logs I didn’t find anything relevant:
<Integration hb9hkn/weekly_scheduler> Checking repository.
<Integration hb9hkn/weekly_scheduler> Running checks against v0.4.1
When installing the card repo all was fine.
I think the problem is that in the hacs.json you have the content_in_root set to true while it should be false. Can you double check?
Thanks for the note. I’ll take a look tomorrow. I’ll post here as soon as I create a new release.
@maikeljkwak : thanks for the alert. I fixed the problem (yes, you were right). I made a change at the last moment without thinking. The integration loads now and it seems to work. I didn’t have a lot of time to test today, but will tomorrow. Pls let me know if there are any other issues.
Thanks
Hello,
I was testing it a bit because I think that might be useful for my use case where I want that other people in a housa can manage the heating in their own rooms. So, here is my feedback:
- When using it in a mobile device it is very easy to change unintencionally the schedule. When I am scrolling down, if I clic in the schedule I can change it by mistake. I think that a double clic or long press would be great to avoid this problem
- I think that hide some fields like “schedule on/off” might be interesting
- When using input_number, if I clic over a timeslot that is already defined it updates to the new value but there is no way to reset it back to null. This is not a problem but if reset is not possible I would consider to have all timeslots with a predefined value by default.
- I would like to have a button-card with a schedule icon and when this button is pressed show this card so the user can modify it. I think this is no going to be possible and that the only options are browser_mod or navigate. I don’t like to use browser_mod because I would need to register browsers etc so I guess the only option is the navigate action and design a new panel where I have this card and a back button. What do you think?
Again, thanks for sharing your work!
Hi,
Thanks for the feedback and proposals. It is the first release, so I’ll be improving it. Unfortunately, I’m going to travel for the next couple of weeks and won’t be able to work on it, but will continue when I return. Comments:
- Yes, it is extremely easy to change the schedule on a mobile. I was thinking about adding a button for mobiles to ‘indicate’ the wish to change schedule or something like a long push. I need to play with it a bit.
- Hiding some fields: yes, good idea
- Reset input_number: I had this before, but then the question was to what number would the reset go? Initially, I had it setup that if a field was empty, then the last defined value was held over. This led to confusions because the value was not visible, but still defined. If you have a proposal what to do with the “empty” fields please share – ‘null’ might break automations or other actions triggered by the value change.
- I don’t like the browser_mod either. I created subviews on my dashboards. So the main dashboard has a button which leads to a subview which has the schedule. I don’t know if this could work for you.
As said, I’ll continue working on this, but there’s going to be slight delay now before I can continue.
Best regards and thanks again
Hi,
Regarding the input_number reset, I would expect that the timeslot goes back to the “blank state” like is was never defined. Or, if the “blank state” does not make sense, set a zero by default instead of blank in all the timeslots
Anyway, this is not a super critical issue because once you know how it works its ok. I just mentioned it because was not very intuitive for me but like you said, probable there are a lot of things to consider in the backend so I don’t know which solution would be the best.
Yeah, I think that navigate action and subviews are the best option. Will have a try.
Again, thanks for sharing your work!