Version 2.0

Version 2 of the application now uses the tado API instead of pings to determine the home state of each user.

• Each rule now holds one or several device names to listen for instead of local IPs.
• If a device gets stale it can be defined how the application reacts (set as home, away, or take the last received state).
• Because no pings are needed anymore, no sudo privileges are needed to run the application.
• Locking the geofencing state to HOME or AWAY now does not get overwritten by the application anymore.

The structure of the config.json file changed:

• removed "max_ping_cnt", "client_state_history_len", "min_home_success_pings"
• added "default_stale_state"
• changed "rules.ips" to "rules. device"

Version 1.0

Last stable version of tado-individual-away-control using pings to determine device states.

• Providing a sample-config.json which needs to be adapted and moved to config.json by the user.
• The application checks if the configuration is set up accordingly.
• Minor changes (no effect on performance/compatibility)

Version 0.2

• Added deep sleep mode. The application will turn down the temperature even more if the desired time has elapsed after all defined devices left the desired zone.
• Improved rule structure. Multiple zones and a default rule can be defined.

The structure of the config.json has changed, keep in mind if upgrading from 0.1.

Version 0.1

Initial implementation.