Sonoff Devices / Sonoff with Tasmota

mine is 3.1 at the moment,
is this the version that cant be done OTA?
as far as im aware anything since version 1.6 can't be OTA'd unfortunately.
I'm also not a fan of soldering at all, mission, but test it out on a few other things and once you get the hang of it it's not so bad.
 
My setup is also done with a D1 mini and relay boards etc.
I soldered two wires to the button of a remote and stashed that inside the container the D1 lives in, that way its all inside the garage roof and can open the gate+garage door.
I used a hall sensor with a neodymium magnet to indicate the open/close positions.
I've got my D1+relay+sheild fastened to the actual garage motor and put the magnet on the arm that winds back when the garage opens.

My gate has huge gaps and these reeds need to be quite close.. where did you mount? Assume a big metal sliding gate? I have what used to be a place to keep the old dirtbins next to my gate that has power so I just stuck the d1 inside there and wired it directly to the gate motor
 
I run 8 sonoff r3's with tasmota, 2 pow r2's i havent flashed yet and over december setup a d1 mini + relay sheild + reed switch for my garage and front gate (no reed on gate, need to find a suitable place to mount it)

If anyone is thinking of getting a Sonoff SV for gates / garage I'd recommend the Wemos D1 - a lot easier, micro USB powered and always in flashing mode. Runs tasmota just fine (see: https://www.inspectmygadgets.com/wemos-d1-mini-garage-door-opener/)

Anyone running Home Assistant? Very cool - I've got my alarm (paradox), Sonoffs via eWeLink as well as Tasmota's, Hikvision cameras, Arlo cameras, chromecasts, google speakers and even my inverter (scraping the json feeds from the inverters web uri) all set up nicely - highly recommend checking it out. Once you've got your head around the configurations it can do a lot without having to build your own app / UI's.
A lot of us here are running Home Assistant as well as Node Red. You're preaching to the choir! :)
 
It most probably has DST enabled as well. Here are the appropriate console commands.
Thanks
So if I use time 1578506400 it will set it to 08/01/2020 20:00:00 ?
 
Thanks
So if I use time 1578506400 it will set it to 08/01/2020 20:00:00 ?
With Time 0(default), this will use NTP, so no need for you to do anything there.
TimeSTD 0 - switches off daylight savings time.
and,
Timezone +2 - should add 2 hours to UTC ( excluding DST)
 
My idea around this is different.

Since I am moving in to a new house in the next 3 months, one of the things I want to do other than home automation is to add solar panels and backup inverter battery power. I am planning to have this hooked up into the main DB board and most of the things I am automating I want to run off the inverter/solar power, such as:
- All lights
- Fridge (otherwise the defrost cycle gets confused with the loadshedding)
- Internet (router + wifi + CPE)
- TV + sound system + droid boxes
- Alarm
- Gate and Garage motors

I won't put the pool or geyser on and the stove is gas which you can use a kettle on too. With the above I should be properly covered that loadshedding wont break anything for and if I lose a sonoff for the pool or geyser its ok. The geyser sonoff you can even consider going in on the main DB board using the 3d printed item the other guy on here made for a sonoff to make it easy to replace.
It's a thought I have too. But even with this setup , the fact that a smart switch in line to the device cuts power to that device when it gets borked and could be not so easy to access to remediate can make things complicated. Hence to have them easily accessible as a minimum would be first prize.
 
Agreed. I was unable to identify any cause. Symptom was devices associated to the wifi but did not obtain a valid IP address (unifi controller reported them as having 255.255.255.255) and pushing the button did not toggle the relay.
One it happened after it was unplugged for a week. The other, just happened over night.
First one was an RF, second was a POWR2

Both were v5.11

Now running 7
Sorry to resurrect this. I have an old Sonoff POW running 5.13. It runs on the "grid side" of my inverter, so goes off during loadshedding.

Tonight after loadshedding, the power came on and then off again, and then eventually came on a while later. This particularly Sonoff is now "borked" - it still functions just fine when I press the button, but fails to get an IP (and indeed, my Unifi shows it on the network with IP 255.255.255.255). Of course, can't reach it at all online and MQTT is dead.

How did you get yours up and running again? Flashed by serial?

When I tried the "long-press button 1 for 40 seconds" nothing happened.
When I tried the device recovery by power cycling 7 times, nothing happened.
 
Sorry to resurrect this. I have an old Sonoff POW running 5.13. It runs on the "grid side" of my inverter, so goes off during loadshedding.

Tonight after loadshedding, the power came on and then off again, and then eventually came on a while later. This particularly Sonoff is now "borked" - it still functions just fine when I press the button, but fails to get an IP (and indeed, my Unifi shows it on the network with IP 255.255.255.255). Of course, can't reach it at all online and MQTT is dead.

How did you get yours up and running again? Flashed by serial?

When I tried the "long-press button 1 for 40 seconds" nothing happened.
When I tried the device recovery by power cycling 7 times, nothing happened.
You need to see if you can flash it again with a newer tasmota.

