#2013 Revamp automatic reconnection

Open
opened 2 weeks ago by TaaviE · 0 comments
TaaviE commented 2 weeks ago
name about
Improvement request Automatic reconnection improvements

Seeing how there’s an increasing amount of different devices and different requirements to how reconnection should work, I think the system might need a refactor. All the autoreconnection settings should also probably be gathered under a single menu?

Use cases to keep in mind when redesigning it:

  • Devices that need balanced effort. Short disconnection is fine, sometimes people move out of range. Exponential backoff. E.g. Mi Bands and Pebbles

  • Devices that need best effort at staying connected. Short disconnection is not fine. Possible alert on disconnection. E.g. iTag/Nut/similar link-loss alert devices.

  • Devices that need low effort. Being disconnected is fine. Would need very infrequent connection for timezone updates for example without taking priority over other devices. E.g. LYWSD02 and similar.

  • Devices that need no connection at all. For gathering readings from devices like the LYWSD02. Scanning for these broadcasts could also be used for reconnection to other devices. (Possible piggy-packing on COVID-19 contact tracing scans?)

Any suggestions and/or improvements? Any potential use-cases I’ve missed?

--- name: Improvement request about: Automatic reconnection improvements --- Seeing how there's an increasing amount of different devices and different requirements to how reconnection should work, I think the system might need a refactor. All the autoreconnection settings should also probably be gathered under a single menu? Use cases to keep in mind when redesigning it: * Devices that need balanced effort. Short disconnection is fine, sometimes people move out of range. Exponential backoff. E.g. Mi Bands and Pebbles * Devices that need best effort at staying connected. Short disconnection is not fine. Possible alert on disconnection. E.g. iTag/Nut/similar link-loss alert devices. * Devices that need low effort. Being disconnected is fine. Would need very infrequent connection for timezone updates for example without taking priority over other devices. E.g. LYWSD02 and similar. * Devices that need no connection at all. For gathering readings from devices like the LYWSD02. Scanning for these broadcasts could also be used for reconnection to other devices. (Possible piggy-packing on COVID-19 contact tracing scans?) Any suggestions and/or improvements? Any potential use-cases I've missed?
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.