Sonoff / Tasmota started regularly showing "Unavailable" on Home Assistant

DavidFW1960 · February 23, 2019, 8:10am

You could go back to 6.3.0 with 2.3.0 core. I have been using 6.4.1.x with core 2.5.0 because there’s some new features and for some inexplicable reason I get a lot of problems when I try to use 2.3.0. I’m currently on 6.4.1.18… as I said the last 6 or so 6.4.1.x’s caused boot loops as well… I think when the next real release comes out I’m going to try 2.3.0 again - the pre-compiled binary… I wish I had never seen 6.4.1 as it rolled out core 2.4.2 which is an utter piece of shit in my use anyway. The beta’s of 2.5.0 were horrible as well. I still get dropouts with the released 2.5.0 but nothing that has been an issue… guess I’ve been lucky the dropouts haven’t coincided with a trigger eh?

When I first started having problems I did raise an issue but they seems more concerned with immediately closing issues over there, or saying it’s not Tasmota and just flat out denying there is any problem unfortunately.

If you can, go 6.3.0 with core 2.3.0 - I had zero dropouts with that release.

A new release can’t be that far off.

bingobob · February 23, 2019, 8:14am

Thanks I’ll try out. Sorry for noob question but where do I get the downloads… ?

DavidFW1960 · February 23, 2019, 8:24am

https://github.com/arendst/Sonoff-Tasmota/releases For the releases…

You will need to flash the minimal first and then the one-off one… You shouldn’t have any problem with the normal one once it has minimal on it it will stop the boot loop.

bingobob · February 23, 2019, 10:48am

Got it, thanks, I’m hoping to fix this up today. Be interesting to see if it solves it. Will report back.

bingobob · February 24, 2019, 7:00am

6.3.0 seems stable for now sticking with that…

But it’s no good! seems like “discovery” doesn’t work until 6.4 !

catch 22…

i need discovery !

arrrrghhh. any ideas ?

DavidFW1960 · February 24, 2019, 8:01am

No it does work fine… but the topic changed in 6.4.1… the sonoff/cmnd of 6.4.1 is/was cmnd/sonoff in 6.3.0

So you managed to downgrade in between the boot looping then?

bingobob · February 24, 2019, 8:04am

yeah - i’ve got that down, lots of clicking and lots of fun.

tasmoadmin is my friend here,

currently trying 6.4.1.4(635edc2-sonoff) (early jan 2019 i think).

bingobob · February 24, 2019, 8:14am

well, no bootlooping but still the old problem

“changed to unavailable” coming up all the time, drat.

DavidFW1960 · February 24, 2019, 8:17am

What core?

I’m on 6.4.1.18 with core 2.5.0… it’s reasonably stable… not too many dropouts but still 2.3.0 core is best.

Are you compiling your own? With core 2.3.0?

DavidFW1960 · February 24, 2019, 8:18am

Yeah but beats pulling them out of fittings…

bingobob · February 24, 2019, 8:56am

absolutely !

now wierdest situation ever… got stabliity but can only turn on not off ! bizarre!

robg · February 25, 2019, 12:26am

Having the same issue.

I’m been using a compiled version “sonoff.bin” from here:

Hence which compiled version do you recommend that’s alread compiled and supports discovery?

Thanks,

Rob.

robg · February 25, 2019, 5:22am

Okay thanks David,

I’ll keep you posted with my findings.

Rob.

robg · February 25, 2019, 6:07am

So tried as suggested and loaded a device on 6.3.0 but not being discovered by HA…
SetOption19 1 and sonoffs/cmnd/state.
Also running latest version of HA.
Any suggestions??

Rob.

DavidFW1960 · February 25, 2019, 6:18am

have you checked the devices in home assistant? There were changes to the topics in 6.4.x and you might need to revert back to pre 6.4.x topics… You should still see them in HA though in devices.

robg · February 25, 2019, 10:57am

Hi David,

Unless the changes in topics prevents them from beng discovered, haven’t got past the fact devices not being discovered on 6.3.0

Rob.

DavidFW1960 · February 25, 2019, 8:25pm

I reflashed one of my S22’s with 6.3.0 yesterday and it was working fine with discovery. I switched to discovery as soon as the Mosquitto broker was upgraded to v3 (now V4). It was working fine with discovery and 6.3.0

robg · February 26, 2019, 7:57am

Okay, just figured it out by chance.
It’s not showing up in the list of MQTT discovered devices for some reason:

But I can see the device andd add the device’s entity to a card.

Assume it’s some sort of bug here, regardless I’ll leave it connected and see if it remains stable.

bingobob · February 26, 2019, 8:27am

Hi all,

Wonder if you can give me a steer.

I picked a 6.3.x point release which has given me stability but some strange behaviour…

My automations are firing the tasmotas on and off fine but the switches in the ha GUI don’t work. Turn on but not off… any ideas what could be going on there?

DavidFW1960 · February 26, 2019, 8:41am

Are they manually configured or using MQTT discovery?