mirror of
https://github.com/esphome/esphome.git
synced 2026-09-27 06:50:22 +00:00
J. Nick Koston
5ec7047151
- A zero-service table on a client with nodes is treated as a failed discovery (warn, release, charge the backoff, disconnect): a real GATT peer always exposes at least GAP/GATT, so an empty table means the materialization failed and the connection must retry instead of sitting inert behind a successful on_connect - The fan-out abort guard also tests cancel_requested_, covering the normal async teardown a node starts from on_connected (the state-only check caught just the synchronous refusal) - nodes_ becomes a StaticVector sized by ESPHOME_BLE_CLIENT_MAX_NODES: the client requests a baseline slot, each neutral write action (which registers itself in its constructor) requests one, and the define rides defines.h for analysis - no realloc machinery on the rp2 target - The Bluedroid empty-table return logs its quiet cases; the service_table=False stub notes the misconfiguration it implies
