Short answer - it depends. 

Slightly longer answer. If you have a valid WU ID and Station Key entered 
in the WS View/WSView Plus app for your Ecowitt device then Ecowitt will be 
sending data to WU. If you have valid (and identical) WU station and id 
settings 
and enable = True under [StdRESTful] [[Wunderground]] in weewx.conf then 
WeeWX will be posting to WU. You can confirm WeeWX is posting by looking at 
the WeeWX log, unless you have altered the default log settings WeeWX will 
log each post to WU (you won't see rapid fire posts being logged though 
unless you explicitly set log_success = True).

So what does that mean? Who knows; WU behaviour is a bit of a mystery. It 
might accept both, it might ignore one always or now and then, or it might 
only function on Wednesdays. My suggestion is use one or the other. Ecowitt 
will be the simplest but if it fails you really get no indication something 
is wrong. WeeWX is equally as simple but also gives you the ability to know 
when WU posts fails as well as giving you more control over what is posted.

Gary

On Saturday, 16 July 2022 at 01:38:29 UTC+10 Thom VC wrote:

> I have finally gotten my Weewx software working and took the steps 
> <https://www.weewx.com/docs/usersguide.htm#Wunderground> to send the data 
> to Wunderground. It appears to be working, but I'm curious how this 
> functions. In order to get the Station ID/API I already had to connect my 
> station to WU via Ecowitt app.
>
> So is WU now showing data straight from Ecowitt? Or does it show what is 
> being directed from Ecowitt-->Weewx--> WU? 
>
> And will WU have access to all back data in Weewx? This is my ultimate 
> goal to have long-term record accessible. 
>
> Thank you for the explanation!
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/6bb20d73-e09c-4b8f-8e20-92dbe1d896b5n%40googlegroups.com.

Reply via email to