Plugin no longer supported due to health issues.

[jono]

I had this same problem. Found this thread and I am back in business. Thank you all for contributing to solving it.

[CFGuy]

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.

[simonmason]

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

[czagar]

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.

[ITguyHS]

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.

[simonmason]

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?

[ITguyHS]

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.

[czagar]

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

[simonmason]

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.

[ITguyHS]

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!

[simonmason]

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.

[ITguyHS]

ITguyHS
The error I get is: "downloadFile: NOAA Weather Condition from: http://w1.weather.gov/xml/current_obs/KMMU.xml. Error: The request was aborted: Could not create SSL/TLS secure channel."

Interesting. If you look at the "NOAA Weather Conditions Setup" under the Locations tab, does it show http://w1.weather.gov/xml/current_obs/ or show https://w1.weather.gov/xml/current_obs/ (the difference being http vs. https)?

[simonmason]

ITguyHS Thanks for this. I went ahead and tried this. Either through this or a combination of other things above it seems like everything is working except current conditions.

The error I get is: "downloadFile: NOAA Weather Condition from: http://w1.weather.gov/xml/current_obs/KMMU.xml. Error: The request was aborted: Could not create SSL/TLS secure channel."

I can access that file without any issues on the homeseer machine in chrome - which I suspect doesn't necessarily mean homeseer can see it. I also manually downloaded the file into the data\weatherxml folder to see if I could fool it. But it looks for an presumably deletes the file judging by the logs.

So I have everything except current conditions working so far. This might be as good as it gets unless there are any other ideas? Thanks.

[ITguyHS]

ITguyHS Thanks for the response. I haven't used CURL as I am not sure what how to? I am doing some searches on this to figure it out, but if you have time to provide some pointers, that would be great.

First, check folder Homeseer HS3\Bin\weatherXML and see if you have curl.exe. It should probably already be there, as Jeff provides it as part of the base install. If it's there, then just go to the Locations tab in weatherXML and look about half-way down for the section titled "NOAA weather forecast setup". Check the "use CURL" box. Leave the "curl path" empty. Stop weatherXML and restart. That's it.

Be aware that the curl support was originally added for Windows XP machines only, but should work in any version of Windows. It bypasses some of the built-in Windows support for http, so it can sometimes be a fix for http transport problems.

[simonmason]

ITguyHS Thanks for the response. I haven't used CURL as I am not sure what how to? I am doing some searches on this to figure it out, but if you have time to provide some pointers, that would be great.