As previously mentioned, I am now coding the replacement (more generalised TRV controller) and am taking on-board your input. Progress has been delayed because SWMBO and I have picked up a cold virus bug which has knocked us a bit sideways for the last week.
Changes I am focusing on at the moment (in no particular order) are:
- Implement as a standard Indigo Thermostat device (easier now that I understand how this works - I didn't when I first started programming plugins)
- Danfoss LC-13 support
- NO TRV support i.e. just use a remote stat to turn the boiler on and off
- An 'architectural' change to use queueing and timers for the schedules which I am hoping will make the plugin less resource hungry.
- Action Groups to be able alter the scheduling dynamically
I have been having a think about the 'room heat up profile' and how that might work. Not sure how many temperature points would need to be accommodated. Also, I suspect the external ambient temperature might affect the 'room heat up profile' e.g. if it is below freezing outside then the room wouldn't be at such a high temperature even if the Stella-Z was.
I am wondering about supporting multiple remote stats in a room. I am not sure about this (particularly as I don't have a requirement for it ). One problem I see is one of trying to average out remote stat temperatures from devices reporting at different intervals and time.
Another requirement that has been asked for is 'occupancy' heating turn on. Again, I can see that different people would have different requirements and definitions of what represents 'occupancy'. Maybe the easiest way to implement this would be to have an Action Group to tell the plugin that the room is occupied and when it is not occupied. Then an occupied setpoint could be specified? This would leave the logic of what constitutes occupancy to be defined by the plugin user?
Quite a bit to think about - I'll focus on the basics first.