MyAcurite data feed no longer working

Looks like Acurite has once again changed protocols and am not getting 503 HTTP Errors on registration and data submission. Data is also outdated.

Per their website, they have released a new PC interface to MyAcurite. Looks like we need to tear it apart and see how it works.

https://support.acurite.com/hc/en-us/articles/360018212073-PC-Connect-for-Windows-Important-Software-Update-

Cheers

Geoff

Hi
do you have a 5 in 1 station, or?

also have you seen this
http://kevin-key.blogspot.com/2014/09/new-version-is-now-available-for.html
which will now still work with the old smart hub

I do have the old 5 in 1 station.

This is a recent change in 2019, not in 2014.

I can always use their program, but then WeatherDisplay is no longer providing the data and I won’t be able to use it.

I stand corrected. The blog you quoted also has 2019 comments which are quite terse, and I don’t know what it refers to. I am not using a “Hub”, I am using VIS Reader to get data to Weather Display. I think this is a different process.

you can still use WD with kevins program, by setting to use the csv file that program creates as the data source

but I think its a bit confusing here
is the vis reader and WD still getting data OK from your 5 in 1 and you are just instead refering to getting data to the acurite server?

Yes. VIS Reader pulls the data fine from the 5 in 1. Just that it doesn’t feed to AcuRite. It is still feeding WD just fine. I’m going to do a capture of the URL’s used and get a CSV using the new native Acurite program and see what’s changed.

did you have WD or VIS program set to update to acurite? (its not very clear)

Used to be WD a while ago. Then VIS currently. Neither are working now due to change at Acurite

so should this then not be something to bring to the attention of the author of the vis program?

CompKing has already gotten some good info at the VIS Reader Forum - here.

Well the function you have internal to WD to feed to Acurite is why I bring this to your attention. Unless you plan to remove it. It no longer functions.

I have also reported it to VIS

CompKing

No Joy on Wireshark. They’ve gone from port 80 HTTP to 443 SSL [No Surprise]

Old URL: http://hubapi.myacurite.com/
New URL (Per DNS record lookup): https://atlasapi.myacurite.com/

Tried passing a URL with same parameters as old API and got a HTTP 400 bad request.

The only option I see is to find out if there is any documentation on this new “Atlas” API by Acurite. Or just not feed them anymore. :frowning:

I will just remove it
Acurite have become a closed shop more and more

Looks like someone has been doing some work with the Atlas platform. Though it looks like a Man in the Middle proxy to interpret the data. Don’t know how they are getting around the SSL portion.

Will keep an eye on the code and see if anything comes up that will help.

https://github.com/acuparse/acuparse

I have seen reference to acuparse
I think they make a "fake’ certificate