connections — scheduled sender uploads impossible on battery (ESP32-S3)
Board: Seeed reTerminal E1002 (ESP32-S3), firmware 2.1 (same behavior on
the previous version), battery powered, deep_sleep_time_seconds 1800,
sender = Home Assistant OpenDisplay integration via ESPHome Bluetooth proxy.
Observation:
On every periodic deep-sleep wake-up the device advertises normally (v1
advertisement with battery/sensor data; status shows connReq=0), but it never
accepts a connection. Every upload attempt during these windows fails with:
Failed to connect after 5 attempt(s): Timeout waiting for connect
response while connecting to XX:XX:XX:XX:XX:XX after 20.0s
Connections DO succeed reliably right after boot (and, before 2.1, after a
button wake). Increasing the awake time to 60 s does not help — the wake
window seems to be beacon-only regardless of its length. There is no
sleep_flags bit for this (all reserved in the Config Builder).
Question / request:
Is beacon-only wake-up intended behavior? If yes, could a config option be
added to make periodic wake-ups connectable (even for just a few seconds)?
Use case: a sender like Home Assistant pushing scheduled dashboard updates to
a battery-powered display without user interaction. Right now this is
impossible — uploads only work after a reboot or button press.
connections — scheduled sender uploads impossible on battery (ESP32-S3)
Board: Seeed reTerminal E1002 (ESP32-S3), firmware 2.1 (same behavior on
the previous version), battery powered, deep_sleep_time_seconds 1800,
sender = Home Assistant OpenDisplay integration via ESPHome Bluetooth proxy.
Observation:
On every periodic deep-sleep wake-up the device advertises normally (v1
advertisement with battery/sensor data; status shows connReq=0), but it never
accepts a connection. Every upload attempt during these windows fails with:
Failed to connect after 5 attempt(s): Timeout waiting for connect
response while connecting to XX:XX:XX:XX:XX:XX after 20.0s
Connections DO succeed reliably right after boot (and, before 2.1, after a
button wake). Increasing the awake time to 60 s does not help — the wake
window seems to be beacon-only regardless of its length. There is no
sleep_flags bit for this (all reserved in the Config Builder).
Question / request:
Is beacon-only wake-up intended behavior? If yes, could a config option be
added to make periodic wake-ups connectable (even for just a few seconds)?
Use case: a sender like Home Assistant pushing scheduled dashboard updates to
a battery-powered display without user interaction. Right now this is
impossible — uploads only work after a reboot or button press.