Flashing the Shelly1 with Tasmota!!! 

That is awesome news!

I will keep it in mind, i dont currently have a usb zwave stick to test open zwave with. Ill have to see about ordering one.

I like the Aeotec Z-stick. It is a bit arcane in its minimalist user interface, but it has worked flawlessly for me so far. I got it from Amazon for about US$45. I finally got openzwave working. Two key points: 1) Some openzwave docker containers didn't work for me. The one that did was eugenmayer/rpi-nodered. 2) Homeassistant 0.86.3 has fixed most of the bugs in the Z-wave interface and now makes the openzwave control panel nearly obsolete. Where I have had to go back to the openzwave container is when I have nodes that get flagged as "dead" because the power was out when they got polled. Unfortunately Hass does not let me recover them easily and a network heal has no effect on them. Openzwave did fix them. YMMV. Just an FYI in case anyone cares, I am running all of these containers on a Raspberry Pi 3 with rasbian OS. My command to properly run the openzwave container was:docker run -d --name="ozw" -v /home/homeassistant/vols/ozw:/opt/open-zwave-control-panel/config --device=/dev/ttyACM0:/dev/ttyACM0 -p 9090:8080 eugenmayer/openzwave-panel (note: I moved the port due to the way my system is set up).

sorry about that, ill look at getting it updated for you!

i like the tasmota software and of course i love getting in and messing with stuff so if i can flash something, i usually do. But you make a good point!

Are you using the stock firmware mqtt with Home Assistant? If yes, what configuration.yaml settings did you you? I've tried for hours and can't get the Shelly 1 to show up in HA. I'm actually getting ready to flash Tasmota on my Shelly 1.

@@ptmoy1 Hmmmh, it was relatively easy to integrate the shellies in HA, I use Hassio 0.84.6 on a Pi. and an external mosquitto Broker on another Pi. But the integrated broker in HA should of course work too. If the Shelly1 is in the same WiFi Network as your MQTT broker, then config the Shellies under "internet & Security - Advanced - Developer Settings" setting checkbox "Enable action execution via MQTT" enter MQTT Server: Address/Port & User/Pwd (if used) of your broker. Cloud is now disabled, it says: : WARNING: If you enable MQTT - actions via Cloud connection will be disabled! Home Assistant: Here I defined a new mqtt-switch: (Notice: Topics of the shellies are fixed in their firmware, Version 1.46 / 08.02.2019 is current version) configuration.yaml: # Switches switch: !include_dir_merge_list switches/ in directory "switches" a file like: mqtt_switches.yaml: Example with Shelly 1: XXXXXX is the ID of the shellies ( eq. 3 lower Bytes of the MAC-Address) ## Shelly Switches - platform: mqtt name: "ShellyXXXXXX" friendly_name: "Porch Light" state_topic: "shellies/shelly1-XXXXXX/relay/0" command_topic: "shellies/shelly1-XXXXXX/relay/0/command" payload_on: "on" payload_off: "off" state_on: "on" state_off: "off" optimistic: false qos: 1 retain: true .. .. Hope, this helps...

@@Take5Instead4 Thanks for your reply. I have 2 Shelly1s. Already flashed one to Tasmota, and got it working in HA. I'll try the second with the stock firmware again using your yaml parameters. I needed to set a time schedule on the tasmotized Shelly1. Had lots of problems getting that to work. Turned out the timezone was wrong. Figuring out how to set to the correct timezone in tasmota was a pain; finally did figured it out. The embedded web UI in the Shelly1 stocked firmware looks to be a bit more capable than the Tasmota's.

@@ptmoy1 The Shelly1 firmware offers more than I currently use. In the end, it's a power switch that I can control with automation scripts in home assistant. In the future I want to use Shelly2 for certain purposes, because they measure the power consumption which can be logged in HA (defining a mqtt sensor in HA).

once its flashed, you should be able to cycle power on it and then the wifi AP should come up.

here is the one that I use, it works great! www.amazon.com/gp/product/B075N82CDL/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1

@@BurnsHA That's the one I got, but the cables don't fit in the ports. Did you grab another cable?

Thanks for the comment!

if you go to the tasmota browser, does it work properly?

there is a predefined template for the shelly1 in tasmota. If you select that, then you should be set!

Thanks, BurnsHA! Good to know. I’ll be flashing my first Shelly 1 today, following your guide. If I have any problems, you’ll hear about it right here! ;D

thanks for the comment!

so you were initially able to see them with the ad-hoc network after they were flashed?

@@BurnsHA correct. After posting i read through the other posts and followed jerry aycock's advice and was able to get back to normal. I am able to once again see the tasmota adhoc sign in page at 192.168.4.1 which is no where near my 10.0.0.1 IP scheme. After i enter ssid and password everything disappears. Where is the 192 ip coming from and how to I change it to my 10.

I figured it out totally my fault not paying attention.

@@chrisnielsen4216 what was wrong?

So you don't see the adhoc wifi network to connect to after flashing?

Finally got it. Had to flash to Blank 2mb bin and start over. Think WIFI pw may have been wrong... THANKS

@@BurnsHA Got it.. thanks.. bad PW.. replaced my keyboard....

that will get you everytime! glad you got it working!

I think you can flash with tuya-convert now, its much easier.

Yes, im definitely going to order a couple of those when they come available.....

whats's the diff between 1 and 2.5?

Plz help bro

what issue are you having?