Re: [mh] xAP basics

[Pete C <ha...@th...>]

Gregg Liming wrote:
> Pete C wrote:
>>
>> .. and nothing in the mh log ..
> 
> I wasn't paying attention to this part of your prior response.  If you 
> did set debug=xap;bsc and you don't see anything in the mh log when you 
> manually change status on the device, then you definitely do not have a 
> hub properly working w/ mh.  You should see xap traffic echoed in the mh 
> log.  So, a far more fundamental problem exists w/ your setup.
>


so, I tried a different xAP hub (was using xapmcsHUB (same guy that
wrote the AdiOcelot xAP app, which gives me a uneasy feeling) and
switched to xFx-Express Hub) now I am getting xAP messages echoed in
mh log ..

I restarted everything .. xAP hub first .. and it's log shows ..

17-Apr-09 21:14:05.9 INFO  Initialising xFx-Express Hub on command line
17-Apr-09 21:14:05.9 INFO  Hit Return to exit
17-Apr-09 21:14:06.2 INFO  Starting...
17-Apr-09 21:14:06.2 INFO  xFx.Hub.Commando UID=FF.0535BEC1:0000 (v13)
17-Apr-09 21:14:06.5 INFO  Selected Ethernet network interface 'Local 
Area Conne
ction 2' Intel(R) PRO/1000 MT Network Connection - Packet Scheduler Miniport
17-Apr-09 21:14:06.5 INFO  Transmit to:  10.0.2.255:3639
17-Apr-09 21:14:06.5 INFO  Listening on: 10.0.2.10:3639
17-Apr-09 21:14:06.5 INFO  Starting hub heartbeat, interval 60 seconds
17-Apr-09 21:15:12.6 INFO  Register mhouse.mh.misterhouse.core on port 
49152, ti
meout 21:17:12
17-Apr-09 21:15:16.2 INFO  Register mhouse.mh.misterhouse.x10_device on 
port 491
53, timeout 21:17:16
17-Apr-09 21:15:16.2 INFO  Register 
mhouse.mh.misterhouse.abstract_device on por
t 49154, timeout 21:17:16
17-Apr-09 21:15:16.2 INFO  Register mhouse.mh.misterhouse.presence on 
port 49155
, timeout 21:17:16
17-Apr-09 21:15:35.7 INFO  Register mcs.AdiOcelot.COMMANDO on port 
32768, timeou
t 21:35:35

.. then in th mh log when I hit the RF button ..

In $bsc_x10_device set callback for $rf_button_a9 using x10_device
No state change for $rf_button_a9
[BSC] $adi_sec_mode extracting subaddress uid =
db1 xap check: p=xAP s=mhouse.mh.misterhouse.core c=xapbsc.cmd 
t=mcs.adiocelot.c
ommando:> d=xap-header
{
v=12
hop=1
uid=FFE90000
source=mhouse.mh.misterhouse.core
class=xapbsc.cmd
target=mcs.AdiOcelot.COMMANDO:>
}
output.state.1
{
level=1/32767
state=on
}

.. then this repeats 4 times .. (most xAP msgs seem to go by 4 times in 
the mh log) ..

db1 xap check: p=xAP s=mhouse.mh.misterhouse.core c=xapbsc.cmd 
t=mcs.adiocelot.c
ommando:> d=xap-header
{
v=12
hop=1
uid=FFE90000
source=mhouse.mh.misterhouse.core
class=xapbsc.cmd
target=mcs.AdiOcelot.COMMANDO:>
}
output.state.1
{
level=1/32767
state=on
}


.. this when I change the value at the device ..

db1 xap check: p=xAP 
s=mcs.adiocelot.commando:ocelot_securitymode.ocelot_var__v0
10.index c=xapbsc.event t= d=xap-header
{
v=13
hop=1
uid=FF.00C7:0B
class=xapBSC.Event
source=mcs.AdiOcelot.COMMANDO:Ocelot_SecurityMode.Ocelot_Var__V010.Index
}
output.state
{
State=ON
Level=1/32767
}

db BSC_Item->event_callback: Process section:output.state from 
mcs.adiocelot.com
mando:ocelot_securitymode.ocelot_var__v010.index
db1 xap check: p=xAP 
s=mcs.adiocelot.commando:ocelot_securitymode.ocelot_var__v0
10.index c=xapbsc.event t= d=xap-header
{
v=13
hop=1
uid=FF.00C7:0B
class=xapBSC.Event
source=mcs.AdiOcelot.COMMANDO:Ocelot_SecurityMode.Ocelot_Var__V010.Index
}
output.state
{
State=ON
Level=1/32767
}

.. and this repeats 4 times ..

db1 xap check: p=xAP 
s=mcs.adiocelot.commando:ocelot_securitymode.ocelot_var__v0
10.index c=xapbsc.event t= d=xap-header
{
v=13
hop=1
uid=FF.00C7:0B
class=xapBSC.Event
source=mcs.AdiOcelot.COMMANDO:Ocelot_SecurityMode.Ocelot_Var__V010.Index
}
output.state
{
State=ON
Level=1/32767
}

.. any thoughts on what is going wrong?