xAP mcs.wol error

[sforeman00]

I have been working on getting the xAP software working and have made great progress. To try a test I decided to load the xAP WOL V1.1.18 app to see if i could get data. While doing so I encountered the following error;

Within xfx Message Viewer:
xap-header
{
v=12
hop=1
uid=FF001500
class=Homeseer.Event
source=mcs.WOL.FOREMAN-HS
}
Event.Log
{
Time=9/7/2009 5:13:20 PM
Type=xapmcsWOL
Data=Readmessage Line 50 Invalid procedure call or argument
}

Also repored in the HS log as;
9/7/2009 5:18:25 PM - xapmcswol - mcs.wol.foreman-hs | readmessage line 50 invalid procedure call or argument
9/7/2009 5:18:27 PM - xapmcswol - mcs.wol.foreman-hs | readmessage line 50 invalid procedure call or argument
9/7/2009 5:18:29 PM - xapmcswol - mcs.wol.foreman-hs | readmessage line 50 invalid procedure call or argument

I am using the xfx-Express Hub and have already loaded the mcsXAP V1.5.4 interface to HS. Is there any issues with running the xfx-express hub

Any help would be appreciated. I really like the idea of xAP but realize I have a long way to go to get things setup.

[Michael McSharry]

I made an update to xapmcsWOL to display the input to ReadMessage when an error is thrown. This will assist in understanding what it wrong. The code segment that generated the error is below where the sMessage is the text received in the xAP message. It seems to be having a problem where it is likey the source address field is null.

20        i = InStr(1, sMessage, "source=", vbTextCompare)
30        If i > 0 Then
40            j = InStr(i, sMessage, Chr(10))
50            sSource = LCase(Mid(sMessage, i + 7, j - i - 7))

I had originally started using the xAP Framework set of hubs and always had the problem of messages being delivered twice. In some cases this caused me problems. This was several years ago so things could have changed. In xapmcsHub I included statistics and include the duplicate/discarded message count. I also played with xPL a little and they are very similar so it is possible to comingle in some situations. I setup xapmcsHub to also act as a hub/bridge so both environments could run together.

You may also want to try xapmcsWritelog. It will display those homeseer.event messages in a window much like Homeseer shows its log. It becomes a central place one can go to look at errors/messages from all my xAP applications.

[sforeman00]

Very interesting.... Here is the latest output;

From message viewer;
The following message caused an error during its processing.
Name/value pair contains no valid separator characters
The message was received from 127.0.0.1:1829
------------
xap-header
{
v=12
hop=1
uid=FF001500
class=Homeseer.Event
source=mcs.WOL.FOREMAN-HS
}
Event.Log
{
Time=9/7/2009 7:26:16 PM
Type=xapmcsWOL
Data=Readmessage xap-header
{
v=12
hop=1
uid=FF400100
class=Weather.Report
source=windy.weather.1
}
Weather.Report
{
tempf=88.2
utc=12:26:11 AM
tempc=31.2
icon=Dusk/Dry
date=20090907
windm= 0
windk= 0
airpressure=1006.4
winddirc=S
humidity=47
rain=0.0
extratemp1=57.8
extratemp2=255.0
extratemp3=-33.3
extrahum1=-100
extrahum2=-100
extrahum3=-100
}
Line 50 Invalid procedure call or argument
}
------------
The error that was generated is as follows:
Name/value pair contains no valid separator characters
Source: xFx
Name/value pair contains no valid separator characters
KCS.xAP.Framework.xAPMessageReaderException: Name/value pair contains no valid separator characters
at KCS.xAP.Framework.Message.xAPInfo.GetPairValueEncodingFormat (String line, Int32 line_number)
at KCS.xAP.Framework.Message.xAPMessageReader.ReadMessagePair(x APMessage message, String line)
at KCS.xAP.Framework.Message.xAPMessageReader.ReadMessage()
at KCS.xAP.Framework.Transport.xAPListener.ProcessQueuedMessage (xAPRawData data)

