Could this 'new' system be causing dropouts for ambient weather and cwop update.
Relying on Ambientweather.net as a data source has its pitfalls. I suppose it could be possible that you are overwhelming your API quota if you are running this app and at the same time you need the Ambientweather.net API to upload to CWOP. Try turning off the use of multiple devices using the Ambientweather.net API. So don't use this app for a while and see if your reliability to CWOP improves. But even for those that don't use the API for anything but for AmbientCWOP.com there have been reliability issues.
I keep getting stale weather messages that are random as time or length of stale information. I also have accounts that show information for my station. Sometimes I get dropouts from weathercloud for same times but I find like this morning all the other stations showing no dropouts but cwop. I am at the point of dropping out of cwop. It's just so frustrating with all these issues.
Well it isn't CWOP's fault nor is it your hardware nor your Internet connection's fault. The problem is using Ambientweather.net and AmbientCWOP.com as a middleman. I've seen others report issues sometimes as Ambientweather.net at times has downtime. This has has nothing to do with using this or other app that leverages their API.
Another alternative if you want to more reliably send data to CWOP I would suggest doing so more directly. All you need is an Ecowitt GW1000 and one of 4 different software choices and a device to run said software (Cumulus MX, Meteobridge, Weather-Display, or WeeWX).
Right now your data path looks like this:
Station ---> Ambientweather.net ---> AmbientCWOP.com ---> CWOP
A more direct and reliable way is:
Station (GW1000) ---> 3rd party software device ---> CWOP