This really is an important service since WU is so unstable. For my friends roll out tomorrow, his neighbors are going to rely on that "share link" to see river temps.
I hope it comes back up tonight!
It does highlight that for free-to-use cloud based services such as these and even the likes of Gmail and O365 you have no contract and no SLA, and to be honest a fairly one sided set of terms and conditions that offers no liability. If you are truly dependant upon these services to make time critical decisions then you should really consider if you need to have a backup plan if the service were to be down, or the service were to disappear along with any historical data.
Even the likes of Google and Microsoft can get tripped up by expiring certificates, it's sorted in a few hours. But what would it mean to you if Ecowitt were to disappear overnight along with all the data?
That's why IT professionals suggest you have a copy of your data locally or/and on your own web site (and if deemed necessary) with the respective SLAs (even though this gives you only a pseudo 100% safety - you cannot financially afford to have a 99.99 % SLA [100 % nobody would give you] for all components of a service involved [front-end, local network, WAN, local server LAN, server], only banks or some governmental institutions can [or do their own hosting]) etc.
99% SLA (it's made over one year usually) means 88 hours (3.67 days) of service downtime accepted !
Usual, affordable SLAs cover 95% = 18.25 days downtime without breaking the SLA !!!
This whole cloud stuff only works reasonably if you have small amounts of data to transfer or have 10 Gbit (and more) network (and internet) access. Anyway "cloud" for most people is just remote storage but it's much more, including the network and server infrastructure.
I keep on laughing when Amazon or Microsoft (and many computer magazines) want to tell me I should make a backup of my PC in the cloud. It's ridiculous. How long does it take to transfer 100 GB (or more) for a disk image, even with a 1 Gbit internet connection (which would be shared in the local access infrastructure) ? And how long does the restore take ? Forget about it.
Such things you organize locally with either classical (external) hard disks (offline, ransomware protected) or with a high(er) capacity NAS with at least 1 Gbit connections, better 10 Gbit.
We simply don't have the access infrastructure yet to use "cloud services" for such purposes.
Of course, the weather data databases are of just a few megabytes size - but still. Your servers can be RPis, your backup media can be old HDDs connected to the RPis. A UPS covering your RPis, your WLAN access point and your consoles [and even your internet access infrastructure] is easily affordable.
I personally am relying on my own local private cloud (in modern terms). My weather data retrieved and logged by Meteobridge, weewx and CumulusMX (potentially a logging "overkill"
) are on different local servers, with a UPS protected local infrastructure, and with a distributed backup concept of the databases.
The weather networks are more for sharing even though I have my own public website using the templates and depiction of my choice. Relying on them for business critical applications is highly careless and irresponsible.
Also, @plunet, the certificate thing is a speculation on your end as this doesn't refer to the ecowitt.net web site but to the webapi.www.ecowitt.net which is responsible for the ecowitt.app, so Ecowitt say. These are different certificates.
The certificate error would not come up when connecting to
https://www.ecowitt.net/home/index?id=your-console-idyour usual access to your Ecowitt dashboard.
What the issue finally was Ecowitt have not revealed and they might not do so at all.