and from HS:
9/7/2009 7:30:54 PM - xapmcswol - mcs.wol.foreman-hs | readmessage xap-header{v=12hop=1uid=ff400100class=weather.reportsource=windy .weather.1
9/7/2009 7:30:57 PM - xapmcswol - mcs.wol.foreman-hs | readmessage xap-header{v=12hop=1uid=ff400100class=weather.reportsource=windy .weather.1
9/7/2009 7:30:58 PM - xapmcswol - mcs.wol.foreman-hs | readmessage xap-header{v=12hop=1uid=ff400100class=weather.reportsource=windy .weather.1
9/7/2009 7:31:00 PM - xapmcswol - mcs.wol.foreman-hs | readmessage xap-header{v=12hop=1uid=ff400100class=weather.reportsource=windy .weather.1


windy.weather.1 is Weather Display and is sending the following;
xap-header
{
v=12
hop=1
uid=FF400100
class=Weather.Report
source=windy.weather.1
}
Weather.Report
{
tempf=87.9
utc=12:31:55 AM
tempc=31.1
icon=Dusk/Dry
date=20090907
windm= 1
windk= 1
airpressure=1006.3
winddirc=E
humidity=47
rain=0.0
extratemp1=57.8
extratemp2=255.0
extratemp3=-33.3
extrahum1=-100
extrahum2=-100
extrahum3=-100
}

They don't seem to like each other.....

[Michael McSharry]

I tried a different approach to showing the erroneous message where I display it in hex rather than ascii. I also show the parameters that the message is complainging about. xapmcsWOL has been reposted with this different debugging

I did download Weather-Display and had no luck with it generating xAP traffic. I did not see any heartbeats and did not see any messages when I used the test button form the xAP control panel. I aslo found nothing in the documentation about it.

I also tried to setup a single 1-wire temp sensor just to have it be a source of changing data. I also had no luck with that setup. It just is not worth the time to figure out Weather-Display to do this test. I can get the same data from your post after you run with the latest update.

[sforeman00]

Michael, thanks for looking at this. Here is the output;

data from message viewer;
xap-header
{
v=12
hop=1
uid=FF001500
class=Homeseer.Event
source=mcs.WOL.FOREMAN-HS
}
Event.Log
{
Time=9/8/2009 5:34:04 AM
Type=xapmcsWOL
Data=Readmessage i=59,j=078, 61, 70, 2D, 68, 65, 61, 64, 65, 72, 0D, 7B, 0D, 76, 3D, 31, 32, 0D, 68, 6F, 70, 3D, 31, 0D, 75, 69, 64, 3D, 46, 46, 34, 30, 30, 31, 30, 30, 0D, 63, 6C, 61, 73, 73, 3D, 57, 65, 61, 74, 68, 65, 72, 2E, 52, 65, 70, 6F, 72, 74, 0D, 73, 6F, 75, 72, 63, 65, 3D, 77, 69, 6E, 64, 79, 2E, 77, 65, 61, 74, 68, 65, 72, 2E, 31, 0D, 7D, 0D, 57, 65, 61, 74, 68, 65, 72, 2E, 52, 65, 70, 6F, 72, 74, 0D, 7B, 0D, 74, 65, 6D, 70, 66, 3D, 37, 31, 2E, 35, 0D, 75, 74, 63, 3D, 31, 30, 3A, 33, 33, 3A, 35, 39, 20, 41, 4D, 0D, 74, 65, 6D, 70, 63, 3D, 32, 31, 2E, 39, 0D, 69, 63, 6F, 6E, 3D, 0D, 64, 61, 74, 65, 3D, 32, 30, 30, 39, 30, 39, 30, 38, 0D, 77, 69, 6E, 64, 6D, 3D, 20, 30, 0D, 77, 69, 6E, 64, 6B, 3D, 20, 30, 0D, 61, 69, 72, 70, 72, 65, 73, 73, 75, 72, 65, 3D, 31, 30, 30, 36, 2E, 39, 0D, 77, 69, 6E, 64, 64, 69, 72, 63, 3D, 45, 0D, 68, 75, 6D, 69, 64, 69, 74, 79, 3D, 38, 34, 0D, 72, 61, 69, 6E, 3D, 30, 2E, 30, 0D, 65, 78, 74, 72, 61, 74, 65, 6D, 70, 31, 3D, 35, 37, 2E, 38, 0D, 65, 78, 74, 72, 61, 74, 65, 6D, 70, 32, 3D, 32, 35, 35, 2E, 30, 0D, 65, 78, 74, 72, 61, 74, 65, 6D, 70, 33, 3D, 2D, 33, 33, 2E, 33, 0D, 65, 78, 74, 72, 61, 68, 75, 6D, 31, 3D, 2D, 31, 30, 30, 0D, 65, 78, 74, 72, 61, 68, 75, 6D, 32, 3D, 2D, 31, 30, 30, 0D, 65, 78, 74, 72, 61, 68, 75, 6D, 33, 3D, 2D, 31, 30, 30, 0D, 7D, 0D
}

data from HS log;
9/8/2009 5:25:19 AM - xapmcswol - mcs.wol.foreman-hs | using xap port 32769
9/8/2009 5:31:46 AM - xapmcswol - mcs.wol.foreman-hs | readmessage i=59,j=078, 61, 70, 2d, 68, 65, 61, 64, 65, 72, 0d, 7b, 0d, 76, 3d, 31, 32, 0d, 68, 6f, 70, 3d, 31, 0d, 75, 69, 64, 3d, 46, 46, 34, 30, 30, 31, 30, 30, 0d, 63, 6c, 61, 73, 73, 3d, 57, 65, 61, 74, 68, 65, 72, 2e, 52, 65, 70, 6f, 72, 74, 0d, 73, 6f, 75, 72, 63, 65, 3d, 77, 69, 6e, 64, 79, 2e, 77, 65, 61, 74, 68, 65, 72, 2e, 31, 0d, 7d, 0d, 57, 65, 61, 74, 68, 65, 72, 2e, 52, 65, 70, 6f, 72, 74, 0d, 7b, 0d, 74, 65, 6d, 70, 66, 3d, 37, 31, 2e, 35, 0d, 75, 74, 63, 3d, 31, 30, 3a, 33, 31, 3a, 34, 30, 20, 41, 4d, 0d, 74, 65, 6d, 70, 63, 3d, 32, 31, 2e, 39, 0d, 69, 63, 6f, 6e, 3d, 0d, 64, 61, 74, 65, 3d, 32, 30, 30, 39, 30, 39, 30, 38, 0d, 77, 69, 6e, 64, 6d, 3d, 20, 30, 0d, 77, 69, 6e, 64, 6b, 3d, 20, 30, 0d, 61, 69, 72, 70, 72, 65, 73, 73, 75, 72, 65, 3d, 31, 30, 30, 36, 2e, 39, 0d, 77, 69, 6e, 64, 64, 69, 72, 63, 3d, 45, 0d, 68, 75, 6d, 69, 64, 69, 74, 79, 3d, 38, 34, 0d, 72, 61, 69, 6e, 3d, 30, 2e, 30, 0d, 65, 78, 74, 72, 61, 74, 65, 6d, 70, 31, 3d, 35, 37, 2e, 38, 0d, 65, 78, 74, 72, 61, 74, 65, 6d, 70, 32, 3d, 32, 35, 35, 2e, 30, 0d, 65, 78, 74, 72, 61, 74, 65, 6d, 70, 33, 3d, 2d, 33, 33, 2e, 33, 0d, 65, 78, 74, 72, 61, 68, 75, 6d, 31, 3d, 2d, 31, 30, 30, 0d, 65, 78, 74, 72, 61, 68, 75, 6d, 32, 3d, 2d, 31, 30, 30, 0d, 65, 78, 74, 72, 61, 68, 75, 6d, 33, 3d, 2d, 31, 30, 30, 0d, 7d, 0d

Also, here is the record from weather-display;
xap-header
{
v=12
hop=1
uid=FF400100
class=Weather.Report
source=windy.weather.1
}
Weather.Report
{
tempf=71.5
utc=10:34:04 AM
tempc=21.9
icon=Night time/Dry
date=20090908
windm= 0
windk= 0
airpressure=1006.9
winddirc=E
humidity=84
rain=0.0
extratemp1=57.8
extratemp2=255.0
extratemp3=-33.3
extrahum1=-100
extrahum2=-100
extrahum3=-100
}

I do get updates from weather-display every 2 seconds with a 60 sec heartbeat. Not sure why it is not working for you....

[CouchPotatoe]

Hmm - Haven't looked at that hex dump in detail but it looks like Weather Display is using chr(13) '0D' as the line delimiter whereas the xAP specification requires chr(10) '0A' . Unless perhaps it's being replaced for display purposes.... ?

K

[Michael McSharry]

This is the same thing that I expected based upon the prior ascii dump. Based upon the WD discussion forum it looks like the xAP interface has been implemented for several years. Apparently it is not being used by anyone. How response is the author to fixing problem with the software?

[CouchPotatoe]

Strange thing is that there are several people using this with xAP and there haven't been reported issues. I also tried it at launch although I didn't purchase it. He is very responsive to emails. Let me download the latest version and check that there is a problem.

What version of weather display are you running - that produced those messages ?

K

In checking I have found that early versions of the xFX hub/Viewer would actually correct such malformed messages as they stored and then resent messages. Later versions and I guess the mcs one (correctly) don't. This might explain why initial tests were OK. I'll update you as I find out more...

[sforeman00]

I am running Weather Display V10.37O Build 02.

I am also running the latest version of xfx Express Hub V13? I can't really find where it says what version it is but I just downloaded it less than a week ago.

I appreciate the help....

[sforeman00]

K, i was wondering if you had an update on this problem.
thanks

[CouchPotatoe]

I emailed Brian over a week ago but I haven't yet had a response .

I have also confirmed that the xAP message format from Weather Display is incorrect and is using '0D' terminators instead of '0A' . This might have slipped through earlier as the hub would have transparently corrected it. There are also a couple of parameter fields that are reporting with leading spaces eg

windm= 2
windk= 2

I'll send him another email.... but I only have the info@ address from his website.

K

[sforeman00]

Thanks K, I have posted a message on thier board as well;

http://www.weather-watch.com/smf/ind...c,41893.0.html

Brian is very responsive so we should see something pretty quick.

[CouchPotatoe]

I have had an email back from Brian...

"ok, i have changed that in the latest .zip beta update, ready now"
19th Sep 10.37O Build 12 .zip upate: Fix fro xAP messages, now use LF instead of CR


So hopefully you're all set to go :-)

K

[sforeman00]

You wouldn't happen know know where Brian keeps the beta code do you?

[sforeman00]

Found the beta code under downloads.

I just installed it and HS is now configured to read in Weather Display data updates. Very Cool! No more scripts....