Domoticz

Hi,
I see that Tasmota firmware have implemented 'offline' thermostat. So when it's set up, it can work with last settings (temperature, logic) even if some WIFI/internet fault occurs.
Is someone tried to implement these advantages (to set up this 'offline' thermostat) to be set up in Domoticz?
It can be very useful for safety reasons - to be WIFI/internet independent. For example - you can control your water heater with a lot of logyc and dynamic profile in Domoticz plugin (for example to use mainly 'cheap' electricity), but to have 'safety' settings that even if no any Domoticz command arrive (if for example - no Wifi/internet at the moment), device to switch off electricity/heating at 85C.. Or just to continue to maintain last settings, not waiting for domoticz/MQTT to sent it commands to switch on or off

My "offline" thermostat works 3rd winter without any problem.
Not Tasmota but ESPeasy with "rules".

ESPeasy holds temperature ( room or floor ) and sends heating status, temeperatures, energy consumption and number of relay actions to Domoticz.
And make some "safety" - check max allowed floor temperature, setpoint in allowed range etc.
Domoticz sends to ESPeasy setpoint and if floor or room temperature is controlled.

Look here:

https://www.youtube.com/watch?v=1ef6tRinOQ4

Now I am using Sonoff Basic instead off Wemos.

Thanks for response kimot,
I past i made similar project and it works, but i was not happy due to several reasons:
1. Mine was with 'custom firmware', based on ESPEasy. So replacing of faulty device was not so easy (this device run on remote location - 500km from home)... Thus i prefer to use 'stock' firmware with 'sonoff' devices - i send some there, and if some device fails - my friend there will go and just replace it without any specific knowledge (i already set devices to connect my home network there, so just minor setting change is done remotely).
2. Reporting and 'synchronizing' of modes, floods Domoticz history..
3. If power-off occured, device forget it's current settings. Yes, in my project i have variable 'flag' for safety reasons - to not switch heater until receive Domoticz settings, but sometimes there we have internet disruptions and it can take long time to get specific data (i used it for water heater, and due to huge consumption, i need to make specific 'heating profile' - temperature to heat water depends on time of the day. S i use there mainly 'cheap night energy', for heating to 'max temp', and then during daytime target temperature rapidly decreases, to decrease 'expensive'power using..
Anyway - maybe rules thermostat idea can be fulfilled and in Tasmota = thanks for idea...

ad 1)
I have one Sonoff with ESPeasy and with "service IP adress"
If some thermostat fails, I replace it with this "service" Sonoff, connect to its "service IP adress" and load config file previously stored for specific thermostat. This will restore everything including working IP. Or you can do this yourself and send alredy set device to your friend.

ad 2)
It is possible synchronize only after reboot, but I'm too lazy )
I can imagine , ESPeasy after reboot set some switch in Domoticz and Domoticz only in this case sends data to ESPeasy.

3)
I too start to safe conditions with heater off after reboot.
But ESPeasy itself can handle events based on specific time.
So it is possible due rules program your specific temperature curve for day

1), yes, i have almost the same setup. But on ESPEasy, when i found Tasmota to be much more easy to setup...
2) yes, in ESPEasy i syncronized only after 'reboot' (noted reboot 'flag''), but my idea was to put 'current settings' to energy independent memory of ESP, so it will continue to work with last commanded settings until internet connection return back in life.
3) I need temperature curves to be easily setup in Domoticz only. So 'thermostat' just to be internet independent only on 'last settings'- to continue to work as termostat, but not to wait 'domoticz'commands to switch it on/off.