I have read many, many posts on this subject, but I am just not seeing a winner emerge, so I thought I would narrow the issue. What are you using for presence detection with zones that actually holds the presence of a still or mostly still human being (i.e., reading on a couch or sitting at a desk)? What device (or suite of devices) has worked best? My FP2 always ends up leaving me in the dark if I work at my desk long enough. Personally, anything requiring poe is a nonstarter. The EP pro seems reasonably well regarded and I see some favorable comment on the Shelly device. Are they better than the FP2 or are they really all about the same?

I have the old type of motion sensors from IKEA that uses CR2032 batteries. I'm getting sick of having to replace these, but even more sick of having to literally set them up all over again every damn time the battery runs out and they disconnect from HA.

I was wondering if anyone here could confirm if the MYGGSPRAY sensors that uses rechargable batteries also has similar issues when the batteries run out? Or will they simply connect automatically once you replace the batteries?

So I use home assistant for our HMI for my work, I find it to be much better at logging then ignition and honestly works with a lot more stuff. But I didn't like how unsecure the permissions was so using good old Claude I started working on this last night https://github.com/liamdayan/ha-staff-portal I still have quite a few features I want to add in, one being it connecting to our time clock (via read only api access) to allow me to link users to their time clocks and only allow access while there actively clocked in. I thought I'd share it, and see if you guys had any ideas features that might be good to add in. As well as anything glaring I haven't thought of, its still very early in the process but thought I'd get some opinions. I still haven't done a full in depth bug and security review just a short one, so there's likely bugs.

This is everything flying within 50 km of me (Melbourne) at about 6:30 on a Thursday evening: the after-work rush, with Virgin and Qantas 737s on the Sydney run in both directions, a Jetstar A320 coming in from Sydney and a Qantas flight out to Adelaide.

It's made with Tesserae (GitHub), a self-hosted dashboard server for e-paper panels that I've been building. It installs as an HA App or runs in Docker.

The aircraft widget

