This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/maxi1134 on 2025-03-04 21:53:31+00:00.

Since i got complains that the previous list was not detailed enough, I asked Mistral to give a resume of each one by analyzing each YAML script.

It might be a tad wonky, but at a glances, it looks good!

The code is all available here:

1. broadcast_alert_in_the_house
Step 1: Store Chromecasts in variables
Two lists are created:
playing_chromecasts: List of chromecast devices that are currently playing.
non_playing_chromecasts: List of chromecast devices not currently playing.
Step 2: Lights
Retrieve a list of lights from the light group and store their current RGB values in variables.
Change all selected lights to a specific color if specified by color.
After 0.5 seconds, restore the lights to their initial state based on the stored RGB values.
Step 3: Announcements
If a message is provided (message), broadcast it using TTS (text-to-speech) across various media players.
Step 4: Music Assistant Announcements
If broadcast_url is present, play an announcement URL on specified media players using the music assistant service.
Step 5: Notifications
Send notifications to selected phones if phone_data is provided.
Step 6: TVs
If no party mode or kink party mode is active:
Broadcast image or URL to paused chromecast devices.
Pause playing chromecasts.
Description: This script broadcasts important alerts in the house by controlling lights, making announcements, sending notifications, and handling TV displays. It's designed for critical communication within the household.

2. change_received_lights_to_random_colors
Step 1: Identify Lights
Extract light entities from a selected group.
Step 2: Repeat to Change Colors
For each light in the identified list, set it to a random color using an HS (hue-saturation) value.
Description: This script changes all lights within a specific group to randomly generated colors.
3. start_visual_playlist_on_plex
Step 1: Identify Chromecasts
Retrieve all chromecast devices.
Step 2: Repeat for Each Device
If the chromecast is off and not in an occupied area:
Set its state to playing a specified Plex playlist with shuffle enabled.
Mute the device after starting playback.
Description: This script starts visual playlists on all unoccupied chromecasts, ensuring they play music or visuals from a specified library with automatic muting if no one is around.

4. non_important_broadcast_alert_in_the_house
Step 1: Store ON Lights in variables
Collect the current state and RGB values of lights that are currently on.
Step 2: Lights
If a color is specified, change all selected lights to this color temporarily.
Restore the initial states after a short delay.
Step 3: Announcements
Make announcements using TTS if a message is provided.
Step 4: TVs
Broadcast an image or URL to paused TV devices.
Description: This script handles less critical alerts by making announcements, broadcasting images/URLs on TVs, and temporarily changing light colors. It's designed for general communication within the household but not as urgent as broadcast_alert_in_the_house.

5. changes_received_lights_to_random_colors
Step 1: Identify Lights
Extract all lights from a specific group.
Step 2: Repeat to Change Colors
Set each light's color randomly using HS values.
Description: This script changes the colors of selected lights to random hues and saturations, adding visual diversity within the house.

6. start_visual_playlist_on_plex
Step 1: Identify Chromecasts
Retrieve all chromecast devices.
Step 2: Repeat for Each Device
For each device:
Check if it's off and not in an active room.
Play a specified playlist with visual effects from Plex.
Description: This script starts predefined visual playlists on unoccupied chromecasts, enhancing the ambiance of an event or activity.

7. changes_all_on_lights_to_random_colors
Step 1: Identify All On Lights
Gather all lights that are currently turned on.
Step 2: Repeat to Change Colors
Set each light's color randomly using HS values.
Description: This script changes the colors of all active lights in the house to random hues, adding a dynamic visual effect suitable for various scenarios like parties or celebrations.

8. changes_all_on_lights_to_random_pastel_colors
Step 1: Identify All On Inside Lights
Gather all inside lights that are currently turned on.
Step 2: Repeat to Change Colors
Set each light's color randomly using pastel HS values.
Description: This script changes the colors of active interior lights to random pastel hues, creating a softer and more calming visual environment.

9. generate_and_save_localai_image
Step 1: Generate Image with LocalAI
Use the specified prompt to generate an image through REST command.
Step 2: Download Generated Image
Save the generated image locally using a downloader service.
Description: This script generates and saves images according to provided prompts, using LocalAI for rendering. It's useful for creating custom visuals based on descriptions or requests.

