Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OTA Updates #9

Open
maximiliani opened this issue Jan 12, 2021 · 1 comment
Open

OTA Updates #9

maximiliani opened this issue Jan 12, 2021 · 1 comment
Labels
enhancement New feature or request

Comments

@maximiliani
Copy link
Member

As already mentioned in MQTT, firmware updates should happen over OTA. In this topic it is necessary to implement OTA and OTA configuration via MQTT.

@maximiliani maximiliani added the enhancement New feature or request label Jan 12, 2021
@JulianFP
Copy link
Member

JulianFP commented Oct 10, 2021

OTA updates should be done without the need of an internet access for the mqtt-devices. This could be implemented like this: The Privatehome Server checks on a regular basis (e.g. daily) for firmware updates. If one is present, it sends the mqtt-devices over mqtt an request to download the new firmware from the Privatehome Server. The devices are only allowed to download the firmware from the same server as they use for the mqtt-connection (to prevend man-in-the-middle attacks). Then the devices download the firmware over http and install it themselves. For this it is necessary, that the private keys are stored in the ESP EEPROM, so that they aren't lost after the update. For some extra security the server could also send the checksum of the binary in the same mqtt request, and the ESP could compare it after downloading with the actual checksum.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants