You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
not a bug but an understanding problem. Until now I used espresence, and there I can set the max distance per room.
For example I have configured bluetooth_proxy for devices in my bedroom and my kitchen for testing now, this rooms are on different floors. The place I put my phone every night is so,etching between the tracker for bedroom and kitchen. But kitchen is around 3 meters away and bedroom tracker around 1.5 meter. And I can see it bouncing between this areas.
The dining area also does pick the kitchen signal even it should not. Espresence was set a max distance for the kitchen tracker so outside the kitchen it was not seen.
Is that possible with Bermuda? Maybe I missed the docu for that config.
I saw the setting in config for all areas but I want to change this per area. Some areas are larger than other so it makes no sense to set this globally
The text was updated successfully, but these errors were encountered:
not a bug but an understanding problem. Until now I used espresence, and there I can set the max distance per room.
For example I have configured bluetooth_proxy for devices in my bedroom and my kitchen for testing now, this rooms are on different floors. The place I put my phone every night is so,etching between the tracker for bedroom and kitchen. But kitchen is around 3 meters away and bedroom tracker around 1.5 meter. And I can see it bouncing between this areas.
The dining area also does pick the kitchen signal even it should not. Espresence was set a max distance for the kitchen tracker so outside the kitchen it was not seen.
Is that possible with Bermuda? Maybe I missed the docu for that config.
I saw the setting in config for all areas but I want to change this per area. Some areas are larger than other so it makes no sense to set this globally
The text was updated successfully, but these errors were encountered: