Announcement

Collapse
No announcement yet.

Barometer and barometer direction not updating

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

  • Barometer and barometer direction not updating

    My barometer and barometer direction devices have not updated in weeks. They are stuck on 30 and steady. This is for both NOAA and Dark Sky barometer and direction. They are both stuck on the same values, 30 and steady.

    I've tried deleting the devices and recreating them, but the error persists.

    I am running 3.0.1.7 beta.




  • #2
    I put a new beta version of .7 up today. I am planning on it going to the HS updater this weekend. If you would update via the Updater Override file and see if it fixes the barometer. I'm not sure what is causing your issue as I have a location running DarkSky and one running NOAA.
    Are you using inches for the Barometer value?
    --
    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
      Barometer is set to inches for both. I updated to the newer beta and it didnt fix the error. But it did add all these new errors:
      Apr-26 6:02:18 PM weatherXML Error setForecastDataHST Icon Image: Index was outside the bounds of the array.
      Apr-26 6:02:18 PM weatherXML Error Day Number: 5
      Apr-26 6:02:18 PM weatherXML Error Day Number: 4
      Apr-26 6:02:18 PM weatherXML Error Day Number: 3
      Apr-26 6:02:18 PM weatherXML Error Day Number: 2
      Apr-26 6:02:18 PM weatherXML Error Day Number: 1
      Apr-26 6:02:18 PM weatherXML Error Day Number: 0
      Apr-26 6:02:18 PM weatherXML Error Day Number: 6
      Apr-26 6:02:17 PM weatherXML Error Day Number: 5
      Apr-26 6:02:17 PM weatherXML Error refID: -1
      Apr-26 6:02:17 PM weatherXML Error getDayOfWeekFromDevice: locID: 1, whichDevice: 6, sDayOfWeek: Thursday, sDayOfWeekNumber: 4
      Apr-26 6:02:17 PM weatherXML Error refID: -1
      Apr-26 6:02:17 PM weatherXML Error getDayOfWeekFromDevice: locID: 1, whichDevice: 6, sDayOfWeek: Thursday, sDayOfWeekNumber: 4
      Apr-26 6:02:17 PM weatherXML Error refID: -1
      Apr-26 6:02:17 PM weatherXML Error getDayOfWeekFromDevice: locID: 1, whichDevice: 5, sDayOfWeek: Wednesday, sDayOfWeekNumber: 3
      Apr-26 6:02:17 PM weatherXML Error refID: -1
      Apr-26 6:02:17 PM weatherXML Error getDayOfWeekFromDevice: locID: 1, whichDevice: 5, sDayOfWeek: Wednesday, sDayOfWeekNumber: 3
      Apr-26 6:02:17 PM weatherXML Error refID: -1
      Apr-26 6:02:17 PM weatherXML Error getDayOfWeekFromDevice: locID: 1, whichDevice: 4, sDayOfWeek: Tuesday, sDayOfWeekNumber: 2
      Apr-26 6:02:17 PM weatherXML Error refID: -1
      Apr-26 6:02:17 PM weatherXML Error getDayOfWeekFromDevice: locID: 1, whichDevice: 4, sDayOfWeek: Tuesday, sDayOfWeekNumber: 2
      Apr-26 6:02:17 PM weatherXML Error refID: -1
      Apr-26 6:02:17 PM weatherXML Error getDayOfWeekFromDevice: locID: 1, whichDevice: 3, sDayOfWeek: Monday, sDayOfWeekNumber: 1
      Apr-26 6:02:17 PM weatherXML Error refID: -1
      Apr-26 6:02:17 PM weatherXML Error getDayOfWeekFromDevice: locID: 1, whichDevice: 3, sDayOfWeek: Monday, sDayOfWeekNumber: 1
      Apr-26 6:02:17 PM weatherXML Error refID: -1
      Apr-26 6:02:17 PM weatherXML Error getDayOfWeekFromDevice: locID: 1, whichDevice: 2, sDayOfWeek: Sunday, sDayOfWeekNumber: 0
      Apr-26 6:02:17 PM weatherXML Error refID: -1
      Apr-26 6:02:17 PM weatherXML Error getDayOfWeekFromDevice: locID: 1, whichDevice: 2, sDayOfWeek: Sunday, sDayOfWeekNumber: 0
      Apr-26 6:02:17 PM weatherXML Error refID: -1
      Apr-26 6:02:17 PM weatherXML Error getDayOfWeekFromDevice: locID: 1, whichDevice: 1, sDayOfWeek: Saturday, sDayOfWeekNumber: 6
      Apr-26 6:02:17 PM weatherXML Error refID: -1
      Apr-26 6:02:17 PM weatherXML Error getDayOfWeekFromDevice: locID: 1, whichDevice: 1, sDayOfWeek: Saturday, sDayOfWeekNumber: 6
      Apr-26 6:02:17 PM weatherXML Error refID: -1
      Apr-26 6:02:17 PM weatherXML Error getDayOfWeekFromDevice: locID: 1, whichDevice: 0, sDayOfWeek: Friday, sDayOfWeekNumber: 5
      Apr-26 6:02:17 PM weatherXML Error refID: -1
      Apr-26 6:02:17 PM weatherXML Error getDayOfWeekFromDevice: locID: 1, whichDevice: 0, sDayOfWeek: Friday, sDayOfWeekNumber: 5
      Apr-26 6:02:17 PM weatherXML Error refID: -1
      Apr-26 6:02:17 PM weatherXML Error getDayOfWeekFromDevice: locID: 1, whichDevice: 7, sDayOfWeek: Friday, sDayOfWeekNumber: 5
      Apr-26 6:02:17 PM weatherXML Error refID: -1
      Apr-26 6:02:17 PM weatherXML Error getDayOfWeekFromDevice: locID: 1, whichDevice: 7, sDayOfWeek: Friday, sDayOfWeekNumber: 5
      Apr-26 6:02:17 PM weatherXML Error refID: -1
      Apr-26 6:02:17 PM weatherXML Error getDayOfWeekFromDevice: locID: 1, whichDevice: 6, sDayOfWeek: Thursday Night, sDayOfWeekNumber: 4
      Apr-26 6:02:17 PM weatherXML Error refID: -1
      Apr-26 6:02:17 PM weatherXML Error getDayOfWeekFromDevice: locID: 1, whichDevice: 6, sDayOfWeek: Thursday, sDayOfWeekNumber: 4
      Apr-26 6:02:17 PM weatherXML Error refID: -1
      Apr-26 6:02:17 PM weatherXML Error getDayOfWeekFromDevice: locID: 1, whichDevice: 5, sDayOfWeek: Wednesday Night, sDayOfWeekNumber: 3
      Apr-26 6:02:17 PM weatherXML Error refID: -1
      Apr-26 6:02:17 PM weatherXML Error getDayOfWeekFromDevice: locID: 1, whichDevice: 5, sDayOfWeek: Wednesday, sDayOfWeekNumber: 3
      Apr-26 6:02:17 PM weatherXML Error refID: -1
      Apr-26 6:02:17 PM weatherXML Error getDayOfWeekFromDevice: locID: 1, whichDevice: 4, sDayOfWeek: Tuesday Night, sDayOfWeekNumber: 2
      Apr-26 6:02:17 PM weatherXML Error refID: -1
      Apr-26 6:02:17 PM weatherXML Error getDayOfWeekFromDevice: locID: 1, whichDevice: 4, sDayOfWeek: Tuesday, sDayOfWeekNumber: 2
      Apr-26 6:02:17 PM weatherXML Error refID: -1
      Apr-26 6:02:17 PM weatherXML Error getDayOfWeekFromDevice: locID: 1, whichDevice: 3, sDayOfWeek: Monday Night, sDayOfWeekNumber: 1
      Apr-26 6:02:17 PM weatherXML Error refID: -1
      Apr-26 6:02:17 PM weatherXML Error getDayOfWeekFromDevice: locID: 1, whichDevice: 3, sDayOfWeek: Monday, sDayOfWeekNumber: 1
      Apr-26 6:02:17 PM weatherXML Error refID: -1
      Apr-26 6:02:17 PM weatherXML Error getDayOfWeekFromDevice: locID: 1, whichDevice: 2, sDayOfWeek: Sunday Night, sDayOfWeekNumber: 0
      Apr-26 6:02:17 PM weatherXML Error refID: -1
      Apr-26 6:02:17 PM weatherXML Error getDayOfWeekFromDevice: locID: 1, whichDevice: 2, sDayOfWeek: Sunday, sDayOfWeekNumber: 0
      Apr-26 6:02:17 PM weatherXML Error refID: -1
      Apr-26 6:02:17 PM weatherXML Error getDayOfWeekFromDevice: locID: 1, whichDevice: 1, sDayOfWeek: Saturday Night, sDayOfWeekNumber: 6
      Apr-26 6:02:17 PM weatherXML Error refID: -1
      Apr-26 6:02:17 PM weatherXML Error getDayOfWeekFromDevice: locID: 1, whichDevice: 1, sDayOfWeek: Saturday, sDayOfWeekNumber: 6
      Apr-26 6:02:17 PM weatherXML Error refID: -1
      Apr-26 6:02:17 PM weatherXML Error getDayOfWeekFromDevice: locID: 1, whichDevice: 0, sDayOfWeek: Tonight, sDayOfWeekNumber: 5
      Apr-26 6:02:17 PM weatherXML Error refID: -1
      Apr-26 6:02:17 PM weatherXML Error getDayOfWeekFromDevice: locID: 1, whichDevice: 0, sDayOfWeek: Friday, sDayOfWeekNumber: 5
      Apr-26 6:02:01 PM weatherXML Error Day Number:
      Apr-26 6:02:01 PM weatherXML Error Day Number:
      Apr-26 6:02:01 PM weatherXML Error Day Number:
      Apr-26 6:02:01 PM weatherXML Error Day Number:
      Apr-26 6:02:01 PM weatherXML Error Day Number:
      Apr-26 6:02:01 PM weatherXML Error Day Number:
      Apr-26 6:02:01 PM weatherXML Error Day Number:
      Apr-26 6:02:01 PM weatherXML Error Day Number:
      Apr-26 6:02:01 PM weatherXML Error refID: -1
      Apr-26 6:02:00 PM weatherXML Error getDayOfWeekFromDevice: locID: 2, whichDevice: 7, sDayOfWeek: False, sDayOfWeekNumber: 5
      Apr-26 6:02:00 PM weatherXML Error refID: -1
      Apr-26 6:02:00 PM weatherXML Error getDayOfWeekFromDevice: locID: 2, whichDevice: 7, sDayOfWeek: False, sDayOfWeekNumber: 5
      Apr-26 6:02:00 PM weatherXML Error refID: -1
      Apr-26 6:02:00 PM weatherXML Error getDayOfWeekFromDevice: locID: 2, whichDevice: 6, sDayOfWeek: False, sDayOfWeekNumber: 4
      Apr-26 6:02:00 PM weatherXML Error refID: -1
      Apr-26 6:02:00 PM weatherXML Error getDayOfWeekFromDevice: locID: 2, whichDevice: 6, sDayOfWeek: False, sDayOfWeekNumber: 4
      Apr-26 6:02:00 PM weatherXML Error refID: -1
      Apr-26 6:02:00 PM weatherXML Error getDayOfWeekFromDevice: locID: 2, whichDevice: 5, sDayOfWeek: False, sDayOfWeekNumber: 3
      Apr-26 6:02:00 PM weatherXML Error refID: -1
      Apr-26 6:02:00 PM weatherXML Error getDayOfWeekFromDevice: locID: 2, whichDevice: 5, sDayOfWeek: False, sDayOfWeekNumber: 3
      Apr-26 6:02:00 PM weatherXML Error refID: -1
      Apr-26 6:02:00 PM weatherXML Error getDayOfWeekFromDevice: locID: 2, whichDevice: 4, sDayOfWeek: False, sDayOfWeekNumber: 2
      Apr-26 6:02:00 PM weatherXML Error refID: -1
      Apr-26 6:02:00 PM weatherXML Error getDayOfWeekFromDevice: locID: 2, whichDevice: 4, sDayOfWeek: False, sDayOfWeekNumber: 2
      Apr-26 6:02:00 PM weatherXML Error refID: -1
      Apr-26 6:02:00 PM weatherXML Error getDayOfWeekFromDevice: locID: 2, whichDevice: 3, sDayOfWeek: False, sDayOfWeekNumber: 1
      Apr-26 6:02:00 PM weatherXML Error refID: -1
      Apr-26 6:02:00 PM weatherXML Error getDayOfWeekFromDevice: locID: 2, whichDevice: 3, sDayOfWeek: False, sDayOfWeekNumber: 1
      Apr-26 6:02:00 PM weatherXML Error refID: -1
      Apr-26 6:02:00 PM weatherXML Error getDayOfWeekFromDevice: locID: 2, whichDevice: 2, sDayOfWeek: False, sDayOfWeekNumber: 0
      Apr-26 6:02:00 PM weatherXML Error refID: -1
      Apr-26 6:02:00 PM weatherXML Error getDayOfWeekFromDevice: locID: 2, whichDevice: 2, sDayOfWeek: False, sDayOfWeekNumber: 0
      Apr-26 6:02:00 PM weatherXML Error refID: -1
      Apr-26 6:02:00 PM weatherXML Error getDayOfWeekFromDevice: locID: 2, whichDevice: 1, sDayOfWeek: False, sDayOfWeekNumber: 6
      Apr-26 6:02:00 PM weatherXML Error refID: -1
      Apr-26 6:02:00 PM weatherXML Error getDayOfWeekFromDevice: locID: 2, whichDevice: 1, sDayOfWeek: False, sDayOfWeekNumber: 6
      Apr-26 6:02:00 PM weatherXML Error refID: -1
      Apr-26 6:02:00 PM weatherXML Error getDayOfWeekFromDevice: locID: 2, whichDevice: 0, sDayOfWeek: False, sDayOfWeekNumber: 5
      Apr-26 6:02:00 PM weatherXML Error refID: -1
      Apr-26 6:02:00 PM weatherXML Error getDayOfWeekFromDevice: locID: 2, whichDevice: 0, sDayOfWeek: False, sDayOfWeekNumber: 5
      Apr-26 6:02:00 PM weatherXML Error refID: -1
      Apr-26 6:02:00 PM weatherXML Error getDayOfWeekFromDevice: locID: 2, whichDevice: 7, sDayOfWeek: Friday, sDayOfWeekNumber: 5
      Apr-26 6:02:00 PM weatherXML Error importDSForecast: sCurDayNumber: 5
      Apr-26 6:02:00 PM weatherXML Error importDSForecast: nDay: 7
      Apr-26 6:02:00 PM weatherXML Error refID: -1
      Apr-26 6:02:00 PM weatherXML Error getDayOfWeekFromDevice: locID: 2, whichDevice: 6, sDayOfWeek: Thursday, sDayOfWeekNumber: 4
      Apr-26 6:02:00 PM weatherXML Error importDSForecast: sCurDayNumber: 4
      Apr-26 6:02:00 PM weatherXML Error importDSForecast: nDay: 6
      Apr-26 6:02:00 PM weatherXML Error refID: -1
      Apr-26 6:02:00 PM weatherXML Error getDayOfWeekFromDevice: locID: 2, whichDevice: 5, sDayOfWeek: Wednesday, sDayOfWeekNumber: 3
      Apr-26 6:02:00 PM weatherXML Error importDSForecast: sCurDayNumber: 3
      Apr-26 6:02:00 PM weatherXML Error importDSForecast: nDay: 5
      Apr-26 6:02:00 PM weatherXML Error refID: -1
      Apr-26 6:02:00 PM weatherXML Error getDayOfWeekFromDevice: locID: 2, whichDevice: 4, sDayOfWeek: Tuesday, sDayOfWeekNumber: 2
      Apr-26 6:02:00 PM weatherXML Error importDSForecast: sCurDayNumber: 2
      Apr-26 6:02:00 PM weatherXML Error importDSForecast: nDay: 4
      Apr-26 6:02:00 PM weatherXML Error refID: -1
      Apr-26 6:02:00 PM weatherXML Error getDayOfWeekFromDevice: locID: 2, whichDevice: 3, sDayOfWeek: Monday, sDayOfWeekNumber: 1
      Apr-26 6:02:00 PM weatherXML Error importDSForecast: sCurDayNumber: 1
      Apr-26 6:02:00 PM weatherXML Error importDSForecast: nDay: 3
      Apr-26 6:02:00 PM weatherXML Error refID: -1
      Apr-26 6:02:00 PM weatherXML Error getDayOfWeekFromDevice: locID: 2, whichDevice: 2, sDayOfWeek: Sunday, sDayOfWeekNumber: 0
      Apr-26 6:02:00 PM weatherXML Error importDSForecast: sCurDayNumber: 0
      Apr-26 6:02:00 PM weatherXML Error importDSForecast: nDay: 2
      Apr-26 6:02:00 PM weatherXML Error refID: -1
      Apr-26 6:02:00 PM weatherXML Error getDayOfWeekFromDevice: locID: 2, whichDevice: 1, sDayOfWeek: Saturday, sDayOfWeekNumber: 6
      Apr-26 6:02:00 PM weatherXML Error importDSForecast: sCurDayNumber: 6
      Apr-26 6:02:00 PM weatherXML Error importDSForecast: nDay: 1
      Apr-26 6:02:00 PM weatherXML Error refID: -1
      Apr-26 6:02:00 PM weatherXML Error getDayOfWeekFromDevice: locID: 2, whichDevice: 0, sDayOfWeek: Friday, sDayOfWeekNumber: 5
      Apr-26 6:02:00 PM weatherXML Error importDSForecast: sCurDayNumber: 5
      Apr-26 6:02:00 PM weatherXML Error importDSForecast: nDay: 0

      Comment


      • #4
        I reverted back to .7 stable release

        Comment


        • #5
          Actually, those aren't errors. They were log entries that I was wanting to check things with and wanted them to stand out in red for ease of finding.
          --
          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


          • #6
            So it won't be confusing I removed the log entries from above and added some others as normal log entries. Grab the beta .7 that I posted just now, and run the Conditions Schedule. Then please email me the logoutput.txt.
            --
            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


            • #7
              Well... I updated to the latest beta and now the weather xml log page only gives one option on the drop down list ("save to file") . The other options are missing. The log never populates anything and is stuck on 0 entries even when I run the schedules for conditions, forecast and daily.

              Click image for larger version

Name:	weatherxmllog.png
Views:	33
Size:	178.1 KB
ID:	1301516

              Comment


              • #8
                nevermind. I forgot to set the debug setting to logoutput. Sent logfile to your email.

                Comment


                • #9
                  Thank you. I am running sound at a church function today but I will look at it tomorrow.
                  --
                  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


                  • #10
                    A man of many talents. No rush. I appreciate your efforts.

                    Comment


                    • #11
                      I setup a location to use the same NOAA station that you are. I can see in the log file you sent that it is pulling in the inches and writing them to the device.
                      I have been checking my devices and they are updating. I am at a loss as to why yours are not working. Do you have the Units rounding set to 0 for pressure? That would at least explaing the rounding. Try setting it to round to 2 decimal places and see if that makes a difference.
                      --
                      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


                      • #12
                        Jeff I had pressure rounding to 0 . Changed it to 2 and now both barometer and barometer direction are updating normally. Thanks!!

                        Comment

                        Working...
                        X