convention icon indicating copy to clipboard operation
convention copied to clipboard

Homie-OTA

Open davidgraeff opened this issue 7 years ago • 5 comments

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.

davidgraeff avatar Nov 06 '18 22:11 davidgraeff

Does it require 3.x or 4.x and the implementation going on in #132 which is tagged for 4.0?

boc-tothefuture avatar Nov 09 '18 10:11 boc-tothefuture

3.x, but compatible to 4.x. The way how properties are defined hasn't changed.

davidgraeff avatar Nov 09 '18 11:11 davidgraeff

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.

Thalhammer avatar Nov 12 '18 09:11 Thalhammer

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

davidgraeff avatar Nov 12 '18 09:11 davidgraeff

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

ogghst avatar Sep 07 '22 09:09 ogghst