Beacon monitor remembers values from when it was disabled

Home Assistant Android version: beta-2762-93844ffe-full

Android version: 11 Phone model: Motorola G9 play Home Assistant version: 2022.10.0 Last working Home Assistant release (if known):

Description of problem: I use the beacon monitor sensor to detect when we get home and open the door. I also have an automation that detects when my spouse parks her car in the garage about 200 m from home (far from reachable with the beacon). I heard the announcement that she had parked the car and that also enables the sensor using:

          - service: notify.mobile_app_petra
            data:
              message: command_beacon_monitor
              data:
                command: turn_on
                channel: beacon
                importance: high

This means her phone now listens for the beacon at home and when her phone sees it another automation will run that will open the door, this automation was triggered at the same time as the previous automation. I opened the developer tools and had a look at her sensor and managed to get a screenshot of the issue

Here she is at least 200 m away with houses blocking and the sensor reports the state it was in when the sensor was turned off as she left home. Because I turn on and off the sensors since it’s not needed and to make sure it does not wrongfully open the door (ironic).

I have managed to replicate the issue that when you enable the sensor and stand close to a beacon, turn it off and move away then turn on again, then the sensor will report the old state for a few seconds before it realizes it’s not there.

Because of this bug the sensor and/or the command to turn it on/off is more or less useless.

Traceback (if applicable, to get the logs you may refer to: https://companion.home-assistant.io/docs/troubleshooting/faqs/#android-crash-logs):

Screenshot of problem:

Additional information:

[Hellis81]

Here is a video of the issue. In my opinion it seems as it’s the app that sends the data.

https://www.youtube.com/watch?v=bLUBbh3HgVw

[Hellis81]

It seems like a bug for sure.