autolog wrote:
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.
That sucks.
Talking of SWMBO - I had to quickly knock up a very rudimentary control page to allow control of the living room heating (Boost, Advance, Extend) as someone wasn't happy no longer having any control of the heating.

It was understandable - making a nice control page I discovered is more than just a pretty interface. Realised there's still a lot more to learn to make it functional. And of course, I haven't barely started when I'm already thinking about changing the UI.
autolog wrote:
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 did think about that. I previously mentioned how I was testing a aluminium shield for the Stella. I've since installed another shield in a room which has my new Netatmo. I'm now able to plot, using Karl's INDIGOplotD plugin the Stella with shield temp and the Netatmo. I've already noticed that the temp deviation is actually fairly consistent as the temp of the radiator increases. I'll post the results after a week of data.
autolog wrote:
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.
It's tempting, since some rooms may have multiple sensors which often include temp. Personally, I would rather have a sensor that reports an accurate temp, or one that is calibrated, than trying to average multiple ones out.
autolog wrote:
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?
If I understand you correctly then you mean use the native Indigo controls to active certain setting in the plugin? Then I for one like that idea. I've been using our iPhones to detect when we're at home and so far that works well, but I'm only using it to trigger SecuritySpy. What's nice about that is when we have friends or family staying we just give them a spare iPhone 4, which I then enable in Indigo to also track with Smartphone Radar.
autolog wrote:Quite a bit to think about - I'll focus on the basics first.

I'm sure there is. Get well soon.
Simon