Announcement

Collapse
No announcement yet.

Can't get Version 3.0 to work

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

    Can't get Version 3.0 to work

    I must be making a simple mistake, but I downloaded Version 3.0 from the Updater, paid for it on the Homeseer website, but when I go to the temperature.asp page i get the following error:

    Script error: Response.Send hs.plugin("mcsTemperature").TemperatureASP(request, response)

    I previously was using version 2.0.0.8 without any major problems. I did not uninstall this prior version, as far as I know - I didn;t see any instructions for doing so.

    Any thoughts? Thanks in advance.

    #2
    associated with the v2 scripts. The plugin handles all of the things that used to be done by scripts.

    I don't know that there is any relationship between that and the error you're seeing, but I do know that needs to be done.

    --Bill

    Comment


      #3
      Bill is correct about cleaning out some V2 legacy. I tried to make a seamless upgrade path, but I did miss the events.

      You should also replace the hspi_mcsTemperature.exe with the one at the top of the problem report thread. Several bug fixes and features have been incorporated since the initial introduction and I can support the current version. It is at Latest plugin version
      You need to bear with me with respect to the manual since much of the setup has changed betwen V3.0 and V3.3. Everybody here is very supportive and any confusion can be quickly addressed.

      After V3.3.3 is installed, go to the setup page (via Plugins/mcsTemperature from the homeseer GUI) review the settings on the various tabs to confirm your configuration. The most important one being the Interfaces tab. Then exit the setup with the Update button. Do this even if you made no changes. This is the trigger I use to request the serials numbers be captured from the sensors delivered by the Temp05 as well as verifying that all databases are setup etc.

      This problem was reported before but no subsequent feedback provided and it did not get worked. I suspect the additional debug code in V3.3.x will be sufficient to point us in the correct direction as to the real cause of the problem.

      There is an outstanding basic problem with V4.25 Temp05 interface, assuming you are using that configuration. A type mismatch error is reported by prior users. I was unable to reproduce the error. If you also get it then please use the "Show Raw Data" button on the setup page and post the results so I can use this data stream for testing.

      [This message was edited by Michael McSharry on Thursday, 23 January 2003 at 10:22 AM.]

      Comment


        #4
        Thanks. I've deleted the v2 events, and downloaded the newest version of the plugin (3.3.4). Loads OK, but now I am also getting the 'type mismatch' error. Here is the raw data from the log:

        1/26/03 11:31:38 PM~!~mcsTemperature Plugin Debug~!~Database Timer=1
        1/26/03 11:32:39 PM~!~mcsTemperature Plugin Debug~!~Database Timer=5
        1/26/03 11:33:39 PM~!~mcsTemperature Plugin Debug~!~Database Timer=4
        1/26/03 11:33:44 PM~!~Temp05 Data~!~
        1/26/03 11:33:45 PM~!~Temp05 Data~!~Sensor #01=57.86F
        1/26/03 11:33:46 PM~!~mcsTemperature Plugin Debug~!~Data from V4 Temp05 Sensor#=1
        1/26/03 11:33:46 PM~!~mcsTemperature Plugin Debug~!~Log Temperature INSERT INTO Temperature(SampleDate) SELECT #1/26/03 11:33:46 PM# AS QT
        1/26/03 11:33:46 PM~!~Temperature Plugin~!~ TemperatureReceiveVersion4: Type mismatch
        1/26/03 11:33:47 PM~!~Temp05 Data~!~Sensor #02=60.00F
        1/26/03 11:33:48 PM~!~mcsTemperature Plugin Debug~!~Data from V4 Temp05 Sensor#=2
        1/26/03 11:33:48 PM~!~Temperature Plugin~!~ TemperatureReceiveVersion4: Type mismatch
        1/26/03 11:33:50 PM~!~Temp05 Data~!~Sensor #03=59.00F
        1/26/03 11:33:50 PM~!~mcsTemperature Plugin Debug~!~Data from V4 Temp05 Sensor#=3
        1/26/03 11:33:50 PM~!~Temperature Plugin~!~ TemperatureReceiveVersion4: Type mismatch
        1/26/03 11:34:39 PM~!~mcsTemperature Plugin Debug~!~Database Timer=3
        1/26/03 11:35:40 PM~!~mcsTemperature Plugin Debug~!~Database Timer=2
        1/26/03 11:36:40 PM~!~mcsTemperature Plugin Debug~!~Database Timer=1
        1/26/03 11:37:40 PM~!~mcsTemperature Plugin Debug~!~Database Timer=5
        1/26/03 11:38:40 PM~!~mcsTemperature Plugin Debug~!~Database Timer=4
        1/26/03 11:38:44 PM~!~Temp05 Data~!~
        1/26/03 11:38:45 PM~!~Temp05 Data~!~Sensor #01=57.86F
        1/26/03 11:38:46 PM~!~mcsTemperature Plugin Debug~!~Data from V4 Temp05 Sensor#=1
        1/26/03 11:38:46 PM~!~mcsTemperature Plugin Debug~!~Log Temperature INSERT INTO Temperature(SampleDate) SELECT #1/26/03 11:38:46 PM# AS QT
        1/26/03 11:38:46 PM~!~Temperature Plugin~!~ TemperatureReceiveVersion4: Type mismatch
        1/26/03 11:38:47 PM~!~Temp05 Data~!~Sensor #02=59.21F
        1/26/03 11:38:48 PM~!~mcsTemperature Plugin Debug~!~Data from V4 Temp05 Sensor#=2
        1/26/03 11:38:48 PM~!~Temperature Plugin~!~ TemperatureReceiveVersion4: Type mismatch
        1/26/03 11:38:49 PM~!~Temp05 Data~!~Sensor #03=59.00F
        1/26/03 11:38:50 PM~!~mcsTemperature Plugin Debug~!~Data from V4 Temp05 Sensor#=3
        1/26/03 11:38:50 PM~!~Temperature Plugin~!~ TemperatureReceiveVersion4: Type mismatch


        Hope this is helpful. It looks like the plugin is reading the sensors, but there is some translation error somewhere.

        [This message was edited by jwshome on Sunday, 26 January 2003 at 11:35 PM.]

        [This message was edited by jwshome on Sunday, 26 January 2003 at 11:59 PM.]

        Comment

        Working...
        X