Known limitations and future improvements
Hub name capture for Move Hub
The Move Hub and Prime Hub only send trier name in scan responses shortly after boot.
If the observer starts after the hub is already running, the name may
not be captured until the hub is restarted. City and Technic hubs
include the name in every regular advertisement and are unaffected.
See also: broadcaster-side workaround (broadcast a self-identification
string at startup).
PREVENTIVE_RESTART_EVENTS is an IRQ event count.
At ~120 ambient IRQ events/sec the default of 6000 gives ~50 seconds between restarts.
A high-noise environment (many BLE devices nearby) will restart more frequently than expected.
A future improvement could measure the actual ambient IRQ rate at
startup and set the threshold automatically.
Single channel per hub displayed
The observer handles multiple channels per hub correctly but all
channels share the same dedup state key. If a hub broadcasts different
values on different channels simultaneously, output may be harder to
follow. A future improvement could group or filter output by channel.
Ctrl-C unreliable under very high print load
With many hubs broadcasting counters at 100ms intervals the print rate
can exceed 10 lines/second, causing Ctrl-C to land mid-print and be
delayed or missed. In real-world use broadcast values change
infrequently and this is not an issue. A print throttle per hub
(minimum interval between printed lines) would address this for
stress-test scenarios.
Known limitations and future improvements
Hub name capture for Move Hub
The Move Hub and Prime Hub only send trier name in scan responses shortly after boot.
If the observer starts after the hub is already running, the name may
not be captured until the hub is restarted. City and Technic hubs
include the name in every regular advertisement and are unaffected.
See also: broadcaster-side workaround (broadcast a self-identification
string at startup).
PREVENTIVE_RESTART_EVENTS is an IRQ event count.
At ~120 ambient IRQ events/sec the default of 6000 gives ~50 seconds between restarts.
A high-noise environment (many BLE devices nearby) will restart more frequently than expected.
A future improvement could measure the actual ambient IRQ rate at
startup and set the threshold automatically.
Single channel per hub displayed
The observer handles multiple channels per hub correctly but all
channels share the same dedup state key. If a hub broadcasts different
values on different channels simultaneously, output may be harder to
follow. A future improvement could group or filter output by channel.
Ctrl-C unreliable under very high print load
With many hubs broadcasting counters at 100ms intervals the print rate
can exceed 10 lines/second, causing Ctrl-C to land mid-print and be
delayed or missed. In real-world use broadcast values change
infrequently and this is not an issue. A print throttle per hub
(minimum interval between printed lines) would address this for
stress-test scenarios.