The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024

Latest message you have seen: xAP Jabber


[Message Prev][Message Next][Thread Prev][Thread Next][Message Index][Thread Index]

Re: xAPFloorPlan & Room Temperatures


  • Subject: Re: xAPFloorPlan & Room Temperatures
  • From: "JamesTraynor" <james@xxxxxxx>
  • Date: Thu, 14 Sep 2006 23:07:34 -0000

hi,

http://www.mi4.biz/files/testing/floorplan20060914.zip

Hopefully this should fix the display issues when dealing with raw
devices.

James

--- In xap_automation@xxxxxxx, "JamesTraynor" <james@...>
wrote:
>
>=20
> Right i've figured out what is going on. It's nothing to do with xAP
> or xPL or anything on the receiving side. It's a fault with the code
> that delivers the graphics to the AJAX floorplan. While it will
> correctly display any number of BSC devices, it currently loads all
> raw devices assigned to the floorplan on to raw device1.  I've fixed
> the issue and i'll upload  an new exe in a couple of days when i've
> finished some other changes.
>=20
> Thanks for all the data
>=20
> James
>=20
> --- In xap_automation@xxxxxxx, "Neil Frost" <neil@>
wrote:
> >
> > I get two separate messages:
> >=20=20
> > xpl-stat
> > {
> > hop=3D1
> > source=3Dgshed-tom10.thefrosts
> > target=3D*
> > }
> > sensor.basic
> > {
> > device=3DBathroom
> > type=3Dtemp
> > current=3D25.18
> > }
> >=20
> > and
> >=20=20
> > xpl-stat
> > {
> > hop=3D1
> > source=3Dgshed-tom10.thefrosts
> > target=3D*
> > }
> > sensor.basic
> > {
> > device=3DNodezero
> > type=3Dtemp
> > current=3D34.26
> > }
> >=20
> >=20=20
> > Floorplan wise i have
> >=20=20
> > Alias=3DBathroom Temp
> > Source=3Dgshed-tom10.thefrosts
> > Class=3Dsensor
> > Section=3Dbasic
> > Item=3Dcurrent
> > ItemValuePair1=3Ddevice=3DBathroom
> >=20
> > and
> >=20=20
> > Alias=3DNodeZero Temp
> > Source=3Dgshed-tom10.thefrosts
> > Class=3Dsensor
> > Section=3Dbasic
> > Item=3Dcurrent
> > ItemValuePair1=3Ddevice=3DNodezero
> >=20=20
> > I've since put lehhane xAPTOM10 app on to test and it works as
> expected... maybe i'll just try and get the xAP messages logged into
> my SQL db....????
> >=20=20
> > Neil
> >=20
> >=20
> > ________________________________
> >=20
> > From: xap_automation@xxxxxxx on behalf of James
> > Sent: Wed 06/09/2006 21:45
> > To: xap_automation@xxxxxxx
> > Subject: Re: [xap_automation] Re: xAPFloorPlan & Room
Temperatures
> >=20
> >=20
> > Could you let me know the settings in Floorplan for each device
and
> an example xPL messages that sets them?
> > Could it be that both sensors are reported by the same xPL
message
> and that xPL messages has multiple items with the same name as in
> >=20
> > {
> > device=3D1
> > value=3D3
> > device=3D2
> > value=3D4
> > }
> > etc
> >=20
> > Thanks
> >=20
> > James
> >=20
> > Neil Frost wrote:=20
> >=20
> > 	I can now get the two (i've just got 2 sensors on the tom10 at
the
> mo) temperatures displayed on the map, trouble is the temperatures are
> displayed side by side and not individually... i assume thats because
> its the same xPL source??
> >=20=09=20
> > 	what I get displayed is: 25.37 =B0C31.50 =B0C (i added the
&deg;C
> suffix) no matter where i put the devices.
> >=20=09=20
> > 	If I change the map for one of the devices then it displays
fine...
> >=20=09=20
> > 	any ideas?
> >=20=09=20
> > 	Neil
> >=20=09=20
> >=20=09=20
> >=20=09
> > 	________________________________
> >=20=09
> > 	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
> >=20=09
> >=20=09
> >=20=09
> >=20=09
> > 	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
> >=20=09
> > 	Guess i'll be adding it to the todo list ;-)
> >=20=09
> > 	J
> >=20=09
> > 	--- In xap_automation@xxxxxxx, "Kevin Hawkins"
<lists@>
> <mailto:lists@> 
wrote:
> >=20=09=20=20
> >=20
> > 		--- In xap_automation@xxxxxxx, "JamesTraynor"
<james@>
wrote:
> >=20=09=09=20=20=20=20
> >=20
> > 			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.
> >=20=09=09=09=20=20=20=20=20=20
> >=20
> > 		    Isn't that great :-)  xAP Desktop (another great J
application)
> > 		allows similar as well
> >=20=09=09
> > 		    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..
> >=20=09=09
> > 		ItemValuePair2=3Dtype=3Dtemp
> >=20=09=09
> > 		   K
> >=20=09=09
> > 		 When you define a raw
> >=20=09=09=20=20=20=20
> >=20
> > 			device you will see 3 'Item Value Pairs', these are entered in
the
> > 			form item=3Dvalue, so in your example:
> >=20=09=09=09
> > 			xpl-stat
> > 			{
> > 			hop=3D1
> > 			source=3Dgshed-tom10.thefrosts
> > 			target=3D*
> > 			}
> > 			sensor.basic
> > 			{
> > 			device=3DBathroom
> > 			type=3Dtemp
> > 			current=3D25.18
> > 			}
> >=20=09=09=09
> > 			becomes:
> >=20=09=09=09
> > 			Alias=3DBathroom Temp
> > 			Source=3Dgshed-tom10.thefrosts
> > 			Class=3Dsensor
> > 			Section=3Dbasic
> > 			Item=3Dcurrent
> > 			ItemValuePair1=3Ddevice=3DBathroom
> >=20=09=09=09
> >=20=09=09=09
> >=20=09=09=09=20=20=20=20=20=20
> >=20
> >=20=09
> >=20=09
> >=20=09
> >=20=09
> >=20=09
> >=20=09
> > 	Yahoo! Groups Links
> >=20=09
> >=20=09
> >=20=09
> >=20=09
> >=20=09
> >=20=09
> >=20=09
> >=20=09
> >=20=09
> >=20=09
> >=20=09=20
> > 	Yahoo! Groups Links
> >
>






=20

xAP_Automation Main Index | xAP_Automation Thread Index | xAP_Automation Home | Archives Home

Comments to the Webmaster are always welcomed, please use this contact form . Note that as this site is a mailing list archive, the Webmaster has no control over the contents of the messages. Comments about message content should be directed to the relevant mailing list.