MQTT Room Automation Broken Suddenly After Working For One Year Or More

Hi!

I’d like to start out with what I’m trying to do, because it’s worked for over a year reliably. I have motion sensors (Shelly) that turn on lights when I enter a room. They turn off the lights when I leave a room, or when there’s no motion detected. This led me to get a Blue Charm Beacon (Bluetooth BLE iBeacon (BC04P-MultiBeacon) – Long Range PHY (300 meters) & Water Resistant with Motion Sensor – Blue Charm Beacons) and follow the instructions in this YouTube video:
https://www.youtube.com/watch?v=p7C2QvmsM8M

Basically, I have a bunch of ESPresense devices around the house. They detect where the Bluetooth beacon is. The Bluetooth beacon has a working battery and I haven’t used KBeacon pro except in the past week to try to troubleshoot this.

This has worked for over a year without any drama.

It stopped working a week ago, and despite a rollback of my Home Assistant version, it still doesn’t work.

Again, the goal is: when I’m still in a room, don’t turn off the lights via Home Assistant. After a frustrating week of trying to fix this, I’m open to throwing money at the problem to make it go away if this just doesn’t work any more in Home Assistant. And no, going back to light switches isn’t happening for reasons.

Technical details follow:


From configuration.yaml:

  • platform: mqtt_room
    name: “My Beacon”
    device_id: “iBeacon:1b6295d5-4f74-4c58-a2d8-cd83ca26bdf4-3838-4949”
    state_topic: “espresense/devices/iBeacon:1b6295d5-4f74-4c58-a2d8-cd83ca26bdf4-3838-4949”
    timeout: 10
    away_timeout: 120

From a sample automation YAML:
alias: Workdays Office Routine
description: “”
mode: single
triggers:

  • at: “08:00:00”
    trigger: time
    conditions:
  • condition: and
    conditions:
    • condition: state
      entity_id: binary_sensor.workday_sensor
      state: “on”
    • condition: not
      conditions:
      • condition: state
        entity_id: sensor.my_beacon
        state: not_home
        actions:

It’d be amazing if someone could say “oh, Home Assistant broke that, and it’s not listed under Repair, but if you type this one magical command it’ll be fixed”. Or if it’s “hey, that’s a terrible configuration, you should spend $200 on this one solution that easily fixes the whole problem and integrates nicely with Home Assistant,” I’m game for that, too.

Home Assistant version: 2024.10.2
Supervisor: 2024.11.2
Operating system: 13.2

Help, please?

It would be amazing if you could develop “stopped working” :wink:
When you go to a doctor saying “I’m ill”, its first question would be “what are your symptoms”, don’t you think so?