Domoticz

Before I go down the route of having a play with this and potentially breaking our heating and having to suffer the wrath of the wife I wonder if someone could answer a question.
I'm quite happy using the Tado app so I was thinking of using this more as a backup, along the lines of duplicating the app programming schedule but setting a slighlty later time for the changes so if a room was supposed to change from 16c to 21c at 7am I would set the device in Domoticz to do the same but at 7:05 so if the internet has died my heating still comes on, is this feasible ?

Thanks

I don't think this is a big issue, since my google home mini also connects to the bridge. And I think also via the homekit protocol, but not sure about that.

jannl wrote: Thursday 13 November 2025 11:55 I don't think this is a big issue, since my google home mini also connects to the bridge. And I think also via the homekit protocol, but not sure about that.

Doesn't that Google Home use internet as well?

With the update I get a lot further. The localhost is running, in the commandline logging I see the zones being fetched from the Tado api.

However, when I issue http://<ip>:4407/zones, I get no error, but also no zones.

Got this far like last time... still same error:

Tado App update works and gets updates in Tado-Local
Other way : change temperature fails... no leader device

I did update : git pull.... several file replaced... rebooted

See attached

<iP>:4407/zones gives:

{
"homes": [
{
"id": xxxxxxx,
"name": "HxMx8x0x"
}
],
"zones": [
{
"zone_id": 1,
"name": "Keuken",
"uuid": "filled in repladed by me",
"leader_device_id": null,
"leader_serial": null,
"leader_type": null,
"is_circuit_driver": false,
"order_id": 0,
"device_count": 1,
"state": {
"cur_temp_c": 23.5,
"cur_temp_f": 74.3,
"hum_perc": 51,
"target_temp_c": 22,
"target_temp_f": 71.6,
"mode": 1,
"cur_heating": 0
},
"home_id": xxxxxxx
},
............................
.............................
............................
],
"count": 8

I also got the no leader device when updating a setpoint.

Pairing once worked, I updated the software, pairing does not succeed anymore.

I am not going to issue a factory reset, so it could be my TadoLocal stops here.....
So I hope there is another solution

jannl wrote: Friday 05 December 2025 12:09 Pairing once worked, I updated the software, pairing does not succeed anymore.

I am not going to issue a factory reset, so it could be my TadoLocal stops here.....
So I hope there is another solution

What software did you update, the Tado Local application or the plugin or both?

propably both, but I removed the tado local first

jannl wrote: Saturday 06 December 2025 13:03 propably both, but I removed the tado local first

Is removing first the way to update? Normally you do some kind of update (eg git pull) to update an application and/or a python plugin.(in Domoticz)

Allthough I mostly agree, that is not always the right way. Especcially when the first install was done by extracting a zip or tarfile.

Anyway, now I removed and reinstalled. I think that should work as well.

sloeber70 wrote: Friday 14 November 2025 19:22 Got this far like last time... still same error:

Tado App update works and gets updates in Tado-Local
Other way : change temperature fails... no leader device

I did update : git pull.... several file replaced... rebooted

See attached

@Sloeber 70 how did you solve the TADO LOCAL: Failed to connect to Zones Fetch: Connection refused (Status: 111) error?