More flexibility on mode
What's Changed
Mode Changes
-
Enhanced
_appnamesupport:- Now, modes can be assigned specific applications. This means a mode will only activate within its designated room, using the format
_<appname>. Note: Existing modes with underscores may be affected—check logs for warnings.
- Now, modes can be assigned specific applications. This means a mode will only activate within its designated room, using the format
-
Customized Mode Names and Language Support:
- Default mode names have been updated to accommodate user language preferences stored in
translations.json. To maintain custom changes across updates, consider copying the file elsewhere. Configure your apps withlightwand_language,
- Default mode names have been updated to accommodate user language preferences stored in
-
Modify "MODE_CHANGE" Event Text:
- The text for the "MODE_CHANGE" event can now be customized using
translations.json, useful if similar events are already configured.
- The text for the "MODE_CHANGE" event can now be customized using
Light Control Enhancements
- HA Selector Integration:
- Define lighting options within a room using the HA selector. Configure this feature with
selector_inputunder options.
- Define lighting options within a room using the HA selector. Configure this feature with
Bed Sensors and Morning Routines
-
Added
out_of_bed_delayto bed sensors:- I tried to address issues with the Aqara FP2 losing detection when my kid is sleeping, and added an
out_of_bed_delayfor rooms you have bed sensors. This feature did not solve my problem.
- I tried to address issues with the Aqara FP2 losing detection when my kid is sleeping, and added an
-
Introduced
prevent_off_to_normaloption:- Useful for maintaining lights off when a room's mode is set to "off," preventing automatic transitions from morning to normal settings (e.g., when kids are home sick or teenagers sleep in). To revert to standard operation, use the reset mode function.
Full Changelog: v1.4.3...v1.5.0