One (hopefully) final question: I went back to Home Assistant, added the Shelly integration, input the IP address, and was shown “The device is using an unsupported firmware version.” Via a web-page (on my desktop) to the Shelly device, I went to Settings->Firmware Update and there saw the message "The current Firmware version of your Shelly device is 20191217-140757/1047-long-id-for-shelly-devices@a0661583 No newer firmware available. " Now I am really confused (and it is hard the believe that firmware that is two plus years old is the most recent).
Set up Unicast CoIoT in the device:
I’d take some screenshots for you but am away from home without remote access at the moment.
There is not option to ‘Enable Colo T’. I did find some stuff about forcing an OTA update and I want to try that, but the website http://archive.shelly-tools.de/, which seems to assemble the proper URL, is asking for a Shelly Type and I have no idea which one to select.
Okay - I figured out that my device is a SHSW-1, so I entered the info and got the following URL: http://192.168.73.210/ota?url=http://archive.shelly-tools.de/version/v1.11.0/SHSW-1.zip. (Not the latest version, but should be close enough for testing purposes). I entered this URL into the address bar of my browser and saw: {“status”:“updating”,“has_update”:false,“new_version”:"",“old_version”:“20191217-140757/1047-long-id-for-shelly-devices@a0661583”}
The false after has_update bothers me…
Not sure what is going on there, I have a spare shelly 1 and will try wiring it up and see what happens.
But there may not be if the firmware is not up to date. Chicken, meet egg!
Yeah ok. That does seem quite old, 2019?
This is the latest firmware:
Firmware: 20220209-092750/v1.11.8-g8c7bb8d
FWIW- I have never gotten this to work with new devices. I just use espHomeFlasher.
I have one Shelley in the wall that has Tasmota flashed to it, but it’s been a couple of years so I forget the process I used to flash Tasmota on it.
Generally, any ESP device, ground pin GPIO0, apply power, (you can remove the ground now or later- it doesn’t matter), flash the bin file, remove the ground on GPIO0 if you haven’t already, reset or power off/on the device.
I may put ESPHome on it in the future, but the switch box that it’s inside of is in an inconvenient location in case the OTA fails. I.E., if it isn’t broken, don’t fix it.
If you definitely don’t manage to use your shelly device you can flash with Tasmota using OTA with this project: https://github.com/yaourdt/mgos-to-tasmota
No need to wire it, works OTA.
Then you will be able to update to ESPHome using the Tasmota dashboard.
Glad I found this thread - I thought I was crazy.
I have the exact same situation/journey as @groston:
- Shelly HA integration reports “Unsupported firmware”
- Update > “On latest firmware - no update available”
- No “Enable CoIoT” in Advanced. Only “Enable MQTT”
- Enable MQTT: Shelly unofficial through HACS via MQTT doesn’t pick it up
- Don’t even see any MQTT messages on boot or at any time from Shelly
curl -X POST -d '{"id":1, "method":"Mqtt.GetStatus"}' http://shelly-ip/rpcreturns “Not Found”
Was about to manually create some kind of REST entity on HA when I found this thread.
Unfortunately, we don’t see this.
I was also dead-set on flashing with ESPHome borne from the frustration and weeks spent trying to get HA to detect the Shelly that is “so well supported” 
I have another boxed Shelly1 that I can try but I’m certain it will be the same firmware as it was purchased at the same time.
Looks like we’re in some kind of strange firmware state so I’ll be happy to keep debugging so that it may help others in the future but I am running out of ideas.
Have you reported on the Shelly forum that your device won’t upgrade? There are threads there about it.
Haven’t come across their forums yet.
Though up until now I wasn’t sure what the actual problem was; thought it was me doing something wrong.
I have raised a ticket with Shelly though!
What firmware does it have?
There is a way to update the firmware locally rather than over the internet. Let me see if I can find it…
May have solved it @nickrout and @tom_l through local update
Dove through the Shelly Forums but it’s all German to me (anyone laughing? anyone?)
This poster claims that there is no egress to WAN (which I most definitely do have) but suggested a local webserver.
My steps on a server that has WAN and a route to the Shelly:
wget http://archive.shelly-tools.de/version/v1.11.0/SHSW-1.zip
python3 -m http.server 9999
(in another terminal)
curl http://<ip-of-shelly1>/ota?url=http://<ip-of-server>:9999/SHSW-1.zip
On the OTA command I received:
{"status":"updating","has_update":false,"new_version":"","old_version":"20191217-140757/1047-long-id-for-shelly-devices@a0661583"
On checking firmware after I get:
$ curl http://<ip-of-shelly>/shelly
{"type":"SHSW-1","mac":"C45BBE76XXXX","auth":false,"fw":"20210720-184522/v1.11.0-g6abd92e","longid":1,"num_outputs":1}
On checking my Internet & Security > Advanced - Developer Settings, I can see CoIoT!
Yep that was the procedure I was looking for (though with webserver software)
Happy to report the Shelly 1 was happily configured on HA!
Thanks for the suggestion of their forums @nickrout 
Glad you have it sorted
1 Like
For the record, this is what I received from Shelly support.
It was an old FW, and you need to update.
and
Try ti connect the device to a hotspot WiFi and update it’s firmware through this network.
Seeing the amount of posts and threads around this, I don’t think the UI update is as flawless as they anticipated.
1 Like