-
Notifications
You must be signed in to change notification settings - Fork 151
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Identify BLE device #171
Comments
Hey @andresp, In the ble sample, the MAC address is printed via RTT logging on first boot. This is what I use to check the MAC address. You can also choose your own MAC address via compilation flags. The identify service is a good idea. The only issue is that currently, to squeeze the battery life to the max, we only advertise for a bit and shut the radio off completely. For an identify service, we'd need to advertise more often and also advertise more non-sensor data, which also consumes extra battery. As most people additionally use a case, the LED is not usually visible for the most part of its operation. I would be fine leaving this behind a config flag, off by default, or having a timer for 10-30 minutes in which the service is active. If someone wants to take a stab at it, I'm happy to review it. |
I do it with the nRF Connect phone app. |
there is a button on the device. I didn't go deep into the code. Couldn't it be used to wake up the board and send the MAC? |
I've been flashing a bunch of b-parasites in bulk and was wondering if there is a quick way to read out the BLE MAC?
As a feature request I would suggest implementing an "identify" command that makes the led flash, if that's possible through BT-Home. This could be helpful when provisioning and locating sensors.
The text was updated successfully, but these errors were encountered: