Announcement

Collapse
No announcement yet.

Object Reference Error

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

  • Object Reference Error

    Started to receive the following errors:
    Aug-28 07:07:27 weatherXML Error setTiedLastUpdate: Object reference not set to an instance of an object.
    Aug-28 07:07:27 weatherXML Error wXMLForecastINI: Object reference not set to an instance of an object.
    Aug-28 07:06:06 weatherXML Error saveTideDict: Object reference not set to an instance of an object.
    Aug-28 07:06:06 weatherXML Error wXMLForecastINI: Object reference not set to an instance of an object.
    Aug-28 07:04:46 weatherXML Error setDay4ToClear: Object reference not set to an instance of an object.
    Aug-28 07:04:46 weatherXML Error wXMLForecastINI: Object reference not set to an instance of an object.
    Aug-28 07:03:22 weatherXML Error Exception in LOG of weatherXML: Object reference not set to an instance of an object.
    Aug-28 07:03:22 weatherXML Error callSpeak: Object reference not set to an instance of an object.
    Not sure if I need to restart the plugin or if there is a different issue. On version 3.0.0.88

    Michael

  • #2
    Check to see if the ini files have gotten corrupted.
    --
    Jeff Farmer
    HS 3, HSPhone
    My HS3 Plugins: CFHSExtras, Random, Restart, Tracker, WeatherXML, PanaBluRay
    Other Plugins In Use: APCUPSD, BLOnkyo, Device History, EasyTrigger, HSTouch Server, PHLocation2, Pushover, RFXCom, UltraGCIR3, UltraMon3, UltraPioneerAVR3, X10, Z-Wave

    Hardware: GoControl Irrigation Controler, Schlage Lever Lock, Schlage Deadbolt, Way2Call Hi-Phone, RFXCom RFXrec433 Receiver, WGL 800, TI-103, Z-Net, Pioneer 1120, Pioneer 1021, Pioneer LX302, Panasonic BDT-110, Panasonic BDT-210 x2

    Comment


    • #3
      Jeff:

      I'm seeing the same kind of error messages whenever HS speaks a weather alert. How do we know if the files are corrupted? I looked at hspi_weatherXML.ini, and I didn't see any odd characters, or anything that looked odd...

      Regards,
      BBB

      Comment


      • #4
        Ok - I think I see where the problem was. In my Alert Trigger I had set a Speaker Client that no longer exists; hopefully that will eliminate the errors.

        BBB

        Comment

        Working...
        X