10. generate_and_save_sd_image
Step 1: Generate Session ID with Stability AI
Request a session ID from the Stability AI API.
Step 2: Download Generated Image
Use the generated image URL to download and save it locally.
Description: This script generates and saves images using the Stability AI API, allowing for high-quality visual content creation based on prompts or descriptions.

11. changes_all_on_lights_to_warm_colors
Step 1: Identify All On Inside Lights
Gather all inside lights that are currently turned on.
Step 2: Repeat to Set Colors
Set each light's color to a warm hue using HS values.
Description: This script changes the colors of active interior lights to warm hues, creating a cozy and inviting atmosphere suitable for gatherings or relaxation.

12. changes_all_on_lights_to_warm_pale_colors
Step 1: Identify All On Inside Lights
Gather all inside lights that are currently turned on.
Step 2: Repeat to Set Colors
Set each light's color to a warm but paler hue using HS values.
Description: This script changes the colors of active interior lights to warmer, less intense hues, providing a softer and more relaxed ambiance.

13. generate_fake_white_colors
Step 1: Identify Active Lights
Gather all lights that are currently turned on and have defined RGB colors.
Step 2: Repeat to Set Colors
Set each light's color randomly using HS values to simulate white light.
Description: This script changes the colors of active lights to random hues that approximate white, creating a subtle visual effect useful for simulating natural lighting conditions.

14. in_home_defense_script
Step 1: Turn Off Automation
Stop automation scripts related to volume adjustments and speaker management.
Step 2: Activate Hubs
Turn on security horn devices located at the front and back doors.
Step 3: Start Siren
Play a siren sound across various media players in the house.
Step 4: Adjust Volume Levels
Increase volume levels of all relevant speakers to ensure maximum alertness.
Step 5: Notify Users
Send an urgent notification with a detailed security message and actions to take.
Step 6: Wait for Home Occupancy Status Change
Continue the sequence until home occupancy status changes or timeout occurs.
Step 7: Stop Siren When Vacated
Stop playing the siren sound once home is vacated.
Description: This script activates a full-scale security response in case of an intruder alert, ensuring maximum visibility and audibility through lights, sounds, notifications, and active speaker management. It's designed to handle critical security situations effectively.

15. inside_only_home_defense_script
Step 1: Turn Off Automation
Stop automation scripts related to volume adjustments.
Step 2: Start Siren
Play a siren sound across various media players inside the house.
Step 3: Adjust Volume Levels
Increase volume levels of all relevant speakers to ensure maximum alertness.
Step 4: Wait for Home Occupancy Status Change
Continue playing the siren until home occupancy status changes or timeout occurs.
Step 5: Stop Siren When Vacated
Stop playing the siren sound once home is vacated.
Description: This script activates a security response specifically inside the house, ensuring maximum alertness through sounds without affecting external areas. It's designed to handle internal security situations effectively while minimizing disturbance outside the premises.

16. start_plex_media_on_requested_player
Step 1: Identify Chromecasts
Retrieve all chromecast devices.
Step 2: Repeat for Each Device
For each device:
Check if it's off and not in an active room.
Play a specified playlist.
Description: This script starts a requested Plex media playlist on unoccupied chromecasts, ensuring that music or videos play as needed without disrupting occupied rooms. It’s useful for setting the mood with specific content in areas where no one is present.

17. set_whole_house_to_cozy_ambiance
Step 1: Set Fireplace Effect
Turn on fireplace effect for all Hue lights.
Step 2: Candle Lights Effects
Activate candle flame effects on selected wall lights.
Step 3: Patio and Office Decorative Lamp Effects
Create a soft, breathing ambiance with specific kelvin temperatures for patio and office decorative lamps.
Step 4: Start Visual Playlist
Play a visual playlist named "Fireplace Visuals" across all TVs.
Description: This script sets the whole house to a cozy ambiance by activating fireplace and candle effects on lights and playing specific visual content on TVs. It’s designed for cr...
***
Content cut off. Read original on https://old.reddit.com/r/homeassistant/comments/1j3mpca/here_are_35_of_my_ha_scripts_along_their_code/

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/DzurisHome on 2025-03-04 17:45:14+00:00.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/primoslate on 2025-03-04 17:03:15+00:00.

My wife wanted a simple way to check if everything was okay when she hears a strange noise at night, especially when I’m not home. Digging through cameras and checking motion sensors manually isn’t exactly convenient, so I built a voice-driven security check (script) that gives her a quick, natural-language update on the house.

Now, she can just ask our HA voice assistant and it:

