-
-
Notifications
You must be signed in to change notification settings - Fork 11
Add Shelly EM Pro support via Shelly.GetStatus (act_power) #86
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
The scheduler was updated to persist all time and threshold settings across reboots using restore_value. It now evaluates its state on boot and immediately applies actions if the current time is already within the scheduled window. A safety check was added so temperature limits override the scheduler instantly, stopping the router when exceeded. Overall, the scheduler is now reboot-safe, state-consistent, and safety-aware.
correct mode: box missing in hour and minutes definition
custom tempo 22h - 6h
|
Thanks for your PR. Before merging, can you also: Add the documentation in English and, if you speak French, aussi en Français. I notice that you provide 2 files in your PR. Can you create a dedicated PR for scheduler_forced_run_safe.yaml with its documentation and tests. |
# Stop Forced Scheduler when temperature is above stop_temperature # or when Safety limit reached is active # Check is done every minute, ONLY during scheduler time window
✅ What is added
/rpc/Shelly.GetStatusem1:X.act_powerreal_power🧪 Tested on
📁 Files added
solar_router/power_meter_shelly_em_pro.yamlℹ️ Notes
/emeter/Xwhich is not available on EM Propower_meter_common.yaml