You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit df32330
Browse filesBrowse the repository at this point in the historyBrowse files
Distinguish operational controls from configuration entities
Follow-up to the EntityCategory work in #28: introduces a "control"
flag on sensor/switch/select/time entity definitions so genuine
operational controls (storage-mode bits, TOU V2 enable switches, TOU
V2 SOC/current/voltage/time entities, Work Mode select, the active-
protocol select) stay in the default category instead of being
lumped into EntityCategory.CONFIG alongside one-time settings.
Also renames storage-mode switch bits to a shorter "Mode - X" scheme,
disables two rarely-used bits (Battery Forcecharge Peakshaving,
Battery Current Correction) by default, and unifies TOU V2 entity
names to "Timed Charge {field} N" (N=1-6 charge slots, 7-12 discharge
slots), mirroring how V1 TOU already uses "Time-Charging" as an
umbrella term for both directions.
A new _apply_control_metadata() helper in hybrid_sensors.py tags and
renames entities by register instead of hand-annotating each dict.
0 commit comments