Announcement

Collapse
No announcement yet.

Plugin no longer supported due to health issues.

Collapse
This is a sticky topic.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    #31
    It shows without the https:

    http://w1.weather.gov/xml/current_obs/

    I don't see anyway to change this in the configuration? But this does resolve when I paste this into a browser.

    Comment


      #32
      Originally posted by simonmason View Post
      It shows without the https:

      http://w1.weather.gov/xml/current_obs/

      I don't see anyway to change this in the configuration? But this does resolve when I paste this into a browser.
      Ahhhhh! What version of the WXML plugin are you using. I'm using 3.0.1.19 and it shows https for me!
      Fred

      HomeSeer Pro 3.0.0.548, HS3Touch, Zwave 3.0.1.252, Envisalink DSC 3.0.0.40, WeatherXML, Z-stick, HS phone, Way2Call

      Comment


        #33
        Same version. Interesting. My hspi_weatherxml.exe is dated 8/17/2019 at 9:59PM - perhaps you have a different compiled exe?

        Or perhaps there is a setting to change this that I haven't figured out yet?

        Thanks.
        Click image for larger version

Name:	Screen Shot 2021-08-13 at 11.11.09 AM.png
Views:	84
Size:	94.6 KB
ID:	1489041

        Comment


          #34
          I've been having the same problem, but have been too busy to try to sort it out. A dug a little deeper and found that under the HomeSeer HS3 directory in Config\weatherXML there is a weatherInfo.ini file with the URLs. I changed the http://*.weather.gov URLs to https and restarted HomeSeer, and now I see the https version in the locations page. However, that seems to have just changed my error from:

          downloadFile: NOAA Weather Condition from: http://w1.weather.gov/xml/current_obs/KDVT.xml. Error: The request was aborted: Could not create SSL/TLS secure channel.

          to

          downloadFile: NOAA Weather Condition from: https://w1.weather.gov/xml/current_obs/KDVT.xml. Error: The request was aborted: Could not create SSL/TLS secure channel.

          From a command prompt, I can use curl to pull the file just fine, so I remain just as stuck as simonmason

          Comment


            #35
            Originally posted by simonmason View Post
            Same version. Interesting. My hspi_weatherxml.exe is dated 8/17/2019 at 9:59PM - perhaps you have a different compiled exe?
            Hmmm. Use Notepad to take a look at file Homeseer HS3/Config/WeatherXML/Weatherinfo.ini. If the entry for NOAADomain is using http, try changing it to https.
            Fred

            HomeSeer Pro 3.0.0.548, HS3Touch, Zwave 3.0.1.252, Envisalink DSC 3.0.0.40, WeatherXML, Z-stick, HS phone, Way2Call

            Comment


              #36
              Same here - switched everything to https and got the same errors as czagar. Tried with and without curl. ITguyHS - if you have a chance, can you check you exe date/time - I am wondering if there is another build?

              Comment


                #37
                Originally posted by simonmason View Post
                Same here - switched everything to https and got the same errors as czagar. Tried with and without curl. ITguyHS - if you have a chance, can you check you exe date/time - I am wondering if there is another build?
                Oops, forgot to answer that! My hspi_weatherxml.exe is also dated 8/17/2019 at 9:59PM. I'm almost out of ideas at this point. Might be something to do with SSL/TLS support within Homeseer, but you'd think if that were the case, I would have the same problem. I googled that error and found some references to problems in .Net, so might be something there. I'm using Win 10 with .Net framework 4.5.1 multitargeting.
                Fred

                HomeSeer Pro 3.0.0.548, HS3Touch, Zwave 3.0.1.252, Envisalink DSC 3.0.0.40, WeatherXML, Z-stick, HS phone, Way2Call

                Comment


                  #38
                  I think I found a solution. I was looking at http://inflectra.com/support/knowledgebase/kb510.aspx which describes different ways to get .NET Framework to communicate with TLS 1.2 servers. I used the .config file suggestion, changing c:\Program Files (x86)\HomeSeer HS3\HSPI_WEATHERXML.exe.config to be like the attached (had to add .txt to be able to upload the file; don't do that for real) by adding

                  <AppContextSwitchOverrides value="Switch.System.Net.DontEnableSystemDefaultTlsVersions= false"/>

                  to the runtime section. I rebooted my system (probably overkill, but easiest way to be sure) and was able to pull conditions successfully.

                  The web page I mentioned has other ways to adjust this as well if you don't want to edit the the .config file.
                  Attached Files

                  Comment


                    #39
                    Awesome, I tried that and it looks to be running. Thanks for this!

                    Comment


                      #40
                      I saw part of the conversation on my phone while at the Cancer center yesterday.
                      If you need to change any of the settings in the ini files, you have to shutdown the plugin, then edit the ini file, save it and restart the plugin. The ini files are only read on the startup of the plugin.
                      In this case the correct fix is the HSPI_WEATHERXML.exe.config.

                      I'll post a health update at the top of the weatherXML forum.
                      --
                      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

                      Working...
                      X