Hi, here are my answers to your questions. I’m afraid that my smartapp cannot implement all your use cases as they are quite specific to your configuration…
1: Yes, but not the way you describe it.
All your Sinope thermostats would be considered as slave thermostats to Dailkin split system (master).
The slave tstats would then synchronize their mode and heating/cooling setpoints with the master. You can use the virtual zone devices to add a delta temp (+/-) to make a zone cooler or hotter if you have colder/hotter rooms. A zone is composed of 1 to many rooms.
The moreHeatThreshold is used to increase the heatingSetpoint if the outside temperature reaches a configurable threshold. It would affect the master’s heatingSetpoint and by ricochet, all the slave thermostats linked to the master.
2: The zoning smartapp can automatically set the right fan speed based on the temp differential in the scheduled zones. The smartapp would modulate the fan speed according to the max temp differiential allowed for the zone. If the temp differential is big (i.e. equal or greater than your own defined threshold), the fan speed would be set to high, otherwise medium or low if the temp differential is small compared to your threshold.
After checking your Dailkin DTH, I must add that yours is not compatible with my logic as the author has not implemented the required fanHigh(), fanMedium(), and fanLow() commands…
3: Usually, motion sensors can be configured to not take into account an animal in the house. Regardless of your ST location mode (Home or Away), all motion sensors are used to toggle the thermostat’s mode…The only exception is at night, where all rooms are considered occupied regardless of the input of all motion sensors.
In brief, there is no way to exclude the motion sensors when the ST hello mode is Away. The smartapp uses the motion sensors to detect if somebody is returning home after an absence.
4: The smartapp can switch between the cool/heat/auto modes based on heat/cool thresholds.
Note: The smartapp would not turn off the master tstat based on some thresholds though.
In my smartapps, I usually avoid switching the master tstat to off as in the major parts of the US and Canada, turning off a master tstat could lead to pipe bursting in the winter and mould in the summer. It’s a safety issue: SmartThings is not the most reliable platform and any scheduling issue or outages could lead to problems.
But,my smartapp can turn off or set all slave thermostats to eco or Away when they are not part of the scheduled zones (ex. heat/cool only the upstairs bedrooms at night, and all other slave tstats in other rooms would be turned off).
However, my smartapp can set any compatible master thermostat to Away or Home if it supports presence (such as the ecobee) .
But, I check your Dailkin DTH, and it doesn’t support the required away() or home() (present) methods.