convention
convention copied to clipboard
Homie-OTA
I'd like to have a second repository soon for a separate homie-ota specification. It will evolve in parallel to this homie-core convention and would require Homie 3.x for defining the topology.
If anybody is interested in defining required topics, please go on.
Does it require 3.x or 4.x and the implementation going on in #132 which is tagged for 4.0?
3.x, but compatible to 4.x. The way how properties are defined hasn't changed.
Are we going to support multiple ways of OTA Update or do we specify one that every device must support? There are a lot of ways to implement OTA.
- Upload over MQTT
- Publish URL and devices download the firmware from a server
- Some obscure vendor defined protocol
While upload via MQTT is fine for simple devices, if you have thousands of them you might want to use a CDN for firmware, which makes url publish a better option.
homie supports broadcast. I'd say the OTA specification negotiates a broadcast channel with every interested device and publishes the update via the broadcast channel.
The following methods would be awesome:
- HTTP pull
- MQTT push
hello, any update on this topic? i'm developing and ESP32 generic firmware using homie and a standard OTA approach through MQTT would help. somethig like this