On the other hand, when i call enable_off; the enable button is still ‘ON’ both on summary page and on edit details page. I don’t know in real if this visual button or json file takes precedence, so i have to test it for some more…
I have to restart HA Scheduler to see the result effects on button.
It is not necessary to restart the addon it is just the frontend to be reload by the related button. (The demon are already received the correct status )
Hi,
Thanks for the feedback but the addon it is born to have a separate schedule web page integrated by ingress to HA + panel tab. At moment the best way to use an input date time from front end of HA it is a standard automation.
Sorry I can’t add these possibility becouse there is some design and development obstacle.
Hi,
is it possible to switch an input_boolean?
Tried to create a template binary_sensor which holds its own state but that did not work.
I just want an entity for a condition in an automation without any action or logic behind.
I don’t care if its an binary sensor, input or switch.
Thx!
I have tested the climate control and the use of :Txx. It seams to work good.
As for climate control, normally there is the need for lowering the temp at night and sometimes even in day time (when you are at work)
Based on this it would be nice to have more “ON” options for each day.
Ex.
Monday:
On 06:00:00:T22 (start heating in the morning)
On 08:00:00:T17 ( lower temp when going to work)
On 15:00:00:T22 (start heating before coming home from work)
On 23:30:00:T17 (lower temp. for night)
I know it is possible to have 4 pcs. separate schedules, but this will be a bit messy if you have 6-7 different climate units to control
Hi,
i’m checking and it is sorted by an internal generated ID i’m changing to add a sort on name of schedule. Tomorrow i’m releasing new version with these little fix
Thanks.
Just for your consideration if you sometime is changing the scheduler with more “ON” options as discussed above
Could it be easier to have a drop down box for selecting “ON” or “OFF”? If implemented with today’s solution, there will at least two “ON” for each schedule
I guess this will be an easier fix than my example above with 4 pcs. of “ON”