1770 lines
186 KiB
JSON
1770 lines
186 KiB
JSON
[
|
||
{
|
||
"id": "c6382818-05ed-4590-be92-b367489fb0e1",
|
||
"result": {
|
||
"structured": "TRIGGER: When Andrei is home sensor [binary_sensor.andrei_is_home] changes state OR when Master person [person.master] changes state. CONDITIONS: None. ACTIONS: Set the value of Currently home input text [input_text.currently_home] to a comma-separated list of user names who are currently detected as home. The list is built by checking if Andrei is home sensor [binary_sensor.andrei_is_home] is 'on', and if so, adding 'Andrei' to the list. The resulting list is then joined into a string.",
|
||
"natural_language": {
|
||
"trigger": "Whenever the state of the 'Andrei is home sensor' [binary_sensor.andrei_is_home] changes, or whenever the state of the 'Master person' [person.master] changes.",
|
||
"conditions": "There are no conditions that must be met for the action to run.",
|
||
"action": "Updates the text field 'Currently home input text' [input_text.currently_home] with a list of people currently at home. It checks if Andrei is detected as home, and if he is, his name is added to the list. The final list is formatted as a comma-separated string."
|
||
},
|
||
"human_like": "Updates a list showing who is currently at home whenever the presence status of Andrei or the Master person changes.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "d8084e61-405b-4f92-8c86-527254cc6753",
|
||
"result": {
|
||
"structured": "TRIGGER: When the system time reaches 00:01:00 daily OR when Home Assistant starts. CONDITIONS: None. ACTIONS: If the current month is November (11) OR December (12) OR January (1) OR February (2) OR March (3), then turn on Winter mode [input_boolean.winter_mode]. Otherwise, turn off Winter mode [input_boolean.winter_mode].",
|
||
"natural_language": {
|
||
"trigger": "The automation runs every day at one minute past midnight, or immediately when Home Assistant starts up.",
|
||
"conditions": "There are no conditions that must be met for the automation to proceed.",
|
||
"action": "It checks the current month. If the month is November, December, January, February, or March, it turns on the Winter mode [input_boolean.winter_mode]. For any other month, it turns the Winter mode [input_boolean.winter_mode] off."
|
||
},
|
||
"human_like": "Automatically switches winter mode on from November through March, and off for the rest of the year.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "38ea50fb-09bc-4d39-a771-1727ab72f265",
|
||
"result": {
|
||
"structured": "TRIGGER: When Home Assistant starts. CONDITIONS: None. ACTIONS: Turn on System startup phase [input_boolean.system_startup_phase].",
|
||
"natural_language": {
|
||
"trigger": "When the Home Assistant system starts up.",
|
||
"conditions": "There are no conditions for this automation.",
|
||
"action": "Turns on the System startup phase [input_boolean.system_startup_phase] helper."
|
||
},
|
||
"human_like": "Turns on a system startup indicator when Home Assistant boots up.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "03e3ffd0-4e1e-4200-b0e3-1ce6a2d77d6a",
|
||
"result": {
|
||
"structured": "TRIGGER: When Home Assistant starts. CONDITIONS: None. ACTIONS: Wait for 2 minutes, then turn off System startup phase [input_boolean.system_startup_phase].",
|
||
"natural_language": {
|
||
"trigger": "When the Home Assistant system starts up.",
|
||
"conditions": "There are no conditions for this automation.",
|
||
"action": "After a two-minute delay, the automation turns off the System startup phase [input_boolean.system_startup_phase]."
|
||
},
|
||
"human_like": "Turns off the system startup phase indicator two minutes after Home Assistant starts, allowing initial processes to settle.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "cc269239-a6dd-422f-ba2a-3d57e4c5981e",
|
||
"result": {
|
||
"structured": "TRIGGER: When the time is exactly 23:00:00. CONDITIONS: None. ACTIONS: Turn on Silent mode [input_boolean.silent_mode].",
|
||
"natural_language": {
|
||
"trigger": "At exactly 11:00 PM.",
|
||
"conditions": "There are no additional conditions.",
|
||
"action": "Activates the silent mode by turning on the Silent mode [input_boolean.silent_mode] input boolean."
|
||
},
|
||
"human_like": "Automatically enables silent mode every night at 11 PM.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "6ed14663-ebe5-4ab3-bc3b-43e682c45f3b",
|
||
"result": {
|
||
"structured": "TRIGGER: At 09:00:00. CONDITIONS: None. ACTIONS: Turn off Silent mode [input_boolean.silent_mode].",
|
||
"natural_language": {
|
||
"trigger": "Every day at 9:00 AM.",
|
||
"conditions": "There are no conditions for this automation.",
|
||
"action": "Turns off the Silent mode [input_boolean.silent_mode]."
|
||
},
|
||
"human_like": "Automatically disables the silent mode every morning at 9 AM.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "7df1e59a-af5d-4496-be72-e687afdbf08e",
|
||
"result": {
|
||
"structured": "TRIGGER: When Living room ventilation status [binary_sensor.livingroom_ventilation_status] changes from on to off. CONDITIONS: System startup phase [input_boolean.system_startup_phase] is off. ACTIONS: Turn off CO2 voice notification sensor [input_boolean.co2_voice_notification_sensor] AND turn off CO2 text notification sensor [input_boolean.co2_text_notification_sensor].",
|
||
"natural_language": {
|
||
"trigger": "When the Living room ventilation status [binary_sensor.livingroom_ventilation_status] turns off.",
|
||
"conditions": "The System startup phase [input_boolean.system_startup_phase] must be off.",
|
||
"action": "Turns off both the CO2 voice notification sensor [input_boolean.co2_voice_notification_sensor] and the CO2 text notification sensor [input_boolean.co2_text_notification_sensor]."
|
||
},
|
||
"human_like": "Resets CO2 notification sensors when the living room ventilation is turned off, provided the system is not starting up.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "5b187cde-0ad5-4132-bb68-a622dd15d6ff",
|
||
"result": {
|
||
"structured": "TRIGGER: When Home Assistant shutdown event occurs. ACTIONS: Perform three independent conditional actions: 1) IF Air conditioner [climate.konditsioner] is on AND Winter mode [input_boolean.winter_mode] is off THEN turn on Climate pre restart state [input_boolean.climate_pre_restart_state] ELSE turn off Climate pre restart state [input_boolean.climate_pre_restart_state]. 2) IF Zhimi fan switch [switch.zhimi_mb3_a5d3_switch_status] is on THEN turn on Fan pre restart state [input_boolean.fan_pre_restart_state] ELSE turn off Fan pre restart state [input_boolean.fan_pre_restart_state]. 3) IF Evolution humidifier [switch.evolution_hf_878] is on THEN turn on Humidifier pre restart state [input_boolean.humidifier_pre_restart_state] ELSE turn off Humidifier pre restart state [input_boolean.humidifier_pre_restart_state].",
|
||
"natural_language": {
|
||
"trigger": "When Home Assistant is shutting down.",
|
||
"conditions": "There are no global conditions. The automation contains three separate conditional checks within its actions.",
|
||
"action": "The automation saves the state of three climate-related devices into helper switches before the system restarts. First, it checks if the Air conditioner [climate.konditsioner] is on and Winter mode [input_boolean.winter_mode] is off; if so, it turns on the Climate pre restart state [input_boolean.climate_pre_restart_state] helper, otherwise it turns it off. Second, it checks if the Zhimi fan switch [switch.zhimi_mb3_a5d3_switch_status] is on; if so, it turns on the Fan pre restart state [input_boolean.fan_pre_restart_state] helper, otherwise it turns it off. Third, it checks if the Evolution humidifier [switch.evolution_hf_878] is on; if so, it turns on the Humidifier pre restart state [input_boolean.humidifier_pre_restart_state] helper, otherwise it turns it off."
|
||
},
|
||
"human_like": "Saves the current on/off state of the air conditioner, fan, and humidifier into helper switches just before Home Assistant shuts down, so their status can be restored later.",
|
||
"complexity": "medium"
|
||
}
|
||
},
|
||
{
|
||
"id": "457a6711-67fa-4cb2-bcab-63c0cc58e054",
|
||
"result": {
|
||
"structured": "TRIGGER: When Home Assistant starts. CONDITIONS: None. ACTIONS: Execute a series of conditional actions: IF Climate pre restart state [input_boolean.climate_pre_restart_state] is on AND Winter mode [input_boolean.winter_mode] is off, THEN turn on Air conditioner [climate.konditsioner]. IF Fan pre restart state [input_boolean.fan_pre_restart_state] is on, THEN turn on Zhimi fan switch [switch.zhimi_mb3_a5d3_switch_status]. IF Humidifier pre restart state [input_boolean.humidifier_pre_restart_state] is on, THEN turn on Evolution humidifier [switch.evolution_hf_878]. Finally, turn off Climate pre restart state [input_boolean.climate_pre_restart_state], Fan pre restart state [input_boolean.fan_pre_restart_state], and Humidifier pre restart state [input_boolean.humidifier_pre_restart_state].",
|
||
"natural_language": {
|
||
"trigger": "When Home Assistant starts up.",
|
||
"conditions": "There are no global conditions for this automation. The actions are performed based on the state of specific helper switches at the time of startup.",
|
||
"action": "The automation checks and restores the state of climate and appliance devices. First, if the 'Climate pre restart state' [input_boolean.climate_pre_restart_state] is on and 'Winter mode' [input_boolean.winter_mode] is off, it turns on the Air conditioner [climate.konditsioner]. Next, if the 'Fan pre restart state' [input_boolean.fan_pre_restart_state] is on, it turns on the Zhimi fan switch [switch.zhimi_mb3_a5d3_switch_status]. Then, if the 'Humidifier pre restart state' [input_boolean.humidifier_pre_restart_state] is on, it turns on the Evolution humidifier [switch.evolution_hf_878]. Finally, it resets all three pre-restart state helpers by turning them off."
|
||
},
|
||
"human_like": "Restores the air conditioner, fan, and humidifier to their previous on/off states when Home Assistant restarts, provided winter mode is not active for the AC.",
|
||
"complexity": "medium"
|
||
}
|
||
},
|
||
{
|
||
"id": "bee019e8-c011-4283-85df-4cbbbc00e92f",
|
||
"result": {
|
||
"structured": "TRIGGER: When Someone is home [binary_sensor.someone_is_home] changes state. CONDITIONS: System startup phase [input_boolean.system_startup_phase] is off AND Force camera off [input_boolean.force_camera_off] is off. ACTIONS: If Someone is home [binary_sensor.someone_is_home] is off, then turn on Cameras group [group.cameras] and send notification 'Камеры включены: Никого нет дома.' to master. If Someone is home [binary_sensor.someone_is_home] is on, then turn off Cameras group [group.cameras] and send notification 'Камеры выключены: Кто-то дома.' to master.",
|
||
"natural_language": {
|
||
"trigger": "Whenever the state of the sensor Someone is home [binary_sensor.someone_is_home] changes.",
|
||
"conditions": "The system must not be in its startup phase, meaning System startup phase [input_boolean.system_startup_phase] is off. Also, the cameras must not be in a forced-off state, meaning Force camera off [input_boolean.force_camera_off] is off.",
|
||
"action": "If no one is home, the automation turns on all cameras in the Cameras group [group.cameras] and sends a notification stating that the cameras are on because no one is home. If someone is home, it turns off all cameras in the Cameras group [group.cameras] and sends a notification stating that the cameras are off because someone is home."
|
||
},
|
||
"human_like": "This automation intelligently manages the camera system, turning it on for security when the house is empty and turning it off for privacy when someone is home, unless overridden by a force-off setting.",
|
||
"complexity": "medium"
|
||
}
|
||
},
|
||
{
|
||
"id": "98df0b92-1c60-4e48-a065-3412a0706124",
|
||
"result": {
|
||
"structured": "TRIGGER: When Chuangmi camera 1 [switch.chuangmi_cn_309825146_ipc019_on_p_2_1] turns on OR when Chuangmi camera 2 [switch.chuangmi_cn_311366982_ipc019_on_p_2_1] turns on. CONDITIONS: Force camera off [input_boolean.force_camera_off] is on. ACTIONS: Turn off Chuangmi camera 1 [switch.chuangmi_cn_309825146_ipc019_on_p_2_1] AND turn off Chuangmi camera 2 [switch.chuangmi_cn_311366982_ipc019_on_p_2_1] AND send a notification to the master user with the message 'Попытка включения камер заблокирована (форсированное отключение).'.",
|
||
"natural_language": {
|
||
"trigger": "When either the Chuangmi camera 1 [switch.chuangmi_cn_309825146_ipc019_on_p_2_1] or the Chuangmi camera 2 [switch.chuangmi_cn_311366982_ipc019_on_p_2_1] is turned on.",
|
||
"conditions": "If the Force camera off [input_boolean.force_camera_off] mode is currently active (set to on).",
|
||
"action": "Immediately turn off both the Chuangmi camera 1 [switch.chuangmi_cn_309825146_ipc019_on_p_2_1] and Chuangmi camera 2 [switch.chuangmi_cn_311366982_ipc019_on_p_2_1] switches, and send a notification to the master user stating that the attempt to turn on the cameras has been blocked due to forced off mode."
|
||
},
|
||
"human_like": "Prevents cameras from being turned on when a forced-off mode is active, automatically turning them back off and notifying the user.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "779498b6-e63f-454d-8866-8e7e7a94d8e4",
|
||
"result": {
|
||
"structured": "TRIGGER: When the time is 03:40:00 daily. CONDITIONS: None. ACTIONS: Call service recorder.purge with parameters keep_days: 90, repack: false, apply_to_entities: [].",
|
||
"natural_language": {
|
||
"trigger": "Every day at 3:40 AM.",
|
||
"conditions": "There are no conditions for this automation.",
|
||
"action": "Purges the recorder database, keeping only the last 90 days of data."
|
||
},
|
||
"human_like": "Automatically cleans up the Home Assistant database every night, keeping only the last 90 days of history.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "8a46561c-f48f-4c93-b53e-d1af940fdb6d",
|
||
"result": {
|
||
"structured": "TRIGGER: When Someone is home [binary_sensor.someone_is_home] changes to off OR at 09:00:00 daily. CONDITIONS: (Weekday is Monday OR Tuesday OR Wednesday OR Thursday OR Friday) AND (Time is after 09:00:00 AND before 17:00:00) AND (Bathroom cleaning mode [input_boolean.bathroom_cleaning_mode] is off) AND (Someone is home [binary_sensor.someone_is_home] is off). ACTIONS: Turn off All lights group [light.all_lights] AND turn off Smart plug switch [switch.smart_plug_in_unit_vykliuchatel] AND turn off Living room TV group [group.living_room_tv].",
|
||
"natural_language": {
|
||
"trigger": "The automation can be triggered in two ways: either when the 'Someone is home' [binary_sensor.someone_is_home] sensor indicates that everyone has left (changes to 'off'), or at exactly 9:00 AM every day.",
|
||
"conditions": "For the actions to run, all of the following must be true: it must be a weekday (Monday through Friday), the current time must be between 9:00 AM and 5:00 PM, the 'Bathroom cleaning mode' [input_boolean.bathroom_cleaning_mode] must be turned off, and the 'Someone is home' [binary_sensor.someone_is_home] sensor must still report that no one is home.",
|
||
"action": "The automation turns off all the lights via the 'All lights group' [light.all_lights], turns off the smart plug for the steamer [switch.smart_plug_in_unit_vykliuchatel], and turns off the living room television via the 'Living room TV group' [group.living_room_tv]."
|
||
},
|
||
"human_like": "On weekdays during work hours, this automation turns off all lights, the steamer, and the TV when no one is home and cleaning mode is inactive.",
|
||
"complexity": "medium"
|
||
}
|
||
},
|
||
{
|
||
"id": "ee320693-2e76-435b-8012-3a908046d4d5e",
|
||
"result": {
|
||
"structured": "TRIGGER: When Someone is home [binary_sensor.someone_is_home] changes to off. CONDITIONS: Someone is home [binary_sensor.someone_is_home] is off. ACTIONS: Turn off Smart plug switch [switch.smart_plug_in_unit_vykliuchatel].",
|
||
"natural_language": {
|
||
"trigger": "When the Someone is home [binary_sensor.someone_is_home] sensor changes to 'off', indicating no one is detected at home.",
|
||
"conditions": "The automation checks that the Someone is home [binary_sensor.someone_is_home] sensor is indeed in the 'off' state.",
|
||
"action": "Turns off the Smart plug switch [switch.smart_plug_in_unit_vykliuchatel]."
|
||
},
|
||
"human_like": "Turns off the steamer's smart plug when the home occupancy sensor detects that everyone has left.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "plant-send-pending-notifications",
|
||
"result": {
|
||
"structured": "TRIGGER: When Master person [person.master] arrives home (state changes to home). CONDITIONS: System startup phase [input_boolean.system_startup_phase] is off. ACTIONS: Wait for 1 minute, then execute the Check All Plants [script.check_all_plants] script.",
|
||
"natural_language": {
|
||
"trigger": "When the Master person [person.master] returns home.",
|
||
"conditions": "The system must not be in its startup phase, meaning the System startup phase [input_boolean.system_startup_phase] is turned off.",
|
||
"action": "After a one-minute delay, run the Check All Plants [script.check_all_plants] script to send any pending plant notifications."
|
||
},
|
||
"human_like": "Sends any pending plant care notifications that accumulated while you were away, one minute after you return home.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "4370eb06-5640-4c42-adde-b91046f301f4-1",
|
||
"result": {
|
||
"structured": "TRIGGER: When Plant alert euphorbia soil [binary_sensor.plant_alert_euphorbia_leuconeura_soil] changes to on. CONDITIONS: Master person [person.master] is home AND System startup phase [input_boolean.system_startup_phase] is off AND (The time elapsed since the last notification timestamp stored in Last euphorbia soil notification [input_datetime.last_euphorbia_leuconeura_soil_notification] is greater than the cooldown period defined by Plants notification cooldown hours [input_number.plants_notification_cooldown_hours] converted to seconds). ACTIONS: Execute the script Plant Check Conditions [script.plant_check_conditions] with data: plant_name = 'Молочай', plant_name_latin = 'euphorbia_leuconeura'.",
|
||
"natural_language": {
|
||
"trigger": "When the Plant alert euphorbia soil [binary_sensor.plant_alert_euphorbia_leuconeura_soil] sensor indicates the soil needs attention by turning on.",
|
||
"conditions": "The Master person [person.master] must be at home, the System startup phase [input_boolean.system_startup_phase] must be off, and a sufficient cooldown period must have passed since the last notification was sent. This cooldown is calculated by comparing the current time to the timestamp stored in Last euphorbia soil notification [input_datetime.last_euphorbia_leuconeura_soil_notification], ensuring it exceeds the number of hours set in Plants notification cooldown hours [input_number.plants_notification_cooldown_hours].",
|
||
"action": "Runs the Plant Check Conditions [script.plant_check_conditions] script, specifying the plant's common name as 'Молочай' and its Latin name as 'euphorbia_leuconeura'."
|
||
},
|
||
"human_like": "Sends a watering notification for the Euphorbia plant when its soil sensor triggers, but only if someone is home, the system is fully started, and a minimum time has passed since the last alert.",
|
||
"complexity": "medium"
|
||
}
|
||
},
|
||
{
|
||
"id": "4370eb06-5640-4c42-adde-b91046f301f4-2",
|
||
"result": {
|
||
"structured": "TRIGGER: When Plant alert euphorbia temperature [binary_sensor.plant_alert_euphorbia_leuconeura_temperature] turns on. CONDITIONS: Master person [person.master] is home AND System startup phase [input_boolean.system_startup_phase] is off AND (The time elapsed since the last notification timestamp stored in Last euphorbia temperature notification [input_datetime.last_euphorbia_leuconeura_temperature_notification] is greater than the cooldown period defined by Plants notification cooldown hours [input_number.plants_notification_cooldown_hours]). ACTIONS: Execute script Plant Check Conditions [script.plant_check_conditions] with data: plant_name = Молочай, plant_name_latin = euphorbia_leuconeura.",
|
||
"natural_language": {
|
||
"trigger": "When the Plant alert euphorbia temperature [binary_sensor.plant_alert_euphorbia_leuconeura_temperature] sensor indicates a temperature alert by turning on.",
|
||
"conditions": "The Master person [person.master] must be at home, the System startup phase [input_boolean.system_startup_phase] must be off, and a sufficient cooldown period must have passed since the last temperature notification for this plant. This cooldown is calculated using the timestamp from Last euphorbia temperature notification [input_datetime.last_euphorbia_leuconeura_temperature_notification] and the duration set in Plants notification cooldown hours [input_number.plants_notification_cooldown_hours].",
|
||
"action": "Runs the Plant Check Conditions [script.plant_check_conditions] script, specifying the plant's common name (Молочай) and its Latin name (euphorbia_leuconeura) as parameters."
|
||
},
|
||
"human_like": "Sends a notification about a temperature issue for the Euphorbia plant when an alert is triggered, but only if someone is home, the system is fully started, and enough time has passed since the last alert.",
|
||
"complexity": "medium"
|
||
}
|
||
},
|
||
{
|
||
"id": "4370eb06-5640-4c42-adde-b91046f301f4-3",
|
||
"result": {
|
||
"structured": "TRIGGER: When Plant alert euphorbia illuminance [binary_sensor.plant_alert_euphorbia_leuconeura_illuminance] turns on. CONDITIONS: Master person [person.master] is home AND System startup phase [input_boolean.system_startup_phase] is off AND the time elapsed since the last notification timestamp stored in Last euphorbia illuminance notification [input_datetime.last_euphorbia_leuconeura_illuminance_notification] is greater than the cooldown period defined by Plants notification cooldown hours [input_number.plants_notification_cooldown_hours] (converted to seconds). ACTIONS: Execute the script Plant Check Conditions [script.plant_check_conditions] with data parameters plant_name: Молочай and plant_name_latin: euphorbia_leuconeura.",
|
||
"natural_language": {
|
||
"trigger": "When the Plant alert euphorbia illuminance [binary_sensor.plant_alert_euphorbia_leuconeura_illuminance] sensor indicates an alert condition by turning on.",
|
||
"conditions": "The Master person [person.master] must be at home, the System startup phase [input_boolean.system_startup_phase] must be off, and a sufficient amount of time must have passed since the last notification was sent for this plant. This cooldown period is determined by the value set in Plants notification cooldown hours [input_number.plants_notification_cooldown_hours].",
|
||
"action": "Runs the Plant Check Conditions [script.plant_check_conditions] script, specifying the common name 'Молочай' and the Latin name 'euphorbia_leuconeura' for the plant."
|
||
},
|
||
"human_like": "Sends a notification about the lighting conditions for the Euphorbia plant when an alert is triggered, but only if someone is home, the system is fully started, and a cooldown period has passed.",
|
||
"complexity": "medium"
|
||
}
|
||
},
|
||
{
|
||
"id": "plant-euphorbia-periodic-check",
|
||
"result": {
|
||
"structured": "TRIGGER: When the time matches a pattern of every 6 hours (hours: /6). CONDITIONS: None. ACTIONS: Execute the script Plant Check Conditions [script.plant_check_conditions] with data: plant_name = Молочай, plant_name_latin = euphorbia_leuconeura.",
|
||
"natural_language": {
|
||
"trigger": "The automation runs every six hours, on the hour.",
|
||
"conditions": "There are no conditions that need to be met for the action to run.",
|
||
"action": "It runs the Plant Check Conditions [script.plant_check_conditions] script, passing the plant's common name 'Молочай' and its Latin name 'euphorbia_leuconeura' as parameters."
|
||
},
|
||
"human_like": "Checks the conditions for the Euphorbia plant every six hours.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "3ee8085c-621a-49f0-98f6-cce0d5c3c49b",
|
||
"result": {
|
||
"structured": "TRIGGER: When Plant alert ficus soil [binary_sensor.plant_alert_ficus_lyrata_soil] changes to on. CONDITIONS: Master person [person.master] is home AND System startup phase [input_boolean.system_startup_phase] is off AND (The current timestamp minus the timestamp of the last notification stored in Last ficus soil notification [input_datetime.last_ficus_lyrata_soil_notification] is greater than the cooldown period defined by Plants notification cooldown hours [input_number.plants_notification_cooldown_hours] converted to seconds). ACTIONS: Execute the script Plant Check Conditions [script.plant_check_conditions] with data: plant_name = 'Фикус лировидный', plant_name_latin = 'ficus_lyrata'.",
|
||
"natural_language": {
|
||
"trigger": "When the Plant alert ficus soil [binary_sensor.plant_alert_ficus_lyrata_soil] sensor indicates the plant needs watering by turning on.",
|
||
"conditions": "The Master person [person.master] must be at home, the System startup phase [input_boolean.system_startup_phase] must be off, and a sufficient amount of time must have passed since the last watering notification was sent. This cooldown period is defined by the Plants notification cooldown hours [input_number.plants_notification_cooldown_hours] setting.",
|
||
"action": "Runs the Plant Check Conditions [script.plant_check_conditions] script to handle the notification process for the Fiddle-leaf Fig plant, passing its common and Latin names as parameters."
|
||
},
|
||
"human_like": "Sends a watering reminder for the Fiddle-leaf Fig plant when its soil is dry, but only if someone is home, the system is fully started, and a notification hasn't been sent recently.",
|
||
"complexity": "medium"
|
||
}
|
||
},
|
||
{
|
||
"id": "3ee8085c-621a-49f0-98f6-cce0d5c3c49c",
|
||
"result": {
|
||
"structured": "TRIGGER: When Plant alert ficus temperature [binary_sensor.plant_alert_ficus_lyrata_temperature] changes to on. CONDITIONS: Master person [person.master] is home AND System startup phase [input_boolean.system_startup_phase] is off AND (The time elapsed since the last notification stored in Last ficus temperature notification [input_datetime.last_ficus_lyrata_temperature_notification] is greater than the cooldown period defined by Plants notification cooldown hours [input_number.plants_notification_cooldown_hours] (converted to seconds)). ACTIONS: Execute script Plant Check Conditions [script.plant_check_conditions] with data: plant_name = 'Фикус лировидный', plant_name_latin = 'ficus_lyrata'.",
|
||
"natural_language": {
|
||
"trigger": "When the Plant alert ficus temperature [binary_sensor.plant_alert_ficus_lyrata_temperature] sensor indicates an alert by turning on.",
|
||
"conditions": "The Master person [person.master] must be at home, the System startup phase [input_boolean.system_startup_phase] must be off, and a cooldown period must have passed since the last temperature notification was sent. This cooldown is determined by the value set in Plants notification cooldown hours [input_number.plants_notification_cooldown_hours].",
|
||
"action": "Runs the Plant Check Conditions [script.plant_check_conditions] script, specifying the plant's common name (Фикус лировидный) and its Latin identifier (ficus_lyrata) as parameters."
|
||
},
|
||
"human_like": "Sends a notification about the Fiddle-leaf Fig's temperature when an alert is triggered, but only if someone is home, the system is fully started, and enough time has passed since the last alert.",
|
||
"complexity": "medium"
|
||
}
|
||
},
|
||
{
|
||
"id": "plant-ficus-periodic-check",
|
||
"result": {
|
||
"structured": "TRIGGER: Every 6 hours (at 0, 6, 12, 18). CONDITIONS: None. ACTIONS: Execute the script Plant Check Conditions [script.plant_check_conditions] with data: plant_name = 'Фикус лировидный', plant_name_latin = 'ficus_lyrata'.",
|
||
"natural_language": {
|
||
"trigger": "The automation runs every six hours, on the hour.",
|
||
"conditions": "There are no conditions to check.",
|
||
"action": "It runs the Plant Check Conditions [script.plant_check_conditions] script, passing the details for the Fiddle-leaf Fig plant (Фикус лировидный, ficus_lyrata)."
|
||
},
|
||
"human_like": "Checks the conditions for the Fiddle-leaf Fig plant every six hours.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "dc1acbee-6ecd-45a4-8eae-ab69034c3117",
|
||
"result": {
|
||
"structured": "TRIGGER: When Bathroom humidity max [binary_sensor.bathroom_humidity_max] changes to on. CONDITIONS: Bathroom relay fan [fan.bathroom_relay_l1] is off. ACTIONS: Turn on Bathroom relay fan [fan.bathroom_relay_l1].",
|
||
"natural_language": {
|
||
"trigger": "When the Bathroom humidity max [binary_sensor.bathroom_humidity_max] sensor indicates that the average humidity in the bathroom has reached a high level.",
|
||
"conditions": "The Bathroom relay fan [fan.bathroom_relay_l1] must currently be off.",
|
||
"action": "Turns on the Bathroom relay fan [fan.bathroom_relay_l1] to ventilate the bathroom."
|
||
},
|
||
"human_like": "Turns on the bathroom fan when the humidity gets too high.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "6ebb6fa8-9cd1-4ebd-839d-44d175e6c319",
|
||
"result": {
|
||
"structured": "TRIGGER: When Bathroom humidity min [binary_sensor.bathroom_humidity_min] changes to on. CONDITIONS: None. ACTIONS: Start Bathroom fan cooldown timer [timer.bathroom_fan_cooldown].",
|
||
"natural_language": {
|
||
"trigger": "When the Bathroom humidity min [binary_sensor.bathroom_humidity_min] sensor indicates that humidity has dropped below the minimum threshold (changes to 'on').",
|
||
"conditions": "There are no conditions that must be met.",
|
||
"action": "Starts the Bathroom fan cooldown timer [timer.bathroom_fan_cooldown]."
|
||
},
|
||
"human_like": "Starts a cooldown timer for the bathroom fan when the humidity falls below a set level.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "7a1db18b-0366-47cf-8260-6109b01447f9",
|
||
"result": {
|
||
"structured": "TRIGGER: When Bathroom fan cooldown timer [timer.bathroom_fan_cooldown] finishes. CONDITIONS: None. ACTIONS: Turn off Bathroom relay fan [fan.bathroom_relay_l1].",
|
||
"natural_language": {
|
||
"trigger": "When the Bathroom fan cooldown timer [timer.bathroom_fan_cooldown] finishes.",
|
||
"conditions": "There are no conditions for this automation.",
|
||
"action": "Turns off the Bathroom relay fan [fan.bathroom_relay_l1]."
|
||
},
|
||
"human_like": "Automatically turns off the bathroom fan when its cooldown timer finishes.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "5525cbdc-3a8d-4464-908e-795c8205b40c",
|
||
"result": {
|
||
"structured": "TRIGGER: When the MQTT device Bathroom MQTT switch device [device_id: cc6ef89720abb376a24e910e13f37902] sends a 'single_left' action. CONDITIONS: None. ACTIONS: If Is night mode [binary_sensor.is_night_mode] is on, then run script Bathroom Toggle Night Mode [script.bathroom_toggle_night_mode]. Otherwise, run script Bathroom Toggle Day Mode [script.bathroom_toggle_day_mode].",
|
||
"natural_language": {
|
||
"trigger": "When the MQTT switch in the bathroom is pressed with a single left-click action.",
|
||
"conditions": "There are no specific conditions that must be met for the automation to proceed.",
|
||
"action": "If the night mode is currently active, the automation runs the 'Bathroom Toggle Night Mode' script. If night mode is not active, it runs the 'Bathroom Toggle Day Mode' script instead."
|
||
},
|
||
"human_like": "Toggles the bathroom lights between day and night modes using a wall switch, depending on whether night mode is active.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "0007279c-13b5-402b-9aef-bf264273fa90",
|
||
"result": {
|
||
"structured": "TRIGGER: When Bathroom open door [binary_sensor.bathroom_open_door] changes from closed (off) to open (on) AND remains open for 1 second OR When Bathroom motions [binary_sensor.bathroom_motions] changes from no motion (off) to motion detected (on) AND remains detected for 1 second. CONDITIONS: Bathroom cleaning mode [input_boolean.bathroom_cleaning_mode] is off AND System startup phase [input_boolean.system_startup_phase] is off AND Bathroom lights startup protection [input_boolean.bathroom_lights_startup_protection] is off. ACTIONS: If Is night mode [binary_sensor.is_night_mode] is on, then run script Bathroom Turn On Night Mode [script.bathroom_turn_on_night_mode]. Otherwise, run script Bathroom Turn On Day Mode [script.bathroom_turn_on_day_mode].",
|
||
"natural_language": {
|
||
"trigger": "When the Bathroom open door [binary_sensor.bathroom_open_door] opens and stays open for at least one second, or when the Bathroom motions [binary_sensor.bathroom_motions] sensor detects motion and that motion continues for at least one second.",
|
||
"conditions": "The automation only runs if the Bathroom cleaning mode [input_boolean.bathroom_cleaning_mode] is off, the System startup phase [input_boolean.system_startup_phase] is off, and the Bathroom lights startup protection [input_boolean.bathroom_lights_startup_protection] is off.",
|
||
"action": "If the system is in night mode, as indicated by Is night mode [binary_sensor.is_night_mode] being on, it runs the 'Bathroom Turn On Night Mode' script. Otherwise, it runs the 'Bathroom Turn On Day Mode' script."
|
||
},
|
||
"human_like": "Automatically turns on the bathroom lights with a day or night mode profile when motion is detected or the door opens, provided the system is not in a cleaning, startup, or protection state.",
|
||
"complexity": "medium"
|
||
}
|
||
},
|
||
{
|
||
"id": "50323f55-c6dd-483a-8799-af3c57e3e363",
|
||
"result": {
|
||
"structured": "TRIGGER: When Bathroom motions [binary_sensor.bathroom_motions] changes to on (motion detected). CONDITIONS: Bathroom timer [timer.timer_bathroom] is active AND Bathroom cleaning mode [input_boolean.bathroom_cleaning_mode] is off. ACTIONS: Cancel Bathroom timer [timer.timer_bathroom].",
|
||
"natural_language": {
|
||
"trigger": "When motion is detected in the bathroom, indicated by the Bathroom motions [binary_sensor.bathroom_motions] sensor turning on.",
|
||
"conditions": "The automation only runs if the Bathroom timer [timer.timer_bathroom] is currently active and the Bathroom cleaning mode [input_boolean.bathroom_cleaning_mode] is turned off.",
|
||
"action": "Cancels the currently running Bathroom timer [timer.timer_bathroom]."
|
||
},
|
||
"human_like": "Cancels the bathroom timer if motion is detected while the timer is running and cleaning mode is not active.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "e519fa4c-bbad-4b0d-b06c-8521b3b10131",
|
||
"result": {
|
||
"structured": "TRIGGER: When Bathroom motions [binary_sensor.bathroom_motions] remains off (no motion) for 1 minute. CONDITIONS: Bathroom all lights group [group.bathroom_all_lights] is on AND Bathroom cleaning mode [input_boolean.bathroom_cleaning_mode] is off. ACTIONS: Start Bathroom timer [timer.timer_bathroom] with a duration equal to the value of Bathroom timer duration [input_number.bathroom_timer_duration] (in minutes) converted to seconds.",
|
||
"natural_language": {
|
||
"trigger": "When the Bathroom motions [binary_sensor.bathroom_motions] sensor detects no motion for a continuous period of one minute.",
|
||
"conditions": "The automation only runs if the Bathroom all lights group [group.bathroom_all_lights] is turned on and the Bathroom cleaning mode [input_boolean.bathroom_cleaning_mode] is turned off.",
|
||
"action": "Starts the Bathroom timer [timer.timer_bathroom], setting its duration based on the current value of the Bathroom timer duration [input_number.bathroom_timer_duration] setting, which is converted from minutes to seconds."
|
||
},
|
||
"human_like": "Starts a countdown to turn off the bathroom lights when no motion is detected for a minute, unless cleaning mode is active.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "b30b7ad8-6563-4279-a78f-1a113f9cb252",
|
||
"result": {
|
||
"structured": "TRIGGER: When Bathroom timer [timer.timer_bathroom] finishes. CONDITIONS: Bathroom cleaning mode [input_boolean.bathroom_cleaning_mode] is off. ACTIONS: Turn off Bathroom all lights group [group.bathroom_all_lights].",
|
||
"natural_language": {
|
||
"trigger": "When the Bathroom timer [timer.timer_bathroom] finishes.",
|
||
"conditions": "If the Bathroom cleaning mode [input_boolean.bathroom_cleaning_mode] is turned off.",
|
||
"action": "Turns off all the lights in the bathroom by switching off the Bathroom all lights group [group.bathroom_all_lights]."
|
||
},
|
||
"human_like": "Turns off the bathroom lights when a timer finishes, but only if cleaning mode is not active.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "0c5020c3-e674-4789-8086-38dbc07253d7",
|
||
"result": {
|
||
"structured": "TRIGGER: When Bathroom spot R1 Philips [light.bathroom_spot_r1_philips] OR Bathroom spot R2 Philips [light.bathroom_spot_r2_philips] OR Bathroom spot L1 Philips [light.bathroom_spot_l1_philips] OR Bathroom spot C1 Philips [light.bathroom_spot_c1_philips] OR Bathroom spot C2 Philips [light.bathroom_spot_c2_philips] becomes unavailable and remains unavailable for 30 seconds. CONDITIONS: System startup phase [input_boolean.system_startup_phase] is off AND Bathroom lights startup protection [input_boolean.bathroom_lights_startup_protection] is off AND Bathroom main light [light.bathroom_main] is off AND (The number of unavailable lights among Bathroom spot R1 Philips [light.bathroom_spot_r1_philips], Bathroom spot R2 Philips [light.bathroom_spot_r2_philips], Bathroom spot L1 Philips [light.bathroom_spot_l1_philips], Bathroom spot C1 Philips [light.bathroom_spot_c1_philips], and Bathroom spot C2 Philips [light.bathroom_spot_c2_philips] is greater than or equal to 2). ACTIONS: Turn on Bathroom main light [light.bathroom_main] AND send a notification to master with the message: '⚠️ Включено резервное освещение в ванной. Недоступны споты.'",
|
||
"natural_language": {
|
||
"trigger": "When any of the bathroom spot lights (Bathroom spot R1 Philips [light.bathroom_spot_r1_philips], Bathroom spot R2 Philips [light.bathroom_spot_r2_philips], Bathroom spot L1 Philips [light.bathroom_spot_l1_philips], Bathroom spot C1 Philips [light.bathroom_spot_c1_philips], or Bathroom spot C2 Philips [light.bathroom_spot_c2_philips]) becomes unavailable and stays that way for 30 seconds.",
|
||
"conditions": "The system startup phase [input_boolean.system_startup_phase] must be off, the bathroom lights startup protection [input_boolean.bathroom_lights_startup_protection] must be off, the Bathroom main light [light.bathroom_main] must be off, and at least two of the five bathroom spot lights must be unavailable.",
|
||
"action": "Turns on the Bathroom main light [light.bathroom_main] and sends a notification to the master with a warning message that backup lighting has been activated in the bathroom because spot lights are unavailable."
|
||
},
|
||
"human_like": "Activates the main bathroom light as a backup if two or more spot lights become unavailable, ensuring the room remains lit.",
|
||
"complexity": "medium"
|
||
}
|
||
},
|
||
{
|
||
"id": "14a6f0ef-8217-4fc6-8dca-067875b950a7",
|
||
"result": {
|
||
"structured": "TRIGGER: When Home Assistant starts. ACTIONS: Wait 30 seconds. THEN, IF Bathroom motions [binary_sensor.bathroom_motions] is off AND remains off for 1 minute, THEN turn off Bathroom all lights group [group.bathroom_all_lights] AND Bathroom main light [light.bathroom_main].",
|
||
"natural_language": {
|
||
"trigger": "When Home Assistant starts up.",
|
||
"conditions": "After a 30-second delay, the automation checks if the Bathroom motions [binary_sensor.bathroom_motions] sensor has been reporting no motion for at least one minute.",
|
||
"action": "If the condition is met, it turns off the Bathroom all lights group [group.bathroom_all_lights] and the Bathroom main light [light.bathroom_main]."
|
||
},
|
||
"human_like": "Ensures the bathroom lights are off after a system restart if no motion has been detected there for a minute.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "048bc34f-9e6d-475c-84ed-0af54dedeed9",
|
||
"result": {
|
||
"structured": "TRIGGER: When Home Assistant starts. CONDITIONS: None. ACTIONS: Turn on Bathroom lights startup protection [input_boolean.bathroom_lights_startup_protection], wait for 5 minutes, then turn off Bathroom lights startup protection [input_boolean.bathroom_lights_startup_protection].",
|
||
"natural_language": {
|
||
"trigger": "When the Home Assistant system starts up.",
|
||
"conditions": "There are no conditions that need to be met.",
|
||
"action": "Immediately turns on the Bathroom lights startup protection [input_boolean.bathroom_lights_startup_protection], waits for five minutes, and then turns it off."
|
||
},
|
||
"human_like": "Activates a temporary protection timer for the bathroom lights for five minutes whenever Home Assistant restarts.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "a658b6fc-d264-4c6b-8185-e3b503f5a7e5",
|
||
"result": {
|
||
"structured": "TRIGGER: When Pixel 8 Pro battery level [sensor.pixel_8_pro_battery_level] remains above 99% for 1 minute. CONDITIONS: Pixel 8 Pro battery state [sensor.pixel_8_pro_battery_state] is charging AND the current time is between 01:00:00 and 07:00:00 AND System startup phase [input_boolean.system_startup_phase] is off AND Pixel 8 Pro battery level [sensor.pixel_8_pro_battery_level] is not 'unknown' or 'unavailable' AND Bedroom plug [switch.0x00158d0002530ba3] is on. ACTIONS: Turn off Bedroom plug [switch.0x00158d0002530ba3] AND write a system log message indicating the plug was turned off at night with the current battery level.",
|
||
"natural_language": {
|
||
"trigger": "When the Pixel 8 Pro battery level [sensor.pixel_8_pro_battery_level] stays above 99% for at least one minute.",
|
||
"conditions": "The Pixel 8 Pro battery state [sensor.pixel_8_pro_battery_state] must be 'charging', the current time must be between 1 AM and 7 AM, the System startup phase [input_boolean.system_startup_phase] must be off, the battery level sensor must be reporting a valid value (not 'unknown' or 'unavailable'), and the Bedroom plug [switch.0x00158d0002530ba3] must be on.",
|
||
"action": "Turns off the Bedroom plug [switch.0x00158d0002530ba3] and logs an informational message to the system log stating the charging plug was turned off at night, including the current battery level."
|
||
},
|
||
"human_like": "Automatically turns off the bedroom charging plug overnight when the Pixel 8 Pro phone is fully charged to prevent overcharging.",
|
||
"complexity": "medium"
|
||
}
|
||
},
|
||
{
|
||
"id": "9f1229c2-0ce2-4483-9953-1f6cdc6fa18e",
|
||
"result": {
|
||
"structured": "TRIGGER: When Bedroom temperature smoothed [sensor.temperatura_v_spalne_sglazhennaia] is below 20° for 1 minute. CONDITIONS: System startup phase [input_boolean.system_startup_phase] is off AND Silent mode [input_boolean.silent_mode] is off AND Bedroom contact sensor [binary_sensor.0x00158d00044d5d11_contact] is open (on) AND Someone is home [binary_sensor.someone_is_home] is on AND Bedroom temperature smoothed [sensor.temperatura_v_spalne_sglazhennaia] is not 'unknown' or 'unavailable' AND Bedroom temperature notice [input_boolean.bedroom_th_notice] is off. ACTIONS: Set variable 'message' to 'Температура в спальне ниже 20°. Динозавры любят тепло! Закройте балкон в спальне.'. IF Master person [person.master] is home, THEN send notification to master with the message AND run script Yandex TTS Temp Status [script.yandex_tts_temp_status]. THEN turn on Bedroom temperature notice [input_boolean.bedroom_th_notice]. THEN start timer Bedroom notice reset timer [timer.bedroom_th_notice_reset] for a duration in minutes defined by Low temperature notification reset period [input_number.low_th_notification_reset_period]. THEN log an info message 'Уведомление о низкой температуре в спальне отправлено (<temperature>°).'.",
|
||
"natural_language": {
|
||
"trigger": "When the smoothed bedroom temperature [sensor.temperatura_v_spalne_sglazhennaia] stays below 20 degrees for at least one minute.",
|
||
"conditions": "The system must be past its startup phase, silent mode must be off, the bedroom contact sensor [binary_sensor.0x00158d00044d5d11_contact] must report the door or window is open, someone must be home, the temperature sensor must be reporting a valid reading (not 'unknown' or 'unavailable'), and the bedroom temperature notice flag [input_boolean.bedroom_th_notice] must be off, indicating a notification hasn't been sent recently.",
|
||
"action": "The automation prepares a message about the low temperature. If the master person [person.master] is at home, it sends this message as a notification to them and also runs a text-to-speech script [script.yandex_tts_temp_status]. It then turns on the bedroom temperature notice flag to prevent repeated alerts, starts a reset timer [timer.bedroom_th_notice_reset] for a configurable period, and logs the event to the system log."
|
||
},
|
||
"human_like": "Sends a notification and a voice announcement when the bedroom gets too cold while a window or door is open and someone is home, then prevents further alerts for a while.",
|
||
"complexity": "medium"
|
||
}
|
||
},
|
||
{
|
||
"id": "fdf3d865-6bdb-4c9b-9acd-fa7f7dc432d6",
|
||
"result": {
|
||
"structured": "TRIGGER: When Bedroom notice reset timer [timer.bedroom_th_notice_reset] finishes. CONDITIONS: None. ACTIONS: Turn off Bedroom temperature notice [input_boolean.bedroom_th_notice] AND write an informational log message: 'Флаг уведомления о температуре в спальне сброшен.'.",
|
||
"natural_language": {
|
||
"trigger": "When the Bedroom notice reset timer [timer.bedroom_th_notice_reset] completes its countdown.",
|
||
"conditions": "There are no conditions for this automation.",
|
||
"action": "Turns off the Bedroom temperature notice [input_boolean.bedroom_th_notice] flag and logs an informational message stating that the bedroom temperature notice flag has been reset."
|
||
},
|
||
"human_like": "Resets the bedroom temperature notification flag after a timer expires.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "fc57ec27-9c9d-489a-8f5f-050b489466f7",
|
||
"result": {
|
||
"structured": "TRIGGER: When a single action is detected on the Hallway MQTT device [device_id:cfd464e1cbfa3da2ddd4f2109d74eb4e]. CONDITIONS: System startup phase [input_boolean.system_startup_phase] is off. ACTIONS: 1. Toggle the Hallway Light Entity [light.89add52cab26b9b6bcad7e86fd6387ec]. 2. If Hallway switch light [light.hallway_switch] is on OR Gateway light [light.gateway_light_04cf8c977cdd] is on, then start Hallway timer [timer.timer_hallway] with a duration equal to Hallway timer duration [input_number.hallway_timer_duration] (in minutes) multiplied by 60 (converted to seconds). Otherwise, cancel Hallway timer [timer.timer_hallway]. 3. Log an info message: 'Свет в прихожей toggled по кнопке.'",
|
||
"natural_language": {
|
||
"trigger": "When a single press action is detected on the MQTT button device in the hallway.",
|
||
"conditions": "The automation only runs if the system startup phase [input_boolean.system_startup_phase] is complete, meaning it is turned off.",
|
||
"action": "First, the automation toggles the main hallway light [light.89add52cab26b9b6bcad7e86fd6387ec]. Then, it checks the state of the lights: if either the Hallway switch light [light.hallway_switch] or the Gateway light [light.gateway_light_04cf8c977cdd] is on, it starts the Hallway timer [timer.timer_hallway] for a duration set by the Hallway timer duration [input_number.hallway_timer_duration] input. If neither light is on, it cancels the same timer. Finally, it writes an informational log entry stating the light was toggled by the button."
|
||
},
|
||
"human_like": "Toggles the hallway light with a button press and manages an automatic timer to turn it off, but only after the system has fully started.",
|
||
"complexity": "medium"
|
||
}
|
||
},
|
||
{
|
||
"id": "3c9a07a9-58ee-4287-87ee-734687c93bba",
|
||
"result": {
|
||
"structured": "TRIGGER: When Hallway door contact [binary_sensor.hallway_door_contact] becomes open (on) AND remains open for 5 seconds. CONDITIONS: Hallway switch light [light.hallway_switch] is off AND current time is between 08:30:00 and 23:00:00 AND System startup phase [input_boolean.system_startup_phase] is off AND Hallway door contact [binary_sensor.hallway_door_contact] state is not 'unknown', 'unavailable', or an empty string. ACTIONS: Turn on Hallway switch light [light.hallway_switch] AND start Hallway timer [timer.timer_hallway] with a duration equal to Hallway timer duration [input_number.hallway_timer_duration] value (in minutes) multiplied by 60 (converted to seconds) AND write an info log message 'Свет в прихожей включён по двери.'.",
|
||
"natural_language": {
|
||
"trigger": "When the Hallway door contact [binary_sensor.hallway_door_contact] is opened and stays open for at least 5 seconds.",
|
||
"conditions": "The Hallway switch light [light.hallway_switch] must be off, the current time must be between 8:30 AM and 11:00 PM, the System startup phase [input_boolean.system_startup_phase] must be off, and the Hallway door contact [binary_sensor.hallway_door_contact] sensor must be reporting a valid state (not 'unknown', 'unavailable', or empty).",
|
||
"action": "Turns on the Hallway switch light [light.hallway_switch], starts the Hallway timer [timer.timer_hallway] for a duration based on the Hallway timer duration [input_number.hallway_timer_duration] setting, and logs an informational message stating the light was turned on due to the door."
|
||
},
|
||
"human_like": "Automatically turns on the hallway light when the door is opened and held open for a few seconds, but only during daytime hours and if the system is not starting up.",
|
||
"complexity": "medium"
|
||
}
|
||
},
|
||
{
|
||
"id": "7f815fb8-98f4-437a-96fc-06984d9a4a25",
|
||
"result": {
|
||
"structured": "TRIGGER: When Hallway motion occupancy [binary_sensor.hallway_motion_occupancy] becomes 'on' AND remains 'on' for 10 seconds. CONDITIONS: Gateway illumination sensor [sensor.illumination_04cf8c977cdd] is below 250 AND System startup phase [input_boolean.system_startup_phase] is 'off' AND Hallway motion occupancy [binary_sensor.hallway_motion_occupancy] is not in the states 'unknown', 'unavailable', or an empty string. ACTIONS: Turn on Gateway light [light.gateway_light_04cf8c977cdd] with brightness at 7% AND Start Hallway timer [timer.timer_hallway] for a duration of (Hallway timer duration [input_number.hallway_timer_duration] multiplied by 60) seconds AND Write an info log message: 'Свет в прихожей включён по движению.'.",
|
||
"natural_language": {
|
||
"trigger": "When motion is detected by the Hallway motion occupancy [binary_sensor.hallway_motion_occupancy] and that detection persists for at least 10 seconds.",
|
||
"conditions": "The Gateway illumination sensor [sensor.illumination_04cf8c977cdd] reports a light level below 250 lux, the System startup phase [input_boolean.system_startup_phase] is off, and the motion sensor's state is valid and not reporting as 'unknown', 'unavailable', or empty.",
|
||
"action": "Turns on the Gateway light [light.gateway_light_04cf8c977cdd] at 7% brightness, starts the Hallway timer [timer.timer_hallway] for a duration calculated from the Hallway timer duration [input_number.hallway_timer_duration] setting, and logs an informational message stating the hallway light was turned on by motion."
|
||
},
|
||
"human_like": "Turns on the hallway light at a low brightness when motion is detected in low ambient light, and starts a timer to manage its duration.",
|
||
"complexity": "medium"
|
||
}
|
||
},
|
||
{
|
||
"id": "3b6e37de-3b10-4201-afad-221dbe4cd4a0",
|
||
"result": {
|
||
"structured": "TRIGGER: When Hallway motion occupancy [binary_sensor.hallway_motion_occupancy] remains off for 10 seconds. CONDITIONS: (Hallway switch light [light.hallway_switch] is on OR Gateway light [light.gateway_light_04cf8c977cdd] is on) AND Bathroom cleaning mode [input_boolean.bathroom_cleaning_mode] is off AND System startup phase [input_boolean.system_startup_phase] is off. ACTIONS: Start Hallway timer [timer.timer_hallway] with a duration calculated from Hallway timer duration [input_number.hallway_timer_duration] (value in minutes multiplied by 60) AND write a system log message 'Таймер прихожей запущен (отсутствие движения).' with level info.",
|
||
"natural_language": {
|
||
"trigger": "When the Hallway motion occupancy [binary_sensor.hallway_motion_occupancy] sensor detects no motion for a continuous period of 10 seconds.",
|
||
"conditions": "At least one of the hallway lights must be on, either the Hallway switch light [light.hallway_switch] or the Gateway light [light.gateway_light_04cf8c977cdd]. Additionally, the Bathroom cleaning mode [input_boolean.bathroom_cleaning_mode] must be off, and the System startup phase [input_boolean.system_startup_phase] must also be off.",
|
||
"action": "Starts the Hallway timer [timer.timer_hallway] for a duration specified by the Hallway timer duration [input_number.hallway_timer_duration] setting (converted from minutes to seconds) and logs an informational message stating that the hallway timer has been started due to a lack of motion."
|
||
},
|
||
"human_like": "Starts a timer to eventually turn off the hallway lights when no motion is detected, provided the system is not in a startup or cleaning mode.",
|
||
"complexity": "medium"
|
||
}
|
||
},
|
||
{
|
||
"id": "479b917d-e4c2-4149-97e7-d12779b9f3ce",
|
||
"result": {
|
||
"structured": "TRIGGER: When Hallway motion occupancy [binary_sensor.hallway_motion_occupancy] becomes on and remains on for 5 seconds. CONDITIONS: (Hallway switch light [light.hallway_switch] is on OR Gateway light [light.gateway_light_04cf8c977cdd] is on) AND System startup phase [input_boolean.system_startup_phase] is off. ACTIONS: Cancel Hallway timer [timer.timer_hallway], then start Hallway timer [timer.timer_hallway] with a duration equal to the value of Hallway timer duration [input_number.hallway_timer_duration] (in minutes) multiplied by 60 (converted to seconds), and finally log an informational message 'Таймер прихожей перезапущен (движение).'.",
|
||
"natural_language": {
|
||
"trigger": "When motion is detected by the Hallway motion occupancy [binary_sensor.hallway_motion_occupancy] and that motion state persists for at least 5 seconds.",
|
||
"conditions": "If either the Hallway switch light [light.hallway_switch] or the Gateway light [light.gateway_light_04cf8c977cdd] is currently turned on, and the System startup phase [input_boolean.system_startup_phase] is not active (i.e., is off).",
|
||
"action": "Cancels any currently running Hallway timer [timer.timer_hallway], then restarts it with a new duration. The duration is calculated by taking the number stored in Hallway timer duration [input_number.hallway_timer_duration] (which is in minutes), multiplying it by 60 to convert to seconds, and using that value. Finally, it writes an informational log entry stating 'Таймер прихожей перезапущен (движение).' (Hallway timer restarted (motion))."
|
||
},
|
||
"human_like": "Restarts the hallway light timer when new motion is detected, but only if the lights are already on and the system is not in its startup phase.",
|
||
"complexity": "medium"
|
||
}
|
||
},
|
||
{
|
||
"id": "7f6bdbae-a73b-4509-8db8-43f71a3525ca",
|
||
"result": {
|
||
"structured": "TRIGGER: When Hallway timer [timer.timer_hallway] finishes. CONDITIONS: Bathroom cleaning mode [input_boolean.bathroom_cleaning_mode] is off. ACTIONS: Turn off Hallway switch light [light.hallway_switch] AND Turn off Gateway light [light.gateway_light_04cf8c977cdd] AND Log an informational message: 'Свет в прихожей выключен по таймеру.'.",
|
||
"natural_language": {
|
||
"trigger": "When the Hallway timer [timer.timer_hallway] finishes.",
|
||
"conditions": "The Bathroom cleaning mode [input_boolean.bathroom_cleaning_mode] must be turned off.",
|
||
"action": "Turns off both the Hallway switch light [light.hallway_switch] and the Gateway light [light.gateway_light_04cf8c977cdd], and logs an informational message stating that the hallway light has been turned off by the timer."
|
||
},
|
||
"human_like": "Automatically turns off the hallway lights when a timer finishes, but only if the bathroom cleaning mode is not active.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "first-door-home-automation",
|
||
"result": {
|
||
"structured": "TRIGGER: When Hallway door contact [binary_sensor.hallway_door_contact] becomes open (on) AND remains open for 5 seconds. CONDITIONS: Hallway first door open [input_boolean.hallway_first_door_open] is off AND Master person [person.master] is home AND (Current time minus Master person [person.master] last_changed timestamp is less than 600 seconds) AND System startup phase [input_boolean.system_startup_phase] is off AND Hallway door contact [binary_sensor.hallway_door_contact] state is not unknown, unavailable, or empty. ACTIONS: Turn on Hallway switch light [light.hallway_switch] AND Turn on Gateway light [light.gateway_light_04cf8c977cdd] with brightness at 100% AND Turn on Hallway first door open [input_boolean.hallway_first_door_open] AND Start Hallway timer [timer.timer_hallway] with duration equal to (Hallway timer duration [input_number.hallway_timer_duration] value multiplied by 60) seconds AND Write a system log message 'Свет в прихожей включён при первом входе.' with level info.",
|
||
"natural_language": {
|
||
"trigger": "When the Hallway door contact [binary_sensor.hallway_door_contact] opens and stays open for at least 5 seconds.",
|
||
"conditions": "The Hallway first door open [input_boolean.hallway_first_door_open] must be off, indicating this is the first door opening since arrival. The Master person [person.master] must be at home. The Master person [person.master] must have arrived home less than 10 minutes ago. The System startup phase [input_boolean.system_startup_phase] must be off, meaning the system is not in its initial startup period. The Hallway door contact [binary_sensor.hallway_door_contact] sensor must be reporting a valid state and not be unknown or unavailable.",
|
||
"action": "Turn on the Hallway switch light [light.hallway_switch]. Turn on the Gateway light [light.gateway_light_04cf8c977cdd] at full brightness. Turn on the Hallway first door open [input_boolean.hallway_first_door_open] to mark that the first door opening has been processed. Start the Hallway timer [timer.timer_hallway] for a duration calculated from the Hallway timer duration [input_number.hallway_timer_duration] setting. Write an informational message to the system log stating that the hallway light was turned on upon first entry."
|
||
},
|
||
"human_like": "Turns on the hallway lights when the door is opened for the first time after someone arrives home, provided they have been home for less than 10 minutes.",
|
||
"complexity": "medium"
|
||
}
|
||
},
|
||
{
|
||
"id": "reset-first-door-flag",
|
||
"result": {
|
||
"structured": "TRIGGER: When Master person [person.master] changes state to not_home. CONDITIONS: None. ACTIONS: Turn off Hallway first door open [input_boolean.hallway_first_door_open] AND write a system log entry with message 'Флаг первого открытия двери сброшен (ушёл из дома).' and level 'info'.",
|
||
"natural_language": {
|
||
"trigger": "When the Master person [person.master] leaves the home, indicated by their state changing to 'not_home'.",
|
||
"conditions": "There are no conditions for this automation.",
|
||
"action": "Turns off the Hallway first door open [input_boolean.hallway_first_door_open] flag and logs an informational message stating 'Флаг первого открытия двери сброшен (ушёл из дома).' (First door opening flag reset (left home))."
|
||
},
|
||
"human_like": "Resets the 'first door open' flag when the master person leaves the home.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "37a7b942-71ea-456e-8f9e-1718c8c34a8d",
|
||
"result": {
|
||
"structured": "TRIGGER: When Outdoor button MQTT device [device_id: d2c3001cdc59660c456de45aec09da91] sends a single action via MQTT. CONDITIONS: System startup phase [input_boolean.system_startup_phase] is off AND Silent mode [input_boolean.silent_mode] is off AND Someone is home [binary_sensor.someone_is_home] is on. ACTIONS: 1. Store whether Working room LED [light.working_room_led] was on in variable 'was_on_led'. 2. Execute script Yandex TTS Click Outdoor Button [script.yandex_tts_click_outdoor_button]. 3. Repeat the following sequence a number of times equal to the integer value of Hallway blink count [input_number.hallway_blink_count]: a. Turn on Gateway light [light.gateway_light_04cf8c977cdd] AND Working room LED [light.working_room_led]. b. Wait 1 second. c. Turn off Gateway light [light.gateway_light_04cf8c977cdd] AND Working room LED [light.working_room_led]. d. Wait 1 second. 4. If 'was_on_led' is true, turn on Working room LED [light.working_room_led]; otherwise, turn it off. 5. Log an informational message: 'Обработан звонок в дверь (мигание выполнено).'",
|
||
"natural_language": {
|
||
"trigger": "When the outdoor button MQTT device is pressed, sending a single action signal.",
|
||
"conditions": "The system must not be in its startup phase, silent mode must be disabled, and at least one person must be detected as being home.",
|
||
"action": "First, the automation checks and remembers if the Working room LED was on. It then triggers a Yandex TTS script, likely to announce the doorbell press. Next, it makes the Gateway light in the hallway and the Working room LED blink on and off. The number of blinks is determined by the 'Hallway blink count' setting. After the blinking sequence, it restores the Working room LED to its original state (on if it was on before, off if it was off). Finally, it logs a message confirming the doorbell press was processed."
|
||
},
|
||
"human_like": "Announces a doorbell press via voice and makes lights blink when someone is home and the system is in normal mode.",
|
||
"complexity": "medium"
|
||
}
|
||
},
|
||
{
|
||
"id": "26345165-2c00-489c-af7b-c4b92110c937",
|
||
"result": {
|
||
"structured": "TRIGGER: When the Outdoor button MQTT device [device_id: d2c3001cdc59660c456de45aec09da91] detects a shake action. CONDITIONS: System startup phase [input_boolean.system_startup_phase] is off AND Silent mode [input_boolean.silent_mode] is off. ACTIONS: Execute the Yandex TTS Shaking Outdoor Button [script.yandex_tts_shaking_outdoor_button] script, send a Telegram notification via master with the message '⚠️ Внимание! Входную кнопку пытаются снять 🛑', and write a warning log entry with the message 'Обнаружена попытка снятия входной кнопки.'.",
|
||
"natural_language": {
|
||
"trigger": "When the Outdoor button MQTT device detects a shake action, indicating someone is trying to remove it.",
|
||
"conditions": "The system must not be in its startup phase, meaning the System startup phase [input_boolean.system_startup_phase] is off, and the Silent mode [input_boolean.silent_mode] must also be off.",
|
||
"action": "The automation will play a text-to-speech announcement using the Yandex TTS Shaking Outdoor Button [script.yandex_tts_shaking_outdoor_button] script, send a Telegram alert to the master with a warning message, and log a warning message to the system log."
|
||
},
|
||
"human_like": "Sends an audible and Telegram alert when the outdoor button is shaken, indicating a possible tampering attempt, provided the system is fully started and not in silent mode.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "b29835d5-9911-47ec-8630-2adda70be854",
|
||
"result": {
|
||
"structured": "TRIGGER: When Bathroom MQTT switch device [device_id: cc6ef89720abb376a24e910e13f37902] sends action 'single_right' OR When Kitchen scenic switch device [device_id: 719cda594198c3eafa3817b9230f2afa] sends action '1_single' OR When Kitchen scenic switch device [device_id: 719cda594198c3eafa3817b9230f2afa] sends action '2_single'. CONDITIONS: System startup phase [input_boolean.system_startup_phase] is off. ACTIONS: If triggered by 'kitchen_switch_right', toggle Kitchen Main Light Entity [6ecc35aae49d8307be87809073a32233]. If triggered by 'scenic_1_single', toggle Kitchen fartuh light [light.kitchen_fartuh]. If triggered by 'scenic_2_single', toggle Kitchen main light [light.kitchen_main_light].",
|
||
"natural_language": {
|
||
"trigger": "When the right button on the Bathroom MQTT switch device [device_id: cc6ef89720abb376a24e910e13f37902] is pressed, or when button '1_single' on the Kitchen scenic switch device [device_id: 719cda594198c3eafa3817b9230f2afa] is pressed, or when button '2_single' on the Kitchen scenic switch device [device_id: 719cda594198c3eafa3817b9230f2afa] is pressed.",
|
||
"conditions": "The automation only runs if the System startup phase [input_boolean.system_startup_phase] is turned off.",
|
||
"action": "Depending on which button was pressed, a different light is toggled. Pressing the right button on the bathroom switch toggles the Kitchen Main Light Entity [6ecc35aae49d8307be87809073a32233]. Pressing the '1_single' button on the scenic switch toggles the Kitchen fartuh light [light.kitchen_fartuh]. Pressing the '2_single' button on the scenic switch toggles the Kitchen main light [light.kitchen_main_light]."
|
||
},
|
||
"human_like": "Controls the kitchen's main and accent lighting using different physical switches, ensuring the system is fully booted before responding.",
|
||
"complexity": "medium"
|
||
}
|
||
},
|
||
{
|
||
"id": "dc8af8f7-c0f5-4244-867b-00fc546039ba",
|
||
"result": {
|
||
"structured": "TRIGGER: When Kitchen need ventilation [binary_sensor.kitchen_need_ventilation] changes from off to on. CONDITIONS: Kitchen fan cool down [input_boolean.kitchen_fan_cool_down] is off AND Kitchen notification cooldown timer [timer.kitchen_notification_cooldown_timer] is idle AND System startup phase [input_boolean.system_startup_phase] is off AND Silent mode [input_boolean.silent_mode] is off. ACTIONS: Execute script Yandex TTS Kitchen Fan Alert [script.yandex_tts_kitchen_fan_alert], turn on Kitchen fan cool down [input_boolean.kitchen_fan_cool_down], and start Kitchen notification cooldown timer [timer.kitchen_notification_cooldown_timer] for a duration calculated from Kitchen notification cooldown minutes [input_number.kitchen_notification_cooldown_min] (default 30 minutes).",
|
||
"natural_language": {
|
||
"trigger": "When the Kitchen need ventilation [binary_sensor.kitchen_need_ventilation] sensor indicates that ventilation is needed by changing its state from off to on.",
|
||
"conditions": "The automation only runs if the Kitchen fan cool down [input_boolean.kitchen_fan_cool_down] flag is off, the Kitchen notification cooldown timer [timer.kitchen_notification_cooldown_timer] is not running, the System startup phase [input_boolean.system_startup_phase] is complete, and the Silent mode [input_boolean.silent_mode] is not active.",
|
||
"action": "It plays a voice alert using the Yandex TTS Kitchen Fan Alert [script.yandex_tts_kitchen_fan_alert] script, sets the Kitchen fan cool down [input_boolean.kitchen_fan_cool_down] flag to on to prevent immediate repeats, and starts the Kitchen notification cooldown timer [timer.kitchen_notification_cooldown_timer] for a configurable period to enforce a longer delay before the next alert."
|
||
},
|
||
"human_like": "Announces a reminder to turn on the kitchen fan when needed, but only if the system is ready and similar alerts haven't been sent recently.",
|
||
"complexity": "medium"
|
||
}
|
||
},
|
||
{
|
||
"id": "8b7c3a73-7d74-4e6f-b1d5-4a9c1e3a9c12",
|
||
"result": {
|
||
"structured": "TRIGGER: When Kitchen need ventilation [binary_sensor.kitchen_need_ventilation] changes from on to off. CONDITIONS: None. ACTIONS: Turn off Kitchen fan cool down [input_boolean.kitchen_fan_cool_down].",
|
||
"natural_language": {
|
||
"trigger": "When the Kitchen need ventilation [binary_sensor.kitchen_need_ventilation] sensor changes its state from 'on' to 'off'.",
|
||
"conditions": "There are no conditions that must be met.",
|
||
"action": "Turns off the Kitchen fan cool down [input_boolean.kitchen_fan_cool_down] flag."
|
||
},
|
||
"human_like": "Resets the kitchen fan cool-down warning when ventilation is no longer needed.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "10f4f44c-a559-4281-9a1b-18aac1fd845b",
|
||
"result": {
|
||
"structured": "TRIGGER: When Home Assistant starts. CONDITIONS: Kitchen need ventilation [binary_sensor.kitchen_need_ventilation] is off. ACTIONS: Turn off Kitchen fan cool down [input_boolean.kitchen_fan_cool_down].",
|
||
"natural_language": {
|
||
"trigger": "When Home Assistant starts up.",
|
||
"conditions": "If the Kitchen need ventilation [binary_sensor.kitchen_need_ventilation] sensor is off.",
|
||
"action": "Turns off the Kitchen fan cool down [input_boolean.kitchen_fan_cool_down] flag."
|
||
},
|
||
"human_like": "Resets the kitchen fan cool-down flag when Home Assistant restarts, provided ventilation is not needed.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "e2d5d614-46cf-4706-9bfe-7a17cd81f0c1",
|
||
"result": {
|
||
"structured": "TRIGGER: When Kitchen need ventilation [binary_sensor.kitchen_need_ventilation] changes from off to on AND remains on for 1 minute. CONDITIONS: System startup phase [input_boolean.system_startup_phase] is off AND Kitchen fan switch [switch.sonoff_10024c81be] is off. ACTIONS: Turn on Kitchen fan switch [switch.sonoff_10024c81be].",
|
||
"natural_language": {
|
||
"trigger": "When the Kitchen need ventilation [binary_sensor.kitchen_need_ventilation] sensor turns on and stays on for one full minute.",
|
||
"conditions": "The system must not be in its startup phase, meaning System startup phase [input_boolean.system_startup_phase] is off. Also, the Kitchen fan switch [switch.sonoff_10024c81be] must already be off to avoid turning it on again unnecessarily.",
|
||
"action": "Turns on the Kitchen fan switch [switch.sonoff_10024c81be]."
|
||
},
|
||
"human_like": "Automatically turns on the kitchen ventilation fan when the air quality sensor indicates a sustained need for fresh air.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "d2986069-fb9c-4425-afc7-1b17f96cfff3",
|
||
"result": {
|
||
"structured": "TRIGGER: When Kitchen need ventilation [binary_sensor.kitchen_need_ventilation] changes from on to off. CONDITIONS: Kitchen fan switch [switch.sonoff_10024c81be] is on. ACTIONS: Start Kitchen fan delay timer [timer.kitchen_fan_delay_timer] with a duration equal to the value of Kitchen fan delay minutes [input_number.kitchen_fan_delay_min] (in minutes) converted to seconds.",
|
||
"natural_language": {
|
||
"trigger": "When the Kitchen need ventilation [binary_sensor.kitchen_need_ventilation] sensor changes from 'needs ventilation' to 'does not need ventilation'.",
|
||
"conditions": "The Kitchen fan switch [switch.sonoff_10024c81be] must be turned on.",
|
||
"action": "Starts the Kitchen fan delay timer [timer.kitchen_fan_delay_timer], setting its duration based on the number of minutes configured in Kitchen fan delay minutes [input_number.kitchen_fan_delay_min]."
|
||
},
|
||
"human_like": "Starts a delay timer for the kitchen fan when ventilation is no longer needed, allowing it to run for a configurable extra period before turning off.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "95fecbf7-3ac8-4b4a-a7a8-a857a307be68",
|
||
"result": {
|
||
"structured": "TRIGGER: When Kitchen fan delay timer [timer.kitchen_fan_delay_timer] finishes. CONDITIONS: Kitchen need ventilation [binary_sensor.kitchen_need_ventilation] is off. ACTIONS: Turn off Kitchen fan switch [switch.sonoff_10024c81be].",
|
||
"natural_language": {
|
||
"trigger": "When the Kitchen fan delay timer [timer.kitchen_fan_delay_timer] completes its countdown.",
|
||
"conditions": "If the Kitchen need ventilation [binary_sensor.kitchen_need_ventilation] sensor indicates that ventilation is not required (is off).",
|
||
"action": "Turns off the Kitchen fan switch [switch.sonoff_10024c81be]."
|
||
},
|
||
"human_like": "Turns off the kitchen fan when its delay timer finishes, but only if the kitchen doesn't currently need ventilation.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "b44e93fc-7746-4ff5-8846-2d350fecb813",
|
||
"result": {
|
||
"structured": "TRIGGER: When Living room ventilation need [binary_sensor.livingroom_ventilation_need] turns on. CONDITIONS: CO2 voice notification sensor [input_boolean.co2_voice_notification_sensor] is off AND System startup phase [input_boolean.system_startup_phase] is off. ACTIONS: Choose based on conditions: IF (Silent mode [input_boolean.silent_mode] is off AND Master person [person.master] is home) THEN execute Yandex TTS CO2 Alert [script.yandex_tts_co2_alert]. ELSE IF (Silent mode [input_boolean.silent_mode] is on AND Master person [person.master] is home) THEN send a notification to master with message 'Уровень CO2 превышает норму. Рекомендуется проветрить гостиную.'. THEN, regardless of the choice outcome, turn on CO2 voice notification sensor [input_boolean.co2_voice_notification_sensor].",
|
||
"natural_language": {
|
||
"trigger": "When the Living room ventilation need [binary_sensor.livingroom_ventilation_need] sensor indicates that ventilation is required by turning on.",
|
||
"conditions": "The automation runs only if the CO2 voice notification sensor [input_boolean.co2_voice_notification_sensor] is currently off, and the System startup phase [input_boolean.system_startup_phase] is also off.",
|
||
"action": "If the Silent mode [input_boolean.silent_mode] is off and the Master person [person.master] is at home, a voice alert is played using the Yandex TTS CO2 Alert [script.yandex_tts_co2_alert] script. If Silent mode [input_boolean.silent_mode] is on but the Master person is still home, a silent text notification is sent to the master with the message 'Уровень CO2 превышает норму. Рекомендуется проветрить гостиную.'. After performing one of these notification actions, the automation turns on the CO2 voice notification sensor [input_boolean.co2_voice_notification_sensor] to flag that a notification has been sent."
|
||
},
|
||
"human_like": "Sends a voice or text alert when the CO2 level in the living room is too high and ventilation is needed, but only if the system is fully started and no recent alert has been sent.",
|
||
"complexity": "medium"
|
||
}
|
||
},
|
||
{
|
||
"id": "31a294d7-4c2d-4289-a8b0-04f2cea38553",
|
||
"result": {
|
||
"structured": "TRIGGER: When Living room ventilation status [binary_sensor.livingroom_ventilation_status] changes from off to on AND remains on for 1 minute. CONDITIONS: CO2 text notification sensor [input_boolean.co2_text_notification_sensor] is off AND System startup phase [input_boolean.system_startup_phase] is off. ACTIONS: (IF Silent mode [input_boolean.silent_mode] is off AND Master person [person.master] is home THEN execute Yandex TTS CO2 Normal [script.yandex_tts_co2_normal]) OR (IF Silent mode [input_boolean.silent_mode] is on AND Master person [person.master] is home THEN send notification to master with message 'Проветривание завершено. Уровень CO2 в норме.'). THEN turn on CO2 text notification sensor [input_boolean.co2_text_notification_sensor].",
|
||
"natural_language": {
|
||
"trigger": "When the Living room ventilation status [binary_sensor.livingroom_ventilation_status] turns on and stays on for one minute.",
|
||
"conditions": "The CO2 text notification sensor [input_boolean.co2_text_notification_sensor] must be off, and the System startup phase [input_boolean.system_startup_phase] must be off.",
|
||
"action": "If silent mode is off and the Master person [person.master] is at home, a text-to-speech announcement is played via the Yandex TTS CO2 Normal [script.yandex_tts_co2_normal] script. If silent mode is on and the Master person [person.master] is at home, a text notification is sent to the master with the message 'Проветривание завершено. Уровень CO2 в норме.' (Ventilation completed. CO2 level is normal.). Finally, the CO2 text notification sensor [input_boolean.co2_text_notification_sensor] is turned on."
|
||
},
|
||
"human_like": "Notifies the user when ventilation is complete and CO2 levels are back to normal, using either a voice announcement or a silent text message depending on the current mode.",
|
||
"complexity": "medium"
|
||
}
|
||
},
|
||
{
|
||
"id": "469fe5d8-4b48-40bb-b967-0d09a83ee4f0",
|
||
"result": {
|
||
"structured": "TRIGGER: When CO2 voice notification sensor [input_boolean.co2_voice_notification_sensor] turns on OR when CO2 text notification sensor [input_boolean.co2_text_notification_sensor] turns on. CONDITIONS: None. ACTIONS: Wait for a delay of X minutes, where X is the integer value of CO2 notification reset period [input_number.co2_notification_reset_period], then turn off CO2 voice notification sensor [input_boolean.co2_voice_notification_sensor] AND turn off CO2 text notification sensor [input_boolean.co2_text_notification_sensor].",
|
||
"natural_language": {
|
||
"trigger": "When either the CO2 voice notification sensor [input_boolean.co2_voice_notification_sensor] or the CO2 text notification sensor [input_boolean.co2_text_notification_sensor] is turned on.",
|
||
"conditions": "There are no conditions that must be met for the action to run.",
|
||
"action": "After waiting for a period of time defined by the CO2 notification reset period [input_number.co2_notification_reset_period] (in minutes), the automation turns off both the CO2 voice notification sensor [input_boolean.co2_voice_notification_sensor] and the CO2 text notification sensor [input_boolean.co2_text_notification_sensor]."
|
||
},
|
||
"human_like": "Automatically resets CO2 notification flags after a configurable delay when they are activated.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "9fff2de3-f169-4fda-8a8a-91966fc51f13",
|
||
"result": {
|
||
"structured": "TRIGGER: When Kitchen scenic switch device [device_id:719cda594198c3eafa3817b9230f2afa] sends an MQTT action for button 4 single press. CONDITIONS: None. ACTIONS: Toggle Living room scone dimmer [light.livingroom_scone_dimmer].",
|
||
"natural_language": {
|
||
"trigger": "When the Kitchen scenic switch device [device_id:719cda594198c3eafa3817b9230f2afa] detects a single press of its fourth button.",
|
||
"conditions": "There are no conditions.",
|
||
"action": "Toggle the Living room scone dimmer [light.livingroom_scone_dimmer] on or off."
|
||
},
|
||
"human_like": "Toggles the living room sconce light on or off when button 4 on the kitchen switch is pressed once.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "54ea7c3d-a37d-4ce4-80ff-f2da00a450c2",
|
||
"result": {
|
||
"structured": "TRIGGER: When Kitchen scenic switch device [device_id:719cda594198c3eafa3817b9230f2afa] sends an MQTT action of type '3_single'. CONDITIONS: None. ACTIONS: Toggle Living room main switch left [light.livingroom_main_switch_left].",
|
||
"natural_language": {
|
||
"trigger": "When the Kitchen scenic switch device [device_id:719cda594198c3eafa3817b9230f2afa] reports a single press of button 3 via MQTT.",
|
||
"conditions": "There are no conditions for this automation.",
|
||
"action": "Toggles the state of the Living room main switch left [light.livingroom_main_switch_left] light, turning it on if it was off, or off if it was on."
|
||
},
|
||
"human_like": "Toggles the living room main light when button 3 on the kitchen switch is pressed once.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "916eb0c3-eee6-409d-9ce2-4dc00c9f7051",
|
||
"result": {
|
||
"structured": "TRIGGER: When Kitchen scenic switch device [device_id: 719cda594198c3eafa3817b9230f2afa] sends an MQTT action for button 4 double press. CONDITIONS: None. ACTIONS: Toggle Living room main switch right [light.livingroom_main_switch_right].",
|
||
"natural_language": {
|
||
"trigger": "When the Kitchen scenic switch device [device_id: 719cda594198c3eafa3817b9230f2afa] detects a double press on its button 4.",
|
||
"conditions": "There are no conditions that must be met.",
|
||
"action": "Toggles the state of the Living room main switch right [light.livingroom_main_switch_right] light, turning it on if it's off, or off if it's on."
|
||
},
|
||
"human_like": "Double-pressing button 4 on the kitchen switch toggles the right main light in the living room.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "f4e42442-155e-4d0a-87c2-3f21fd72025d",
|
||
"result": {
|
||
"structured": "TRIGGER: When Doors in kitchen living room [binary_sensor.doors_in_kitchen_livingroom] becomes open (on) AND remains open for 1 minute. CONDITIONS: None. ACTIONS: (IF Air conditioner [climate.konditsioner] is NOT off AND Winter mode [input_boolean.winter_mode] is off THEN turn on Door open climate pre state [input_boolean.door_open_climate_pre_state] AND turn off Air conditioner [climate.konditsioner]) AND (IF Zhimi fan switch [switch.zhimi_mb3_a5d3_switch_status] is on THEN turn on Door open fan pre state [input_boolean.door_open_fan_pre_state] AND turn off Zhimi fan switch [switch.zhimi_mb3_a5d3_switch_status]) AND (IF Evolution humidifier [switch.evolution_hf_878] is on THEN turn on Door open humidifier pre state [input_boolean.door_open_humidifier_pre_state] AND turn off Evolution humidifier [switch.evolution_hf_878]).",
|
||
"natural_language": {
|
||
"trigger": "When the Doors in kitchen living room [binary_sensor.doors_in_kitchen_livingroom] sensor indicates the door is open and remains in that state for one minute.",
|
||
"conditions": "There are no conditions that must be met for the automation to proceed.",
|
||
"action": "The automation performs three independent checks and actions. First, if the Air conditioner [climate.konditsioner] is not turned off and the Winter mode [input_boolean.winter_mode] is disabled, it will turn on the Door open climate pre state [input_boolean.door_open_climate_pre_state] and then turn off the air conditioner. Second, if the Zhimi fan switch [switch.zhimi_mb3_a5d3_switch_status] is on, it will turn on the Door open fan pre state [input_boolean.door_open_fan_pre_state] and turn off the fan. Third, if the Evolution humidifier [switch.evolution_hf_878] is on, it will turn on the Door open humidifier pre state [input_boolean.door_open_humidifier_pre_state] and turn off the humidifier."
|
||
},
|
||
"human_like": "Turns off the air conditioner, fan, and humidifier in the living room if the door has been open for a minute, but only if they were on, and remembers their previous state for later restoration.",
|
||
"complexity": "medium"
|
||
}
|
||
},
|
||
{
|
||
"id": "0347cae6-1b2f-436a-a54c-792feafa9620",
|
||
"result": {
|
||
"structured": "TRIGGER: When Doors in kitchen living room [binary_sensor.doors_in_kitchen_livingroom] becomes closed (off). CONDITIONS: None. ACTIONS: (IF Door open climate pre state [input_boolean.door_open_climate_pre_state] is on AND Winter mode [input_boolean.winter_mode] is off THEN turn on Air conditioner [climate.konditsioner]) AND (IF Door open fan pre state [input_boolean.door_open_fan_pre_state] is on THEN turn on Zhimi fan switch [switch.zhimi_mb3_a5d3_switch_status]) AND (IF Door open humidifier pre state [input_boolean.door_open_humidifier_pre_state] is on THEN turn on Evolution humidifier [switch.evolution_hf_878]) AND turn off Door open climate pre state [input_boolean.door_open_climate_pre_state], Door open fan pre state [input_boolean.door_open_fan_pre_state], and Door open humidifier pre state [input_boolean.door_open_humidifier_pre_state].",
|
||
"natural_language": {
|
||
"trigger": "When the Doors in kitchen living room [binary_sensor.doors_in_kitchen_livingroom] sensor indicates the door is closed.",
|
||
"conditions": "There are no conditions that must be met before proceeding with the actions.",
|
||
"action": "The automation performs a series of checks and actions. First, if the Door open climate pre state [input_boolean.door_open_climate_pre_state] is on and the Winter mode [input_boolean.winter_mode] is off, it turns on the Air conditioner [climate.konditsioner]. Second, if the Door open fan pre state [input_boolean.door_open_fan_pre_state] is on, it turns on the Zhimi fan switch [switch.zhimi_mb3_a5d3_switch_status]. Third, if the Door open humidifier pre state [input_boolean.door_open_humidifier_pre_state] is on, it turns on the Evolution humidifier [switch.evolution_hf_878]. Finally, it turns off all three pre-state indicators: Door open climate pre state [input_boolean.door_open_climate_pre_state], Door open fan pre state [input_boolean.door_open_fan_pre_state], and Door open humidifier pre state [input_boolean.door_open_humidifier_pre_state]."
|
||
},
|
||
"human_like": "Restores the air conditioner, fan, and humidifier in the living room to their previous on states when the door is closed, provided winter mode is not active for the air conditioner.",
|
||
"complexity": "medium"
|
||
}
|
||
},
|
||
{
|
||
"id": "b9867c28-be9f-425e-9fee-0aea777d04c0",
|
||
"result": {
|
||
"structured": "TRIGGER: When Air conditioner [climate.konditsioner] changes state from 'off'. CONDITIONS: Winter mode [input_boolean.winter_mode] is 'on'. ACTIONS: Turn off Air conditioner [climate.konditsioner], send notification to master with message 'Кондиционер принудительно отключён: включён Зимний режим.', and execute Yandex TTS Kondicioner Warning [script.yandex_tts_kondicioner_warning].",
|
||
"natural_language": {
|
||
"trigger": "Whenever the Air conditioner [climate.konditsioner] is turned on from an off state.",
|
||
"conditions": "The Winter mode [input_boolean.winter_mode] must be active (set to on).",
|
||
"action": "Immediately turn the Air conditioner [climate.konditsioner] back off, send a notification to the master device stating 'Кондиционер принудительно отключён: включён Зимний режим.', and run the Yandex TTS Kondicioner Warning [script.yandex_tts_kondicioner_warning] script."
|
||
},
|
||
"human_like": "Prevents the air conditioner from running when Winter Mode is active by turning it off and sending a warning if someone tries to turn it on.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "4d19ce98-16f7-41ea-afcf-34ffb4e64b4a",
|
||
"result": {
|
||
"structured": "TRIGGER: When Air conditioner filter remaining life [sensor.konditsioner_filter_remaining_life] remains below 10% for 1 minute. CONDITIONS: System startup phase [input_boolean.system_startup_phase] is off AND Silent mode [input_boolean.silent_mode] is off AND Filter replace notified [input_boolean.filter_replace_notified] is off AND current time is between 08:00:00 and 20:00:00. ACTIONS: Send a notification via notify.master with message 'Необходимо заменить фильтр в кондиционере' AND turn on Filter replace notified [input_boolean.filter_replace_notified].",
|
||
"natural_language": {
|
||
"trigger": "When the Air conditioner filter remaining life [sensor.konditsioner_filter_remaining_life] sensor reports a value below 10% for at least one minute.",
|
||
"conditions": "The system must not be in its startup phase, silent mode must be off, the filter replacement notification must not have already been sent, and the current time must be between 8:00 AM and 8:00 PM.",
|
||
"action": "Sends a Telegram notification stating 'Необходимо заменить фильтр в кондиционере' and then marks the notification as sent by turning on the Filter replace notified [input_boolean.filter_replace_notified] switch."
|
||
},
|
||
"human_like": "Sends a daytime Telegram reminder to replace the air conditioner filter when its remaining life falls below 10%, ensuring it only notifies once and respects system quiet hours.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "da15cbba-b4f0-42e5-8bcd-5e9affe17073",
|
||
"result": {
|
||
"structured": "TRIGGER: When Air conditioner filter remaining life [sensor.konditsioner_filter_remaining_life] is above 10% for 1 minute. CONDITIONS: None. ACTIONS: Turn off Filter replace notified [input_boolean.filter_replace_notified].",
|
||
"natural_language": {
|
||
"trigger": "When the Air conditioner filter remaining life [sensor.konditsioner_filter_remaining_life] sensor reports a value above 10% for at least one minute.",
|
||
"conditions": "There are no conditions for this automation.",
|
||
"action": "Resets the notification flag by turning off Filter replace notified [input_boolean.filter_replace_notified]."
|
||
},
|
||
"human_like": "Resets the filter replacement notification when the air conditioner's filter life improves back above 10%.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "12858001-138d-4238-97f9-e5a501c6fe18",
|
||
"result": {
|
||
"structured": "TRIGGER: When Multi outlet left [switch.my_multi_outlet_left] OR Multi outlet right [switch.my_multi_outlet_right] becomes unavailable AND remains unavailable for 1 minute. CONDITIONS: System startup phase [input_boolean.system_startup_phase] is off AND Silent mode [input_boolean.silent_mode] is off AND Someone is home [binary_sensor.someone_is_home] is on. ACTIONS: Send a notification to the master notification target with a message containing the triggered entity ID AND write a warning log entry.",
|
||
"natural_language": {
|
||
"trigger": "When either the Multi outlet left [switch.my_multi_outlet_left] or the Multi outlet right [switch.my_multi_outlet_right] becomes unavailable and stays in that state for at least one minute.",
|
||
"conditions": "The system must not be in its startup phase, silent mode must be turned off, and at least one person must be at home.",
|
||
"action": "Sends a notification to the master notification target, warning that the specific outlet is unavailable, possibly due to a power outage or UPS issue. It also logs a warning message to the system log."
|
||
},
|
||
"human_like": "Sends an alert when a smart outlet becomes unavailable for a minute, indicating a possible power cut or UPS problem, but only if the system is fully started, silent mode is off, and someone is home.",
|
||
"complexity": "medium"
|
||
}
|
||
},
|
||
{
|
||
"id": "server_room_fan_control",
|
||
"result": {
|
||
"structured": "TRIGGER: When Server temperature high [binary_sensor.server_temp_high] changes from off to on OR When Server temperature high [binary_sensor.server_temp_high] changes from on to off. CONDITIONS: System startup phase [input_boolean.system_startup_phase] is off AND Server temperature sensor [sensor.0xa4c13861a18df7c8_temperature] is not 'unknown' AND not 'unavailable'. ACTIONS: IF trigger is high THEN cancel Server temp off persist timer [timer.server_temp_off_persist] AND cancel Server fan delay timer [timer.server_fan_delay] AND turn on Server fan [fan.server_fan] AND log an info message. IF trigger is low AND Server fan [fan.server_fan] is on THEN start Server temp off persist timer [timer.server_temp_off_persist] with a duration of (Server temp off persist minutes [input_number.server_temp_off_persist_min] value * 60) seconds AND log an info message.",
|
||
"natural_language": {
|
||
"trigger": "When the Server temperature high [binary_sensor.server_temp_high] sensor changes state, either from off to on (indicating high temperature) or from on to off (indicating low temperature).",
|
||
"conditions": "The system must not be in its startup phase, meaning System startup phase [input_boolean.system_startup_phase] is off. Also, the raw temperature sensor, Server temperature sensor [sensor.0xa4c13861a18df7c8_temperature], must be reporting a valid reading and not be in an 'unknown' or 'unavailable' state.",
|
||
"action": "If the trigger was the temperature becoming high, the automation cancels two timers (Server temp off persist timer [timer.server_temp_off_persist] and Server fan delay timer [timer.server_fan_delay]), turns on the Server fan [fan.server_fan], and logs an informational message. If the trigger was the temperature becoming low and the fan is currently on, the automation starts the Server temp off persist timer [timer.server_temp_off_persist] for a duration calculated from the Server temp off persist minutes [input_number.server_temp_off_persist_min] setting and logs a message about starting the low-temperature confirmation timer."
|
||
},
|
||
"human_like": "Controls the server room fan based on temperature, turning it on immediately when it gets hot and starting a confirmation timer when it cools down before potentially turning it off.",
|
||
"complexity": "medium"
|
||
}
|
||
},
|
||
{
|
||
"id": "server_temp_off_persist_finished",
|
||
"result": {
|
||
"structured": "TRIGGER: When Server temp off persist timer [timer.server_temp_off_persist] finishes. CONDITIONS: Server temperature high [binary_sensor.server_temp_high] is off AND Server fan [fan.server_fan] is on. ACTIONS: Start Server fan delay timer [timer.server_fan_delay] for a duration calculated from Server fan delay minutes [input_number.server_fan_delay_min] (default 5 minutes) AND write an info log message.",
|
||
"natural_language": {
|
||
"trigger": "When the Server temp off persist timer [timer.server_temp_off_persist] finishes.",
|
||
"conditions": "The Server temperature high [binary_sensor.server_temp_high] sensor must be off, indicating a low temperature, and the Server fan [fan.server_fan] must be currently on.",
|
||
"action": "Starts the Server fan delay timer [timer.server_fan_delay] for a duration specified by the Server fan delay minutes [input_number.server_fan_delay_min] setting (defaulting to 5 minutes) and logs an informational message about starting the fan delay timer."
|
||
},
|
||
"human_like": "After a low server temperature is confirmed, this automation starts a delay timer before turning off the server fan.",
|
||
"complexity": "medium"
|
||
}
|
||
},
|
||
{
|
||
"id": "server_fan_delay_off",
|
||
"result": {
|
||
"structured": "TRIGGER: When Server fan delay timer [timer.server_fan_delay] finishes. CONDITIONS: Server temperature high [binary_sensor.server_temp_high] is off. ACTIONS: Turn off Server fan [fan.server_fan] AND write a system log message containing the current temperature from sensor.0xa4c13861a18df7c8_temperature.",
|
||
"natural_language": {
|
||
"trigger": "When the Server fan delay timer [timer.server_fan_delay] completes.",
|
||
"conditions": "The Server temperature high [binary_sensor.server_temp_high] sensor must indicate that the temperature is not high (i.e., it is in the 'off' state).",
|
||
"action": "Turns off the Server fan [fan.server_fan] and logs an informational message to the system log, which includes the current temperature reading from the sensor.0xa4c13861a18df7c8_temperature."
|
||
},
|
||
"human_like": "Turns off the server fan after a timer expires, but only if the server temperature is still low.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "29873ab9-335c-4c39-9898-b01b5a482606",
|
||
"result": {
|
||
"structured": "TRIGGER: When the physical button on device Workroom LED button device [device_id: 8067572bca7252311fc2ce6152f90f34] is pressed once (single action). CONDITIONS: None. ACTIONS: Toggle (switch on/off) the light Working room LED [light.working_room_led].",
|
||
"natural_language": {
|
||
"trigger": "When the physical button associated with the Workroom LED button device [device_id: 8067572bca7252311fc2ce6152f90f34] is pressed once.",
|
||
"conditions": "There are no conditions for this automation.",
|
||
"action": "Toggles the state of the Working room LED [light.working_room_led], turning it on if it's off, or off if it's on."
|
||
},
|
||
"human_like": "A single press of a physical button toggles the desk lighting in the working room on or off.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "abe6206a-a428-4b31-928f-789c38355279",
|
||
"result": {
|
||
"structured": "TRIGGER: When Workroom temperature average [sensor.srednee_znachenie_temperatury_v_masterskoi_2] remains below 20 for 1 minute. CONDITIONS: Workroom balcony contact [binary_sensor.masterskaia_balkon_contact] is on AND System startup phase [input_boolean.system_startup_phase] is off AND Workroom temperature notice [input_boolean.workroom_th_notice] is off AND (Workroom temperature average [sensor.srednee_znachenie_temperatury_v_masterskoi_2] is not unknown AND not unavailable AND Workroom balcony contact [binary_sensor.masterskaia_balkon_contact] is not unknown AND not unavailable). ACTIONS: Set variable telegram_message to 'Температура в мастерской ниже 20°. Это мастерская, а не холодильник! Закройте дверь.'. THEN, choose: IF Silent mode [input_boolean.silent_mode] is off AND Master person [person.master] is home, THEN play text announcement on Yandex station [media_player.yandex_station_ff98f0294437799304d0788d]. ELSE IF Silent mode [input_boolean.silent_mode] is on AND Master person [person.master] is home, THEN send notification to master with telegram_message. FINALLY, turn on Workroom temperature notice [input_boolean.workroom_th_notice] AND write a system log entry.",
|
||
"natural_language": {
|
||
"trigger": "When the average temperature in the workroom [sensor.srednee_znachenie_temperatury_v_masterskoi_2] stays below 20 degrees for at least one minute.",
|
||
"conditions": "The workroom balcony door must be open [binary_sensor.masterskaia_balkon_contact], the system must be past its startup phase [input_boolean.system_startup_phase], a previous temperature notice must not be active [input_boolean.workroom_th_notice], and both the temperature sensor and the balcony door sensor must be reporting valid, non-error states.",
|
||
"action": "First, a message is prepared. Then, depending on the system's silent mode setting and whether the master is home, the automation either announces the message via a Yandex smart speaker [media_player.yandex_station_ff98f0294437799304d0788d] or sends a silent notification. Afterwards, it turns on a flag [input_boolean.workroom_th_notice] to prevent repeated alerts and logs the event."
|
||
},
|
||
"human_like": "Notifies the user when the workroom gets too cold, assuming the balcony door is open, by either announcing it out loud or sending a quiet message.",
|
||
"complexity": "medium"
|
||
}
|
||
},
|
||
{
|
||
"id": "9bdeb719-0792-4176-8451-367273fdbb4c",
|
||
"result": {
|
||
"structured": "TRIGGER: When Workroom temperature notice [input_boolean.workroom_th_notice] turns on. ACTIONS: Wait for a delay period defined by the value of Low temperature notification reset period [input_number.low_th_notification_reset_period] (in minutes). Then, turn off Workroom temperature notice [input_boolean.workroom_th_notice].",
|
||
"natural_language": {
|
||
"trigger": "When the Workroom temperature notice [input_boolean.workroom_th_notice] is turned on.",
|
||
"conditions": "There are no conditions for this automation.",
|
||
"action": "After waiting for a period of time specified by the Low temperature notification reset period [input_number.low_th_notification_reset_period] (in minutes), the automation will turn off the Workroom temperature notice [input_boolean.workroom_th_notice]."
|
||
},
|
||
"human_like": "Automatically clears the temperature alert for the workroom after a configurable delay.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "set_telegram_allowed_users_on_start",
|
||
"result": {
|
||
"structured": "TRIGGER: When Home Assistant starts. CONDITIONS: None. ACTIONS: Set the value of Telegram allowed users [input_text.telegram_allowed_users] to 'secret telegram_allowed_users_list'.",
|
||
"natural_language": {
|
||
"trigger": "When the Home Assistant system starts up.",
|
||
"conditions": "There are no conditions that must be met.",
|
||
"action": "Sets the value of the Telegram allowed users [input_text.telegram_allowed_users] input text field to 'secret telegram_allowed_users_list'."
|
||
},
|
||
"human_like": "Initializes the list of allowed Telegram users when Home Assistant starts.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "telegram_bot_start",
|
||
"result": {
|
||
"structured": "TRIGGER: When a Telegram command event with command '/start' occurs. CONDITIONS: System startup phase [input_boolean.system_startup_phase] is off. ACTIONS: Send an HTML-formatted welcome message to the Telegram chat ID from the trigger, execute the Send Main Menu [script.send_main_menu] script targeting the same chat ID, and write an informational system log entry noting the bot start and the user ID from the trigger.",
|
||
"natural_language": {
|
||
"trigger": "When a user sends the '/start' command to the Telegram bot.",
|
||
"conditions": "The system must not be in its startup phase, meaning the System startup phase [input_boolean.system_startup_phase] is turned off.",
|
||
"action": "Sends a welcome message in HTML format to the user's Telegram chat, then runs the Send Main Menu [script.send_main_menu] script to present the main menu, and finally logs an informational message to the system log recording the bot's activation and the user's ID."
|
||
},
|
||
"human_like": "Sends a welcome message and the main menu to a user when they start the Telegram bot, but only after the system has fully started up.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "telegram_bot_main_menu",
|
||
"result": {
|
||
"structured": "TRIGGER: When a Telegram command event with command '/main_menu' is received. CONDITIONS: System startup phase [input_boolean.system_startup_phase] is off. ACTIONS: Execute script Send Main Menu [script.send_main_menu] with the chat_id from the trigger event data.",
|
||
"natural_language": {
|
||
"trigger": "When a user sends the '/main_menu' command via Telegram.",
|
||
"conditions": "The system startup phase [input_boolean.system_startup_phase] must be off, indicating the system is fully initialized.",
|
||
"action": "Sends the main menu interface to the user's Telegram chat by running the Send Main Menu [script.send_main_menu] script."
|
||
},
|
||
"human_like": "Sends the main menu to a Telegram user when they request it, but only after the system has finished starting up.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "telegram_bot_menu_back",
|
||
"result": {
|
||
"structured": "TRIGGER: When a Telegram callback event occurs with data '/menu_back'. CONDITIONS: System startup phase [input_boolean.system_startup_phase] is off. ACTIONS: Delete the Telegram message identified by the trigger's message_id and chat_id, then execute the script Send Main Menu [script.send_main_menu] targeting the same chat_id.",
|
||
"natural_language": {
|
||
"trigger": "When a user interacts with a Telegram bot and selects the 'back' option from a menu, generating a callback event with the specific data '/menu_back'.",
|
||
"conditions": "The automation only runs if the System startup phase [input_boolean.system_startup_phase] is not active, meaning the system has finished its initial startup process.",
|
||
"action": "The bot deletes the message containing the menu that the user interacted with, and then sends the main menu interface to the user in the same chat."
|
||
},
|
||
"human_like": "Handles the 'back' button in the Telegram bot by removing the current menu and showing the main menu, but only after the system has fully started.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "telegram_bot_livingroom_control",
|
||
"result": {
|
||
"structured": "TRIGGER: When a Telegram callback event with data '/livingroom_control' is received. CONDITIONS: System startup phase [input_boolean.system_startup_phase] is off. ACTIONS: Delete the Telegram message that triggered the event, then run the Send Living Room Status [script.send_livingroom_status] script, targeting the chat where the event originated.",
|
||
"natural_language": {
|
||
"trigger": "When a user interacts with a Telegram bot and selects the '/livingroom_control' callback option.",
|
||
"conditions": "The automation only runs if the System startup phase [input_boolean.system_startup_phase] is off, meaning the system is not in its initial startup sequence.",
|
||
"action": "First, the bot deletes the original message that triggered the callback. Then, it executes the Send Living Room Status [script.send_livingroom_status] script, sending the status information to the same chat."
|
||
},
|
||
"human_like": "When a user selects the living room control option in Telegram, this automation clears the menu message and sends the current status of the living room.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "telegram_bot_workroom_control",
|
||
"result": {
|
||
"structured": "TRIGGER: When a Telegram callback event with data '/workroom_control' is received. CONDITIONS: System startup phase [input_boolean.system_startup_phase] is off. ACTIONS: Delete the original Telegram message using the chat_id and message_id from the trigger event, then execute the Send Workroom Status [script.send_workroom_status] script, passing the chat_id from the trigger event as the target.",
|
||
"natural_language": {
|
||
"trigger": "When a user interacts with a Telegram bot and selects the '/workroom_control' callback option.",
|
||
"conditions": "The system must be fully started, meaning the System startup phase [input_boolean.system_startup_phase] is turned off.",
|
||
"action": "The automation deletes the original menu message from the Telegram chat and then runs the Send Workroom Status [script.send_workroom_status] script, sending the status information back to the same chat."
|
||
},
|
||
"human_like": "Handles a Telegram menu request for workroom controls, sending the current status after confirming the system is ready.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "telegram_bot_bedroom_control",
|
||
"result": {
|
||
"structured": "TRIGGER: When a Telegram callback event occurs with data '/bedroom_control'. CONDITIONS: System startup phase [input_boolean.system_startup_phase] is off. ACTIONS: Delete the Telegram message that triggered the event, then execute the Send Bedroom Status [script.send_bedroom_status] script, targeting the chat from the trigger.",
|
||
"natural_language": {
|
||
"trigger": "When a user interacts with a Telegram bot and selects the '/bedroom_control' callback option.",
|
||
"conditions": "The automation only runs if the System startup phase [input_boolean.system_startup_phase] is off, meaning the system is not in its initial startup phase.",
|
||
"action": "First, the automation deletes the original Telegram message that initiated the callback. Then, it runs the Send Bedroom Status [script.send_bedroom_status] script, sending the bedroom status information to the same Telegram chat."
|
||
},
|
||
"human_like": "Responds to a Telegram menu selection by deleting the request message and sending the current bedroom status to the user.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "telegram_bot_kitchen_control",
|
||
"result": {
|
||
"structured": "TRIGGER: When a Telegram callback event occurs with data '/kitchen_control'. CONDITIONS: System startup phase [input_boolean.system_startup_phase] is off. ACTIONS: Delete the Telegram message that triggered the event AND execute the Send Kitchen Status [script.send_kitchen_status] script, targeting the chat where the event originated.",
|
||
"natural_language": {
|
||
"trigger": "When a user interacts with a Telegram bot by pressing a button or selecting a menu option that sends the callback data '/kitchen_control'.",
|
||
"conditions": "The system must be out of its startup phase, meaning the System startup phase [input_boolean.system_startup_phase] is turned off.",
|
||
"action": "The automation first deletes the original Telegram message that contained the interactive element. Then, it runs the Send Kitchen Status [script.send_kitchen_status] script, sending its output to the same Telegram chat."
|
||
},
|
||
"human_like": "Responds to a Telegram menu command by clearing the request and sending the current kitchen status.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "telegram_bot_bathroom_control",
|
||
"result": {
|
||
"structured": "TRIGGER: When a Telegram callback event with data '/bathroom_control' is received. CONDITIONS: System startup phase [input_boolean.system_startup_phase] is off. ACTIONS: Delete the original Telegram message using its message_id and chat_id from the trigger event, then execute the script Send Bathroom Status [script.send_bathroom_status] targeting the chat_id from the trigger event.",
|
||
"natural_language": {
|
||
"trigger": "When a user interacts with a Telegram bot by pressing a button or sending a callback with the command '/bathroom_control'.",
|
||
"conditions": "The automation only runs if the System startup phase [input_boolean.system_startup_phase] is off, meaning the system is not in its initial startup sequence.",
|
||
"action": "The automation first deletes the original Telegram message that triggered the callback, then runs the Send Bathroom Status [script.send_bathroom_status] script to send updated information back to the same Telegram chat."
|
||
},
|
||
"human_like": "Handles a Telegram bot request for bathroom control by deleting the request message and sending the current bathroom status.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "telegram_bot_hallway_control",
|
||
"result": {
|
||
"structured": "TRIGGER: When a Telegram callback event with data '/hallway_control' is received. CONDITIONS: System startup phase [input_boolean.system_startup_phase] is off. ACTIONS: Delete the Telegram message that triggered the event, then execute the script Send Hallway Status [script.send_hallway_status] targeting the chat where the event originated.",
|
||
"natural_language": {
|
||
"trigger": "When a user interacts with a Telegram bot by pressing a button or selecting a menu option that sends the callback data '/hallway_control'.",
|
||
"conditions": "The automation only runs if the System startup phase [input_boolean.system_startup_phase] is off, meaning the system is not currently in its initial startup sequence.",
|
||
"action": "First, the Telegram message that triggered this automation is deleted. Then, the script named Send Hallway Status [script.send_hallway_status] is run, sending status information back to the same Telegram chat."
|
||
},
|
||
"human_like": "Responds to a Telegram menu command for hallway control by deleting the command message and sending the current hallway status, but only after the system has fully started.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "telegram_bot_system_control",
|
||
"result": {
|
||
"structured": "TRIGGER: When a Telegram callback event with data '/system_control' is received. CONDITIONS: System startup phase [input_boolean.system_startup_phase] is off. ACTIONS: Delete the original Telegram message using the message_id and chat_id from the trigger event AND execute the script Send System Status [script.send_system_status] with the target chat_id from the trigger event.",
|
||
"natural_language": {
|
||
"trigger": "When a user interacts with a Telegram bot and selects the '/system_control' callback option.",
|
||
"conditions": "The system must not be in its startup phase, meaning the System startup phase [input_boolean.system_startup_phase] is turned off.",
|
||
"action": "The automation deletes the original message that initiated the callback from the Telegram chat and then runs the Send System Status [script.send_system_status] script, sending the system status information back to the same chat."
|
||
},
|
||
"human_like": "Responds to a Telegram bot command by deleting the request message and sending the current system status, but only after the system has fully started up.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "telegram_bot_toggle_livingroom_main_switch_left",
|
||
"result": {
|
||
"structured": "TRIGGER: When a Telegram callback event occurs with data '/toggle_livingroom_main_switch_left'. CONDITIONS: System startup phase [input_boolean.system_startup_phase] is off. ACTIONS: Execute the script Toggle Device [script.toggle_device] with parameters: entity set to Living room main switch left [light.livingroom_main_switch_left], domain set to 'light', menu_script set to Send Living Room Status [script.send_livingroom_status], message_id set to the triggering event's message ID, chat_id set to the triggering event's chat ID, and user_id set to the triggering event's user ID.",
|
||
"natural_language": {
|
||
"trigger": "When a specific Telegram callback event is received, containing the command '/toggle_livingroom_main_switch_left'.",
|
||
"conditions": "The automation only runs if the System startup phase [input_boolean.system_startup_phase] is turned off, indicating the system is not in its initial startup phase.",
|
||
"action": "It runs the Toggle Device [script.toggle_device] script to toggle the state of the Living room main switch left [light.livingroom_main_switch_left] light. It also passes along details from the Telegram event, like the message, chat, and user IDs, and specifies that the Send Living Room Status [script.send_livingroom_status] script should be used for the menu response."
|
||
},
|
||
"human_like": "Toggles the left main living room light via a Telegram command, but only after the system has fully started up.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "telegram_bot_toggle_livingroom_main_switch_right",
|
||
"result": {
|
||
"structured": "TRIGGER: When a Telegram callback event occurs with data '/toggle_livingroom_main_switch_right'. CONDITIONS: System startup phase [input_boolean.system_startup_phase] is off. ACTIONS: Execute the script Toggle Device [script.toggle_device] with parameters: entity set to Living room main switch right [light.livingroom_main_switch_right], domain set to light, menu_script set to Send Living Room Status [script.send_livingroom_status], message_id set to the Telegram message ID, chat_id set to the Telegram chat ID, and user_id set to the Telegram user ID.",
|
||
"natural_language": {
|
||
"trigger": "When a specific Telegram callback event is received, containing the command '/toggle_livingroom_main_switch_right'.",
|
||
"conditions": "The system must be out of its startup phase, meaning the System startup phase [input_boolean.system_startup_phase] is turned off.",
|
||
"action": "Runs the Toggle Device [script.toggle_device] script to toggle the state of the Living room main switch right [light.livingroom_main_switch_right] light. The script is provided with the Telegram message details and is instructed to use the Send Living Room Status [script.send_livingroom_status] script for menu updates."
|
||
},
|
||
"human_like": "Allows toggling the right main living room light via a Telegram button, but only after the system has fully started.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "telegram_bot_toggle_livingroom_scone_dimmer",
|
||
"result": {
|
||
"structured": "TRIGGER: When a Telegram callback event occurs with data '/toggle_livingroom_scone_dimmer'. CONDITIONS: System startup phase [input_boolean.system_startup_phase] is off. ACTIONS: Execute script Toggle Device [script.toggle_device] with parameters: entity = light.livingroom_scone_dimmer, domain = light, menu_script = script.send_livingroom_status, message_id = trigger event message ID, chat_id = trigger event chat ID, user_id = trigger event user ID.",
|
||
"natural_language": {
|
||
"trigger": "When a specific Telegram callback event is received, containing the command '/toggle_livingroom_scone_dimmer'.",
|
||
"conditions": "The automation only runs if the System startup phase [input_boolean.system_startup_phase] is off, indicating the system is not in its initial startup phase.",
|
||
"action": "Calls the Toggle Device [script.toggle_device] script to toggle the Living room scone dimmer [light.livingroom_scone_dimmer] light. It also passes along details from the Telegram event, such as the message, chat, and user IDs, and specifies that the Send Living Room Status [script.send_livingroom_status] script should be used for the menu."
|
||
},
|
||
"human_like": "Toggles the living room scone dimmer light via a Telegram bot command when the system is fully started.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "telegram_bot_toggle_livingroom_socket_corner_r",
|
||
"result": {
|
||
"structured": "TRIGGER: When a Telegram callback event occurs with data '/toggle_livingroom_socket_corner_r'. CONDITIONS: System startup phase [input_boolean.system_startup_phase] is off. ACTIONS: Execute script Toggle Device [script.toggle_device] with parameters: entity set to Living room socket corner R [switch.livingroom_socket_corner_r], domain set to switch, menu_script set to Send Living Room Status [script.send_livingroom_status], message_id set to the Telegram message ID, chat_id set to the Telegram chat ID, and user_id set to the Telegram user ID.",
|
||
"natural_language": {
|
||
"trigger": "When a specific Telegram callback event is received, containing the command '/toggle_livingroom_socket_corner_r'.",
|
||
"conditions": "The system must be out of its startup phase, meaning the System startup phase [input_boolean.system_startup_phase] is off.",
|
||
"action": "Runs the Toggle Device [script.toggle_device] script to toggle the state of the Living room socket corner R [switch.livingroom_socket_corner_r]. It also passes along details from the Telegram event, like the message, chat, and user IDs, and specifies that the Send Living Room Status [script.send_livingroom_status] script should be used for the menu response."
|
||
},
|
||
"human_like": "Allows toggling a living room socket via a Telegram bot command, but only after the system has fully started up.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "telegram_bot_toggle_livingroom_socket_l",
|
||
"result": {
|
||
"structured": "TRIGGER: When a Telegram callback event occurs with data '/toggle_livingroom_socket_l'. CONDITIONS: System startup phase [input_boolean.system_startup_phase] is off. ACTIONS: Execute the script Toggle Device [script.toggle_device] with parameters: entity set to Living room socket L [switch.livingroom_socket_l], domain set to switch, menu_script set to Send Living Room Status [script.send_livingroom_status], message_id set to the Telegram message ID, chat_id set to the Telegram chat ID, and user_id set to the Telegram user ID.",
|
||
"natural_language": {
|
||
"trigger": "When a user interacts with a Telegram bot and selects the callback option for '/toggle_livingroom_socket_l'.",
|
||
"conditions": "The system must be past its startup phase, meaning the System startup phase [input_boolean.system_startup_phase] is turned off.",
|
||
"action": "Runs the Toggle Device [script.toggle_device] script to toggle the state of the Living room socket L [switch.livingroom_socket_l]. It also passes along details from the Telegram interaction, like the message, chat, and user IDs, and specifies that the Send Living Room Status [script.send_livingroom_status] script should be used for the menu response."
|
||
},
|
||
"human_like": "Allows you to toggle the left living room socket via a Telegram bot button, but only after the system has fully started up.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "telegram_bot_toggle_livingroom_socket_r",
|
||
"result": {
|
||
"structured": "TRIGGER: When a Telegram callback event occurs with data '/toggle_livingroom_socket_r'. CONDITIONS: System startup phase [input_boolean.system_startup_phase] is off. ACTIONS: Execute the script Toggle Device [script.toggle_device] with parameters: entity set to Living room socket R [switch.livingroom_socket_r], domain set to 'switch', menu_script set to Send Living Room Status [script.send_livingroom_status], message_id set to the Telegram message ID, chat_id set to the Telegram chat ID, and user_id set to the Telegram user ID.",
|
||
"natural_language": {
|
||
"trigger": "When a specific Telegram callback event is received, containing the command '/toggle_livingroom_socket_r'.",
|
||
"conditions": "The automation only runs if the System startup phase [input_boolean.system_startup_phase] is off, meaning the system is not in its initial startup phase.",
|
||
"action": "It runs the Toggle Device [script.toggle_device] script to toggle the Living room socket R [switch.livingroom_socket_r] switch. The script is also provided with details from the Telegram event, like the message, chat, and user IDs, and is instructed to use the Send Living Room Status [script.send_livingroom_status] script for any follow-up menu updates."
|
||
},
|
||
"human_like": "Toggles the right living room power socket via a Telegram button press, but only after the system has fully started up.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "telegram_bot_toggle_workroom_light",
|
||
"result": {
|
||
"structured": "TRIGGER: When a Telegram callback event occurs with event data containing the command '/toggle_workroom_light'. CONDITIONS: System startup phase [input_boolean.system_startup_phase] is off. ACTIONS: Execute the script Toggle Device [script.toggle_device] with parameters: entity set to Workroom switch [light.workroom_switch], domain set to light, menu_script set to Send Workroom Status [script.send_workroom_status], message_id extracted from the trigger event, chat_id extracted from the trigger event, and user_id extracted from the trigger event.",
|
||
"natural_language": {
|
||
"trigger": "When a user interacts with a Telegram bot button or command that sends the specific callback data '/toggle_workroom_light'.",
|
||
"conditions": "The system must not be in its startup phase, meaning the System startup phase [input_boolean.system_startup_phase] is turned off.",
|
||
"action": "Calls the 'Toggle Device' script to toggle the state of the Workroom switch [light.workroom_switch] light. It also passes along details from the Telegram interaction, such as the message ID, chat ID, and user ID, and specifies that the 'Send Workroom Status' script should be used for the menu response."
|
||
},
|
||
"human_like": "Allows a user to toggle the workroom light via a Telegram bot button, but only after the system has fully started up.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "telegram_bot_toggle_workroom_led",
|
||
"result": {
|
||
"structured": "TRIGGER: When a Telegram callback event occurs with data '/toggle_workroom_led'. CONDITIONS: System startup phase [input_boolean.system_startup_phase] is off. ACTIONS: Execute script Toggle Device [script.toggle_device] with parameters: entity set to Working room LED [light.working_room_led], domain set to light, menu_script set to Send Workroom Status [script.send_workroom_status], message_id set to the Telegram message ID, chat_id set to the Telegram chat ID, and user_id set to the Telegram user ID.",
|
||
"natural_language": {
|
||
"trigger": "When a specific Telegram callback event is received, containing the command '/toggle_workroom_led'.",
|
||
"conditions": "The automation only runs if the System startup phase [input_boolean.system_startup_phase] is off, meaning the system is not in its initial startup phase.",
|
||
"action": "Calls the Toggle Device [script.toggle_device] script to toggle the state of the Working room LED [light.working_room_led]. It also passes along the Telegram message ID, chat ID, and user ID from the triggering event, and specifies the Send Workroom Status [script.send_workroom_status] script to be used for a menu update."
|
||
},
|
||
"human_like": "Allows toggling the workroom LED light via a Telegram button, but only after the system has fully started up.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "telegram_bot_toggle_workroom_plug",
|
||
"result": {
|
||
"structured": "TRIGGER: When a Telegram callback event with data '/toggle_workroom_plug' is received. CONDITIONS: System startup phase [input_boolean.system_startup_phase] is off. ACTIONS: Execute the Toggle Device [script.toggle_device] script with parameters: entity set to Smart plug switch [switch.smart_plug_in_unit_vykliuchatel], domain set to 'switch', menu_script set to Send Workroom Status [script.send_workroom_status], message_id set to the triggering message ID, chat_id set to the triggering chat ID, and user_id set to the triggering user ID.",
|
||
"natural_language": {
|
||
"trigger": "When a specific Telegram callback event, containing the command '/toggle_workroom_plug', is received.",
|
||
"conditions": "The automation only runs if the System startup phase [input_boolean.system_startup_phase] is off, meaning the system is not in its initial startup phase.",
|
||
"action": "It calls the Toggle Device [script.toggle_device] script to toggle the state of the Smart plug switch [switch.smart_plug_in_unit_vykliuchatel]. The script is also provided with details from the Telegram event, such as the message, chat, and user IDs, and is instructed to use the Send Workroom Status [script.send_workroom_status] script for a follow-up menu."
|
||
},
|
||
"human_like": "Allows a user to toggle a smart plug in the workroom via a Telegram bot command, but only after the system has fully started.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "telegram_bot_toggle_bedroom_light",
|
||
"result": {
|
||
"structured": "TRIGGER: When a Telegram callback event occurs with data '/toggle_bedroom_light'. CONDITIONS: System startup phase [input_boolean.system_startup_phase] is off. ACTIONS: Execute the script Toggle Device [script.toggle_device] with data: entity 'light.bedroom_switch_main', domain 'light', menu_script 'script.send_bedroom_status', message_id from the trigger event, chat_id from the trigger event, user_id from the trigger event.",
|
||
"natural_language": {
|
||
"trigger": "When a user interacts with a Telegram bot button or command that sends the specific callback data '/toggle_bedroom_light'.",
|
||
"conditions": "The system must be out of its startup phase, meaning the System startup phase [input_boolean.system_startup_phase] is turned off.",
|
||
"action": "Runs the Toggle Device [script.toggle_device] script to toggle the Bedroom switch main [light.bedroom_switch_main] light. It also passes along information from the Telegram event, such as the message ID, chat ID, and user ID, and specifies the Send Bedroom Status [script.send_bedroom_status] script to be used for a menu update."
|
||
},
|
||
"human_like": "Toggles the main bedroom light via a Telegram bot command, but only after the system has fully started up.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "telegram_bot_toggle_bedroom_scone_t",
|
||
"result": {
|
||
"structured": "TRIGGER: When a Telegram callback event with data '/toggle_bedroom_scone_t' is received. CONDITIONS: System startup phase [input_boolean.system_startup_phase] is off. ACTIONS: Execute script Toggle Device [script.toggle_device] with parameters: entity = light.bedroom_left_switch_right, domain = light, menu_script = script.send_bedroom_status, message_id = {{ trigger.event.data.message.message_id }}, chat_id = {{ trigger.event.data.chat_id }}, user_id = {{ trigger.event.data.user_id }}.",
|
||
"natural_language": {
|
||
"trigger": "When a specific Telegram callback event is received, identified by the data '/toggle_bedroom_scone_t'.",
|
||
"conditions": "The System startup phase [input_boolean.system_startup_phase] must be off, indicating the system is not in its initial startup phase.",
|
||
"action": "Calls the Toggle Device [script.toggle_device] script to toggle the light Bedroom left switch right [light.bedroom_left_switch_right]. It also passes along Telegram-specific data like the chat ID, user ID, and message ID, and specifies that the Send Bedroom Status [script.send_bedroom_status] script should be used for the menu response."
|
||
},
|
||
"human_like": "Allows a user to toggle Tatiana's bedroom scone light via a Telegram button, but only after the system has fully started.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "telegram_bot_toggle_bedroom_scone_a_small",
|
||
"result": {
|
||
"structured": "TRIGGER: When a Telegram callback event occurs with data '/toggle_bedroom_scone_a_small'. CONDITIONS: System startup phase [input_boolean.system_startup_phase] is off. ACTIONS: Execute the script Toggle Device [script.toggle_device] with parameters: entity set to Bedroom right switch left [light.bedroom_right_switch_left], domain set to 'light', menu_script set to Send Bedroom Status [script.send_bedroom_status], message_id set to the Telegram message ID, chat_id set to the Telegram chat ID, and user_id set to the Telegram user ID.",
|
||
"natural_language": {
|
||
"trigger": "When a specific Telegram callback event is received, containing the command '/toggle_bedroom_scone_a_small'.",
|
||
"conditions": "The automation only runs if the System startup phase [input_boolean.system_startup_phase] is off, meaning the system is not in its initial startup phase.",
|
||
"action": "It calls the Toggle Device [script.toggle_device] script to toggle the state of the Bedroom right switch left [light.bedroom_right_switch_left] light. It also passes along details from the Telegram event, like the message and user identifiers, and specifies that the Send Bedroom Status [script.send_bedroom_status] script should be used for the menu response."
|
||
},
|
||
"human_like": "Toggles a bedroom light via a Telegram button press, but only after the system has fully started up.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "telegram_bot_toggle_bedroom_scone_a_big",
|
||
"result": {
|
||
"structured": "TRIGGER: When a Telegram callback event occurs with data '/toggle_bedroom_scone_a_big'. CONDITIONS: System startup phase [input_boolean.system_startup_phase] is off. ACTIONS: Execute the script Toggle Device [script.toggle_device] with parameters: entity set to Bedroom right switch right [light.bedroom_right_switch_right], domain set to light, menu_script set to Send Bedroom Status [script.send_bedroom_status], message_id set to the Telegram message ID from the trigger, chat_id set to the Telegram chat ID from the trigger, and user_id set to the Telegram user ID from the trigger.",
|
||
"natural_language": {
|
||
"trigger": "When a specific Telegram callback event is received, containing the command '/toggle_bedroom_scone_a_big'.",
|
||
"conditions": "The automation only runs if the System startup phase [input_boolean.system_startup_phase] is off, indicating the system is fully started.",
|
||
"action": "It runs the Toggle Device [script.toggle_device] script to toggle the state of the Bedroom right switch right [light.bedroom_right_switch_right] light. It also passes along Telegram details like the message, chat, and user IDs, and specifies that the Send Bedroom Status [script.send_bedroom_status] script should be used for the menu response."
|
||
},
|
||
"human_like": "Toggles the big scone light in the bedroom via a Telegram button press, but only after the system has fully started.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "telegram_bot_toggle_bedroom_plug_left",
|
||
"result": {
|
||
"structured": "TRIGGER: When a Telegram callback event occurs with data '/toggle_bedroom_plug_left'. CONDITIONS: System startup phase [input_boolean.system_startup_phase] is off. ACTIONS: Execute the script Toggle Device [script.toggle_device] with parameters: entity set to Bedroom plug left [switch.0x00158d0002530bd9], domain set to 'switch', menu_script set to Send Bedroom Status [script.send_bedroom_status], message_id set to the triggering event's message ID, chat_id set to the triggering event's chat ID, and user_id set to the triggering event's user ID.",
|
||
"natural_language": {
|
||
"trigger": "When a specific Telegram callback event is received, identified by the data '/toggle_bedroom_plug_left'.",
|
||
"conditions": "The System startup phase [input_boolean.system_startup_phase] must be off, indicating the system is not in its initial startup phase.",
|
||
"action": "Runs the Toggle Device [script.toggle_device] script to toggle the state of the Bedroom plug left [switch.0x00158d0002530bd9]. It also passes along details from the Telegram event, such as the message ID, chat ID, and user ID, and specifies that the Send Bedroom Status [script.send_bedroom_status] script should be used for the menu response."
|
||
},
|
||
"human_like": "Toggles the left bedroom plug via a Telegram button press, but only after the system has fully started up.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "telegram_bot_toggle_bedroom_plug_right",
|
||
"result": {
|
||
"structured": "TRIGGER: When a Telegram callback event occurs with data '/toggle_bedroom_plug_right'. CONDITIONS: System startup phase [input_boolean.system_startup_phase] is off. ACTIONS: Execute the script Toggle Device [script.toggle_device] with parameters: entity set to Bedroom plug [switch.0x00158d0002530ba3], domain set to 'switch', menu_script set to Send Bedroom Status [script.send_bedroom_status], message_id from the trigger event, chat_id from the trigger event, and user_id from the trigger event.",
|
||
"natural_language": {
|
||
"trigger": "When a user interacts with a Telegram bot and sends a specific callback command '/toggle_bedroom_plug_right'.",
|
||
"conditions": "The system must be out of its startup phase, meaning the System startup phase [input_boolean.system_startup_phase] is turned off.",
|
||
"action": "It runs a script called Toggle Device [script.toggle_device] to toggle the state of the Bedroom plug [switch.0x00158d0002530ba3]. The script also receives additional data from the Telegram event, such as the message and user identifiers, and is instructed to use the Send Bedroom Status [script.send_bedroom_status] script for any follow-up menu actions."
|
||
},
|
||
"human_like": "Allows a user to toggle the bedroom plug on or off via a Telegram bot command, but only after the system has fully started.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "telegram_bot_toggle_kitchen_main_light",
|
||
"result": {
|
||
"structured": "TRIGGER: When a Telegram callback event occurs with data '/toggle_kitchen_main_light'. CONDITIONS: System startup phase [input_boolean.system_startup_phase] is off. ACTIONS: Execute the script Toggle Device [script.toggle_device] with parameters: entity set to Kitchen main light [light.kitchen_main_light], domain set to light, menu_script set to Send Kitchen Status [script.send_kitchen_status], message_id set to the triggering Telegram message ID, chat_id set to the triggering chat ID, and user_id set to the triggering user ID.",
|
||
"natural_language": {
|
||
"trigger": "When a specific Telegram callback event is received, containing the command '/toggle_kitchen_main_light'.",
|
||
"conditions": "The automation only runs if the System startup phase [input_boolean.system_startup_phase] is off, indicating the system is not in its initial startup phase.",
|
||
"action": "It runs the Toggle Device [script.toggle_device] script to toggle the Kitchen main light [light.kitchen_main_light], and also passes along details from the Telegram event (like the message, chat, and user IDs) to the script, along with a reference to the Send Kitchen Status [script.send_kitchen_status] script."
|
||
},
|
||
"human_like": "Allows toggling the kitchen's main light on or off via a specific Telegram button or command, but only after the system has fully started up.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "telegram_bot_toggle_kitchen_fartuh",
|
||
"result": {
|
||
"structured": "TRIGGER: When a Telegram callback event occurs with data '/toggle_kitchen_fartuh'. CONDITIONS: System startup phase [input_boolean.system_startup_phase] is off. ACTIONS: Execute the Toggle Device [script.toggle_device] script with parameters: entity set to Kitchen fartuh switch [switch.kitchen_fartuh], domain set to 'switch', menu_script set to Send Kitchen Status [script.send_kitchen_status], message_id set to the Telegram message ID, chat_id set to the Telegram chat ID, and user_id set to the Telegram user ID.",
|
||
"natural_language": {
|
||
"trigger": "When a specific button or command is pressed in a Telegram chat, identified by the callback data '/toggle_kitchen_fartuh'.",
|
||
"conditions": "The automation only runs if the System startup phase [input_boolean.system_startup_phase] is off, meaning the system is not in its initial startup sequence.",
|
||
"action": "It runs the 'Toggle Device' script, which toggles the Kitchen fartuh switch [switch.kitchen_fartuh] and uses the 'Send Kitchen Status' script to update the Telegram interface with the new state, replying to the specific message and user that triggered it."
|
||
},
|
||
"human_like": "Allows toggling the kitchen switch via a button in a Telegram chat, but only after the system has fully started up.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "telegram_bot_toggle_bathroom_light",
|
||
"result": {
|
||
"structured": "TRIGGER: When a Telegram callback event occurs with data '/toggle_bathroom_light'. CONDITIONS: System startup phase [input_boolean.system_startup_phase] is off. ACTIONS: Execute the script Toggle Device [script.toggle_device] with parameters: entity set to Bathroom light [light.light_bathroom], domain set to light, menu_script set to Send Bathroom Status [script.send_bathroom_status], and message_id, chat_id, and user_id extracted from the triggering event.",
|
||
"natural_language": {
|
||
"trigger": "When a user interacts with a Telegram bot and selects the callback option for toggling the bathroom light.",
|
||
"conditions": "The system must be past its startup phase, meaning the System startup phase [input_boolean.system_startup_phase] is turned off.",
|
||
"action": "Runs the Toggle Device [script.toggle_device] script to toggle the Bathroom light [light.light_bathroom], and provides the Send Bathroom Status [script.send_bathroom_status] script and Telegram message details for feedback."
|
||
},
|
||
"human_like": "Allows users to toggle the bathroom light via a Telegram bot button, but only after the system has fully started.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "telegram_bot_toggle_bathroom_fan",
|
||
"result": {
|
||
"structured": "TRIGGER: When a Telegram callback event occurs with data '/toggle_bathroom_fan'. CONDITIONS: System startup phase [input_boolean.system_startup_phase] is off. ACTIONS: Execute script Toggle Device [script.toggle_device] with parameters: entity = Bathroom relay fan [fan.bathroom_relay_l1], domain = fan, menu_script = Send Bathroom Status [script.send_bathroom_status], message_id = {{ trigger.event.data.message.message_id }}, chat_id = {{ trigger.event.data.chat_id }}, user_id = {{ trigger.event.data.user_id }}.",
|
||
"natural_language": {
|
||
"trigger": "When a user interacts with a Telegram bot button or command that sends the specific callback data '/toggle_bathroom_fan'.",
|
||
"conditions": "The system must not be in its startup phase, meaning the System startup phase [input_boolean.system_startup_phase] is turned off.",
|
||
"action": "Calls the Toggle Device [script.toggle_device] script to toggle the state of the Bathroom relay fan [fan.bathroom_relay_l1]. It also passes along details from the Telegram event, such as the message and user identifiers, and specifies the Send Bathroom Status [script.send_bathroom_status] script to handle any follow-up status message."
|
||
},
|
||
"human_like": "Allows you to turn the bathroom fan on or off remotely via a Telegram bot button, but only after the system has fully started up.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "telegram_bot_toggle_hallway_light",
|
||
"result": {
|
||
"structured": "TRIGGER: When a Telegram callback event occurs with data '/toggle_hallway_light'. CONDITIONS: System startup phase [input_boolean.system_startup_phase] is off. ACTIONS: Execute the script Toggle Device [script.toggle_device] with parameters: entity set to Hallway switch light [light.hallway_switch], domain set to 'light', menu_script set to Send Hallway Status [script.send_hallway_status], message_id set to the Telegram message ID, chat_id set to the Telegram chat ID, and user_id set to the Telegram user ID.",
|
||
"natural_language": {
|
||
"trigger": "When a specific Telegram callback event is received, specifically one containing the command '/toggle_hallway_light'.",
|
||
"conditions": "The automation only runs if the System startup phase [input_boolean.system_startup_phase] is off, meaning the system is not in its initial startup phase.",
|
||
"action": "It calls the Toggle Device [script.toggle_device] script to toggle the Hallway switch light [light.hallway_switch]. It also passes along information from the Telegram event, like the message, chat, and user IDs, and specifies the Send Hallway Status [script.send_hallway_status] script for a follow-up menu."
|
||
},
|
||
"human_like": "Allows you to toggle the hallway light on or off via a specific button in a Telegram bot, but only after the system has fully started.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "telegram_bot_toggle_hallway_gateway_light",
|
||
"result": {
|
||
"structured": "TRIGGER: When a Telegram callback event occurs with data '/toggle_hallway_gateway_light'. CONDITIONS: System startup phase [input_boolean.system_startup_phase] is off. ACTIONS: Execute the Toggle Device [script.toggle_device] script with parameters: entity light.gateway_light_04cf8c977cdd, domain light, menu_script script.send_hallway_status, message_id from the trigger event, chat_id from the trigger event, and user_id from the trigger event.",
|
||
"natural_language": {
|
||
"trigger": "When a specific Telegram callback event is received, containing the command '/toggle_hallway_gateway_light'.",
|
||
"conditions": "The automation only runs if the System startup phase [input_boolean.system_startup_phase] is off, meaning the system is not in its initial startup sequence.",
|
||
"action": "Calls the Toggle Device [script.toggle_device] script to toggle the state of the Gateway light [light.gateway_light_04cf8c977cdd]. It also passes along information from the Telegram event, such as the message ID, chat ID, and user ID, and specifies the Send Hallway Status [script.send_hallway_status] script to be used for a status menu."
|
||
},
|
||
"human_like": "Toggles the hallway gateway light via a Telegram command when the system is fully started.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "telegram_bot_toggle_router_socket",
|
||
"result": {
|
||
"structured": "TRIGGER: When a Telegram callback event occurs with data '/toggle_router_socket'. CONDITIONS: System startup phase [input_boolean.system_startup_phase] is off. ACTIONS: Execute the script Toggle Device [script.toggle_device] with parameters: entity set to Multi outlet left [switch.my_multi_outlet_left], domain set to 'switch', menu_script set to Send System Status [script.send_system_status], message_id set to the Telegram message ID, chat_id set to the Telegram chat ID, and user_id set to the Telegram user ID.",
|
||
"natural_language": {
|
||
"trigger": "When a specific Telegram callback event is received, specifically one containing the command '/toggle_router_socket'.",
|
||
"conditions": "The automation only runs if the System startup phase [input_boolean.system_startup_phase] is not active (i.e., it is off).",
|
||
"action": "It runs the Toggle Device [script.toggle_device] script, which will toggle the state of the Multi outlet left [switch.my_multi_outlet_left] switch. It also passes along details from the Telegram event, like the message, chat, and user IDs, and specifies that the Send System Status [script.send_system_status] script should be used for the menu."
|
||
},
|
||
"human_like": "Allows a user to toggle the router's power socket via a Telegram command, but only after the system has finished starting up.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "telegram_bot_toggle_minipc_socket",
|
||
"result": {
|
||
"structured": "TRIGGER: When a Telegram callback event occurs with data /toggle_minipc_socket. CONDITIONS: System startup phase [input_boolean.system_startup_phase] is off. ACTIONS: Execute the script Toggle Device [script.toggle_device] with parameters: entity set to Multi outlet right [switch.my_multi_outlet_right], domain set to switch, menu_script set to Send System Status [script.send_system_status], message_id set to the Telegram message ID, chat_id set to the Telegram chat ID, and user_id set to the Telegram user ID.",
|
||
"natural_language": {
|
||
"trigger": "When a user interacts with a Telegram bot and selects the callback option for toggling the MiniPC socket.",
|
||
"conditions": "The system must not be in its startup phase, meaning the System startup phase [input_boolean.system_startup_phase] is turned off.",
|
||
"action": "Calls the Toggle Device [script.toggle_device] script to toggle the state of the Multi outlet right [switch.my_multi_outlet_right] switch. It also passes along Telegram details like the message ID, chat ID, and user ID, and specifies that the Send System Status [script.send_system_status] script should be used for the menu."
|
||
},
|
||
"human_like": "Allows a user to toggle the MiniPC power socket via a Telegram bot button, but only after the system has fully started up.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "telegram_bot_toggle_bathroom_power",
|
||
"result": {
|
||
"structured": "TRIGGER: When a Telegram callback event with data '/toggle_bathroom_power' is received. CONDITIONS: System startup phase [input_boolean.system_startup_phase] is off. ACTIONS: Execute the Toggle Device [script.toggle_device] script with parameters: entity set to Bathroom main light [light.bathroom_main], domain set to 'light', menu_script set to Send System Status [script.send_system_status], message_id set to the triggering Telegram message ID, chat_id set to the triggering chat ID, and user_id set to the triggering user ID.",
|
||
"natural_language": {
|
||
"trigger": "When a specific Telegram callback command, '/toggle_bathroom_power', is received.",
|
||
"conditions": "The system must be past its startup phase, meaning the System startup phase [input_boolean.system_startup_phase] is turned off.",
|
||
"action": "Runs the 'Toggle Device' script to toggle the Bathroom main light [light.bathroom_main]. It also passes along details from the Telegram message, like the message ID, chat ID, and user ID, and specifies that the 'Send System Status' script should be used for the menu."
|
||
},
|
||
"human_like": "Allows toggling the bathroom light on or off via a specific Telegram command, but only after the system has fully started up.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "telegram_bot_toggle_silent_mode",
|
||
"result": {
|
||
"structured": "TRIGGER: When a Telegram callback event occurs with data '/toggle_silent_mode'. CONDITIONS: System startup phase [input_boolean.system_startup_phase] is off. ACTIONS: Execute the script Toggle Device [script.toggle_device] with parameters: entity as input_boolean.silent_mode, domain as input_boolean, menu_script as script.send_system_status, message_id from the trigger event, chat_id from the trigger event, and user_id from the trigger event.",
|
||
"natural_language": {
|
||
"trigger": "When a user interacts with the Telegram bot and selects the callback option for toggling silent mode.",
|
||
"conditions": "The system must be out of its startup phase, meaning the System startup phase [input_boolean.system_startup_phase] is turned off.",
|
||
"action": "Runs the Toggle Device [script.toggle_device] script to switch the Silent mode [input_boolean.silent_mode] state, and it also prepares to send a system status update via the Send System Status [script.send_system_status] script, using the Telegram message and user details from the trigger."
|
||
},
|
||
"human_like": "Allows a user to toggle the system's silent mode on or off via a Telegram bot button, but only after the system has fully started up.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "telegram_bot_toggle_force_cctv_mode",
|
||
"result": {
|
||
"structured": "TRIGGER: When a Telegram callback event occurs with data '/toggle_force_cctv_mode'. CONDITIONS: System startup phase [input_boolean.system_startup_phase] is off. ACTIONS: Execute the script Toggle Device [script.toggle_device] with parameters: entity set to Force camera off [input_boolean.force_camera_off], domain set to input_boolean, menu_script set to Send System Status [script.send_system_status], message_id set to the Telegram message ID, chat_id set to the Telegram chat ID, and user_id set to the Telegram user ID.",
|
||
"natural_language": {
|
||
"trigger": "When a specific Telegram callback command '/toggle_force_cctv_mode' is received.",
|
||
"conditions": "The system must be past its startup phase, meaning the System startup phase [input_boolean.system_startup_phase] is turned off.",
|
||
"action": "Runs the Toggle Device [script.toggle_device] script to toggle the state of the Force camera off [input_boolean.force_camera_off] switch. It also passes along Telegram details like the message, chat, and user IDs to the script, and specifies that the Send System Status [script.send_system_status] script should be used for the menu response."
|
||
},
|
||
"human_like": "Allows a user to toggle the 'Force camera off' mode via a Telegram button, but only after the system has fully started up.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "telegram_bot_confirm_reboot",
|
||
"result": {
|
||
"structured": "TRIGGER: When a Telegram callback event occurs with data '/confirm_reboot'. CONDITIONS: System startup phase [input_boolean.system_startup_phase] is off. ACTIONS: Send a Telegram message with an HTML-formatted warning and an inline keyboard containing 'Confirm' and 'Cancel' buttons to the chat ID from the trigger event, AND write a warning log entry containing the user ID from the trigger event.",
|
||
"natural_language": {
|
||
"trigger": "When a user interacts with a Telegram bot and selects the '/confirm_reboot' callback action.",
|
||
"conditions": "The system must not be in its startup phase, meaning the System startup phase [input_boolean.system_startup_phase] is turned off.",
|
||
"action": "Sends a confirmation request message via Telegram to the user who triggered it, asking them to confirm or cancel a system reboot. It also logs a warning message about the reboot request, including the user's ID."
|
||
},
|
||
"human_like": "Asks for user confirmation via Telegram before rebooting the system, ensuring the system is not currently starting up.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "telegram_bot_force_reboot",
|
||
"result": {
|
||
"structured": "TRIGGER: When a Telegram callback event with data '/force_reboot' is received. CONDITIONS: System startup phase [input_boolean.system_startup_phase] is off. ACTIONS: Send a Telegram message to the chat ID from the trigger event with the warning '⚠️ Система будет перезагружена через 5 секунд'. Wait for 5 seconds. Restart Home Assistant. Write a warning log entry stating 'Система перезагружена через Telegram (user: [user_id from trigger event])'.",
|
||
"natural_language": {
|
||
"trigger": "When a specific Telegram callback command, '/force_reboot', is received.",
|
||
"conditions": "The system must not be in its startup phase, meaning the System startup phase [input_boolean.system_startup_phase] is turned off.",
|
||
"action": "Sends a warning message to the Telegram chat that initiated the command, notifying the user the system will reboot in 5 seconds. After the delay, it restarts the Home Assistant system and logs the event with the user's ID."
|
||
},
|
||
"human_like": "Allows a user to force a system reboot via a Telegram command, sending a warning and logging the action.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "telegram_bot_pve_status_refresh",
|
||
"result": {
|
||
"structured": "TRIGGER: When a Telegram callback event occurs with data '/pve_status_refresh'. CONDITIONS: System startup phase [input_boolean.system_startup_phase] is off. ACTIONS: Delete the Telegram message that triggered the callback using its message_id and chat_id, then execute the Send PVE Status [script.send_pve_status] script, targeting the same chat_id.",
|
||
"natural_language": {
|
||
"trigger": "When a user interacts with a specific Telegram bot button or command, sending the callback data '/pve_status_refresh'.",
|
||
"conditions": "The automation only runs if the System startup phase [input_boolean.system_startup_phase] is turned off, indicating the system is not in its initial boot sequence.",
|
||
"action": "First, the automation deletes the original Telegram message that initiated the request. Then, it runs the Send PVE Status [script.send_pve_status] script to send updated Proxmox Virtual Environment status information to the same Telegram chat."
|
||
},
|
||
"human_like": "Refreshes and sends the Proxmox server status in a Telegram chat when requested, but only after the system has fully started up.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "telegram_bot_reboot_haos12",
|
||
"result": {
|
||
"structured": "TRIGGER: When a Telegram callback event occurs with data '/reboot_haos12'. CONDITIONS: System startup phase [input_boolean.system_startup_phase] is off. ACTIONS: Press QEMU HAOS12 Reboot [button.qemu_haos12_3_100_reboot], wait 5 seconds, then execute Send PVE Status [script.send_pve_status] targeting the chat ID from the trigger event.",
|
||
"natural_language": {
|
||
"trigger": "When a specific Telegram callback command '/reboot_haos12' is received.",
|
||
"conditions": "The system must not be in its startup phase, meaning System startup phase [input_boolean.system_startup_phase] is turned off.",
|
||
"action": "Press the QEMU HAOS12 Reboot [button.qemu_haos12_3_100_reboot] button, wait for 5 seconds, and then run the Send PVE Status [script.send_pve_status] script, sending its output to the Telegram chat where the command originated."
|
||
},
|
||
"human_like": "Reboots the HAOS12 virtual machine via Telegram command and then sends a status update, but only if the system is not currently starting up.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "telegram_bot_stop_mariadb",
|
||
"result": {
|
||
"structured": "TRIGGER: When a Telegram callback event with data '/stop_mariadb' is received. CONDITIONS: System startup phase [input_boolean.system_startup_phase] is off. ACTIONS: Press LXC MariaDB 101 Stop [button.lxc_mariadb_101_stop], wait for 5 seconds, then execute Send PVE Status [script.send_pve_status] targeting the chat ID from the trigger event.",
|
||
"natural_language": {
|
||
"trigger": "When a specific Telegram callback command, '/stop_mariadb', is received.",
|
||
"conditions": "The automation only runs if the System startup phase [input_boolean.system_startup_phase] is turned off.",
|
||
"action": "It presses the LXC MariaDB 101 Stop [button.lxc_mariadb_101_stop] button, waits for five seconds, and then runs the Send PVE Status [script.send_pve_status] script, sending the status to the chat where the command originated."
|
||
},
|
||
"human_like": "Stops the MariaDB server via a Telegram command and then sends a status update after a short delay.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "telegram_bot_reboot_mariadb",
|
||
"result": {
|
||
"structured": "TRIGGER: When a Telegram callback event occurs with data '/reboot_mariadb'. CONDITIONS: System startup phase [input_boolean.system_startup_phase] is off. ACTIONS: Press LXC MariaDB 101 Reboot [button.lxc_mariadb_101_reboot], wait 5 seconds, then execute Send PVE Status [script.send_pve_status] targeting the chat ID from the trigger event.",
|
||
"natural_language": {
|
||
"trigger": "When a specific Telegram callback event is received, containing the command '/reboot_mariadb'.",
|
||
"conditions": "The System startup phase [input_boolean.system_startup_phase] must be off, indicating the system is not in its initial boot sequence.",
|
||
"action": "Press the LXC MariaDB 101 Reboot [button.lxc_mariadb_101_reboot] button to reboot the container, wait for 5 seconds, and then run the Send PVE Status [script.send_pve_status] script, sending the status update to the Telegram chat where the command originated."
|
||
},
|
||
"human_like": "Reboots the MariaDB LXC container via a Telegram command and sends a status update, but only when the system is not starting up.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "telegram_bot_start_jackett",
|
||
"result": {
|
||
"structured": "TRIGGER: When a Telegram callback event occurs with data '/start_jackett'. CONDITIONS: System startup phase [input_boolean.system_startup_phase] is off. ACTIONS: Press LXC Jackett 102 Start [button.lxc_jackett_102_start], wait 5 seconds, then execute Send PVE Status [script.send_pve_status] targeting the chat ID from the trigger event.",
|
||
"natural_language": {
|
||
"trigger": "When a specific Telegram callback event is received, containing the command '/start_jackett'.",
|
||
"conditions": "The automation only runs if the System startup phase [input_boolean.system_startup_phase] is not active (i.e., it is off).",
|
||
"action": "It starts the Jackett LXC container by pressing the LXC Jackett 102 Start [button.lxc_jackett_102_start] button, waits for five seconds, and then sends a status update for the Proxmox VE system to the Telegram chat where the command originated."
|
||
},
|
||
"human_like": "Starts the Jackett container via a Telegram command and sends a status update, but only when the system is not in its startup phase.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "telegram_bot_stop_jackett",
|
||
"result": {
|
||
"structured": "TRIGGER: When a Telegram callback event occurs with data '/stop_jackett'. CONDITIONS: System startup phase [input_boolean.system_startup_phase] is off. ACTIONS: Press LXC Jackett 102 Stop [button.lxc_jackett_102_stop], wait 5 seconds, then execute Send PVE Status [script.send_pve_status] script, passing the chat_id from the trigger event as the target.",
|
||
"natural_language": {
|
||
"trigger": "When a specific Telegram callback event is received, containing the command '/stop_jackett'.",
|
||
"conditions": "The system must not be in its startup phase, meaning the System startup phase [input_boolean.system_startup_phase] is turned off.",
|
||
"action": "Press the LXC Jackett 102 Stop [button.lxc_jackett_102_stop] button, wait for five seconds, and then run the Send PVE Status [script.send_pve_status] script, sending its output to the Telegram chat that originated the command."
|
||
},
|
||
"human_like": "Stops the Jackett LXC container via a Telegram command and then sends a status update after a short delay.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "telegram_bot_reboot_jackett",
|
||
"result": {
|
||
"structured": "TRIGGER: When a Telegram callback event with data '/reboot_jackett' is received. CONDITIONS: System startup phase [input_boolean.system_startup_phase] is off. ACTIONS: Press LXC Jackett 102 Reboot [button.lxc_jackett_102_reboot], wait 5 seconds, then execute Send PVE Status [script.send_pve_status] targeting the chat ID from the trigger event.",
|
||
"natural_language": {
|
||
"trigger": "When a specific Telegram callback command '/reboot_jackett' is received.",
|
||
"conditions": "The System startup phase [input_boolean.system_startup_phase] must be off, indicating the system is not in its initial startup phase.",
|
||
"action": "Press the LXC Jackett 102 Reboot [button.lxc_jackett_102_reboot] button, wait for 5 seconds, and then run the Send PVE Status [script.send_pve_status] script, sending its output to the Telegram chat where the command originated."
|
||
},
|
||
"human_like": "Reboots the Jackett LXC container via a Telegram command and then sends a status update, but only when the system is not starting up.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "telegram_bot_start_jellyfin",
|
||
"result": {
|
||
"structured": "TRIGGER: When a Telegram callback event occurs with data '/start_jellyfin'. CONDITIONS: System startup phase [input_boolean.system_startup_phase] is off. ACTIONS: Press LXC Jellyfin 103 Start [button.lxc_jellyfin_103_start], wait 5 seconds, then execute Send PVE Status [script.send_pve_status] targeting the chat ID from the trigger event.",
|
||
"natural_language": {
|
||
"trigger": "When a Telegram callback event is received containing the command '/start_jellyfin'.",
|
||
"conditions": "The System startup phase [input_boolean.system_startup_phase] must be off.",
|
||
"action": "Press the LXC Jellyfin 103 Start [button.lxc_jellyfin_103_start] button, wait for 5 seconds, and then run the Send PVE Status [script.send_pve_status] script, sending its output to the Telegram chat where the command originated."
|
||
},
|
||
"human_like": "Starts the Jellyfin server container via a Telegram command and sends a status update after a short delay.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "telegram_bot_stop_jellyfin",
|
||
"result": {
|
||
"structured": "TRIGGER: When a Telegram callback event occurs with data '/stop_jellyfin'. CONDITIONS: System startup phase [input_boolean.system_startup_phase] is off. ACTIONS: Press the LXC Jellyfin 103 Stop [button.lxc_jellyfin_103_stop] button, wait 5 seconds, then run the Send PVE Status [script.send_pve_status] script, passing the chat_id from the trigger event data.",
|
||
"natural_language": {
|
||
"trigger": "When a specific Telegram callback event is received, containing the command '/stop_jellyfin'.",
|
||
"conditions": "The automation only runs if the System startup phase [input_boolean.system_startup_phase] is off, indicating the system is not in its initial boot sequence.",
|
||
"action": "It presses the LXC Jellyfin 103 Stop [button.lxc_jellyfin_103_stop] button to stop the Jellyfin container, waits for five seconds, and then executes the Send PVE Status [script.send_pve_status] script, sending the status update to the Telegram chat that originated the command."
|
||
},
|
||
"human_like": "Stops the Jellyfin server via Telegram command and sends a status update, but only when the system is fully booted.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "telegram_bot_reboot_jellyfin",
|
||
"result": {
|
||
"structured": "TRIGGER: When a Telegram callback event occurs with data '/reboot_jellyfin'. CONDITIONS: System startup phase [input_boolean.system_startup_phase] is off. ACTIONS: Press LXC Jellyfin 103 Reboot [button.lxc_jellyfin_103_reboot], wait 5 seconds, then run Send PVE Status [script.send_pve_status] with the chat_id from the trigger event.",
|
||
"natural_language": {
|
||
"trigger": "When a specific Telegram callback command, '/reboot_jellyfin', is received.",
|
||
"conditions": "The system must not be in its startup phase, meaning the System startup phase [input_boolean.system_startup_phase] is turned off.",
|
||
"action": "It will press the reboot button for the Jellyfin LXC container, wait five seconds, and then send a status update about the Proxmox VE system back to the Telegram chat where the command originated."
|
||
},
|
||
"human_like": "Allows rebooting the Jellyfin server via a Telegram command and then sends a status update, but only when the main system is not starting up.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "telegram_bot_start_deluge",
|
||
"result": {
|
||
"structured": "TRIGGER: When a Telegram callback event occurs with data '/start_deluge'. CONDITIONS: System startup phase [input_boolean.system_startup_phase] is off. ACTIONS: Press LXC Deluge 104 Start [button.lxc_deluge_104_start], wait 5 seconds, then execute Send PVE Status [script.send_pve_status] with the chat_id from the trigger event.",
|
||
"natural_language": {
|
||
"trigger": "When a Telegram callback event is received containing the command '/start_deluge'.",
|
||
"conditions": "The System startup phase [input_boolean.system_startup_phase] must be off.",
|
||
"action": "Press the LXC Deluge 104 Start [button.lxc_deluge_104_start] button, wait for five seconds, and then run the Send PVE Status [script.send_pve_status] script, sending the status to the chat where the Telegram command originated."
|
||
},
|
||
"human_like": "Starts the Deluge LXC container via a Telegram command and then sends a status update after a short delay.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "telegram_bot_stop_deluge",
|
||
"result": {
|
||
"structured": "TRIGGER: When a Telegram callback event occurs with data '/stop_deluge'. CONDITIONS: System startup phase [input_boolean.system_startup_phase] is off. ACTIONS: Press LXC Deluge 104 Stop [button.lxc_deluge_104_stop], wait 5 seconds, then execute Send PVE Status [script.send_pve_status] targeting the chat ID from the trigger event.",
|
||
"natural_language": {
|
||
"trigger": "When a specific Telegram callback command '/stop_deluge' is received.",
|
||
"conditions": "The system startup phase [input_boolean.system_startup_phase] must be off, indicating the system is not in its initial startup phase.",
|
||
"action": "Press the LXC Deluge 104 Stop [button.lxc_deluge_104_stop] button, wait for 5 seconds, and then run the Send PVE Status [script.send_pve_status] script, sending its output to the Telegram chat where the command originated."
|
||
},
|
||
"human_like": "Stops the Deluge LXC container via a Telegram command and then sends a status update, but only after the system has fully started up.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "telegram_bot_reboot_deluge",
|
||
"result": {
|
||
"structured": "TRIGGER: When a Telegram callback event with data '/reboot_deluge' is received. CONDITIONS: System startup phase [input_boolean.system_startup_phase] is off. ACTIONS: Press LXC Deluge 104 Reboot [button.lxc_deluge_104_reboot], wait for 5 seconds, then execute Send PVE Status [script.send_pve_status] targeting the chat ID from the trigger event.",
|
||
"natural_language": {
|
||
"trigger": "When a specific Telegram callback command, '/reboot_deluge', is received.",
|
||
"conditions": "The system must not be in its startup phase, meaning the System startup phase [input_boolean.system_startup_phase] is turned off.",
|
||
"action": "It will press the LXC Deluge 104 Reboot [button.lxc_deluge_104_reboot] button, wait for five seconds, and then run the Send PVE Status [script.send_pve_status] script, sending its output to the Telegram chat where the command originated."
|
||
},
|
||
"human_like": "Allows rebooting the Deluge LXC container via a Telegram command and then sends a status update, but only when the system is fully started.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "telegram_bot_start_torrserver",
|
||
"result": {
|
||
"structured": "TRIGGER: When a Telegram callback event occurs with data '/start_torrserver'. CONDITIONS: System startup phase [input_boolean.system_startup_phase] is off. ACTIONS: Press LXC Debian 105 Start [button.lxc_debian_105_start], wait 5 seconds, then execute Send PVE Status [script.send_pve_status] targeting the chat ID from the trigger event.",
|
||
"natural_language": {
|
||
"trigger": "When a specific Telegram callback command, '/start_torrserver', is received.",
|
||
"conditions": "The system startup phase [input_boolean.system_startup_phase] must be off, indicating the system is not in its initial boot sequence.",
|
||
"action": "Press the button for LXC Debian 105 Start [button.lxc_debian_105_start] to start the container, wait for 5 seconds, and then run the Send PVE Status [script.send_pve_status] script, sending the status to the Telegram chat where the command originated."
|
||
},
|
||
"human_like": "Starts the TorrServer LXC container via a Telegram command and then sends a status update, but only if the system is not currently starting up.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "telegram_bot_stop_torrserver",
|
||
"result": {
|
||
"structured": "TRIGGER: When a Telegram callback event with data /stop_torrserver is received. CONDITIONS: System startup phase [input_boolean.system_startup_phase] is off. ACTIONS: Press LXC Debian 105 Stop [button.lxc_debian_105_stop], wait 5 seconds, then run Send PVE Status [script.send_pve_status] with the chat_id from the trigger event.",
|
||
"natural_language": {
|
||
"trigger": "When a Telegram callback event is received containing the specific command '/stop_torrserver'.",
|
||
"conditions": "The system must not be in its startup phase, meaning the System startup phase [input_boolean.system_startup_phase] must be off.",
|
||
"action": "Press the LXC Debian 105 Stop [button.lxc_debian_105_stop] button, wait for five seconds, and then execute the Send PVE Status [script.send_pve_status] script, sending the status to the Telegram chat that originated the command."
|
||
},
|
||
"human_like": "Stops the TorrServer LXC container via a Telegram command and then sends a status update, but only if the system is not currently starting up.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "telegram_bot_reboot_torrserver",
|
||
"result": {
|
||
"structured": "TRIGGER: When a Telegram callback event occurs with data '/reboot_torrserver'. CONDITIONS: System startup phase [input_boolean.system_startup_phase] is off. ACTIONS: Press the LXC Debian 105 Reboot [button.lxc_debian_105_reboot] button, wait for 5 seconds, then execute the Send PVE Status [script.send_pve_status] script, passing the chat_id from the trigger event.",
|
||
"natural_language": {
|
||
"trigger": "When a specific Telegram callback command, '/reboot_torrserver', is received.",
|
||
"conditions": "The System startup phase [input_boolean.system_startup_phase] must be off, indicating the system is not in its initial boot sequence.",
|
||
"action": "Press the LXC Debian 105 Reboot [button.lxc_debian_105_reboot] button to restart the container, wait five seconds, and then run the Send PVE Status [script.send_pve_status] script, sending the status update to the Telegram chat that originated the command."
|
||
},
|
||
"human_like": "Allows rebooting the TorrServer LXC container via a Telegram command and then sends a status update.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "telegram_bot_start_minimserver",
|
||
"result": {
|
||
"structured": "TRIGGER: When a Telegram callback event occurs with data '/start_minimserver'. CONDITIONS: System startup phase [input_boolean.system_startup_phase] is off. ACTIONS: Press LXC Minim 107 Start [button.lxc_minim_107_start], wait 5 seconds, then run Send PVE Status [script.send_pve_status] with the chat_id from the triggering event.",
|
||
"natural_language": {
|
||
"trigger": "When a specific Telegram callback event is received, containing the command '/start_minimserver'.",
|
||
"conditions": "The automation only runs if the System startup phase [input_boolean.system_startup_phase] is off, meaning the system is not currently in its startup phase.",
|
||
"action": "It presses the LXC Minim 107 Start [button.lxc_minim_107_start] button, waits for five seconds, and then executes the Send PVE Status [script.send_pve_status] script, sending the status to the Telegram chat that originated the request."
|
||
},
|
||
"human_like": "Starts the MinimServer LXC container via a Telegram command and then sends a status update after a short delay.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "telegram_bot_stop_minimserver",
|
||
"result": {
|
||
"structured": "TRIGGER: When a Telegram callback event occurs with data '/stop_minimserver'. CONDITIONS: System startup phase [input_boolean.system_startup_phase] is off. ACTIONS: Press the LXC Minim 107 Stop [button.lxc_minim_107_stop] button, wait for 5 seconds, then execute the Send PVE Status [script.send_pve_status] script, passing the chat_id from the trigger event as the target.",
|
||
"natural_language": {
|
||
"trigger": "When a specific Telegram callback command '/stop_minimserver' is received.",
|
||
"conditions": "The system must not be in its startup phase, meaning the System startup phase [input_boolean.system_startup_phase] helper is turned off.",
|
||
"action": "It first presses the button to stop the Minim server LXC container (LXC Minim 107 Stop [button.lxc_minim_107_stop]), waits for five seconds, and then runs a script to send the Proxmox VE status (Send PVE Status [script.send_pve_status]) back to the Telegram chat where the command originated."
|
||
},
|
||
"human_like": "Stops the Minim server container via Telegram command and then sends a status update, but only when the system is fully booted.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "telegram_bot_reboot_minimserver",
|
||
"result": {
|
||
"structured": "TRIGGER: When a Telegram callback event occurs with data '/reboot_minimserver'. CONDITIONS: System startup phase [input_boolean.system_startup_phase] is off. ACTIONS: Press LXC Minim 107 Reboot [button.lxc_minim_107_reboot], wait 5 seconds, then execute Send PVE Status [script.send_pve_status] with target chat ID from the trigger event.",
|
||
"natural_language": {
|
||
"trigger": "When a Telegram callback event is received containing the specific data '/reboot_minimserver'.",
|
||
"conditions": "The system startup phase [input_boolean.system_startup_phase] must be off, indicating the system is not in its initial boot sequence.",
|
||
"action": "Press the LXC Minim 107 Reboot [button.lxc_minim_107_reboot] button, wait for five seconds, and then run the Send PVE Status [script.send_pve_status] script, sending the status to the Telegram chat that triggered the event."
|
||
},
|
||
"human_like": "Reboots the MinimServer LXC container via a Telegram command and then sends a status update, but only when the system is not starting up.",
|
||
"complexity": "low"
|
||
}
|
||
},
|
||
{
|
||
"id": "064cbd85-8d52-40ac-98bd-98164ad1434c",
|
||
"result": {
|
||
"structured": "TRIGGER: When Home Assistant shuts down OR When Home Assistant starts. CONDITIONS: None. ACTIONS: If the trigger is shutdown, then if Washing machine active [binary_sensor.washing_machine_active] is on, turn on Washing machine pre restart state [input_boolean.washing_machine_pre_restart_state]; otherwise, turn off Washing machine pre restart state [input_boolean.washing_machine_pre_restart_state]. If the trigger is start, then if Washing machine pre restart state [input_boolean.washing_machine_pre_restart_state] is on, write a warning system log message 'System start: стиральная машина была активна до перезагрузки.'; then, turn off both Washing machine running [input_boolean.washing_machine_running] and Washing machine pre restart state [input_boolean.washing_machine_pre_restart_state].",
|
||
"natural_language": {
|
||
"trigger": "When Home Assistant is shutting down or when it is starting up.",
|
||
"conditions": "There are no conditions that must be met before the actions are performed.",
|
||
"action": "On shutdown, it checks if the Washing machine active [binary_sensor.washing_machine_active] is on. If it is, it turns on the Washing machine pre restart state [input_boolean.washing_machine_pre_restart_state] to remember the machine was active. If the machine is not active, it turns off the pre restart state. On startup, it checks the saved pre restart state. If it is on, it writes a warning message to the system log stating that the washing machine was active before the restart. Regardless of the pre restart state, it then turns off both the Washing machine running [input_boolean.washing_machine_running] and the Washing machine pre restart state [input_boolean.washing_machine_pre_restart_state]."
|
||
},
|
||
"human_like": "This automation saves the washing machine's active state before a Home Assistant restart and resets its running status afterwards, logging a warning if it was active.",
|
||
"complexity": "medium"
|
||
}
|
||
},
|
||
{
|
||
"id": "04a14878-99d3-4030-a17d-bfa3c75b1f9b",
|
||
"result": {
|
||
"structured": "TRIGGER: When Washing machine power [sensor.bathroom_washing_machine_power] is above 5 watts OR When Washing machine power [sensor.bathroom_washing_machine_power] is below 5 watts for 2 minutes. CONDITIONS: Washing machine power [sensor.bathroom_washing_machine_power] is not 'unknown' or 'unavailable'. ACTIONS: IF trigger is start THEN turn on Washing machine running [input_boolean.washing_machine_running] AND set Washing machine started at [input_datetime.washing_machine_started_at] to current datetime AND log 'Стиральная машина запущена.'. ELSE IF trigger is finish AND Washing machine running [input_boolean.washing_machine_running] is on AND the elapsed time since Washing machine started at [input_datetime.washing_machine_started_at] is greater than or equal to Washing machine min cycle minutes [input_number.wm_min_cycle_min] (converted to seconds) THEN turn off Washing machine running [input_boolean.washing_machine_running] AND log 'Стиральная машина завершена.'. OTHERWISE IF trigger is finish AND Washing machine running [input_boolean.washing_machine_running] is on THEN log 'Низкая мощность обнаружена, но цикл < минимального времени — игнорируем окончание.'.",
|
||
"natural_language": {
|
||
"trigger": "The automation triggers when the power consumption of the Washing machine power [sensor.bathroom_washing_machine_power] rises above 5 watts, or when it drops and stays below 5 watts for a continuous period of 2 minutes.",
|
||
"conditions": "The automation only runs if the Washing machine power [sensor.bathroom_washing_machine_power] sensor is reporting a valid state, meaning it is not 'unknown' or 'unavailable'.",
|
||
"action": "If the trigger was the power rising above 5 watts, the automation marks the machine as running by turning on the Washing machine running [input_boolean.washing_machine_running] helper, records the current time in the Washing machine started at [input_datetime.washing_machine_started_at] helper, and logs a startup message. If the trigger was the power staying low for 2 minutes, and the machine is currently marked as running, and the elapsed time since the start is at least the minimum cycle duration defined by the Washing machine min cycle minutes [input_number.wm_min_cycle_min] helper, then it marks the machine as not running by turning off the running helper and logs a completion message. If the low-power trigger fires but the elapsed time is less than the minimum, it logs a message indicating the potential false finish is being ignored."
|
||
},
|
||
"human_like": "This automation tracks when the washing machine starts and finishes a cycle based on its power consumption, ensuring short power drops aren't mistaken for the end of a cycle.",
|
||
"complexity": "medium"
|
||
}
|
||
},
|
||
{
|
||
"id": "d1e78a7d-56c3-4d4e-b2a4-8a23f1a62a45",
|
||
"result": {
|
||
"structured": "TRIGGER: When Washing machine finished [binary_sensor.washing_machine_finished] turns on and remains on for 2 minutes. CONDITIONS: System startup phase [input_boolean.system_startup_phase] is off AND Silent mode [input_boolean.silent_mode] is off AND Someone is home [binary_sensor.someone_is_home] is on AND Washing machine running [input_boolean.washing_machine_running] is off AND (The time elapsed since the timestamp stored in Washing machine started at [input_datetime.washing_machine_started_at] is greater than or equal to the number of minutes specified in Washing machine min cycle minutes [input_number.wm_min_cycle_min] converted to seconds). ACTIONS: Execute script Yandex TTS Washing Machine Finished [script.yandex_tts_washing_machine_finished], send a Telegram notification to master with the message '🏠 Стирка закончена! 🧼', and write an info log entry 'Уведомление о завершении стирки отправлено.'.",
|
||
"natural_language": {
|
||
"trigger": "When the Washing machine finished [binary_sensor.washing_machine_finished] sensor reports the wash is finished (turns on) and stays in that state for two minutes.",
|
||
"conditions": "The system must not be in its startup phase, silent mode must be off, someone must be home, the washing machine must not be marked as currently running, and the elapsed time since the wash cycle started must be at least the minimum cycle duration configured in the system.",
|
||
"action": "Announces the completion via a Yandex Text-to-Speech script, sends a Telegram notification to the master user, and logs the event in the system log."
|
||
},
|
||
"human_like": "Announces that the laundry is finished via voice and Telegram, but only if the system is ready, someone is home, and the wash cycle was long enough.",
|
||
"complexity": "medium"
|
||
}
|
||
},
|
||
{
|
||
"id": "washing_machine_reminder_no_motion",
|
||
"result": {
|
||
"structured": "TRIGGER: When Washing machine finished [binary_sensor.washing_machine_finished] remains on for 15 minutes. CONDITIONS: System startup phase [input_boolean.system_startup_phase] is off AND Silent mode [input_boolean.silent_mode] is off AND Someone is home [binary_sensor.someone_is_home] is on AND Bathroom motions [binary_sensor.bathroom_motions] is off AND Bathroom open door [binary_sensor.bathroom_open_door] is off. ACTIONS: Execute Yandex TTS Washing Machine Reminder [script.yandex_tts_washing_machine_reminder] AND log the message 'Напоминание о стирке отправлено.' with level info.",
|
||
"natural_language": {
|
||
"trigger": "When the Washing machine finished [binary_sensor.washing_machine_finished] sensor has been in the 'on' state for a continuous period of 15 minutes.",
|
||
"conditions": "The system must not be in its startup phase, silent mode must be off, someone must be detected at home, there must be no motion in the bathroom, and the bathroom door must be closed.",
|
||
"action": "Plays a text-to-speech reminder about the washing machine and logs a confirmation message to the system log."
|
||
},
|
||
"human_like": "Sends a voice reminder about the finished washing machine when no one is in the bathroom to notice it, but only if the house is occupied and not in silent mode.",
|
||
"complexity": "medium"
|
||
}
|
||
},
|
||
{
|
||
"id": "2f26dfda-2840-424a-a840-8c4acda8eaf6",
|
||
"result": {
|
||
"structured": "TRIGGER: When a Yandex speaker event occurs with the exact message: 'С возвращением, дорогой мне человек! Я скучала без тебя!'. CONDITIONS: System startup phase [input_boolean.system_startup_phase] is off AND Silent mode [input_boolean.silent_mode] is off. ACTIONS: Turn on Bathroom light [light.light_bathroom], then wait 4 seconds, then execute script Yandex TTS PPM Status [script.yandex_tts_ppm_status], then wait 6 seconds, then execute script Yandex TTS Temp Status [script.yandex_tts_temp_status], then wait 3 seconds, then execute script Yandex TTS Humidity Status [script.yandex_tts_hum_status].",
|
||
"natural_language": {
|
||
"trigger": "When a Yandex smart speaker says the specific greeting phrase: 'С возвращением, дорогой мне человек! Я скучала без тебя!' (Welcome back, my dear person! I missed you!).",
|
||
"conditions": "The system must not be in its startup phase, meaning System startup phase [input_boolean.system_startup_phase] is off, and the Silent mode [input_boolean.silent_mode] must also be off.",
|
||
"action": "The automation turns on the Bathroom light [light.light_bathroom]. After a 4-second delay, it runs a script to announce the air quality (PPM) status via Yandex TTS. Following a 6-second pause, it announces the temperature status, and after another 3-second pause, it announces the humidity status."
|
||
},
|
||
"human_like": "When greeted by the Yandex speaker upon arrival, this automation turns on the bathroom light and then announces the air quality, temperature, and humidity in a sequence.",
|
||
"complexity": "medium"
|
||
}
|
||
},
|
||
{
|
||
"id": "661464a3-ab6d-438e-847b-f2b6ddfee59a",
|
||
"result": {
|
||
"structured": "TRIGGER: When an event of type 'yandex_speaker' occurs with the event data value 'Я буду скучать! Возвращайся быстрее'. ACTIONS: Wait for 4 seconds. Then, execute the script Yandex TTS Door Status [script.yandex_tts_door_status]. Then, turn off all lights in the group All lights group [light.all_lights]. Then, turn on all switches in the group Cameras group [group.cameras]. Then, if Master person [person.master] is at home, send a notification to master with the message 'Свет в квартире выключен! Приятной дороги!'.",
|
||
"natural_language": {
|
||
"trigger": "When a Yandex speaker event is triggered with the specific phrase 'Я буду скучать! Возвращайся быстрее'.",
|
||
"conditions": "There are no conditions that must be met before the actions run.",
|
||
"action": "After a 4-second delay, the automation runs the 'Yandex TTS Door Status' script [script.yandex_tts_door_status], turns off all lights [light.all_lights], and turns on all cameras in the 'Cameras group' [group.cameras]. If the Master person [person.master] is at home, it also sends a notification to the master with the message 'Свет в квартире выключен! Приятной дороги!'."
|
||
},
|
||
"human_like": "When a farewell phrase is spoken to a Yandex speaker, this automation turns off all lights, activates the cameras, and sends a departure notification if the master is home.",
|
||
"complexity": "medium"
|
||
}
|
||
},
|
||
{
|
||
"id": "a8c5eb07-9381-46d5-bc65-0f52dd7079a8",
|
||
"result": {
|
||
"structured": "TRIGGER: When Temperature below 20 [binary_sensor.temperature_below_20] turns on AND remains on for 1 minute. CONDITIONS: System startup phase [input_boolean.system_startup_phase] is off AND Silent mode [input_boolean.silent_mode] is off. ACTIONS: Execute script Yandex TTS Door Status [script.yandex_tts_door_status].",
|
||
"natural_language": {
|
||
"trigger": "When the Temperature below 20 [binary_sensor.temperature_below_20] sensor indicates the temperature is below 20 degrees and stays in that state for at least one minute.",
|
||
"conditions": "The system must not be in its startup phase, meaning System startup phase [input_boolean.system_startup_phase] is off, and the silent mode must be disabled, meaning Silent mode [input_boolean.silent_mode] is off.",
|
||
"action": "Runs the Yandex TTS Door Status [script.yandex_tts_door_status] script, which likely announces the temperature status via a Yandex smart speaker."
|
||
},
|
||
"human_like": "Announces via Yandex speakers when the temperature has been below 20 degrees for a minute, provided the system is fully started and silent mode is off.",
|
||
"complexity": "low"
|
||
}
|
||
}
|
||
] |