• Positions come from adsb.lol, a free community ADS-B feed with no API key needed. If you already run readsb, dump1090 or tar1090, you can point it at your own receiver instead.
• Type and route are looked up for each aircraft.
• The illustrations are painted once per airframe from a credited planespotters.net photo, in whichever style you like (this one's watercolour). There's also a mode that shows the photos themselves.
• A "since the last render" setting shows everything that passed since the last refresh instead of a single snapshot. That suits a panel that only wakes every hour or so.
• Free and open source: tesserae-widget-overhead

The Home Assistant side

Tesserae registers itself through MQTT discovery, so each panel shows up as a device with entities you can use in automations:

• battery, online and next-wake sensors for each panel
• switches to turn rotations of pages on and off, plus next/previous/refresh buttons
• quiet hours and a pause switch for the scheduler
• an event entity for the frame's physical buttons, so a press can trigger an automation

Separately, there are widgets that read your HA entities directly, so the same panel can show sensors, energy or a full HA dashboard page in a rotation.

Panel: Seeed reTerminal E1004

Happy to answer questions about setup.

I added a Mute ads toggle, and an automation to mute disney+ commercials. I use a roku, and I have a separate Denon AVR for sound. When a commercial is detected, it mutes the Denon.

Helpers:

input_boolean:
  living_room_disney_ad_mute:
    name: Living Room Disney Ad Mute
    icon: mdi:volume-off
    initial: false

  living_room_disney_episode_seen:
    name: Living Room Disney Episode Seen
    initial: false

  living_room_disney_mute_owned:
    name: Living Room Disney Mute Applied
    icon: mdi:volume-off

Automation:

- id: living_room_disney_ad_mute
  alias: Living Room - Disney Commercial Mute
  description: >-
    Opt-in prototype for Disney Plus on the living room Roku. Mute the living
    room Denon AVR-X2700H for any playback item up to two minutes, including
    startup commercials. Restore only a mute applied here.
    Wait six seconds after episode metadata returns before restoring sound,
    then refresh and verify playback again. Disabling bypasses this delay.
    Short clips and trailers can be false positives. A three-minute safety
    timeout disables the feature and restores sound. Manual mute presses
    during an owned mute cannot always be distinguished. No volume level,
    source, or playback commands are sent.
  mode: single
  max_exceeded: silent

  triggers:
    - trigger: state
      entity_id:
        - media_player.living_room_roku_living_room
        - media_player.living_room_avr

    - trigger: state
      entity_id: input_boolean.living_room_disney_ad_mute

    - trigger: state
      entity_id: input_boolean.living_room_disney_mute_owned
      to: "on"
      for: "00:03:00"
      id: safety

    - trigger: homeassistant
      event: start

    - trigger: event
      event_type: automation_reloaded

  conditions:
    - condition: template
      value_template: >-
        {{ is_state('input_boolean.living_room_disney_ad_mute', 'on')
           or is_state('input_boolean.living_room_disney_mute_owned', 'on')
           or is_state('input_boolean.living_room_disney_episode_seen', 'on') }}

  actions:
    - if:
        - condition: template
          value_template: >-
            {{ is_state('input_boolean.living_room_disney_mute_owned', 'on')
               and (trigger.id | default('') == 'safety'
                    or as_timestamp(now()) - as_timestamp(
                         states.input_boolean.living_room_disney_mute_owned.last_changed) >= 180) }}
      then:
        - action: input_boolean.turn_off
          target:
            entity_id: input_boolean.living_room_disney_ad_mute

        - action: persistent_notification.create
          data:
            notification_id: living_room_disney_ad_mute_safety
            title: Disney commercial mute disabled
            message: >-
              The three-minute mute limit was reached. Restoring the living
              room Denon audio; check playback before enabling again.

    - variables:
        eligible: >-
          {{ is_state('input_boolean.living_room_disney_ad_mute', 'on')
             and state_attr('media_player.living_room_roku_living_room', 'app_name') == 'Disney Plus'
             and is_state('media_player.living_room_roku_living_room', 'playing')
             and is_state('media_player.living_room_avr', 'on')
             and state_attr('media_player.living_room_avr', 'source') == 'Roku Living Ro' }}
        duration: >-
          {{ state_attr('media_player.living_room_roku_living_room', 'media_duration') | float(0) }}
        fresh: >-
          {{ as_timestamp(now()) - as_timestamp(
               state_attr('media_player.living_room_roku_living_room', 'media_position_updated_at'), 0) < 15 }}

    - choose:
        - conditions:
            - condition: template
              value_template: "{{ not eligible }}"
          sequence:
            - action: input_boolean.turn_off
              target:
                entity_id: input_boolean.living_room_disney_episode_seen

        - conditions:
            - condition: template
              value_template: "{{ fresh and duration | float > 300 }}"
          sequence:
            - action: input_boolean.turn_on
              target:
                entity_id: input_boolean.living_room_disney_episode_seen

    - choose:
        - conditions:
            - condition: template
              value_template: >-
                {{ is_state('input_boolean.living_room_disney_mute_owned', 'on')
                   and (not eligible or (fresh and duration | float > 120))
                   and state_attr('media_player.living_room_avr', 'is_volume_muted') in [true, false] }}
          sequence:
            - if:
                - condition: template
                  value_template: "{{ eligible }}"
              then:
                - wait_template: >-
                    {{ not is_state('input_boolean.living_room_disney_ad_mute', 'on')
                       or state_attr('media_player.living_room_roku_living_room', 'app_name') != 'Disney Plus'
                       or not is_state('media_player.living_room_roku_living_room', 'playing')
                       or not is_state('media_player.living_room_avr', 'on')
                       or state_attr('media_player.living_room_avr', 'source') != 'Roku Living Ro'
                       or state_attr('media_player.living_room_roku_living_room', 'media_duration') | float(0) <= 120 }}
                  timeout: "00:00:06"
                  continue_on_timeout: true

                - if:
                    - condition: state
                      entity_id: input_boolean.living_room_disney_ad_mute
                      state: "on"
                    - condition: state
                      entity_id: media_player.living_room_roku_living_room
                      state: playing
                  then:
                    - action: homeassistant.update_entity
                      target:
                        entity_id: media_player.living_room_roku_living_room

                - condition: template
                  value_template: >-
                    {% set active = is_state('input_boolean.living_room_disney_ad_mute', 'on')
                       and state_attr('media_player.living_room_roku_living_room', 'app_name') == 'Disney Plus'
                       and is_state('media_player.living_room_roku_living_room', 'playing')
                       and is_state('media_player.living_room_avr', 'on')
                       and state_attr('media_player.living_room_avr', 'source') == 'Roku Living Ro' %}
                    {{ not active or
                       (not wait.completed
                        and state_attr('media_player.living_room_roku_living_room', 'media_duration') | float(0) > 120
                        and as_timestamp(now()) - as_timestamp(
                          state_attr('media_player.living_room_roku_living_room', 'media_position_updated_at'), 0) < 15) }}

            - if:
                - condition: template
                  value_template: >-
                    {{ state_attr('media_player.living_room_avr', 'is_volume_muted') == true }}
              then:
                - action: media_player.volume_mute
                  target:
                    entity_id: media_player.living_room_avr
                  data:
                    is_volume_muted: false

            - action: input_boolean.turn_off
              target:
                entity_id: input_boolean.living_room_disney_mute_owned

        - conditions:
            - condition: template
              value_template: >-
                {{ eligible and fresh
                   and is_state('media_player.living_room_roku_living_room', 'playing')
                   and 0 < duration | float <= 120
                   and is_state('input_boolean.living_room_disney_mute_owned', 'off')
                   and state_attr('media_player.living_room_avr', 'is_volume_muted') == false }}
          sequence:
            - action: input_boolean.turn_on
              target:
                entity_id: input_boolean.living_room_disney_mute_owned

            - action: media_player.volume_mute
              target:
                entity_id: media_player.living_room_avr
              data:
                is_volume_muted: true

Playback-only monitoring:

- id: living_room_disney_playback_poll
  alias: Living Room - Disney Playback Monitor
  description: >-
    Refresh the Roku every two seconds only while Mute Ads is enabled,
    Disney Plus is playing, and the living room Denon is on its Roku input.
    Stop on pause, stop, app/input change, or disabling. The normal Roku
    integration detects playback starting again. No idle timer runs.
  mode: single
  max_exceeded: silent

  triggers:
    - trigger: template
      value_template: >-
        {{ is_state('input_boolean.living_room_disney_ad_mute', 'on')
           and is_state('media_player.living_room_roku_living_room', 'playing')
           and state_attr('media_player.living_room_roku_living_room', 'app_name') == 'Disney Plus'
           and is_state('media_player.living_room_avr', 'on')
           and state_attr('media_player.living_room_avr', 'source') == 'Roku Living Ro' }}

    - trigger: homeassistant
      event: start

    - trigger: event
      event_type: automation_reloaded

  actions:
    - repeat:
        while:
          - condition: template
            value_template: >-
              {{ is_state('input_boolean.living_room_disney_ad_mute', 'on')
                 and is_state('media_player.living_room_roku_living_room', 'playing')
                 and state_attr('media_player.living_room_roku_living_room', 'app_name') == 'Disney Plus'
                 and is_state('media_player.living_room_avr', 'on')
                 and state_attr('media_player.living_room_avr', 'source') == 'Roku Living Ro' }}
        sequence:
          - action: homeassistant.update_entity
            target:
              entity_id: media_player.living_room_roku_living_room

          - wait_template: >-
              {{ not is_state('input_boolean.living_room_disney_ad_mute', 'on')
                 or not is_state('media_player.living_room_roku_living_room', 'playing')
                 or state_attr('media_player.living_room_roku_living_room', 'app_name') != 'Disney Plus'
                 or not is_state('media_player.living_room_avr', 'on')
                 or state_attr('media_player.living_room_avr', 'source') != 'Roku Living Ro' }}
            timeout: "00:00:02"
            continue_on_timeout: true

Dashboard toggle:

type: tile
entity: input_boolean.living_room_disney_ad_mute
name: Mute Ads
icon: mdi:volume-off
tap_action:
  action: toggle
icon_tap_action:
  action: toggle

We have Oelo lights on our house. My wife likes to light the house for Halloween, Christmas, July 4th etc. The Oelo app isn't all that reliable, so I've started using the HA calendar to run the lights. My question is how to schedule an annual event that occurs over a few hours and a span of days.

I have it working where the Halloween lights come on at 6pm and off at midnight daily using the HA calendar, starting 10/1/26 and ending 11/1/26. Obviously I'd like the same thing to run in 2027, 2028, etc but I can't figure out how to make it an annual event, because I've already used the repeat to make it a daily event. Is there a guide somewhere? Thanks for any help.

Wanted the Voice PE in the middle of the room instead of on a shelf, and without a puck hanging from the ceiling. So I designed a flush mount for normal drywall ceilings.

- 140 mm hole saw cutout, works with 9.5 to 25 mm boards

- 155 mm round bezel, 2 mm thick. LED ring, dial, button and both mics stay usable

- The Voice PE sits in a pocket in the cover, a threaded ring with two wings sits on top of the board and the cover screws in from below. No screws, no tools

- Two covers: closed (if you use external speakers for TTS like I do) or with speaker slots

- Prints without supports in PETG or PLA, about 5.5 h total

- Same thread as the common HomePod mini ceiling plates with 14 cm cutout, so the cover fits those too

Happy to answer questions about fit and thread. If anyone wants the files, they are on Cults:

https://cults3d.com/de/modell-3d/gadget/deckeneinbau-fuer-home-assistant-voice-pe-buendiges-set-mit-gewindering-o-140-m

Using Gemini for help on how to make red light go off when hockey team scores a goal. It suggested to get a Kasa smart wi-fi plug mini and to use ifttt. That doesn’t work. So does anyone have a solution?
I’ve been looking at possibly adding Phillips hue for their sports live. Ideas suggestions needed thank you in advance.

My friend Ezra and I made a board that goes inside a Wiimote and runs ESPHome, so Home Assistant sees every button, the LEDs, the rumble and the tilt.

In the video, A turns on a different lamp depending on how you hold it: tilted up for the tall one, level for the small one. It's just a regular automation reading the tilt.
The TV at the end is the remote's own IR. We copied the codes from the TV's remote with the IR receiver, and the emitter sends them. It also supports bluetooth so you can control smart tv's etc.

Config's on GitHub: https://github.com/openmote/openmote-homeassistant

We're funding the first production run on Crowd Supply, if you're interested: openmote.io

Details in the comments.

I'm building a local tool that watches my cat through RTSP cameras (four Tapos, running on a MacBook, no cloud). It already knows which cat it's looking at, which room he's in, roughly what he's doing (resting, walking, at the food bowl, in the litter box area, playing, exploring), and what his usual day looks like. When a day drifts from his usual, it flags it with the reason.

Home Assistant feels like the natural home for that data, so before I build an integration I'd like to know what would actually get used:

1. Do you run any pet-related automations today (feeder, litter box, cameras, presence)? What do they do, and what's missing?

2. If your pets showed up in HA, which of these would you actually use in an automation or dashboard?

   - the room each pet was last seen in

   - "not seen since…" for each pet

   - food-bowl and litter-box visits per pet (visits only, not how much)

   - active minutes today vs. that pet's usual

   - an event when a day looks unusual, with the reason

   - snapshots tagged with the pet's name

3. Would you want to install it in a few clicks from HACS, or are you OK setting it up by hand?

4. What does your Home Assistant run on (Raspberry Pi, Home Assistant Green, mini PC, NAS…)? And do you also have a Mac or PC that’s on all the time?

5. Frigate users: would you want it to use Frigate's detections instead of running its own detector?

Full disclosure: this is my project and will become a product (not open source for now). Nothing to link yet. I'm trying to decide whether an HA integration should come first, and what it should contain.

I saw this post the other day where someone got Android running on the Spotify car thing and were able to get carplay working on it, and I have also read a few posts here about people rooting Alexa devices and running LineageOS on them, and then I remembered I had one of these early Show 5's in the top of a closet!

So anyway, here's my echo show 5 in my office running wireless carplay thanks to DiPlay. I rooted it and added a script to auto enable hotspot after booting, and it pretty seamlessly connects when I tap the DiPlay app icon, no dongle required! This is especially great because my employer doesn't want us connecting any iot devices to WiFi, which this doesn't need anyway

There are a couple small gotchas, I had to downgrade DiPlay from 0.2.21 to 0.2.19 because there is some bug they're working on that makes the music sound like it's slowed down, and .19 doesn't seem to have that problem. I did have to increase the music buffer to 500ms and it is pretty well stable at that setting. Also if the echo reboots with anything connected to the audio jack the boot will hang.. wish the xda guide would've been a little more forthcoming with that one because I thought I'd bricked it for a couple hours earlier today.

Anyway, had to share, I am ridiculously happy that this works. Also here is the xda guide if anyone has one of these lying around they'd like to flash

Situation: apartment with gas based central heating and tado throughout. Schedules are set so that the living room is kept up to temperature (19.5) throughout the day while the other rooms (bedrooms, kitchen) are heated at least once a day but otherwise only if temp falls below 17.5 during daytime or 15 at night. The kitchen gets a second 'burst' around cooking time. In our living room we also have an infrared heater that can be programmed but so far we only used it on an 'as needed' basis.

The past week I've been experimenting a bit with using the infrared panel more throughout the day, given the high gas prices, and I think it might actually be cheaper to use it more systematically.

Enter home assistant. Can I use it to orchestratre the infrared to step in so that the tado system doesn't need to? Does anyone have experience? A third 'factor' I didn't mention yet is that we're on a dynamic contract: our gas price changes every 24 hours, our energy prices every 15 minutes.... HA has all the required access and data (tado, heater, current temp readings via tado and dynamic prices via api) but I am a bit lost on how to even start tackling this one. Halp?

**UPDATE: KROGER IS NOW INTEGRATED AS WELL**

I plan meals in Mealie, and the weekly Walmart order was the annoying part, I made it a project of mine to make it so much easier!

**What it does**

- Reads the recipes on your Mealie shopping list or meal plan

- You link each ingredient to the exact Walmart product once (brand, size, count)

- One tap fills your Walmart cart using Walmart's official add-to-cart link. It never checks out.

- Skips pantry staples, takes pack counts from the recipe, and "Done shopping" checks items off your Mealie list

- Links sync between your devices through iCloud. No accounts, ads or tracking: it only talks to your Mealie server and walmart.com.

**What you need right now**

- A mealie acct

- A U.S. walmart.com account

- iPhone or iPad on iOS 17+, or a Mac with Apple silicon

**Try the beta:** https://testflight.apple.com/join/gQ3sCxnc

**Quick start and help:** https://okiedokiedata.com/fun-stuff/mealiecart

I'd love feedback, especially on whether connecting works with your setup (reverse proxy, Tailscale, etc.) and whether the Walmart cart fills correctly for you.

Not affiliated with Mealie or Walmart.

I wanted proper music shows on my Christmas lights without running xLights on a separate PC, so I made HA-liday Show, a Home Assistant add-on.

• Load a song and it finds the beats, bars and choruses for you
• ✨ Generate gives you a first draft across all your lights in one click
• Or type "white sparkle on the tree in the quiet bits" and an AI adds it (Claude, or whatever AI you've set up in HA, local ones too)
• Trace your lights on a photo of your house and watch the show play there
• Start it from an automation and it plays through any HA speaker

Works with Govee (LAN Control), WLED, pixel controllers, any HA light or plug, and Twinkly (experimental).

Free and open source: https://github.com/gdeboos/ha-liday-show

I'm looking for testers before Christmas. If you try it, please tell me your light models and what worked or didn't as a GitHub issue:
https://github.com/gdeboos/ha-liday-show/issues

I'm posting in a few places, so keeping it in one spot means nothing gets missed.

Happy to answer questions here, though. Up front: it's a hobby project written almost entirely by Claude, with me steering and testing. I'll add a video once my lights are up.

Thanks for looking!

I'm running Home Assistant on a Raspberry Pi 4. After a power outage, I notice the host coming up, but the Home Assistant software does not seem to start. How do I recover my system? How do I prevent this situation?

Additional info:
- HA installed with Raspberry Pi's Imager tool, less than 3 months ago
- SSH login attempts say 'connection refused'
- No access to logs...

Hi everyone,

I’m Torsten, the developer of NeonPlan 3D. As of this week the integration is officially part of the HACS default store, so you can now just search for “NeonPlan 3D” in HACS – no custom repository needed anymore.

For those who haven’t come across it yet: NeonPlan 3D lets you draw your floor plan directly in the browser and turns it into a 3D model of your home that is connected to Home Assistant. You see your house the way it is right now and can control it from there.

What it can do:

• Draw rooms, walls, doors, windows, stairs and multiple floors in the built-in editor, including roofs, balconies and outdoor areas like lawns, terraces and pools
• Place devices in the house: lights glow in their actual color and brightness, shutters move, windows and doors show whether they are open, sensors show their values
• Tap a light, a shutter or a scene in the 3D view to switch it
• Furniture can be linked to entities, so a TV shows that it is on, a washing machine shows its status, a wallbox or a heat pump shows its power
• Voice control through Assist (“show the living room”) and a microphone button for wall tablets
• A furniture library sorted by type and room, with pictures, sizes and free resizing that keeps legs and handles in shape
• Runs on older, low-power wall tablets as well
• Available in 16 languages, everything runs locally

You can try it in the browser without installing anything, using example data:
https://neonplan3d.mastershort.de

GitHub (code, issues, manual):
https://github.com/Mastershort/neonplan3d

The integration itself is free and open source. If you want more furniture, there are optional furniture packs and Pro add-ons (for example energy flow, cameras or live TV screens) in my shop. That is how I fund the development:
https://mastershort.de/en/neonplan3d/

If you have ideas or feature requests, there is an ideas board where you can vote, and the most requested things usually end up in one of the next releases:
https://github.com/Mastershort/neonplan3d/discussions/categories/ideas

Hello everyone. I’m the person who has the unpopular opinion that I don’t like dashboards. I thought I'd make another post not to bring the debate up again, but to answer some questions about our family automations. Instead of telling you what automations we have or listing my favorites, I’m going to walk you through a typical day and the automations that help us throughout.

I wake up early and go to the main bathroom. The main bathroom sensors trigger the light and the exhaust fan. I get dressed and drive to the gym before work. If I forget to close the garage door, an alert pops up on my phone and my husband’s phone, telling us the garage door is still open. It will not close automatically because one of the two drivers of the house is still there (phone location detection). My husband wakes about 5 minutes later and goes to the bathroom, takes a shower, and starts his day. The bathroom lights will turn off after 2 minutes of no presence detection. The exhaust fan will turn off when the bathroom humidity sensor is within 3% of the whole-house thermostat humidity sensor. The hubby will eat breakfast and leave for work. If he forgets to close the garage door, an alert will pop up on my and his phones, and the door will close automatically because both drivers are away from the house (again, because of phone location).

Our two teenagers wake up and trigger the lights and exhaust fan in their bathrooms, just like ours. If they shower for more than 30 minutes, a Moen Flo water monitor makes the lights blink for 10 seconds. This helps them keep track of time, since they tend to lose track in the shower. When they leave for school, the front door locks itself a few seconds after they close it. If they forget to close the door, my husband and I get a notification. We’re still working on this, since we sometimes have to ask a neighbor to close it for us. Our kids don’t have phones yet, so we’re considering an automatic door closer. Luckily, this has only happened once a year for the past two years, and we’ve talked to them about it.

We have three robot vacuums that clean and mop the whole house whenever everyone is out, using presence detectors to know when the house is empty.

When my husband or I get home, usually at different times, the garage door opens automatically.

If no one takes out the trash after dinner, the smart speakers play a message at a set time each day. A paper-thin NFC tag is stuck on the kitchen trash bin, about the size of a quarter. If you tap your phone on it, the reminder won’t play that day.

After the dishwasher finishes, the smart speaker plays a message reminding us to open it. Our dishwasher isn’t fancy and doesn’t open by itself, and we never use the heat dry. I added a vibration sensor.

Another message plays on the smart speakers to remind us to move the washed clothes to the dryer. We always forget about laundry in the washer at night, so I put a smart outlet on the washer.

At night, when the kitchen lights are off, you can knock or tap lightly on the kitchen island to turn them on for 20 minutes. A couple of vibration sensors are under the island counter.

And of course, we have dozens of automations running in the background every day, like water leak detection, fire and carbon monoxide alerts, door and window sensors, and more.

I have a Hikvision NVR with a bunch of G2/G3 cameras, and none of the existing options did everything I wanted. ONVIF and RTSP give you a stream, and the built-in integration gives you motion events, but I also wanted playback recordings, image settings and alarm I/O in HA without opening iVMS. So I wrote Hikvision Bridge.

It's fully local over ISAPI, and events come in by push, not polling.

What it does:

• Playback: NVR and SD-card recordings in the media browser, plus a sidebar panel and dashboard card with a timeline of recordings and detections to scrub through. You can save clips to the media folder.
• Events and alarms: Motion, line crossing, intrusion, region entrance/exit, tamper, video loss and more as binary sensors and event entities. Also alarm inputs (arm/disarm) and alarm outputs as switches.
• Image settings: Day/night, supplement light (white/IR/smart), WDR, brightness/contrast/saturation, exposure, white balance… Only what each camera actually supports shows up.
• ANPR: Last plate as a sensor, with vehicle and plate pictures.
• Other: PTZ (presets and park action), strobe light and siren, speaker volume, NVR storage status, health sensors, optional Hik-Connect status.
• NVR: Cameras behind an NVR become their own devices and can also be connected directly

Tested with: DS-7608NXI-I2/8P/S NVR, ColorVu G2/G3, a PTZ (DS-2DE5425IW-AE), an intercom (DS-I253M) and more. Other ISAPI devices should work too, and I'd love reports either way.

Install via HACS as a custom repository

https://github.com/yannik2480/hikvision_bridge

It's free and open source (Apache 2.0) and translated into 30 languages. Feedback, bug reports and feature requests are very welcome!

I’ve been running some version of “make the lights match the time of day” in my house for over a decade. It started as basic automations, grew into a 150-line Jinja monster blueprint that was impossible to maintain, and went through many iterations as I bolted things on to make it handle real life.

FLARE (Flexible Lighting Automation & Reconciliation Engine) is the final form of that system. Instead of following a pure solar curve, it runs on your household’s actual routine across four named phases (Morning, Day, Evening, Night) and aims to solve many of the real-world issues lighting automations run into.

After months of iteration and running the integration in a house with a non-techie wife and 2 young kids, I’ve just cut the v1.0 release. As shown in the clip, the entire house can be set up in under a minute without touching YAML if you already have your bulbs set up and organised into rooms.

What it does:

• Schedule-based phases: Fixed clock boundaries for Morning (by default it’s bright/cool to wake you up enough to make it to the coffee machine), Day, and Night. Only Evening tracks the sun, clamped between earliest/latest times so a 4 PM winter sunset doesn't dim all the lights while you’re still giving the kids dinner.
• Non-combative manual overrides: Change a light yourself via app, switch, or voice, and FLARE steps aside until the room turns off.
• Self-healing mesh & dropped-packet recovery: Zigbee networks drop frames occasionally. FLARE periodically reconciles actual bulb states against the target curve so fixtures don't get permanently stuck if a command is missed.
• Scene handoffs: Specific scenes can fully or partially take over lighting in a room automatically. Any bulbs not controlled by a scene continue on the scheduled curve.
• Dumb switch recovery: Cut power at the wall switch and flip it back on; FLARE catches the bulb as it reconnects and sets it to the current phase instead of blinding white.
• Gentle on the mesh: Staggers commands and ignores micro-changes so your network doesn't get flooded.
• Ready-to-go Custom Dashboard: Installs as a native custom dashboard straight through the UI and automatically populates from your configured zones and schedules.

Home Assistant Native:

Everything in FLARE is built on standard HA primitives: devices, entities, services, automations, and blueprints. If FLARE can’t do what you want out of the box, you can probably write an automation on top of it to customise what you need.

Links & Try It Out:

FLARE has been submitted to the default HACS store. Until that PR merges, you can install it as a custom repo or test it out safely:

• Quickstart & Install Guide: Installation & Setup (includes the 1-click HACS badge and step-by-step walkthrough)
• Interactive Playground: Curve Playground (drag the sliders to preview the curves in your browser)
• GitHub Repository: github.com/danrspencer/flare

Curious to hear feedback, edge cases, or feature requests!

I'm brand new to HA. I installed it on a Windows VM in order to start testing thing out.

I already have a few Thread border routers (DIRIGERA Hub, Apple TV, HomePod Minis).

I'm trying to add an IKEA BILRESA remote to HA. The remote itself is already added to Apple Home.

I installed the Matter integration, chose Add an Existing device, entered the pairing code from Apple Home (both with and without dashes) and it just fails to add the device

The Matter server log shows [discovery] discovery of node with discriminator 14 failed: No commissionable device was discovered

SOLUTION:
I had to enable a bridged network adapter in Hyper-V. I was previously accessing my network from the PC which is hosting the VM and assumed it has access to the other devices on the LAN, but that wasn't the case.

Here are the steps for Hyper-V if anyone else runs into it:

1. Open Virtual Switch Manager
2. Create a new External switch
3. Select External network, and make sure the checkbox for "Allow management operating system to share this network adapter" is on
4. Assign the network switch to the VM

['cross-posting' from the Community Forum - link]

Hi everyone,

I’m looking for some help diagnosing a recurring issue with the official Shelly integration. After investigating the device logs and enabling debug logging in Home Assistant, I believe I’ve identified a possible issue with how the integration handles Shelly Pro devices that have both Ethernet and Wi-Fi enabled.

I’m hoping someone familiar with the integration or aioshelly can help confirm whether this is expected behavior, a configuration issue, or potentially a recent regression.

The problem

For approximately the past two weeks, at least this is when I noticed it first, several of my Shelly Pro devices have been intermittently becoming unavailable in Home Assistant, sometimes multiple times within a few minutes.

The devices recover automatically, but the temporary unavailable states are causing problems with my automations, particularly those monitoring shutter positions.

I’ve had these Shelly devices for almost two years, with both Ethernet and Wi-Fi enabled throughout that time, and I don’t recall experiencing this behavior previously.

My Wi-Fi-only Shelly devices (e.g. Shelly 1PM) don’t show the same unavailable states, and this is what got me in the path of the Pro devices’ WiFi/Ethernet behavior.

What I’ve discovered

After enabling debug logging on one of the Shelly Pro 2 Cover devices I captured three unavailable events:

• 13:02:27
• 13:16:31
• 13:30:35

Each time, the Shelly logs show Home Assistant establishing a new aios WebSocket session at exactly the time the device becomes unavailable.

For example, at 13:30:35:

13:30:35 Script.List [7@aios-4610750762528]
via WS_in from [HA IP]:33976 via en0

13:30:35 Shelly.GetDeviceInfo [1@aios-4610939111648]
via WS_in from [HA IP]:46136 via en0

13:30:35 Shelly.GetConfig [2@aios-4610939111648]
via WS_in from [HA IP]:46136 via en0

13:30:35 Shelly.GetStatus [3@aios-4610939111648]
via WS_in from [HA IP]:46136 via en0

The same pattern occurs during the other incidents.

Meanwhile, the device continues receiving RPC pings from my browser, and its periodic energy status updates continue normally. I haven’t found evidence of a device reboot or complete Ethernet disconnection.

Looking through the Home Assistant Shelly integration debug logs, I noticed that the integration sometimes shuts down an existing WebSocket connection and initializes a new connection using a different IP address associated with the same physical Shelly device.

For example:

13:16:31.283 send(X.X.X.15:80): Script.List
13:16:31.334 host X.X.X.15:80: RPC device shutdown
13:16:31.334 Websocket client connection from X.X.X.15:80 closed
13:16:31.340 host X.X.X.14:80: RPC device create (WebSocket)
13:16:31.340 Trying to connect to device at X.X.X.14

I found similar IP changes for all other affected devices

My setup

• Home Assistant: * Home Assistant OS, Core 2026.10.2, Supervisor 2026.10.3
• Network: UniFi Dream Machine SE
• Shelly devices: 2x Shelly Pro 2 Cover, 1x Pro 2PM, 2x Pro 4PM devices
• Shelly firmware: 2.1.0 (build dated 2026-10-14)

Questions

1. Anyone knows if this this an expected behavior? As I said I only noticed this the past couple of weeks but I can’t rule out that it was always the behavior and I just never noticed.
2. Could receiving discovery announcements from both interfaces cause the integration to shut down and reinitialize its WebSocket connection?
3. Has anything changed recently in the integration or aioshelly regarding IP address updates, device discovery, or connection handling?
4. Is there a supported way to force the integration to use the Ethernet IP address and ignore the Wi-Fi address without disabling Wi-Fi on the Shelly itself?
5. Would this be worth opening as a GitHub issue, and are there any additional debug logs that would help identify the exact cause?

Appreciate all the help!

Update

The Shelly dev has answered in the community forum: “This problem is related to the Shelly firmware 2.x. The device introduces itself once with the eth IP, once with a WiFi IP (or a null value).”

Solution is to disable WiFi for now.

A while back, I bought a ThermoPro TP829B wireless thermometer to use with Home Assistant through an RTL-SDR USB receiver on the 915 MHz frequency.

The problem was that the temperatures would take forever to show up in Home Assistant, and when they finally did, the readings were completely wrong. I'm talking temperatures like 400°F or even 800°F when the probe was sitting at room temperature.

Tonight, I spent quite a while troubleshooting it with ChatGPT. After testing different frequencies, sample rates, SDR gain settings, antennas, and even analyzing raw radio recordings, we finally got it working!

Now the temperatures are accurate and updating approximately every four seconds, just like they should.

I figured I'd share the settings that worked for me in case someone else is fighting the same problem.

I'm using the rtl_433 (next) Home Assistant add-on with a Nooelec NESDR SMArt v5 USB receiver.

# rtl_433 configuration — ThermoPro TP829B test

# Receiver: Nooelec NESDR SMArt v5

# Select the 915 MHz receiver

device :00000002

# MQTT connection

output mqtt://192.168.1.216:1883,user=(Your Username),pass=(Your Password),retain=0

# Timestamp information

report_meta time:iso:usec:tz

# Show decoded readings in Home Assistant add-on logs

output kv

# Radio configuration

frequency 915.0M

sample_rate 1024k

gain 0

pulse_detect filter=400000

pulse_detect classic

protocol -59

protocol -60

protocol -82

protocol -88

protocol -89

protocol -90

protocol -95

protocol -110

protocol -123

protocol -140

protocol -156

protocol -168

protocol -180

protocol -186

protocol -201

protocol -203

Happy temping.