Oh Ok. So I think I maybe misunderstood some posts I found online. So I 
dont pay anything aslong as I dont download the data to frequently? In some 
postings they say, that you have to pay after one year anyway.
I saw the API thing before, but here you can only download the real time 
data, I guess. For me it would be enough to download all data once a month 
or so. Is this possible?

Whatever - I would prefer to have a self-managed datalogger for many 
reasons.
The most important reason is, that I would also see the inside temperature 
which is not possible because of " privacy policies". Also there is one 
more temp-sensor, which also dont show up.
And to have "everything in my hands".

So can anyone help me?

BR,
Steinwolf
galfert schrieb am Sonntag, 17. Januar 2021 um 17:12:55 UTC+1:

> It is not true that WU doesn't let you download your own data. The 
> confusion is that you can't download data the old way with a .csv download 
> file. The new way to download your own data is to use an API key that you 
> can generate under your account setting. Then you must use this new API 
> method to download your data. There is even a WeeWX extension to use this 
> new method that has been created.
>
> The reason for this change is that before anyone could download any amount 
> of data and there were no controls to limit bandwidth usage. With the new 
> API key method you are limited in the amount of bandwidth you can use on a 
> monthly basis. This limits bandwidth abuse and it allows WU to better run 
> their servers and reduce costs. If you are a business and you were 
> previously downloading tons of data from WU, then those efforts have been 
> blocked. You'll now have to purchase a commercial license in order to 
> continue to download the amounts of data that you were before. You could 
> say that a few bad apples with their abuse ruined the simplicity of the 
> previous .csv download method. There were a few years where WU servers were 
> hardly ever up. Sure things are not still perfect with WU but they 
> certainly are a lot better than they were before these controls were 
> implemented.
>
>
>
>
> On Sunday, January 17, 2021 at 10:41:11 AM UTC-5 Steinwolf wrote:
>
>> Hello,
>> I need help with the Bresser 6in1 Pro Wifi. (sends data to 
>> WeatherUnderground). Unfortunatelly it is the "stupid" not FINEOffset 
>> version, so I have to use the interceptor, but I'm unable to get the 
>> interceptor working. 
>> I'm really unhappy with WU (now they even dont let you download your own 
>> data!) and thats why I will use weewx. 
>> By the way - this whole raspbian, linux,... thing is also new to me, so I 
>> struggle with this all and can only do things I found on the internet. So 
>> please, in case you write back, dont think I know anything - tell me like 
>> I'm a litte kid or so ;)
>>
>> My setup: 
>> Bresser Weather 6in1 Pro WiFi (the one with the display) (IP 
>> 192.168.188.60- I guess, because the Bresser configuration site is here)
>> Raspberry Pi3 (with weewx, interceptor and apache)
>> Fritz.Box as router
>>
>> IPs: 
>> Bresser Weather IP 192.168.188.60 (I guess, because the Bresser 
>> configuration site is here) 
>> Raspbi IP LAN 192.168.188.34, IP WLan  192.168.188.35 
>> (raspbiweather.fritz.box also works) 
>> FritzBox IP (as gateway?) 192.168.188.1
>>
>> The problem:
>> I permanently get this error:
>>
>> pi@raspbiWeather:~ $ sudo /etc/init.d/weewx status
>> ● weewx.service - LSB: weewx weather system
>>    Loaded: loaded (/etc/init.d/weewx; generated)
>>    Active: active (exited) since Sun 2021-01-17 13:50:40 GMT; 3s ago
>>      Docs: man:systemd-sysv-generator(8)
>>   Process: 2410 ExecStart=/etc/init.d/weewx start (code=exited, 
>> status=0/SUCCESS)
>>
>> Jän 17 13:50:40 raspbiWeather python3[2426]: weewx[2426] CRITICAL 
>> weewx.engine:     ****      self._server = Consumer.TCPServer(address, 
>> port, handler)
>> Jän 17 13:50:40 raspbiWeather python3[2426]: weewx[2426] CRITICAL 
>> weewx.engine:     ****    File "/usr/share/weewx/user/interceptor.py", line 
>> 584, in __init__
>> Jän 17 13:50:40 raspbiWeather python3[2426]: weewx[2426] CRITICAL 
>> weewx.engine:     ****      TCPServer.__init__(self, (address, int(port)), 
>> handler)
>> Jän 17 13:50:40 raspbiWeather python3[2426]: weewx[2426] CRITICAL 
>> weewx.engine:     ****    File "/usr/lib/python3.7/socketserver.py", line 
>> 452, in __init__
>> Jän 17 13:50:40 raspbiWeather python3[2426]: weewx[2426] CRITICAL 
>> weewx.engine:     ****      self.server_bind()
>> Jän 17 13:50:40 raspbiWeather python3[2426]: weewx[2426] CRITICAL 
>> weewx.engine:     ****    File "/usr/lib/python3.7/socketserver.py", line 
>> 466, in server_bind
>> Jän 17 13:50:40 raspbiWeather python3[2426]: weewx[2426] CRITICAL 
>> weewx.engine:     ****      self.socket.bind(self.server_address)
>> Jän 17 13:50:40 raspbiWeather python3[2426]: weewx[2426] CRITICAL 
>> weewx.engine:     ****  OSError: [Errno 99] Die angeforderte Adresse kann 
>> nicht zugewiesen werden
>> Jän 17 13:50:40 raspbiWeather python3[2426]: weewx[2426] CRITICAL 
>> __main__: Unable to load driver: [Errno 99] Die angeforderte Adresse kann 
>> nicht zugewiesen werden
>> Jän 17 13:50:40 raspbiWeather python3[2426]: weewx[2426] CRITICAL 
>> __main__:     ****  Exiting...
>>
>> So that " Die angeforderte Adresse kann nicht zugewiesen werden" means in 
>> english "The requested address cannot be assigned".
>>
>> I think that the IP address of the PWS is wrong or so?
>> If I do (didn't know what the commands exactly do, but found this on 
>> another help thread of some user) "sudo tcpdump -Anpl -s0 -w - -i eth0 src 
>> 192.168.188.60 | stdbuf -oL strings -n8", I get (after a few seconds 
>> waiting and Cntr+C) this:
>>
>> tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 
>> 262144 bytes
>>         _services
>> 3881D711F7A3-mysimplelink
>> 3881D711F7A3-mysimplelink
>> 3881D711F7A3-mysimplelink
>> ^C2 packets captured
>> 2 packets received by filter
>> 0 packets dropped by kernel
>>
>> " 3881D711F7A3-mysimplelink" is the Bresser PWS on the Fritzbox. Pakets 
>> received are sometimes more, sometimes less. I guess that the PWS sends 
>> every 10 secs or so, and thats why. 
>>
>> So is this correct? Than why it doesn't work? 
>>
>> In the weewx config I have:
>> station_type = Interceptor
>>
>> ##############################################################################
>>
>> [Interceptor]
>>     # This section is for the network traffic interceptor driver.
>>
>>     # The driver to use:
>>     driver = user.interceptor
>>     #device_type = lw30x
>>     device_type = wu-client
>>     #mode = sniff
>>     address = 192.168.188.60
>>     #port = 80
>>
>>
>> ##############################################################################
>>
>> Port is with "#" because I dont know the port and the the query above 
>> only works without " and port 80".
>>
>> Please be so kind and help.
>> BR,
>> Steinwolf
>>
>

-- 
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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/69593e46-c066-4b45-aa75-88c91e4a07e5n%40googlegroups.com.

Reply via email to