After an unrecoverable corruption, I have installed HASSOS new and restored the configuration files which has many things up and running again - except Tasmota which was working perfectly prior to this - all devices on Tasmota 10.0. Process was install HASSOS on new virtual machine - configured so DHCP gave exact same address as the previous 2+ year old debian machine, then restore configuration from backup.
None of the tasmota devices will now connect to HA, I can however get into the tasmota web pages.
I had it all running using ‘native’ discovery rather than mqtt discovery, so I have tried the setoption19 command but made zero progress in two days.
Well I have managed to work my way through this mostly. It seems that 2 days prior when I upgraded my access point I had failed to notice that the tasmota devices were struggling ever since. This is because I changed from a Ubiquiti Unifi AC-Lite to a U6-LongRange.
I had to do the following:
Add the mosquito broker to my new HA instance
Reconfigure it in the integration area so that it had a username configured correctly
[This fixed the mqtt issues]
I then had to fix the Tasmota issues.
Apparently Tasmota devices store a “profile” of the wifi network(s) they connect to. I had to purge this profile by getting into the console and using the Tasmota command “RESET 3” this clears out the profile but also requires a power off and power on again after it resets.
In the process of ‘solving’ this problem I also learned about the Tasmota ‘SLEEP’ command, the default sleep setting is 50, in the process of troubleshooting I have now set this to 0 (zero).