@DavidFW1960 - Yes I can access the web interface. Apart from this upgrade process everything about my Sonoffs is working perfectly (except for one that seems to always turn on when it joins the network but that is another story 
).
It is a bit of a mystery which I’d put down to some quirk at my end except that @PierreScerri has/had the same problem.
@reloxx13 - Are you suggesting there is no upgrade path from 5.12.0 to 6.1.1? I thought only much earlier versions had upgrade issues.
The blog linked to indeed says you need to have 5.14 before 6.1.x
Mine will also switch on when it joins the LAN.
Yes, thanks. I went to look and saw that too.
I then got side tracked before I could reply to thank @reloxx13
I was side tracked by a @DrZzs video which spoke a bit about all sorts of issues with version 6.x so I think for the time being I might leave mine at 5.12 as I am having no issues. Or possibly go to 5.14
Interesting. I’ll have to look for that video. I haven’t had any issues at all.
Have you checked your MQTT broker for a retain command on that switch? What does the console show as soon as it boots and turns on? Either sometime in the Sonoff is telling it that it needs to fire up when it boots or MQTT is telling it to turn on from a retained message.
Don’t get that, as we’ve discussed before, we seem to use the same settings and mine don’t.
@DavidFW1960 - It was the latest live stream (https://www.youtube.com/watch?v=4syhAh1WwLo) I don’t normally watch them (sorry @DrZzs) but for some reason I started this one, It is some time before minute 37 because that is where I stopped.
@digiblur - thanks, I’ll check all my settings. I am pretty sure all my sonoffs are identical but I’ll have a good look using the details you suggest.
HI
Just saw this post.
I have 2 Sonoff Basics on 5.12 that will not upgrade to 5.14. In fact I had to reflash them with 5.12 via FTDL. Which was a pain as I had to remove them from their installation.
My Sonoff Duals (11) were on 6.1 and alos would not upgrade.
Yesterday I set the ssl setting to false in the Tasmoadmin add-on and the Duals upgraded in one go after a couple of 30 second retries. the only thing is that Tasmoadmin is now not accessible from the Hassio panel. It is accessible directly from a bowser or from the add-on itself in the Hassio.io tab.
I’ll try one of the Basics eventually. Will let you know how it goes.
Check your panel setting. I bet it still has the ssl URL set.
This is what I have:
panel_iframe:
tasmoadmin:
title: TasmoAdmin
icon: mdi:lightbulb-on
url: http://hassio.local:9541What about you http settings?
@DavidFW1960 Please stop responding with guesses. Be either complete and sure about your answer or do not answer at all. This is causing a lot of conversation, which is going nowhere and starts to look like a chat. (Please use Discord).
@PierreScerri Apparently, mixing SSL & non-SSL has become an issue for firmware upgrades. I’m looking into a solution on the add-on part to solve this. For now disabling SSL indeed works, but the payoff will be the integration within the Home Assistant frontend. You cannot mix SSL/non-SSL in a webpage, which is the case here (Home Assistant in SSL, TasmoAdmin is non-SSL).
I’m going to try to offer both (SSL for the frontend) and both SSL/non-SSL access to the firmware for upgrading. This will take some time from my end, so please be patient.
Firmware upgrading issues
About the 6.x firmware and the upgrade of firmware via TasmoAdmin in general, a more appropriate place to report these issues would be the TasmoAdmin GitHub repository. Remember this add-on is wrapping the software, but does not modify its basic functionality.
https://github.com/reloxx13/TasmoAdmin/issues
I know @reloxx13 is active in this topic, now and then, nevertheless, I would help the project to report on the original software GitHub to be able to keep track of issues and solutions.
…/Frenck
http:
# Secrets are defined in the file secrets.yaml
api_password: !secret http_password
# Uncomment this if you are using SSL/TLS, running in Docker container, etc.
base_url: !secret http_base_url
ssl_certificate: /ssl/fullchain.pem
ssl_key: /ssl/privkey.pem
The base url is a duckdns address. I need use this for remote access.
I don’t need to use TasmoAdmin remotely.
Also I’m running Hassio which I believe runs in a docker container (don’t quite understand dockers yet). It says to use base_url if using a docker or SSL.
Hi
Sorry for all the banter. As it is I can use TasmoAdmin one way or the other. That’s fine. Thank you for your intervention. I will take your advice and be patient.
Thank you.
@PierreScerri There is nothing wrong with your configuration.
Enabling SSL on the TasmoAdmin (without exposing it to the internet) would cause a firmware upgrade to be picked up from a different host (e.g., hassio.local, or IP address). In that case, the certificate becomes invalid, since it was issued for your duckdns.org address.
For now disabling SSL on the TasmoAdmin will work, until a better solution has been implemented. The downside of this, is loosing the ability to embed it into the Home Assistant frontend.
…/Frenck
It’s been 5 days since you responded to anyone in this thread and people just try to help!
And I thank you for that! Just asking you to keep something in mind when responding.
5 whole days? That is just outrageous! 
Lets move on.
I keep getting the following error when going to the TasmoAdmin page: “COULD NOT CREATE OR WRITE IN CONFIG FILE”
I tried uninstalling and instaling but the error persists. Any ideas?
I love this add-on. I’m running version 0.4.0 on HASS.IO version 0.75.2. My server is using duckdns ssl and all is good. I just changed my system over from netgear to unify equipment. I’m not sure if Ibroke something or something else happened but I cannot seem to run the update routine anymore (see below)
{
"log_level": "info",
"ssl": true,
"certfile": "fullchain.pem",
"keyfile": "privkey.pem",
"ipv6": false
}
The front end is working just fine. Just not able to download updates.
What do you have set in the addon for the update server?