The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024


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

RE: Strange Viewer issue


  • Subject: RE: Strange Viewer issue
  • From: "Patrick Lidstone \(Personal e-mail\)" <patrick@xxxxxxxxxxxx>
  • Date: Wed, 2 Jun 2004 14:49:03 +0100

I think there's a lot to be said for 1 UID per port. How else would you
be
able to tell whether or not an app had "gone away" and been
replaced by
a new app which just happens to reuse the same port. I'm pretty sure
that my
hub assumes this, and this was certainly the intention of the spec.
(even if
it is poorly expressed).

Patrick

> -----Original Message-----
> From: Kevin Hawkins [mailto:lists@xxxxxxx]
> Sent: 02 June 2004 14:07
> To: xAP_developer@xxxxxxx
> Subject: RE: [xAP_developer] Strange Viewer issue
>
>
> A question..
>
> 	The HomeSeer application manifests itself as several
> xAP applications on the network and each one generates a
> heartbeat - within each virtual application are multiple
> hardware subID's
>
> 	here are three examples
>
> xap-hbeat
> {
>     v=12
>     hop=1
>     uid=FF411100
>     class=xap-hbeat.alive
>     source=mi4.homeseer.median.Master
>     interval=60
>     port=3639
> }
>
> xap-hbeat
> {
>     v=12
>     hop=1
>     uid=FF411200
>     class=xap-hbeat.alive
>     source=mi4.homeseer.median.A
>     interval=60
>     port=3639
> }
>
> xap-hbeat
> {
>     v=12
>     hop=1
>     uid=FF413800
>     class=xap-hbeat.alive
>     source=mi4.homeseer.median.91
>     interval=60
>     port=3639
> }
>
> Now what we see here is the UID changing correctly for each
> xAPp and ending in '00' as it should but the port remains the
> same - what issues could that cause ?? ..and particularly how
> could these upset a remote hub perhaps ?? What about a local hub ??
> In this case no local hub was used and the HS app acquired
> 3639.   This
> message does not work via the xPLHAL hub so it confused the
> remote hub somehow too.
>
> xap-header
> {
>     v=12
>     hop=1
>     uid=FF411100
>     class=message.display
>     source=mi4.homeseer.median.Master
>     target=mi4.watcher.*
> }
> Display.text
> {
>     priority=1
>     line1=Track has changed
>     line2=Coldplay
>     line3=
>     line4=
>     line5=
> }
> Display.look
> {
>     align=Left
> }
>
> 	Kevin
>
>
>
>    > -----Original Message-----
>    > From: Kevin Hawkins [mailto:lists@xxxxxxx]
>    > Sent: 02 June 2004 13:46
>    > To: xAP_developer@xxxxxxx
>    > Subject: RE: [xAP_developer] Strange Viewer issue
>    >
>    > Right... Narrowed this down a bit.
>    >
>    > 	No problem as far as I can tell with any xFX app.  If I
>    > remove the hub on the machine on which Watcher is running
>    > then it works fine and if I run Viewer as the hub it also
>    > works fine but I have been using xPLHAL as my hub and that
>    > doesn't work. It works when the message originates from
>    > Viewer on a different machine but not when it originates
>    > from HomeSeer.
>    > 	I use xPLHAL as the xAP hub on this machine because it
>    > provides the xAP to xPL bridging and it can only do this
>    > when working as a hub.
>    >
>    > 	More anon.
>    >
>
>
>
> ------------------------ Yahoo! Groups Sponsor
> --------------------~-->
> Yahoo! Domains - Claim yours for only $14.70
> http://us.click.yahoo.com/Z1wmxD/DREIAA/yQLSAA>
/dpFolB/TM
>
>
> --------------------------------------------------------------
> ------~->
>
>
> Yahoo! Groups Links
>
>
>
>
>




xAP_Development Main Index | xAP_Development Thread Index | xAP_Development 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.