Yes, here is the Tasmota flash video
1 Like
What advantages does the Tasmota software have over the native software?
Why is it worth the effort of flashing?
2 Likes
Depends on your use case, Tasmota has more options and controls, i.e. multiple clicks, familiar interface, etc… I had Tasmota on all my Sonoff’s.
But like I said, if you just want a basic light switch, factory firmware works well enough without any flashing.
1 Like
Thanks for the share 
Have you been able to investigate if the other devices of that manufacturer use too ESP inside ?
I confirm that Shelly works like out if the box.setup in 5 minutes per device . No need to flash it. Like this it’s still possible to control the relay if homeassistant goes down 
very good devices will add them to all my sockets in the house 
I used the original firmware and setup MQTT. I used Alexa-local in Node Red to enable Alexa commands, but am now wondering if I could’ve just used Emulated Hue instead. Anybody know?
Its an on/off switch. Why change firmware on a perfectly working device? It is already working with HA and wilö never be able to do more than switch on/off, whatever firmware
I’ve used Shelly 1 in several applications and no longer flash them with Tasmota. I find with the factory firmware they stay connected. No dropouts or laggy web interface.
I have been using four of Allterco Robotics’ Shelly 1 devices for a couple of weeks now. The most recent original firmware version 1.3.5 (last time I have checked) supports MQTT. The switches sell for 10 € in Germany. Since the GPIO pins are accessible without disassembling the device one could flash something different, but why?
There is only one slightly annoying fact about the switches. Even if you activate the retain flag for MQTT status updates, they will spam the MQTT broker with their (unchanged) state every 20 seconds or so.
1 Like
At least to shelly 2 there is a 1.4 fw. Contact the support about the spamming
Incorrect.
With the right firmware, the shelly will be able to run its own automations, import sensor / state info from HA, trigger events to HA using double / triple / custom clicks of the switch.
Perhaps you are right, I never use it for something else than it is meant for. I can switch itvon off with an automation and that is enough. If I need something else I buy a device for that
Do you have a simple working configuration of Shelly1 for lights?
If yes, will you please share ?
I updated OP with my shelly1 light configuration using original firmware.
Hope that helps.
Sorry, not english here, what is OP and where to find it?
Ok i found it, but i need all the processes you explain before configuring it?
Or using shelly firmware i don’t need it?
OP = original post, 1st post here 
This post only used the original shelly1 firmware, you can watch this by HookUp which show step by step in setting up the original shelly1 app for HA.
Added my setup note and configuration.yaml to 1st post also.
I just received my Shelly1’s in the mail this week and started to experiment with them today. I came accross some issue with MQTT.
- The Shelly1 posts periodic updates of the state of the switch and the relay. The value of the relay is always correct but the value of the switch is always reported as 0, even if it should be 1. The value of the switch is still reported correctly when it changes.
- I was able to disable the periodic update by going to http://192.168.x.x/settings?mqtt_update_period=0 and this solved the issue with the incorrect periodic status reports.
- However this introduced a new issue where the status of the relay is not reported back when it changes. This still works fine for the switch.
I’m using the latest firmware ( 20190103-091629/v1.4.4) and have tried this on multiple Shelly1’s.
For now I can work with this because I use Philips Hue bulbs anyway and really only need the switch input but this bug makes Home Assistant automations using the switch as input and the relay as output unusable.
I will try to report this bug to the developer so hopefully it can be fixed in a future firmware update.
1 Like