• Checks all motion and contact sensors
• Pulls fresh snapshots from security cameras
• Runs an LLM-powered image analysis to flag anything unusual
• Reads out a simple summary of what’s going on

It’s been great for peace of mind, and it makes security feel much more accessible. I put together a video walkthrough showing how I set it up, along with the YAML if anyone wants to try something similar:

Curious if anyone else has done something similar? or if there are other ways you’re using Home Assistant plus a security system in unique ways.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/matthiasdebaat on 2025-03-04 15:53:53+00:00.

In the upcoming releases, we aim to make automation creation easier with u/jenova70. Please let us know your thoughts on our proposed solution to the issues we want to address.

Issues

Home Assistant's automation engine is one of the most powerful on the market, but this comes at a cost: It’s not the easiest to approach.

1. Triggers and conditions are hard to choose and configure

Entity and Numeric state triggers are powerful and flexible but can be challenging to understand, especially for those who are new to Home Assistant. Device triggers are easier to use, but these don't let us fully use the power of the automation editor.When we want to search on a common trigger, like motion or temperature, we won't get any results. As these are part of the State or Numerical state trigger.

2. Common triggers and conditions are complex to achieve

In order to perform seemingly easy tasks, we must understand how data flows into the internal state machine and how it is represented. For example:

• "When the target temperature of my thermostat goes above 22 degrees". Requires knowledge that this is an attribute, not a state.
• "When my front door opens". We need to understand that it's a binary_sensor, lock or cover.

3. Difficult to trigger something on a scope that is bigger than an entity

Automation is tightly coupled with the state machine. If something isn’t in the state machine, it’s difficult (or impossible) to automate. Currently, the only workaround is creating helpers to persist such data. For example:

• "When at least one light in the living room turns on". We have to create a group helper.
• "When any of my switches labeled always_on turns off". Labels are not available as trigger target. We can walk around that by creating some pretty advanced templates.
• "When presence is detected on the second floor". Areas are not available as trigger target.

Our solution

We plan to unwrap the triggers and conditions, allowing integrations to provide them. This is similar to what we did for actions. Integrations will define available triggers, conditions, and actions, which Home Assistant will then display in the automation editor. This will result in:

1. Generic triggers and conditions such as light, climate and fan. And specific such as Sonos or LG Web OS.
2. The ability to target areas, devices, and labels. Not just entities.
3. A more intuitive “Add Trigger/Condition” dialog that only shows relevant options and supports search.

With these improvements, we will be able to create automations like:

• "When there is motion in the living room area, turn on all living room lights"
• "When a leak is detected, and if no-one is home, send a notification"
• "When lights labeled xmas turn on, start the Christmas playlist in living room"

Of course, we will still be able to use the State and Numerical state triggers for more complex use cases.

First results from user test are great. We feel like we are heading in the right direction, but want to continue getting feedback from the community. How do you feel about these improvements? Is there anything we may have missed here? We're open for feedback!

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/krypta83 on 2025-03-04 12:06:03+00:00.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/dmitridr81 on 2025-03-04 07:52:10+00:00.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/sms066 on 2025-03-04 04:04:09+00:00.

Original Title: My dashboard after a few weeks of tweaking. Each slider for lights has a pop up for the individual lights... lights with effects have sub button menus... tv remote comes up when my work around for lg turns the TV on... I think it's coming along pretty well for a small home.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/IceburgIV on 2025-03-04 01:35:02+00:00.

Hi… My name is Iceburg and I’m an automationaholic.

Today marks my first day in a long time being happy with all my automations and not tweaking or installing another IoT device.

Thanks for the 24 hour chip.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/itsphilbin on 2025-03-04 01:15:43+00:00.

I’m curious to know how others perceive Zigbee these days. While I’m quite optimistic about Matter (and Thread), it seems like we’re currently in a state of transition, bridging the gap between a mature Zigbee ecosystem and an immature Matter ecosystem.

On the one hand, Matter lacks sufficient device support to fully commit to it at this stage. On the other hand, investing heavily in Zigbee devices that I might eventually replace with Matter equivalents seems impractical.

I’d love to hear from others about their strategies and perspectives.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/Necessary_Ad_238 on 2025-03-03 22:25:46+00:00.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/-ManWhat on 2025-03-03 16:53:43+00:00.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/FinibusBonorum on 2025-03-03 16:02:49+00:00.

