2.16.0 detects BLE phones only for several minutes, than marks as Away

Describe the bug I am using Room Assistant to track two iPhones using BLE. I useone Raspberry Pi Zero W and one Raspberry Pi 3B with internal Bluetooth adapters. After updating Room Assistant on both PIs to 2.16.0 I noticed that Room Assistant no longer have stable tracking of phones when they are at home. Here how it looks in Home Assistant:

The problem occurs with two phones and on two PIs. I tried to restart Room Assistant service, PIs, MQTT Broker, HA, iPhones, Room Assistant companion apps.

I have relatively small apartment, before 99% of time both PIs tracked the phones when they were at home.

The only thing that changed (apart from updating to 2.16.0) is that I started to use ids under the tagOverrides elements in the config.

Relevant configuration On both PIs I have the same configuration, except for names and ids under the tagOverrides element.

global:
  integrations:
    - homeAssistant
    - bluetoothLowEnergy
cluster:
  autoDiscovery: false
homeAssistant:
  sendAttributes: true
  mqttUrl: 'mqtt://192.168.1.178:1883'
  mqttOptions:
    username: %username%
    password: %password%
bluetoothLowEnergy:
  timeout: 120
  updateFrequency: 1
  allowlist:
    - '%uid-for-first-phone%'
    - '%uid-for-second-phone%'
  tagOverrides:
    '%uid-for-first-phone%':
      name: BLE Kitchen Andrey iPhone 11 Pro Max
      id: kitchen_andrey_iphone_11_pro_max
    '%uid-for-second-phone%':
      name: BLE Kitchen Katya iPhone 12 Pro Max
      id: kitchen_katya_iphone_12_pro_max

Environment

• room-assistant version: 2.16.0
• installation type: NodeJS
• hardware: Raspberry Pi Zero W, Raspberry Pi 3B
• OS: Raspbian GNU/Linux 10 (buster)

[mKeRix]

There seems to be a bug with the id overrides for BLE then. I’ll put this to the top of the roadmap so that I take a look at fixing it soon-ish.

[gasecki]

Is there any chance that similar behavior may be existing in 2.19? I cannot get my RA stable on BLE / RPiZero2W.