The API has not been publicly posted yet, but if you have an application that wishes to use it you can approach Ecowitt directly through Lucy or via Galfert or myself and we might be able to provide the API documentation.
The alternative is to use the custom server output approach where your app receives the data rather than interrogating (requests the data) the GW1000
Quite a few folks have gone down that road as it does not require the API documentation
I will definetely try to do some "pull" experiments before start querying requests around.
Ofcourse as an introvert insecure developer I would prefer an official documentation/position from companies about their policies instead of having to ask around to people for "mights" and "maybes" risking to waste time if they realize that people tinkering isn't the best for them but this is the world we're living and this is just an hobby project for me.
You and Galfert saw my posts about my intention to work on it and didn't offer to help. I'm not a begger and I never understood security through obscurity.
They could have encrypted the traffic and sell to whoever wanted to pay for a commercial software if they don't want people to play with their stuff.
btw rhese half baked polices are just annoyingly common all over tech companies, its definetely nothing new or specific about Ecowitt, Ambient Weather or whoever is in charge in this specific case.
I'll discuss my progress on
https://discord.gg/7yXwugw