[OpenTRV-dev] Anatomy of a TRV

[Damon Hart-Davis]

Hi

No problem at all if the TRV is a split unit (ie temp sensor and PIR remote from valve), but also some of the whackier ideas such as noticing disturbances in the radio field etc may be fine on the valve.

Also, I quite like having multiple methods such as low light levels (which I already use reasonably successfully), PIR, looking for stray IR handset signals, and detecting voice.  (The ATmega was showing doing real-time FFT in the Arduino event, at least well enough for that task I think.)  A combination could be pretty robust.

Rgds

Damon


On 28 Mar 2013, at 09:41, Stuart Poulton wrote:

> I don't think occupancy detection would work on the TRV, given the location of most TRV's
> 
> Occupancy detection isn't the easiest thing to accomplish it has long been the holy grail of home automation.
> 
> Stuart
> 
> 
> On 28 Mar 2013, at 09:37, Jack Kelly wrote:
> 
>> On the topic of IR / ultrasound:
>> 
>> Any sort of occupancy detection built into the TRV would be very interesting for a future design iteration, IMHO.  IR / ultrasound / CO2 (*very* expensive!) / vibration detector (microphone with low pass filter) etc.
>> 
>> In general, my hunch is that only the very geekiest folks will ever bother to explicitly program an efficient room-by-room heating schedule so anything we can do to automate the generation of a room-by-room schedule could significantly widen the appeal of the system (conditional on the system not frightening users: there's a real risk that people will worry that they're being spied on).
>> 
>> (BTW, one of my MSc students will almost certainly be doing her summer project on room-by-room occupancy prediction based on PIR and individual appliance power data: not as easy as it might first appear!).
>> 
> 
> _______________________________________________
> OpenTRV-dev mailing list
> EMAIL ADDRESS HIDDEN
> http://lists.opentrv.org.uk/listinfo/opentrv-dev
>