False positive Bluetooth problem

Hello !

I think I have a configuration problem somewhere.
But I want to be sure :slight_smile:

I’m currently doing presence management via a Nut 3 (long battery life — 1 year for now)

Here are the scenes and config:
The Nut:

Bluetooth integration config:

User in and out scene:


Check scene:

Basically every minute I scan and if the Nut is there or not then I send the information to my main instance

If someone can help me solve this mystery please :smiley:

PS: I added messages to make it easier to see ^^

The scenes look fine to me, but you’re using the same timing everywhere (scan frequency, scene check frequency, time before the device is considered « absent »); in my tutorial I used the following settings:

  • Bluetooth scan every 2 minutes
  • Away scene checked every 5 minutes
  • Nut considered absent after 10 minutes of not being seen. That means that for a device to be considered absent, it has to not be seen 5 times. In your case, once is enough. You see the point? :slight_smile:

Source: Gérer la présence avec la détection Bluetooth | Gladys Assistant

In my opinion what’s happening in your case is that because the timing is the same everywhere, it doesn’t have time to finish the Bluetooth scan and the device is immediately considered absent.

If you scan every minute, what I would do is set the non-detection duration to 2 minutes so that there’s at least enough time to finish a scan (a scan takes several dozen seconds)

1 Like

Thank you for taking the time to reply to me :slight_smile:
I’ll make the change accordingly and I’ll keep you posted :slight_smile:

1 Like

After 2 days, no more false positives, thank you!

1 Like