Skip to content

M1 Beta: Define OTA update path for standalone ESP controller #21

Description

@mastertape

Roadmap reference: docs/roadmap/m1-dhl-retrofit-beta.md

Define the beta OTA update path for the standalone ESP controller.

Acceptance criteria:

  • OTA mechanism candidate is selected or compared.
  • Local/trusted-network update assumptions are documented.
  • First successful OTA test is defined as beta acceptance criterion.
  • Failure modes are listed.
  • Rollback/failure-safety requirements for later versions are noted.
  • OTA does not require cloud service.
  • Security assumptions for update authorization are documented.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:firmwareDevice firmware and local controller behaviorarea:securitySecurity, safety and abuse preventionpriority:P1Important for first prototype

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions