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
This is a follow-up to #52 and possibly the same as #24.
After flashing badgemagic-firmware compiled from v0.1-12-g9cda337, the badge is now not found via BLE. Recall that in #52 with the OEM firmware, the badge was found but the connection failed.
I noticed that the BLE device name changed from LSLED to LED Badge Magic:
% badgemagic --transport ble --list-devices|grep LED
- […]: name=Some("LED Badge Magic") services=[0000fee0-0000-1000-8000-00805f9b34fb]
Changing BADGE_BLE_DEVICE_NAME from "LSLED" to "LED Badge Magic" resolves this issue and lets me upload examples/smiley.toml via BLE.
The text was updated successfully, but these errors were encountered:
Let's give more control to users. At the current state, we could upload bitmap content to someone's badge accidentally, especially with the coming-up always-on BLE feature. To resolve this, I've made the device name configurable in fossasia/badgemagic-firmware#67
So let UUID and device name be decided by users as arguments, and should have defaults if the arguments are not specified to avoid complexity for new users.
This is a follow-up to #52 and possibly the same as #24.
After flashing badgemagic-firmware compiled from
v0.1-12-g9cda337
, the badge is now not found via BLE. Recall that in #52 with the OEM firmware, the badge was found but the connection failed.I noticed that the BLE device name changed from
LSLED
toLED Badge Magic
:Changing
BADGE_BLE_DEVICE_NAME
from"LSLED"
to"LED Badge Magic"
resolves this issue and lets me uploadexamples/smiley.toml
via BLE.The text was updated successfully, but these errors were encountered: