[Message Prev][Message
Next][Thread Prev][Thread Next][Message
Index][Thread Index]
Re: HomeSeer, mcsXap plugin, Line 230 Type Mismatch
--------------060503000802030400060400
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sorry .. my last reply didn't seem to make it
I tried your message and it did give the same error. What it appears
is that the HomeSeer plugin is sensitive to parameter ordering in the
header (it shouldn't be). I re-ordered your message and it works OK.
If this is consistent with your findings perhaps you could leave a
message on the mcs forum that let's Michael know...
xap-header
{
v=12
hop=1
class=xAPBSC.info
uid=FFEECE00
source=BBxAP.xAPp.xAPMocker
}
input.state
{
State=ON
Text=18
}
Just a comment on xAPBSC. It is a simple and yet very capable
schema but it is bi-directional and so takes a little more in terms of
implementation to work as it should (must). It uses sub addressing
extensively and so your reporting endpoints should each have a unique
sub address, which in xAP v1.2 is between 01 and FE ie FFEECE01 to
FFEECEFE. The '00' endpoint is the application itself and the FF
endpoint is reserved. As such the UID you are using should end in 01.
Also - although still (!) not formally documented xAP v1.3 is in
widespread use. The main change here is that the UID field is sent in
this format which includes a '.' and a ':' that segment the value into
<network>.<address>:<subaddress>
v=13
UID=FF.EECE:00
The other change is that each of these segments can be any number of
even hex digits (uppercase).
Typically the <network> segment is still two digits ie 'FF' and the
<application> is 4 or 6 digits. The sub address is now allowed to be
more than 2 digits (which was the main reason for this change) and is
typically 2, 4 or 6 digits. Any even number of digits can be used in
any segment however.
v=13
UID=FF.1234:567A
UID=FF.AABBCC:12
UID=FF.1234:ABCDEF12
are all valid . This also has some ramifications in wildcard matching
and the xAPBSC schema matching in that the ID= value inside a
xAPBSC.cmd can now be any number of even hex digits (uppercase) too.
ID=AB12
Cheers Kevin
PS As you explore wildcard matching I wanted to clarify something.
I'll post some examples if you need more info...
A '*' matches any positional element , and the element must be present
A '>' matches everything onwards, either to the ':' or the end of the
address, and the positional element need not be present.
On 06/07/2011 11:35, Tom Wadeson wrote:
> I've written an xAP application to broadcast mock temperature readings
> over the network at set intervals. It's playing nicely with the xFx
> Hub and Viewer, but when HS2 is on the network I receive those errors
> in the logger.
>
> As the subject suggests, I'm receiving the error "Line 230 Type
> Mismatch".
>
> Anyone have any suggestions? I haven't been able to find a fix on any
> forums.
>
> Also, can someone confirm that the schema I'm using (which I believe
> to be valid BSC) is correct in this scenario?
>
> Thanks.
>
> Complete Error Message:
>
> 06/07/2011 11:31:00 - mcsXap - ProcessMessage
>
xap-header{source=BBxAP.xAPp.xAPMockerv=12class=xAPBSC.infouid=FFEECE00hop=1}input.state{State=ONText=18}
> Line 230 Type mismatch
>
>
--------------060503000802030400060400
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<head>
<style type="text/css">
<!--
/* start of attachment style */
.ygrp-photo-title{
clear: both;
font-size: smaller;
height: 15px;
overflow: hidden;
text-align: center;
width: 75px;
}
div.ygrp-photo{
background-position: center;
background-repeat: no-repeat;
background-color: white;
border: 1px solid black;
height: 62px;
width: 62px;
}
div.photo-title
a,
div.photo-title a:active,
div.photo-title a:hover,
div.photo-title a:visited {
text-decoration: none;
}
div.attach-table div.attach-row {
clear: both;
}
div.attach-table div.attach-row div {
float: left;
/* margin: 2px;*/
}
p {
clear: both;
padding: 15px 0 3px 0;
overflow: hidden;
}
div.ygrp-file {
width: 30px;
valign: middle;
}
div.attach-table div.attach-row div div a {
text-decoration: none;
}
div.attach-table div.attach-row div div span {
font-weight: normal;
}
div.ygrp-file-title {
font-weight: bold;
}
/* end of attachment style */
-->
</style>
</head>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01
Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<!-- **begin egp html banner** -->
<br><br>
<!-- **end egp html banner** -->
Sorry .. my last reply didn't seem to make it<br>
<br>
I tried your message and it did give the same error.
What it
appears is that the HomeSeer plugin is sensitive to parameter
ordering in the header (it shouldn't be). I re-ordered your
message
and it works OK. If this is consistent with your findings perhaps
you could leave a message on the mcs forum that let's Michael
know...<br>
<br>
xap-header<br>
{<br>
v=12<br>
hop=1<br>
class=xAPBSC.info<br>
uid=FFEECE00<br>
source=BBxAP.xAPp.xAPMocker<br>
}<br>
input.state<br>
{<br>
State=ON<br>
Text=18<br>
}<br>
<br>
Just a comment on
xAPBSC. It is a simple and yet very
capable schema but it is bi-directional and so takes a little more
in terms of implementation to work as it should (must).
It uses
sub addressing extensively and so your reporting endpoints should
each have a unique sub address, which in xAP v1.2 is between 01 and
FE ie FFEECE01 to FFEECEFE. The '00' endpoint
is the application
itself and the FF endpoint is reserved. As such the UID
you are
using should end in 01.<br>
<br>
Also - although still (!) not
formally documented xAP v1.3 is
in widespread use. The main change here is that the UID
field is
sent in this format which includes a '.' and a ':' that segment
the
value into
<network>.<address>:<subaddress><br>
<br>
v=13<br>
UID=FF.EECE:00 <br>
<br>
The other change is that each of these segments can be
any number
of even hex digits (uppercase). <br>
<br>
Typically the <network> segment is still two digits ie 'FF'
and the <application> is 4 or 6 digits. The sub
address is
now allowed to be more than 2 digits (which was the main reason for
this change) and is typically 2, 4 or 6 digits. Any
even number of
digits can be used in any segment however.<br>
<br>
v=13<br>
UID=FF.1234:567A<br>
UID=FF.AABBCC:12<br>
UID=FF.1234:ABCDEF12<br>
<br>
are all valid . This also has some
ramifications in wildcard
matching and the xAPBSC schema matching in that the ID= value inside
a xAPBSC.cmd can now be any number of even hex digits
(uppercase)
too. <br>
<br>
ID=AB12<br>
<br>
Cheers Kevin<br>
<br>
PS As you explore wildcard matching I wanted to clarify
something.
I'll post some examples if you need more info... <br>
<br>
A '*' matches any positional element , and the element must be
present<br>
<br>
A '>' matches everything onwards, either to the ':' or the end of
the address, and the positional element need not be present.<br>
<br>
<br>
<br>
<br>
<br>
On 06/07/2011 11:35, Tom Wadeson wrote:
<blockquote
cite="mid:CAAuuRUYQryPiT=ZX3ZGYUwDcmfR79d4a-2YEpZN-OfNcTKqthw@xxxxxxx"
type="cite">
<span style="display: none;"> </span>
<div id="ygrp-text">
<div>I've written an xAP application to broadcast mock
temperature readings over the network at set intervals.
It's playing nicely with the xFx Hub and Viewer, but when
HS2 is on the network I receive those errors in the
logger.</div>
<div><br>
</div>
As the subject suggests, I'm receiving the error "Line 230
Type Mismatch".
<div><br>
</div>
<div>Anyone have any suggestions? I haven't been able to
find a fix on any forums. </div>
<div><br>
</div>
<div>Also, can someone confirm that the schema I'm using
(which I believe to be valid BSC) is correct in this
scenario?</div>
<div><br>
</div>
<div>Thanks.<br>
<div><br>
</div>
<div>Complete Error Message:</div>
<div><br>
</div>
<div>
<div>
<div>06/07/2011 11:31:00 - mcsXap - ProcessMessage
xap-header{source=BBxAP.xAPp.xAPMockerv=12class=xAPBSC.infouid=FFEECE00hop=1}input.state{State=ONText=18}
Line 230 Type mismatch</div>
</div>
</div>
<div><br>
</div>
</div>
</div>
<!-- end group email -->
</blockquote>
<br>
<!-- **begin egp html banner** -->
<br>
<br>
<!-- **end egp html banner** -->
<div width="1" style="color: white; clear:
both;"/>__._,_.___</div>
<!-- Start Recommendations -->
<!-- End Recommendations -->
<!-- **begin egp html banner** -->
<img src="http://geo.yahoo.com/serv?s=97476590/grpId=9674343/grpspId=1705007709/msgId=4753/stime=1309960223";
width="1" height="1"> <br>
<!-- **end egp html banner** -->
<!-- **begin egp html banner** -->
<br>
<div style="font-family: verdana; font-size: 77%; border-top: 1px
solid #666; padding: 5px 0;" >
Your email settings: Individual EmailTraditional <br>
<a href="http://groups.yahoo.com/group/xap_automation/join;_ylc=X3oDMTJmdjUzdmNrBF9TAzk3NDc2NTkwBGdycElkAzk2NzQzNDMEZ3Jwc3BJZAMxNzA1MDA3NzA5BHNlYwNmdHIEc2xrA3N0bmdzBHN0aW1lAzEzMDk5NjAyMjM-";>Change
settings via the Web</a> (Yahoo! ID required) <br>
Change settings via email: <a href="mailto:xap_automation-digest@xxxxxxx?subject=Email
Delivery: Digest">Switch delivery to Daily Digest</a> <a
href = "mailto:xap_automation-fullfeatured@xxxxxxx?subject=Change
Delivery Format: Fully Featured">Switch to Fully Featured</a>
<br>
<a href="http://groups.yahoo.com/group/xap_automation;_ylc=X3oDMTJkZWQ3M2hsBF9TAzk3NDc2NTkwBGdycElkAzk2NzQzNDMEZ3Jwc3BJZAMxNzA1MDA3NzA5BHNlYwNmdHIEc2xrA2hwZgRzdGltZQMxMzA5OTYwMjIz";>
Visit Your Group
</a>
<a href="http://docs.yahoo.com/info/terms/";>
Yahoo! Groups Terms of Use
</a>
<a href="mailto:xap_automation-unsubscribe@xxxxxxx?subject=Unsubscribe";>
Unsubscribe
</a>
<br>
</div>
<br>
<!-- **end egp html banner** -->
<div style="color: white; clear:
both;"/>__,_._,___</div>
</body>
</html>
--------------060503000802030400060400--
xAP_Automation Main Index |
xAP_Automation Thread Index |
xAP_Automation Home |
Archives Home
|