Comments (8)
OK, I can still reproduce this readily. I've set up an automation as you described to check your hypothesis, and it does fire when I change the setpoint. I do not think it is surprising though, as you'd want to be able to set up automations when the setpoint changes.
Scheduler does not compare the old state with the new state so even if the operational mode remains the same
This seems like a bug to me. The checkbox reads 'Re-evaluate when conditions change' which implies to re-evaluate only when they change and not when they don't change. I believe you'd need to compare, otherwise you lose orthogonality between setpoint and operation mode.
from scheduler-component.
I just released v3.3.0 which adds a check comparing the old vs new state when HA triggers a state change event. The schedules will only be triggered when the state of the condition entities has changed.
I hope this helps for your usage. Otherwise let me know.
from scheduler-component.
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days
from scheduler-component.
It would have been nice to get some attention on this problem; at any rate at the moment I seem not to be able to observe it any longer. (HA update may have made the problem disappear)
from scheduler-component.
Your TRV integration triggers a 'state change' for the climate entity when you change the setpoint.
Scheduler does not compare the old state with the new state so even if the operational mode remains the same, this could the schedule to be triggered.
Likewise, if you create an automation in HA to trigger on a state change of your climate entity, it would also be fired every time the setpoint (and not operational mode) changes.
If you want to specifically use the operation mode as condition in the schedule, you should consider to create a template sensor to store the operation mode of the climate device (for example the hvac_action
attribute), and use this template sneosr in your condition.
from scheduler-component.
Thanks, I will investigate further based on your indications, if I see the problem again.
However, I confirm that I cannot reproduce any longer at the moment.
I was running HA 2023.10.3 when I got the problem, now I am on 2023.12.3, so maybe the upgrade changed something. Do you have any information to that effect?
from scheduler-component.
Do you have any information to that effect?
No. Scheduler has not been updated since last May, so any change would be on the side of HA.
from scheduler-component.
The side of HA was what I was talking about, precisely. :)
from scheduler-component.
Related Issues (20)
- No load the integration HOT 3
- Scheduler doesn't work after midnight HOT 3
- Deprecation warning that 'scheduler' calls `async_track_state_change` instead of `async_track_state_change_event` HOT 5
- auto repeat HOT 1
- Conditions to allow more entities kinds, not only switch and light. Boolean input would be great. Binary sensors too. HOT 2
- Schedule vacuum with rooms HOT 2
- Schedule scheme with conditions HOT 1
- async_dispatcher_send error HOT 14
- Scheme does not run end state HOT 5
- Warning message when upgrading to 2024.7.0 HOT 1
- Schedule switch error in version 3.3.4 during a script repeat loop HOT 4
- custom integration 'scheduler' calls `async_track_state_change` instead of `async_track_state_change_event - will be removed in Home Assistant 2025.5 HOT 1
- Error in latest release when disabling schedule via service switch.turn_off HOT 1
- "object NoneType can't be used in 'await' expression" HOT 1
- Time to next trigger per task is not shown anymore HOT 2
- Schedule switch not activated when switch toggle target is a label
- Ensure scheduler state (eg. manual run with checking time and conditions) HOT 4
- scheduler doesn't work anymore since last update HOT 1
- Service to enable/disable/run a schedule providing the entity the schedule is related for.
- KeyError: 'service' in Scheduler Component after Home Assistant 2024.8.0 Update HOT 8
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from scheduler-component.