I am running Home Assistant in Docker with ever more sensors+devices. I also run a lot of other unrelated Docker services. It all works "just right" but it gets hairy if something breaks or I want to change something. It's hard to remember how to configure certain things, or why I set up something in a particular way. My documentation is a sprawling Google Doc in dire need of completion and maintenance.

What's your solution for documenting home infrastructure that's actually maintainable? I am asking about your method more than any specific tools. (But you're welcome to mention tools, too.)

I am looking for practical methods that actually work for you, and that don't require more time than managing the systems themselves. How do you document your home tech without it becoming yet another full-time job?

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/Boffy31 on 2025-03-03 10:41:26+00:00.

Hey HA folks! 👋

I wanted to share a custom Home Assistant dashboard card I built to track my EV lease mileage in real-time.

🔧 How It Works

• Uses sensor.leaf_odometer to pull my car’s odometer reading
• Compares it against my lease start mileage (242 miles) and the lease start date
• Calculates how many miles I should have driven based on an 8,000 miles/year allowance
• Displays whether I’m over, under, or exactly on pace
• Changes the text color dynamically:
  • 🔴 Over limit
  • 🟢 Under limit

🛠️ Code (for those interested)

I used custom:config-template-card (From HACS) with a markdown card to display the status dynamically:

type: custom:config-template-card
entities:
  - sensor.leaf_odometer
card:
  type: markdown
  title: Lease Mileage Position
  content: >
    {% set odometer = states('sensor.leaf_odometer') | float(0) %} 
    {% set lease_start_miles = 242 %}
    {% set start_date_str = '2025-02-17' %}
    {% set allocated_miles_per_year = 8000 %}

    {% set start_date = as_datetime(start_date_str).astimezone() %}
    {% set now_date = now().astimezone() %}
    {% set days_elapsed = (now_date - start_date).days %}
    {% set fraction_of_year = days_elapsed / 365 %}
    {% set allowed_to_date = fraction_of_year * allocated_miles_per_year %}
    {% set miles_since_lease_start = odometer - lease_start_miles %}
    {% set difference = miles_since_lease_start - allowed_to_date %}

    {% if difference > 0 %}
      ## Over by {{ difference | round(0) }} miles
    {% elif difference < 0 %}
      ## Under by {{ difference | abs | round(0) }} miles
    {% else %}
      ## Exactly on pace!
    {% endif %}

🎯 Why I Made This

I wanted an easy way to see at a glance whether I’m over or under my lease mileage without manually doing the maths. Now I can adjust my driving habits accordingly.

Would love to hear your thoughts. Any ideas for improving this?

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/maxi1134 on 2025-03-03 15:50:10+00:00.

Here is a list of my most used ones:

And here the complete list:

adjust closet tablet screen brigthess to match the lights alert house wide when there is smoke in the kitchen alert if the front door remains unlocked for too long alert maxi if someone enters his room while alarm is set to armed home alert maxi if someone goes into the hotbox during a party alert maxi in the room where he is when his phone rings alert maxi is someone comes in while he is sleeping alert maxi that his laptop battery is low alert maxi that is phone is ringing alert maxi when a work timer ends alert maxi when people are too noisy on the patio during a party alert people in the back to go away alert that the front door remained open alert that the vacuum is stuck alert when cooking timer is finished alert when dryer finishes alert when microwave finishes alert when someone is in the back alert when someone is in the front alert when the fridge remains open alert when the horn goes off and offer to turn it off alert when the stove water is boiling alert when there is motion inside during arm away alert when there is noise on the terasse alert when washer finishes arm alarm away when user home is off for 10 minutes arm night alarm when everyone is sleeping assist control covers assist equalize volume in the house assist identify the device assist mute esp32 endpoints when room is unoccupied assist play media assist play music default assist play next song assist play playlist assist play song by artist now assist quick color change phrase assist restart music assistant assist set thermostats assist show cameras on tvs assist start media on tv assist stop home group music assist trigger find my phone assist turn off esp32 endpoint screens when room is unoccupied assist turn on esp32 endpoint screens when room is occupied assist unmute esp32 endpoints when room is occupied auto close closet tablet screen when someone is sleeping auto vacuum the entrance automaticaally turn off sleeper in patio automatically turn back door light back off automatically turn off acid time mode automatically turn off aerating appartment automatically turn off bathroom light automatically turn off party mode automatically turn off sleeper in livingroom automatically turn off the back security horn after 2 minutes and ask if it should restart automatically turn off the security horn after 2 minutes and ask if it should restart automatically turn off tvs automatically turn off waiting uber bedroom hue tap remote automation change light to random colors on press change light to random pastel colors on press close covers when chromecasts starts movie closer bedroom cover when sleeper turns on control brightness of closet tablet to avoid discharge control brightness of front door phone to avoid discharge control hallway tablet charging control livingroomtablet charging dial hallway automation dial kitchen control automation dial library wall control automation dial livingroom library control dial office control automation dial office desk control automation dial salon automation dim wall lights when livingroom tv is playing and beige couch or matress is occupied disable waiting someone after an hour disarm alarm away when user home turns on disarm alarm night when maxi awakes display chillingroom display interface display room color on tvs when mimiclights mode is triggered display room color on tvs when mimiclights mode is triggered 2 doorbell doorbell show received notification answer on phone execute sleep actions when sleeper in closet turns on front door announcement on unlock front door automation on unlock for conditional codes hotbox down dial automation hotbox down display automation hotbox top black hue dial automation lock back door 5 minutes after unlocking lock front door 5 mintuesa after unlocking lock front door when it is closed for 5 seconds lock front door when it is closed for 5 seconds 2 lock tablets on triggered alarm lower hotbox down light when maxi open his webcam lower sound when assist in progress lower volume if police is detected in the front during a party manage bedroom ac through maxi occupancy music assistant llm automation music assistant local only voice support blueprint 2 mute chromecasts when they start vituals mute speakers in the office when computer mic is in use mute speakers when a microphone is in use in the room mute speakers when chromecast starts playing mute speakers when the room is empty new automation notify on potential package notify when someone leaves through front door open bedroom covers when the person awakes open phone to 911 number when smoke call 911 philips hue dial automation play music when maxi awakes at home play muzak in the bathroom when someone enters play random music prepare house when it gets empty raise bathroom volume when door closes raise lights brightness when a movie is paused and the brightness is below 30 raise music on the playing speaker when the bathroom fans goes on raise volume when the ac starts in a room reload tablet page when motion is detected in the kitchen reload tablets 4 minutes after ha restarts reload tablets when frigate changes state reset doorbell stuff on unlock restart ffmpeg noise detection if it crashes set front door screen text set speakers volume on initial playback v2 set the kitchen hub volume to 100 on app launch set wallpaper engine colors to match the lights show main screen when music stops on hallway tablet sleep actions when maxi is sleeping is turned on anywhere sleep actions when sleeper in hotbox is turned on sleep actions when sleeper in livingroom is turned on sleep actions when sleeper in patio is turned on speaker automatic volume v4 start bathroom fan when bathroom humidity is 10 points over house humidity start rain sounds where maxi is sleeping start visuals upon button press stop bathroom speaker when door opens stop bathroom speaker when no motion and door open stop bedroom speaker when i awake stop speakers on disarm tell maxi about the weather when he awakes tell maxi when his watch is charged trigger all home defense script through notification trigger back horn when someone loiters for too long at the door trigger in home defense script after the alarm is triggered for 6 continious minutes trigger in home defense script through phone notification trigger in home defense script through phone notification 2 trigger kinky ambiance script when kinky party turns on trigger party script when party mode turns on trigger police announcement on triggered alarm trigger psychedelic script when acid mode turns on trigger sleeper in hotbox on double press turn acs on and off depending on house occupancy turn assist screens on when listening turn back door lights on when someone is detected turn camera to doorway on doorbell action turn down volume when ac goes off turn light on when someone is detected in the front turn lights to purple when a movie is played turn lights to white when we stop a movie turn off acid time when everyone goes to bed turn off all the lights when all sleeping turns on turn off assists screens when done listening turn off bathroom fan when humidity falls turn off closet fan after 5 minutes of non occupancy turn off front door screen if it remains open 10 minutes turn off front door screen on clear of occupancy turn off horns on alarm disarm turn off lights colors adaptation when an event is ongoing turn off lights when a room is empty turn off lights when house is empty turn off livingroom lights when bedroom sleeper turns on turn off phone bluetooth emitter when maxi leaves home turn off sleeper in bedroom when lights turns on turn off sleeper in closet after 10 hours turn off sleeping mode for adaptative lighting on all sleeping turns on off turn off speakers after 15 minutes of pause turn off the front door light in relation to the sun position turn on color adaptation when events end turn on front door screen on occupancy turn on lighs automatically turn on light automation once alarm is disarmed turn on media automations when alarm is disarmed turn on party mode when over 5 guests are over turn on phone bluetooth emitter when maxi arrives home turn on sleeper in bedroom boolean when sensor turns to on turn on the front door light in relation to the sun position undim wall lights when livingroom tv is stopped undo sleep actions when sleeper in hotbox is turned off undo sleep actions when sleeper in livingroom is turned off undo sleep actions when sleeper in patio is turned off undo sleeper actions when sleeper in closet turns off undo sleeping actions for maxi when he awakes unlock tablets on disarmed alarm unmute speakers unmute speakers in the office when computer mic goes off unmute speakers when tv stops update map extractor camera

And here the code for them:

Edit:

I also asked Qwen 2.5 to create a list of my automations along a description for those that accept LLM output:

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/dark__mode on 2025-03-03 05:53:58+00:00.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/guesswhochickenpoo on 2025-03-03 04:44:41+00:00.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/lordjustice17 on 2025-03-03 03:38:03+00:00.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/emcee_you on 2025-03-03 02:30:53+00:00.

You know...you see these posts and it never happens to you. Some guy gets a box of like 12 hard drives or a pile of memory sticks or 30 6XL wolf howling at the moon t-shirts.

Well, today it happened to me. I just needed to upgrade to the new Matter Link hub, and when I opened the box, I was greeted with a surprise:

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/mcttech on 2025-03-02 20:48:28+00:00.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/Equal-Individual56 on 2025-03-02 17:35:53+00:00.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/rjSampaio on 2025-03-02 14:00:43+00:00.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/TimidPocketLlama on 2025-03-02 11:35:24+00:00.

Yesterday a careless home health aide who was caring for my dad left the refrigerator door open. He is hard of hearing and did not hear the beeping. I didn’t get home until about 2 and a half hours after she left. Our groceries seem to be okay, fortunately.

So I’m thinking of getting door sensors and setting them to alert our phones if the door is left open more than 2 minutes. But I’m concerned that the door could be closed enough to satisfy the door sensor but still not all the way. (With our freezer in particular, it has been closed enough to satisfy even the freezer door alarm itself but still frosted over inside.) Could anyone recommend temperature monitors or would you have any better suggestions?

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/5yleop1m on 2025-03-02 06:25:46+00:00.

Don't update to 2.1.2 until this issue is fixed -

If you did update and don't have a backup, the same issue link has instructions on how to revert.

For anyone dealing with this and didn't have a backup, here's how to roll back. 

1. Make sure you have access to the `addons` folder in HA. I did this by installing the samba add-on and setting up SMB access to HA. - https://github.com/dianlight/hassio-addons/tree/master
2. Download the source code zip archive for the hassio-zigbee2mqtt add-on version 2.1.1 from the releases page - https://github.com/zigbee2mqtt/hassio-zigbee2mqtt/releases
3. Extract the zip archive somewhere
4. Connect to the SMB share for HA and go to the add-ons folder/share
5. Go to the folder you extracted in step 3, copy the contents into the add-ons SMB share. The contents should include folders like `common`, `zigbee2mqtt`, `zigbee2mqtt-edge`, etc. Copy these folders and all the files in the folder
6. Restart Home Assistant
7. Once restarted, go to the add-ons page. You might have to do a `ctrl + shift + r`
8. You should see a new row of addons under "local addons"
9. Go to the already running 2.1.2 Zigbee2Mqtt addon and copy everything from the 'configuration' section
10. Return to the local Zigbee2Mqtt addon and paste everything into the 'configuration' section
11. Stop the 2.1.2 Zigbee2Mqtt 
12. Start the local Zigbee2Mqtt addon
13. Everything should work again

I got the idea for this from - https://www.youtube.com/watch?v=yxbZAv0oYcE

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/kingshit909 on 2025-03-02 03:29:56+00:00.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/PoisonWaffle3 on 2025-03-01 22:45:28+00:00.

The Reolink doorbells (particularly the PoE ones) are almost perfect, but the main thing they're missing is a way to trigger our existing mechanical chimes. I'm personally not a huge fan of the little plug in chime that they provide.

I've mentioned my setup/solution around here a few times and I very frequently get questions about it, so I thought I'd put together a guide. This guide will be mainly applicable to doorbells based in the USA (as I'm from the USA and familiar with doorbell wiring here), but may or may not be applicable to doorbells elsewhere, as I'm not familiar with how they're wired outside of the US.

The automation is fairly simple:

-Trigger: Reolink Doorbell 'visitor' button is pressed

-Action: Close a smart relay for ~100ms to apply power to your doorbell chime

There are multiple ways to wire this, and multiple types of relays that will work fine. I personally chose to use an old school Shelly1 that I had lying around that was flashed with ESPHome, but a Shelly 1 Mini Gen 3 (or a Shelly 1PM Mini Gen 3, if you choose to switch the mains power) would be perfect.

First, you'll want to scope out how your doorbell/doorbells is/are wired. In my case, things are laid out like this:

Doorbell transformer -> doorbell -> chime 1 -> chime 2

I've also seen layouts like this (the two tones are usually separate chimes but inside the same physical casing):

/--- doorbell 1 -> chime tone 1

Doorbell transformer <

\--- doorbell 2 -> chime tone 2

Depending how things are laid out and your comfort level with wiring, you may have a few different options for wiring in the relay(s):

Wiring Option 1 (how I personally did mine), best for a single doorbell: Use the relay to switch the doorbell transformer itself off and on. With this option you'll need to close the doorbell circuit with a Wago or wire nut so that the chime is triggered when the relay closes. Since Shelly relays (and most smart relays in general) can be powered by 120V or 240V mains voltage, you can install the Shelly relay inside the electrical junction box that feeds the doorbell transformer, and everything can be easily kept safe and up to code.

Note the wago connecting the two doorbell wires, closing the circuit

Here's how I did the wiring at my doorbell transformer. Hot and neutral come from the center of the junction box (note the black circle) and go directly into wagos. Since this is an original Shelly 1 that's able to be powered by one source but switch another, we need to feed the black (hot/live 120V) into both the L (live power in) and I (switched input). (Note that it kind of looks like there's something connected to the SW switch input terminal on the Shelly, but there is not. That goes to the outlet that mounts to the front of the junction box.) The neutral also goes directly into a wago, then splits to go to the N (neutral) on the Shelly, to the outlet, and to the doorbell transformer.

Wiring Option 2: Leave the doorbell transformer powered at all times, and use the relay(s) to close the doorbell circuit(s). If you have two doorbells and want the two different chime tones this will be your best option, though finding locations to place and power the relays may be interesting.

You'll want to use two separate relays (a pair of original Shelly 1, for example), NOT a single Shelly 2PM or 2.5. The issue is that you generally can't drive these relays with the output power from the doorbell transformer, so you'll need to power them with 12V DC (you should get one that supports DC), and then have the relays switch the power from the doorbell transformer. The dual-relay Shelly's are designed to be powered from the power source that they're also switching, so they won't work here. Note that it's against code to mix mains power and DC inside of a junction box, so you really should use a 12V DC power adapter (that plugs into an outlet) and power your relays with 12V DC so it can all safely live outside of a junction box.

Wiring layouts are going to vary quite a bit on dual-doorbell setups, so you'll have to familiarize yourself with how yours is laid out and find a relay/powering layout that works for your situation.

The Automation: Depending on what kind of relays you use and what firmware they're running, you have a few options.

Automation Option 1: I already had ESPHome installed on my relay, so I used that to create a 'button' entity that closes the relay for 100ms when triggered. I have the automation 'press' the button to close the relay and apply power to the doorbell transformer for 100ms.

Automation Option 2: If you aren't interested in running ESPHome, you can set up your Shelly relay should appear as a switch in HomeAssistant. You can configure your automation to turn the switch on, wait 100ms, then turn the switch back off.

Of course you can always add additional actions, like sending a notification with a picture to your phone, or pushing a video feed from the doorbell to a wall mounted tablet, but I included the basics in the above screenshots.

I'm sure there are plenty of unusual doorbell wiring setups, so this isn't meant to be an exhaustive guide. If you run into any issues feel free to do some research on general doorbell wiring/layout, as it may help you understand how yours is wired. The wiring in my own house was fairly straightforward, but it was a complete mess at my parents house (I wired in a different smart doorbell for them as well).

I may or may not be able to help with questions on individual setups, but feel free to chime in here if you do have any questions.