Support for (Multi) Geofence

[SirTypesALot]

Hoi!

I just came across this project, and I’m loving what you guys are doing. I’ve been experimenting with Tado’s cloud APIs myself, and I’ve gathered some information that I think could be really useful and attractive for future users of this project.

I’ve implemented my own multi-geofence feature at home, which allows me to specify which rooms should respond to which subset of users’ locations when calculating the away-from-home temperature. I’ve also figured out the algorithms and formulas to determine a room’s temperature based on the (closest) user’s location, while factoring in the room’s schedule, energy-saving mode, which controls how aggressively the temperature is lowered when away, and other elements just like the official Tado app does.

If the project finds this useful, I would be happy to help, properly document everything, and assist with getting it implemented.

[rhuijben]

Thanks.

For me personally this feature wouldn't work, but I really like the idea. (Several users working 8 hours shifts within a few km/mile from home... And very slow heating in the primary rooms), but I would guess others might find it interesting.

I'm just not sure if you should tie this to tado, or if you can expose this useful feature to other systems too.

I started this library to get the live info stable+realtime in Domoticz, so I can combine multiple scripts there. And hoping to create a foundation where others can use it in other systems.

The real power of my custom smarthome is where I can combine multiple sensor types... And this is not in the low level tado integration for me.

I'm also working on a few other Domoticz related projects to bring my smarthome to a new levrl... In most of these I'm trying to replace polling -what most older libraries do- with event streams.
(I forked+extensively refactored DZGA-flask to a similar live model in https://GitHub.com/ampscm/dzLive using the Domoticz we socket support)

I'm not entirely sure where your code fits in.
It could use the rest api of this project to trigger changes on the Tado side. But the idea of the project is that you could just as easy do the change on Domoticz, without any latency in either direction.

If you see a good fit here as extension of this project, perhaps we should add it here... And otherwise would we should do our best to make the projects work good together.

These projects are all 'microservices' that should fit together. But I haven't found a way to nicely manage them together.

[rhuijben]

In #22 a full scheduler was added to the project. With that added this feature makes more sense as a full replacement for the cloud infra from Tado.