Service: http hosting binary images

[smadds]

UPDATED 2nd July
Now checking for new version every 10 minutes and if so copying all assets from the latest release, as listed here:

https://github.com/arendst/Sonoff-Tasmota/releases/latest

and host them in this folder:

http://sonoff.maddox.co.uk/tasmota/

then updating the version number on my mqtt server (see comment below)

Also copying sonoff.bin to sonoff.ino.bin for backward compatibility.

UPDATED 6th April
Now copying everything (*) from /api/arduino folder to hosted area. Currently this adds http://sonoff.maddox.co.uk/tasmota/sonoff-minimal.ino.bin, in case anyone is doing 2-stage uploads.

UPDATED 23rd Feb

Not sure if this is useful for anyone, but I am hosting the binary image on an http server to allow Sonoffs to update via URL (Github insists on https which is beyond the standard configuration of firmware).

Every 10 minutes I check for a new version, and if so pull the update and compile to the following URL:
> http://sonoff.maddox.co.uk/tasmota/sonoff.ino.bin

Every hour, on the hour I get the latest binary from
> https://github.com/arendst/Sonoff-Tasmota/raw/master/api/arduino/sonoff.ino.bin
and host it at
> http://sonoff.maddox.co.uk/tasmota/sonoff.ino.bin

I was wary of doing this with the old version of the software, due to the number of tweaks needed in the config file before compiling. Still, if you want the raw mqtt-ota version from
> https://github.com/arendst/Sonoff-MQTT-OTA-Arduino/raw/master/api/arduino/sonoff.ino.bin
it's also available at
> http://sonoff.maddox.co.uk/mqtt-ota/sonoff.ino.bin

[wiktorschmidt]

@smadds maybe you could provide an alternative approach (using Github releases). I described it here:
arendst/Sonoff-MQTT-OTA-Arduino#260

[smadds]

Looking at your suggestion again, @wiktorschmidt, I read it as making a secure connection to create a local copy on a trusted machine on the local network. Is this correct?

[ThomDietrich]

@smadds that's a nice gesture of yours. I went ahead and included your URL in an automatic upgrade example over in the wiki: https://github.com/arendst/Sonoff-Tasmota/wiki/openHAB
I hope that is fine with you. Thanks!

I'll also subscribe to this thread to stay up to date with changes.

[wiktorschmidt]

@smadds sorry I wasn't clear

What I meant is that instead of linking to
https://github.com/arendst/Sonoff-Tasmota/raw/master/api/arduino/sonoff.ino.bin
you can link to the automatically compiled (via TravisCI) firmware.bin file that can be found here:
https://github.com/arendst/Sonoff-Tasmota/releases/latest
is a little bit more tricky as there is no "direct link" to the bin file - you need to extract it from JSON via github API: https://api.github.com/repos/arendst/Sonoff-Tasmota/releases/latest it's assets[0].browser_download_url

Thanks for putting it together!

[ThomDietrich]

@wiktorschmidt Interesting! Regarding the openHAB solution above: I will stay with the direct link for now. JSON parsing is an easy job in openHAB but would definitely make the example less comprehensible.

[wiktorschmidt]

@ThomDietrich absolutely - this would have to be implemented by @smadds to make sense. Obviously parsing JSON is not a good idea on the openHAB side :)

One can also look at https://github.com/carolynvs/github-release-proxy - this solves the http/https problem quite elegantly.

[ThomDietrich]

At the end of the day it would probably be best if @arendst hosted an "official" build behind a static http url.

[wiktorschmidt]

@ThomDietrich it IS hosted by @arendst on github. The only problem is that it's only available via https

[ThomDietrich]

@wiktorschmidt no, @smadds is providing a local copy. At least that's what he says in his first posting ;)

[smadds]

Not sure about local, @ThomDietrich, my HTTP copies are hosted on a cloud VPS.

Yes, happy for anyone to access them as a contribution to this excellent project.

Oh the power of issuing an mqtt "cmnd/sonoffs/update" !

[smadds]

UPDATED 23rd Feb:

NOW JUST COMPILING THE BASIC VERSION

Just to say that I have extended the number of .bin files available by using platformio on the server to locally compile the Tasmota branch for different boards. The script now looks every 10 minutes for a change in version number and recompiles the targets if required.

I have added nodemcu and ESP8285 (sonoff touch etc.) to the standard sonoff versions. The URLS are:-

• http://sonoff.maddox.co.uk/tasmota/sonoff.ino.bin
• http://sonoff.maddox.co.uk/tasmota/sonoff-nodemcu.ino.bin
• http://sonoff.maddox.co.uk/tasmota/sonoff-8285.ino.bin

If anyone needs another target that platformio is capable of compiling on Linux then let me know. (RPi is NOT currently available as it needs compiling on an RPi)

The old branch is still being copied from the github repository hourly as before.

[arendst]

Starting with version 3.9.12 there is no need to compile specifically for the ESP8285 if the image is uploaded by webpage or OTA.

If the device is configured for Sonoff 4CH OR Sonoff Touch, both ESP8285, the downloaded ESP8266 firmware image is updated with the specific ESP8285 DOUT option before it gets written to the device flash during reboot.

For serial uploaded images it is still MANDATORY to use the DOUT flag during compiling and uploading to ESP8285 devices.

[jaysuk]

Do I still need to compile separate images for devices with 1M memory and ones with 4M memory?

[arendst]

Well if you want to...
I use 1M images on all my sonoff related hardware so also on ESP12Es, Wemos and the Pow which has 4M too.