Announcement

Collapse

Contacting HomeSeer This Week

HomeSeer is open and operational this week. All orders are being processed and shipped as usual. However, some staff are working from home. If you need to contact HomeSeer for support or customer service, please use our Email or Chat options. https://homeseer.com/contact-us/
See more
See less

xAP conduit address config problem

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

  • xAP conduit address config problem

    All,
    I am trying to get homeseer to talk to Xlobby (different PC) with the new plugin.
    I have narrowed the problem down that the Xap conduit on homeseer does not have its address configed properly. See below for one of the xAP conduit status messages going out:

    xap-header
    {
    v=12
    hop=1
    uid=FF416304
    class=xAPBSC.event
    source=mi4.homeseer..116:Outside.Temperature
    }
    output.state
    {
    State=ON
    Text=53.8
    }

    Its missing the field after "mi4.homeseer.".
    What did I forget to configure so it shows the PC location?

    Thanks.

  • #2
    Originally posted by a0192677
    All,
    I am trying to get homeseer to talk to Xlobby (different PC) with the new plugin.
    I have narrowed the problem down that the xAP conduit on homeseer does not have its address configed properly. See below for one of the xAP conduit status messages going out:

    <snip>
    source=mi4.homeseer..116:Outside.Temperature
    Yes...as you say the xAP HomeSeer plugin hasn't picked up the windows machine name automatically which should be between the two periods in the address.

    source=mi4.homeseer.<machinename><machinename>"machinename". 116:Outside.Temperature

    I wonder, is this an oldish version of Windows you are running on by any chance ?? There isn't current a way to configure this.. looks like a way might be needed to manually define it or pick it up differently.

    K</machinename></machinename></snip>

    Comment


    • #3
      I am running Win98 so sounds like my problem.
      Thanks.

      Comment


      • #4
        Here is the VB Module I use to obtain the computer name and it works with 98/2K/XP. Winsock also provides a way to get this information.


        Public Declare Function GetComputerName Lib "kernel32" Alias "GetComputerNameA" _
        (ByVal lpBuffer As String, nSize As Long) As Long


        Public Function GetThisComputerName() As String
        '
        ' This routine will obtain the Computers name from the system. The
        ' second time it is called it returns the static 'sName' variable
        '
        Static sName As String
        Dim lBuffLen As Long
        Dim sBuffer As String
        Dim lRet As Long

        10 If Len(sName) > 0 Then
        20 GetThisComputerName = sName
        30 Exit Function
        40 Else
        50 lBuffLen = 128
        60 sBuffer = String$(lBuffLen, vbNullChar)
        70 lRet = GetComputerName(sBuffer, lBuffLen)
        80 If lRet < 0 Then
        '
        ' Handle API error Here
        '
        90 Exit Function
        100 End If
        110 sName = Left$(sBuffer, lBuffLen)
        120 GetThisComputerName = sName
        130 End If
        End Function

        Comment


        • #5
          Thanks for everyone's help.

          The developer upgraded the XAP_conduit to allow the computer name to be inserted in the settings file:
          http://groups.yahoo.com/group/xap_au...n/message/1260
          (need to subscribe to xap_automation)

          All is well now.

          Comment

          Working...
          X