WXforum.net
Weather Related Organizations => WeatherUnderground => Topic started by: dbashand on March 11, 2021, 11:50:20 AM
-
My pws went offline 11:45 cst on 3/9. Restarted all of the things. Anyone else seeing this issue?
-
Yes, WeatherUnderground says this:
“On March 9th we ended support for uploads using TLS 1.1. This protocol has been deprecated industry wide since 2020 and is no longer supported by most software. Weather Underground had delayed implementation of the protocol’s deprecation to give device manufacturers time to update their firmware, but some stations without firmware update capabilities may no longer be able to communicate with Weather Underground.”
AcuRite is also looking into the problem
-
I'm amazed that there are not more reports.
What weather station brand / model were you using?
-
AcuRite 5-in-1 with Wi-Fi
-
I found some other reports on Reddit:
https://www.reddit.com/r/myweatherstation/comments/m21cgv/acurite_5in1_01540sb_showing_offline_on/
All Acurite users.
-
Offline also using Acurite 5 in 1 since 3/9.
-
I'm wondering a few things?...
- Up until how recently was this affected Acurite model sold?
- Is this Acurite model still available....hopefully not.
- What solutions does Acurite have? (Firmware update?...replacement display console?...Access device?)
And lastly a more complex issue that perhaps some web gurus can explain if I'm wrong somewhere...
- Why is this WU upload blocking TLS 1.1 even an issue? I thought WU uploads occurred in clear text HTTP GET protocol?
Sure the official WU upload protocol defines it to use HTTPS...
https://support.weather.com/s/article/PWS-Upload-Protocol?language=en_US
but at least previously HTTP also worked (is HTTPS now enforced with greater security than TLS 1.1?)...example:
https://www.rubydoc.info/gems/weather-underground/WeatherUnderground/Uploader
Even if they enforce HTTPS with greater than TLS 1.1, as I understand the HTTPS GET protocol the data payload is still part of the clear text URL when using GET....I think. This is because the data is contained in the URL when using GET. So yes TLS 1.1 is insecure and I can understand removing support for it ...but in this case I don't even see what there is to protect. Maybe I'm wrong somewhere...I'll admit that I probably know enough to even confuse myself.
-
My Acurite manual is for Professional Weather Display model 06086M. This model number is also on the device itself. I purchased it on March 17 2019.
-
I just purchased the 06086M a few months ago to discover that it stopped transmitting data to the WU. I opened a ticket with the WU and they have been responsive and told me that they were looking into the issue. I decided to open a ticket with WU and learned that they stopped supporting TLS 1.1 earlier this month. I am very disappointed that the weather station that I bought for the singular purpose that it transmitted data to WU will not work. I am hopeful, but not holding my breath that there is some sort of solution that Acurite will offer.
-
I just purchased the 06086M a few months ago to discover that it stopped transmitting data to the WU. I opened a ticket with the WU and they have been responsive and told me that they were looking into the issue. I decided to open a ticket with WU and learned that they stopped supporting TLS 1.1 earlier this month. I am very disappointed that the weather station that I bought for the singular purpose that it transmitted data to WU will not work. I am hopeful, but not holding my breath that there is some sort of solution that Acurite will offer.
And now my device is working again after checking with the WU support and reporting my findings back to Acurite support? Not sure what is happening here.
-
I just purchased the 06086M a few months ago to discover that it stopped transmitting data to the WU. I opened a ticket with the WU and they have been responsive and told me that they were looking into the issue. I decided to open a ticket with WU and learned that they stopped supporting TLS 1.1 earlier this month. I am very disappointed that the weather station that I bought for the singular purpose that it transmitted data to WU will not work. I am hopeful, but not holding my breath that there is some sort of solution that Acurite will offer.
And now my device is working again after checking with the WU support and reporting my findings back to Acurite support? Not sure what is happening here.
Weather Underground responded back General WU Feedback Email <feedback@wunderground.com>
Fri 3/12/2021 2:01 PM
No, the devices guy returned the protocol to working to try to give AcuRite more time.
Anything you can do to update your instrument, by all mean, please do!
Thank you!
--Victoria
-
Acurite emailed me and let me know that WU will leave TLS on for an additional 6 months while they try to sort out this issue.
-
Does that mean that mean that the 06086M can do firmware updates?
-
Acurite didn't indicate what sort of fix they were working on.
-
Although the connection for now has been restored by WU, I also had the same connection issue here. I'm using the 5 in 1 Wi-Fi direct model 01540SB. I'm not sure what they will do to remedy this issue especially if there is a firmware update required. My model, the 01540SB doesn't have a USB port and relies sole on a Wi-Fi connection.
-
Just checked back with accurite and they do not have a permanent solution yet. Our grace period for updating WU ends sometime in September (I believe).
-
FYI, I believe that WU pulled the plug on TLS1.1 connection again meaning that these displays will no longer be able to send reports. You should hit Acurite up on this topic if you were affected.
-
I have the ATLAS 5-in-1 with WiFi (Model 06059M) and it's still sending data.
-
My Acurite connection went offline on 10/4.
-
My pws went offline 11:45 cst on 3/9. Restarted all of the things. Anyone else seeing this issue?
Isn't this a function of the software used to upload data? If so, could affected Acurite users switch to Cumulus or weeWX to upload their data?
-
Yes, WeatherUnderground says this:
“On March 9th we ended support for uploads using TLS 1.1.
Because reporting how fast the wind is currently blowing requires nuclear-weapons-launch-code-level security, apparently...
-
Isn't this a function of the software used to upload data? If so, could affected Acurite users switch to Cumulus or weeWX to upload their data?
You could also proxy it, if your device is hardcoded to report direct to WU then you could use DNS spoofing to direct it to a server you control and use a MITM proxy to change "1.1" to "1.2" when you connect to WU.
-
And my PWS display is FUBAR - a dump of the page indicates the display is MS-EDGE - O.N.L.Y.
So it wasn't broke - but we're IBM so F! the rest of you.
-
Some good news. I emailed Acurite after reading this other WXforum thread https://www.wxforum.net/index.php?topic=42827.0 and they were most helpful. As soon as I provided proof of purchase Acurite sent me an updated console that works with WU. It connected to my sensor and WU with no problems. My station is back up. I want to complement Acurite support for their prompt help and providing the replacement console free of charge.