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

MCS Temp--Error in SetDeviceLastChange

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

  • MCS Temp--Error in SetDeviceLastChange

    Hello, I upgraded to HSP 2.5.0.80 and now am getting the following error every time MCSTemp updates. I have attached my .ini

    6/10/2013 5:51:59 PM - Plug-In - Found plug-in: mcsTemperature, version: 6.4.0.0


    6/10/2013 5:54:06 PM - Warning - Setting device string, housecode is not set. String is: <table><td><img alt='Voltage' src='/images/sensors/voltage.gif' height='16' width='16'><img alt=' ' src='/images/sensors/blank3.gif'></td><td valign='middle' align='left'><font color='gray'>0 v</font></td></table>
    6/10/2013 5:54:06 PM - Error - In SetDeviceLastChange:Length of argument 'String' must be greater than zero.

    Sorry if I missed this somewhere.

    Thanks,
    David
    Attached Files
    Last edited by DSteiNeuro; June 10th, 2013, 08:19 PM.
    DSteiNeuro

    HS3Pro

    MSI Cubi Intel(R) Core(TM) i5-5200U CPU @ 2.20GHz, 2201 Mhz, 2 Core(s), 4 Logical Processor(s) 16GB DDRl RAM

    Enabled Plug-Ins
    BLRussound, BLSpeech, HSTouch Server, JowiHue, MyQ, Nest, Rain8, Squeezebox, Ultra1Wire3, UltraGCIR3, Vista Alarm, X10,Z-Wave

  • #2
    Best change of understanding problem is with a general debug output. It seems to be indicating that some device that is selected has a blank house code or a full blank device code.

    Comment


    • #3
      Here is the debug log. Nothing popped out at me.
      I tried deleting the .ini file and letting MCS Temp rebuild, but the error came back as soon as I started copying the virtual devices to HS. I also develted the HS devices and let MCS Temp rebulid these.

      I ended up rolling back to the prior version of HSPro, but would like to get this to work so that I can use the Aeon Multisensors which require the newer version of HSPro.

      Thanks if you can find anything.

      David
      Attached Files
      DSteiNeuro

      HS3Pro

      MSI Cubi Intel(R) Core(TM) i5-5200U CPU @ 2.20GHz, 2201 Mhz, 2 Core(s), 4 Logical Processor(s) 16GB DDRl RAM

      Enabled Plug-Ins
      BLRussound, BLSpeech, HSTouch Server, JowiHue, MyQ, Nest, Rain8, Squeezebox, Ultra1Wire3, UltraGCIR3, Vista Alarm, X10,Z-Wave

      Comment


      • #4
        The issue appears to be associated with reading the internal ADC from the Temp08 which likely does not show up as a devices when mcsTemperature asks the Temp08 for a list of devices at startup.

        It will be difficult to setup to try to get to the bottom of it, but I would like you to try the following. In your mcsTemperature.ini file you have the following.

        1B00000075179A26="$5,05:05,0,0,0"
        1B00000075179A26V="$51,05:01,0,0,0"
        INTERNAL_ADC__00V="$57,,0,0,0"
        1B00000075179A26A="%51,05:01,0,0,0"

        Change the internal ADC to be the following and then start HS2 up.

        INTERNAL_ADC__00V="$57,09,0,0,0"

        Comment


        • #5
          I suspecyed this as well and tried several time to change the device code in the Sensor table with no luck.

          I will try editing the .ini as suggested.

          May be a while because I rolled back to the prior version of HSPro and everything is stable again. I saw the same error on other threads. I think that maybe Rich changed the error checking.

          Thanks
          DSteiNeuro

          HS3Pro

          MSI Cubi Intel(R) Core(TM) i5-5200U CPU @ 2.20GHz, 2201 Mhz, 2 Core(s), 4 Logical Processor(s) 16GB DDRl RAM

          Enabled Plug-Ins
          BLRussound, BLSpeech, HSTouch Server, JowiHue, MyQ, Nest, Rain8, Squeezebox, Ultra1Wire3, UltraGCIR3, Vista Alarm, X10,Z-Wave

          Comment

          Working...
          X