Announcement

Collapse
No announcement yet.

xapmcs1wire can't switch a DS2405 to On or Off

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    #16
    Yes the hub , viewer and xapmswonewirerun on the same computer

    Remove the target address will come to :

    xap-header
    {
    v=12
    hop=1
    uid=FF411100
    class=xAPBSC.cmd
    source=mi4.homeseer.xpsp2-cfec901bc.Master
    }
    output.state.1
    {
    id=30
    state=On
    level=0%
    }
    is ok ?

    Have you see my ini file ? it's ok ?

    thanks

    Comment


      #17
      What do you think if i use your xapmcsScript to send a message to xap without homeseer ?
      With this i can personalise the message?
      If i find the good message to send, it is more simple to reproduce in HS?

      Comment


        #18
        The xAP viewer is the most flexible debug tool so xapmcsScript will not produce any better results.

        I noticed that xapmcs1wire is V1.3 which means the UID should look something like FF.0005:00
        I'm not certain if it will handle the V1.2 format. I cannot test any xap applications while I'm traveling so the best I can do is give ideas to try.

        I think the target is required, but can be wildcarded such as
        target=mcs.onewire.xpsp2-cfec901bc:>
        I suspect the problem is more basic than just the target format so wildcarding likely will not help.

        Comment


          #19
          Hi Michael,

          I'm out of my home for this week end. I haved one probleme when i install the xapmsconewire with UID FF.0005.00. in the viewer, he display me a error with syntax of UID. I change to FF05.00 and it's ok.
          The name of my computer (xpsp2-cfec901bc) cause problem ? with the char "-" in it ??
          In the start of week, i'll rename the computer and test, rename the UID and test.
          i'll keep abreast to you.

          bye

          Comment


            #20
            Is is not a problem for xapmcs1wire with the "-" as the software does not have any special use for it. I do not know what xap hub you are using and if it cares or not.

            Each received xAP message passes through the following conditions before a message should appear in the HS log for xAPBSC.cmd. I'll venture a guess that you are not receiving any xAp messages at xapmcs1wire which would point the finger at the hub. The UID should not matter at this point in the logic so it is also unlikely that changing it will make a difference. I added an output to the hs log for every xAP message received. This will assess if the hub if routing the messages to xapmcs1wire.

            Code:
            70            If Not (.CompareTarget(xap.XapSource) Or .CompareTarget("Unknown")) Then
            80                GoTo Normal_Exit
            90            End If
                          
            100           If .CompareClass("xAPBSC.query") Then
            110               If .CompareTarget(xap.XapSource) Then
            120                   BSCQuery .MsgTarget
            130               End If
            140           ElseIf .CompareClass("xAPBSC.cmd") Then
            150               If .CompareTarget(xap.XapSource) Then
            160                   sState = .GetItem("output.state", "State")
            170                   If DebugLog Then
            180                       hsWritelog PLUGIN_DEBUG, "BSCCmd Output.State ID=" & sID
            190                   End If
            Last edited by Michael McSharry; April 20, 2009, 01:29 PM.

            Comment


              #21
              Hi Michael,

              I'm very sorry. I have stop my hub (Hub in windows services) and start your hub.

              And it's ok my 2406 and 2405 change to On or Off via homeseer.

              Very very thanks.

              Bestoueb

              Comment

              Working...
              X