[OpenTRV-dev] Feedback Mechanisms.

[Stuart Poulton]

Happy to hear about how other people are doing UI's 

Cheers

Stuart

On 22 Mar 2013, at 12:29, Damon Hart-Davis wrote:

> Hi,
> 
> I seem to be getting enough local control with the single LED and single button interface that I have at the moment.  That gives local override and status.  I can describe the UI I have a little more if that is of interest.
> 
> I also hope to be able to double up the programming interface to provide a limited CLI that a c/o a GUI on a laptop should be able to provide a simple secure interface to set schedules and so on.
> 
> Rgds
> 
> Damon
> 
> 
> On 22 Mar 2013, at 11:47, Stuart Poulton wrote:
> 
>> Dear All,
>> 
>> Again, I'd be interested in opinions.
>> 
>> Whats sort of feedback do users need at the TRV level ? All of our current TRV's provide an LCD, which is fine, but it increases the amount space required.
>> If settings could be done wirelessly, and current state of the valve (position and battery voltage) reported back, does anything other than maybe a flashing LED need to be present ?
>> 
>> What about local control, how often is it actually used to override the current settings of the valve ?
>> 
>> Stuart
>> _______________________________________________
>> OpenTRV-dev mailing list
>> EMAIL ADDRESS HIDDEN
>> http://lists.opentrv.org.uk/listinfo/opentrv-dev
>> 
> 
> _______________________________________________
> OpenTRV-dev mailing list
> EMAIL ADDRESS HIDDEN
> http://lists.opentrv.org.uk/listinfo/opentrv-dev