There is a setting where if tasmota loose power 3 times in a row, it factory reset the config. If you lucky, there is a random ssid to connect to. Otherwise flash it, disable that setting to reset after 3 power off on.
 
You need to see if you can flash it again with a newer tasmota.

There is a setting where if tasmota loose power 3 times in a row, it factory reset the config. If you lucky, there is a random ssid to connect to. Otherwise flash it, disable that setting to reset after 3 power off on.
Go near the Sonoff. If it's reset, there is a ssid, that you can probably connect to with your phone and hopefully restore the config

PSA: hope everyone has config backups of all their sonoffs with tasmota. I have mines sitting on OneDrive which makes it easier. Have had to do this one of my now ex-tasmota powr2 and was easy.
 
You need to see if you can flash it again with a newer tasmota.

There is a setting where if tasmota loose power 3 times in a row, it factory reset the config. If you lucky, there is a random ssid to connect to. Otherwise flash it, disable that setting to reset after 3 power off on.
I checked - was no tasmota-xxxxx SSID was being broadcast.
I tried 40-second button hold - nothing. Doesn't seem to reset.
I tried the fast-power-cycle (turn on/off 7 times in quick succession) - nothing (since this one is "grid-side" and more susceptable towards Load shedding, I may have disabled SetOption65).

So yeah, removed it tonight (nothing like messing about in one's flowerbed in the dark messing about some externally mounted electrical box) and relfashed it. Seems fine. Took a moment to connect to the wifi, which had me worried, but seems to be online now.
 
I checked - was no tasmota-xxxxx SSID was being broadcast.
I tried 40-second button hold - nothing. Doesn't seem to reset.
I tried the fast-power-cycle (turn on/off 7 times in quick succession) - nothing (since this one is "grid-side" and more susceptable towards Load shedding, I may have disabled SetOption65).

So yeah, removed it tonight (nothing like messing about in one's flowerbed in the dark messing about some externally mounted electrical box) and relfashed it. Seems fine. Took a moment to connect to the wifi, which had me worried, but seems to be online now.
Seriously needing to climb into the roof and everywhere else a few years ago to reflash/configure them when the eskom quick off/on caused them all to think I wanted to reset them - was not a fun exercise. I resolved that day never to have these things in inaccessible places and then also not to reset automatically!

Anyway, I only few left now. All will be replaced by Tuya when they give up - and sonoff's give up!
 
Seriously needing to climb into the roof and everywhere else a few years ago to reflash/configure them when the eskom quick off/on caused them all to think I wanted to reset them - was not a fun exercise. I resolved that day never to have these things in inaccessible places and then also not to reset automatically!

Anyway, I only few left now. All will be replaced by Tuya when they give up - and sonoff's give up!
Are you flashing your Tuya's?

Interestingly enough after this particular loadshedding bout, both this Sonoff POW (running Tasmota) and my one CBI Astute (running stock) didn't come online. The CBI eventually recovered, the Sonoff didn't.

In the past I've had Shelly's who didn't want to come online again - until I flashed them to Tasmota. Much better afterwards, but of course all of it became better after I got an inverter and batteries (although I should say, I still see one of my Yeelights get into a weird state when the inverter switches over to battery power during loadshedding - apparently that couple of ms is enough to sometimes freak it out).

It might just be age too, or it might be an older Tasmota version, but it does seem like my older devices are more prone to this type of issue than the newer ones. I hardly touch a tasmota device after I flash them initially - until I HAVE to.
 
Are you flashing your Tuya's?

Interestingly enough after this particular loadshedding bout, both this Sonoff POW (running Tasmota) and my one CBI Astute (running stock) didn't come online. The CBI eventually recovered, the Sonoff didn't.

In the past I've had Shelly's who didn't want to come online again - until I flashed them to Tasmota. Much better afterwards, but of course all of it became better after I got an inverter and batteries (although I should say, I still see one of my Yeelights get into a weird state when the inverter switches over to battery power during loadshedding - apparently that couple of ms is enough to sometimes freak it out).

It might just be age too, or it might be an older Tasmota version, but it does seem like my older devices are more prone to this type of issue than the newer ones. I hardly touch a tasmota device after I flash them initially - until I HAVE to.
No, I leave them with Tuya. I don't have the time to figure out how to break something to flash it. With my luck all I will break it permanently.

Tuya has been very reliable for me inside HA so I am sticking with it. I don't even use Tuya Local.

Talking about Tasmota, all my SONOFF devices randomly did get partially wiped a few weeks ago. They kept their IP (unifi) and configuration, but all became 'BASIC' (these are for the SV, POWR2 and basics I still have left). I had to choose the module type again and you could see all previous stats come back e.g. for the POW R2s. The SVs lost their GPIO14 config (but a quick restore from the backup and all was well). Their firmware was not updated .

All that happened as far as I can tell was home assistant shutdown for a backup (happens every day at the same time) but something changed that day - it was not power loss, wifi drop or anything so still scratching my head what did that - was annoying.

The Tuya's bless them at least just seem to work!
 
Top
Sign up to the MyBroadband newsletter
X