[Message Prev][Message
Next][Thread Prev][Thread Next][Message
Index][Thread Index]
RE: Re: xAPFloorPlan & Room Temperatures
- Subject: RE: Re: xAPFloorPlan & Room Temperatures
- From: "Neil Frost" <neil@xxxxxxxxxxxxx>
- Date: Wed, 6 Sep 2006 00:33:53 +0100
------_=_NextPart_001_01C6D143.BF6D194E
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
I can now get the two (i've just got 2 sensors on the tom10 at the mo)
temp=
eratures displayed on the map, trouble is the temperatures are displayed
si=
de by side and not individually... i assume thats because its the same xPL
=
source??
=20
what I get displayed is: 25.37 =B0C31.50 =B0C (i added the °C
suffix) n=
o matter where i put the devices.
=20
If I change the map for one of the devices then it displays fine...
=20
any ideas?
=20
Neil
=20
=20
________________________________
From: xap_automation@xxxxxxx on behalf of JamesTraynor
Sent: Tue 05/09/2006 21:23
To: xap_automation@xxxxxxx
Subject: [xap_automation] Re: xAPFloorPlan & Room Temperatures
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, "Kevin Hawkins" <lists@...>
wrote:
>
> --- In xap_automation@xxxxxxx, "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=3Dhumidity) but if so you should add a second
> pair relation as well..
>
> ItemValuePair2=3Dtype=3Dtemp
>
> K
>
> When you define a raw
> > device you will see 3 'Item Value Pairs', these are entered in
the
> > form item=3Dvalue, so in your example:
> >
> > xpl-stat
> > {
> > hop=3D1
> > source=3Dgshed-tom10.thefrosts
> > target=3D*
> > }
> > sensor.basic
> > {
> > device=3DBathroom
> > type=3Dtemp
> > current=3D25.18
> > }
> >
> > becomes:
> >
> > Alias=3DBathroom Temp
> > Source=3Dgshed-tom10.thefrosts
> > Class=3Dsensor
> > Section=3Dbasic
> > Item=3Dcurrent
> > ItemValuePair1=3Ddevice=3DBathroom
> >
> >
>
xAP_Automation Main Index |
xAP_Automation Thread Index |
xAP_Automation Home |
Archives Home
|