I've just made my first purchase of Athom kit.
First impressions: excellent!
The physical construction and the ease of setup is really good.
However, I have 8 UK style power switches (model PG04V2). I upgraded them to the latest Tasmota 12.2.0 on arrival and configured them all fine.
I've noticed that they are all randomly restarting. Can be minutes or hours in beween.
I hear a click of the relay and sometimes there's a tiny drop out of power. When I check the Information page, the restart reason is "Software Watchdog".
My TasmoAdmin page shows the device uptime has zeroed and started again.
Has anyone else experienced this?
Could this be a hardware issue? A Tasmota bug? A client application causing a timeout (MQTT or TasmoAdmin)?
I am using Mosquitto And Indigo so similar to you. Having gone back to v10.1.0 I have had no more problems but to be sure I am also using 'PowerOnState 4' on the modem, router and various 'servers' as I have no reason to turn them off (just using the plugs as power monitors) that also stopped the problem in v12.2.0 and a PowerOnState 3 will allow the plug to be turned off by the button and by automation software If required for controlling lights, TV etc.
I contacted the Tasmota developers and they reckoned that the TasmoAdmin software I was keeping open to monitor my devices is not meant for this purpose.
They said it is quite intensive in its continuous web calls and thus can cause a watchdog time-out of the device, which will trigger a restart.
I can agree that TasmoAdmin is quite buggy but its a pity it can cause this issue.
My conclusion at the moment is that Tasmota v12.2.0 must be putting a bit more load on the device than v10.1 was doing.Thus the little bit of extra load is causing a watchdog time-out.
I'm now avoiding keeping TasmoAdmin open in a browser and I'm just using MQTT with Mosqitto and Home Assistant.
I'm interested to know what client you are using to communicate with Tasmota. Are you putting a load on the web interface?
If you look in the console with logging set to "weblog 2", do you see that the last restart reason was "software watchdog" ?
Alex, you are not alone, I also am having the same random turning off using v12.2.0 which is why I am on here at present.
Will try your suggestion of moving back to v10.1 on both my v1 and v2 UK plugs, this never happened using v10 (or v11) and has only started on v12.
To get the space required for the downgrade I did the following.
I downloaded the minimal file from http://ota.tasmota.com/tasmota/release-10.1.0/tasmota-minimal.bin.gz to my MacBook and downgraded from that file using the 'Upgrade by file upload' option and then downloaded http://ota.tasmota.com/tasmota/release-10.1.0/tasmota.bin.gz and installed the full v10.1using the same method. I now have a full version of v10.1 and hopefully no more phantom reboots!
As far as I can see there is no reason to go past V10 for these plugs (either v1 or v2), we just 'think' the latest is the best, not always true in this case!
After 6 hours, the switch that was downgraded to Tasmota v10.1 has not restarted itself. So that looks good. I guess I should downgrade the others as well.
Do you know if there is a specific issue with Tasmota v12.2 that's causing this?
[By the way, after downgrading, the TasmoAdmin service will no longer communicate with the switch. "It reports a JSON error 4: syntax error". To repair this, I had to do a factory reset and set up from scratch.]
Okay, I worked it out. I found and upgraded to the tasmota-minimal.bin.gz first, then I could downgrade to tasmota 10.1
I'll monitor the results over a few hours and report back.
Hi and thanks for the suggestion.
Unfortuately the 'downgrade' fails due to "Not enough space"
I know that normally when upgrading there's a minimal firmware step in the middle so that space is made. How do I clear enough space manually?
Try downgrading the firmware version to 10.1