Re: Re: xAPFloorPlan & Room Temperatures

[Kevin Hawkins <lists@xxxxxxxxxxxxxxxxx>]

Isn't it an AND that he needs ...? If so just shortened your 'todo'
list..

K

JamesTraynor wrote:
>
>
> but, and there is always a but, the item value pairs are ANDs not ORs
> so if you have move than one then all have to be true
>
> Guess i'll be adding it to the todo list ;-)
>
> J
>
> --- In xap_automation@xxxxxxx
> <mailto:xap_automation%40yahoogroups.com>,
"Kevin Hawkins" <lists@...>
> wrote:
> >
> > --- In xap_automation@xxxxxxx
> <mailto:xap_automation%40yahoogroups.com>,
"JamesTraynor" <james@> wrote:
> > >
> > > It then gets more awkward, especially for Floorplan, as xPL
put
> > > context throughout messages in most schemas and this was one
of the
> > > original reasons for me going xAP rather than xPL, but
that's also
> > > another story.
> > > Anyways, don't worry Floorplan to the rescue.
> >
> > Isn't that great :-) xAP Desktop (another great J application)
> > allows similar as well
> >
> > Re the below I don't know if the 'type' parameter can change in
> > your usage (eg to type=humidity) but if so you should add a
second
> > pair relation as well..
> >
> > ItemValuePair2=type=temp
> >
> > K
> >
> > When you define a raw
> > > device you will see 3 'Item Value Pairs', these are entered
in the
> > > form item=value, so in your example:
> > >
> > > xpl-stat
> > > {
> > > hop=1
> > > source=gshed-tom10.thefrosts
> > > target=*
> > > }
> > > sensor.basic
> > > {
> > > device=Bathroom
> > > type=temp
> > > current=25.18
> > > }
> > >
> > > becomes:
> > >
> > > Alias=Bathroom Temp
> > > Source=gshed-tom10.thefrosts
> > > Class=sensor
> > > Section=basic
> > > Item=current
> > > ItemValuePair1=device=Bathroom
> > >
> > >
> >
>
>