Yes, after that it’s just the vagaries of Bluetooth, isn’t it?
@gaetanb76 are you sure you don’t see your Nut? Is it charged?
I don’t know what else to say!
The integration starts, the scan works and sees devices
[quote=« pierre-gilles, post:21, topic:7758 »]
Yes,
I don’t think we’re talking about the presence check here; he’s just looking at the « search » Bluetooth tab in the Bluetooth integration
it’s possible but I think we need more feedback to do tnr on that part too, in my opinion ^^
Unless the automated tests are OK on the GitHub side 
1 Like
Yes, I changed the battery yesterday. The Nut is visible and connected to the Nut app on my smartphone.
Indeed, it is in « Bluetooth Discovery » that it is not detected. Its MAC address does not appear.
Yes I confirm, I wanted to help, but indeed I’ll wait until everything is back in order, no hard feelings
Well that’s where I’m no longer sure, because I installed the Bluetooth container on the RPI where Gladys runs and with docker ps I have all the containers started, I thought Gladys would pick up that Bluetooth container and integrate it
No, you created a brand-new full installation of Gladys specifically to test Bluetooth.
Ah, I think, unless I’m mistaken, that the nuts must be connected to only one « master »
That is to say that you have to disconnect it from the app, then remove the battery to reset it and finally see it reappear, I had noticed that on Gladys V3.
Maybe that’s changed!
1 Like
And how do I start it?
Glad
@gaetanb76
from what I understand from this:
a master can have multiple slaves but a slave only connects to a single master
1 Like
[quote=« gaetanb76, post:30, topic:7758, full:true »]
to Glad
Indeed, that makes sense.
I disconnected the Bluetooth on my smartphone and the nut appears correctly in Gladys, without removing the battery.
Everything is ok Chief @pierre-gilles
I added the nut and created a scene triggered by the nut’s state change.
I created the presence on the dashboard.
toto is marked as « At home »
*** edit ***
I reconnected the Bluetooth on my smartphone.
The user is still present on the dashboard.
I’m going to let the instance run for a day or two to see if anything changes.
3 Likes
Amazing! Thank you to the three of you for the tests and for your feedback 
Make sure to delete your test container and the volume containing the test DB
I’m going to deploy this fix to prod!
3 Likes
Sorry for the waste of time,
One last question " the volume containing the test DB to be deleted " is it this one " ?
gladysassistant_test_bluetooth
@gaetanb76 and @pierre-gilles, thank
Yes, that’s the folder:
/var/lib/gladysassistant_test_bluetooth
Should I delete
/var/lib/gladysassistant_test_bluetooth
sudo rm -r /var/lib/gladysassistant_test_bluetooth
or just
sudo rm gladysassistant_test_bluetooth
sudo rm -rf /var/lib/gladysassistant_test_bluetooth
1 Like
Thanks @VonOx
I’ll do that
@VonOx was faster than me
-f, --force => ignore nonexistent files, do not prompt for confirmation
-r, -R, --recursive => remove directories and their contents recursively