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

Help with loading mcsXap

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

  • Help with loading mcsXap

    Hi,

    Just loaded homeseer 2 today, loaded a few devices, now
    hoping to control them remotely using Xap.

    I installed mcsXapHub121, its up and running.

    I opened up mcsXap_1_4_3.zip and copy the HTML dir
    to homeseer's html dir, and then copy the hspi_mcsXap.ocx
    to homeseer's base dir.

    DOS box regsvr32 hspi_mcsXap.ocx, OK

    Copied DLL's from mcsXapNet2_2_0_18.zip to HS base dir

    Restarted HS, and this is what I see in log:

    1/26/2008 3:44:13 PM Error Unable to initialize HomeSeer 1.x compatibility interface: Retrieving the COM class factory for component with CLSID {4B3C1F4A-4B61-4897-B13F-5DF3D40C7954} failed due to the following error: 80040154.
    1/26/2008 3:44:13 PM Startup Checking for available plug-ins
    1/26/2008 3:44:13 PM Info Found plug-in: X10 CM11A/CM12U, version: 1.0.1.0
    1/26/2008 3:44:13 PM Error Cannot access plug-in (may need to be re-installed): HSPI_POWERLINCUSB.HSPI -> Object variable or With block variable not set.
    1/26/2008 3:44:13 PM Error Cannot access plug-in (may need to be re-installed): HSPI_WMP9.HSPI -> Object variable or With block variable not set.
    1/26/2008 3:44:13 PM Error Cannot access plug-in (may need to be re-installed): HSPI_TOUCHPAD.HSPI -> Object variable or With block variable not set.
    1/26/2008 3:44:13 PM Error Cannot access plug-in (may need to be re-installed): HSPI_MCSXAP.HSPI -> Object variable or With block variable not set.
    1/26/2008 3:44:13 PM Info Found plug-in: mcsXap, version: 2.2.0.18


    Any help MUCH appreciated


    -Rick

  • #2
    You will want to use either the VB6 or the .NET version of mcsXap plugin, but not both. The VB6 is the stable one while the .NET stops communicating for some.

    Remove either the mcsXap DLLs (.NET) or unregister and remove the .ocx.

    The other errors are based upon access of the HST-provided plugins. Perhaps the above confused it, but otherwise you will need to ask others as to why such messages are occurring.

    Comment


    • #3
      I've not had much luck with the .net version, so am just trying the VB6 one. Using the latest 1.4.3, registered the .ocx etc., but get the following in the HS log. Is there something more I need to do ?

      08/02/2008 21:38:14 - Info - Initializing Plug-in: mcsXap
      08/02/2008 21:38:14 - mcsXap - Version 1.4.3 Registered with Homeseer
      08/02/2008 21:38:14 - COM Plugin - Calling InitIO
      08/02/2008 21:38:34 - mcsXap - Using xAP port 32769
      08/02/2008 21:38:34 - Warning - A program/plug-in is using the outdated RegisterLink function for xAP - please contact the plug-in author and request an update that uses RegisterLinkEx.
      08/02/2008 21:38:35 - Info - Finished initializing plug-in mcsXap

      Comment


      • #4
        Nothing you need to do, but it looks as if an HS1 function is being discontinued with HS2. I will need to look at the current SDK to see what needs to be done. I suspect it is only a warning at this time, but the worst case is that no button will appear for mcsXap and your access will only be from the menu where HS puts the log

        Comment


        • #5
          Originally posted by Michael McSharry View Post
          worst case is that no button will appear for mcsXap and your access will only be from the menu where HS puts the log
          Thanks Michael, I parked xAP for a while, but now that I've had another look, that is what is happening, there is no button in the HS browser screen, but when I try to access it from the HS GUI screen, it completely paralyses the GUI interface, so I have to shut it down from the Windows Task Manager screen.

          Comment


          • #6
            I addressed the warning message with the 1.5.4 build of the .ocx. Beyond that the only thing I can suggest is that you keep the center of the display clear so a form will not be hidden behind the window and this form may be waiting for input. The configuration should be done via a browser. The GUI form was retained, but not well maintained.

            Comment

            Working...
            X