On Wednesday, 22 May 2019 17:28:21 UTC+10, wysiwyg wrote:
>
>
> 2/ I think you have guess right with loop records: The station is my own
> development, Today I have 2 hardware:
> - one outdoor sensor (Temp, humi, rain, UV) emits every 150sec
> - one indoor sensor (barometer, intemp) emits every
There is another issue too, where a messages is sent without yearly rain as
this one, where the daily rainin is used by intercetor. It should not mix
the yearly and daily measurements it should use only one of them which
exists in all messages. But when it uses the daily it zeros the total rail
so
Those lines smell very much of WOW. Might want to disable WOW uploads as
well as WeatherCloud.
Gary
On Wednesday, 22 May 2019 16:38:31 UTC+10, Gábor Szabados wrote:
>
> There is another issue too, where a messages is sent without yearly rain
> as this one, where the daily rainin is used by
Hi !
Thank you Gary for your explanation!
I think you hit the bullseye (is it ok to say that ? English is not my
mother-language).
Let me explain:
1/ Yes, I showed archive records logs, but report engine start right after
record, so I assumed the record task as the reference for timings to
I think its fixed. Looks like by clearing the entries re the internet
services wunderground and the others some how it retained them even though
they were blanked out this is even after a restart of the unit.
The only way around it was to do a factory reset and seems to have done the
trick.
May 22 17:45:40 UBUNTUMATE-1000H weewx[3154]: interceptor: MainThread:
unrecognized parameter uv=0
May 22 17:45:40 UBUNTUMATE-1000H weewx[3154]: interceptor: MainThread:
unrecognized parameter stationtype=EasyWeatherV1.3.2
May 22 17:45:40 UBUNTUMATE-1000H weewx[3154]: interceptor: MainThread:
Just tried disabling rapid fire but no change. Its still incrementing as
previously... That 2.2.x figure still pops up.. Not sure where its pulling
this from
using rain_total 2.248
May 22 16:04:39 UBUNTUMATE-1000H weewx[2069]: interceptor: MainThread:
ignored parameter action=updateraw
May
Hallo
Ich habe diese Wetterstation Renkforce WH2315
Wenn jemand weis das diese Wetterstation mit weewx auf Lununtu oder
Raspberry pi kompatibel ist da soll er mir sagen was ich falsch gemacht
habe.
No, as I said, that's not the problem. I solved that yesterday. The
intermittent data is the problem. I searched the web for the error in the data
flow and I think I'm the only one...
Thanks anyway.
--
You received this message because you are subscribed to the Google Groups
"weewx-user"
I will post a cleaner log when I arrive home.
--
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
Hi!
You are right, the delay is not critical, just a bit annoying:
I used to rely on page update ~20sec after each round 5min, now it's a bit
more random (sometime one more minute as you can see in logs).
It's just disturbing when working a skin template ( sometime I just wait
for next
please try the wh23xx driver, not the fousb driver:
https://github.com/matthewwall/weewx-wh23xx
m
--
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
For one thing, the URL of this form:http://www.wunderground.com/weatherstation/WXDailyHistory.asp?ID=SOMESTATION=5=22=2019=1Is now redirecting to one using HTTPS:https://www.wunderground.com/weatherstation/WXDailyHistory.asp?ID=SOMESTATION=5=22=2019=1Also, the redirect itself takes an
Jarom,
CURL is pretty sophisticated in its ability to emulate browser state in pretty
much any way but JavaScript. When it worked this morning, I saw some cookies
were involved.
It may well be that the python way isn't handling that part.
I don't know enough about how python fetches pages to
Sort of a noob question or maybe a feature request: how about adding a web
interface to search the database for historic weather data? I grab the
wunderground data that I have uploaded to add to various farm records a few
months or even a year after the fact. If WU is getting worse perhaps I
Hey, Doug,
Creating a front end to search your own local data would certainly be doable.
For sure, directing end-users to our own sites and letting them search our
historical data would be useful.
But that wouldn't fix the problem at hand. :-/
The wunderfixer utility is there to query what data
Hard to make say too much from such a short log extract. Did you restart
WeeWX? Would be worthwhile seeing the log from a restart onwards covering a
least a couple of archive periods.
Gary
On Wednesday, 22 May 2019 16:10:09 UTC+10, Joe Santas wrote:
>
> Just tried disabling rapid fire but no
Hey WeeWX'ers!!! =D
I have a fix in the hopper.
There's nothing that can be done for the occasional HTTP 404, or even 503's I
am now seeing, but the HTTP 403 was due to a change on WU's part where they are
rejecting certain HTTP User-Agent strings. The fact that they are putting
Akamai in
On Wednesday, May 22, 2019 at 9:20:16 AM UTC-7, Steve2Q wrote:
> I know this may be way OT, but I have looked and could not find an answer
> elsewhere.
>
>
>
Try googling for your exact message:
"*Authentication is required to restart 'weewx.service'. Multiple
identities can be used for
Thanks, Vince...lost an old friend this past weekend...not thinking
straight.
Just needed to put sudo in front of the command
On Wednesday, May 22, 2019 at 1:21:08 PM UTC-4, vince wrote:
>
> On Wednesday, May 22, 2019 at 9:20:16 AM UTC-7, Steve2Q wrote:
>
>> I know this may be way OT, but I
I SSH'd into my Pi to do a weewx restart;
I used to type /etc/init.d/weewx restart and the command just worked
Now it says the following:
pi@raspberrypi:~ $ /etc/init.d/weewx restart
[] Restarting weewx (via systemctl): weewx.service AUTHENTICATING
FOR
I was able to get it to work twice in my web browser, but as you said, it
is sporadic. I don't ever recall them using Akamai before so that may very
well be a contributing factor.
I wonder if we can find out the origin address and see what happens if we
can bypass Akamai...
On Wednesday, May
Interesting, using curl sometimes I can it fine, but wunderfixer is always
getting a 403 Forbidden, as if it is actively being blocked... When it
doesn't work in curl I get `HTTP/1.1 404 Not Found` and when it does work I
get `HTTP/1.1 200 OK`. Curl never gets a 403 error.
On Wednesday, May
Hi,
Just downloaded the new update it does not display the main page and in the
apache log file is the following
[Wed May 22 16:25:54.543403 2019] [:error] [pid 18454] [client
192.168.0.39:59752] PHP Fatal error: Uncaught Error: Call to undefined
function mb_internal_encoding() in
I tried the 3.9.1 version and I get Could not get Weather Underground data.
Exiting.
Curl still works, even for yesterday's data. Tracing the script it doesn't
appear to be actually attempting the download.
On Wednesday, May 22, 2019 at 7:03:49 PM UTC-6, Leon Shaner wrote:
>
> Say, we need
I'm still working on this.CURL is telling me they are not only using https, but also TLSv1.2.Here is a transcript, in case one of y'all beats me to the fix. =D
--
You received this message because you are subscribed to the Google Groups "weewx-user" group.
To unsubscribe from this group and
Hey, Steve,
I must have missed the context, but if you are looking at overall system memory
growth, well, it's a normal / healthy thing for a Linux kernel to try to use as
much memory as possible at all times, to keep from having to go back to disk
for code pages as different processes context
Hey, Steve,
You're logged in as user pi.
When (re)starting weewx via a system service, such as "/etc/init.d/weewx
restart" or "systemctl restart weewx" you have to elevate to root by one means
or another.
The fact that it prompted you to pick a method of running under root is just a
Hello,
of course I can give more details :-)
So as you know I'm augmenting some extra data to my archive records which I
get from emulated davis loop packaged.
My file whichs contains always the latest data looks like this:
Am Mittwoch, 22. Mai 2019 13:05:30 UTC+2 schrieb mwall:
>
> please try the wh23xx driver, not the fousb driver:
>
> https://github.com/matthewwall/weewx-wh23xx
>
> m
>
Danke für die Antwort.
Auf dem Lubuntu Laptop konnte ich den Treiber installieren.
Das ganze funktioniert auch.
Aber auf dem
A little follow up. As the memory growth is still happening, I implemented
a script which runs the program free -m and does a little calculation to
determine if memory use is over 80% (or any % I want to use). If mem >80%
weewx is restarted. So at least it now will run unattended.
A new
Hi Leon,
Agreed, I realize my post is a bit off topic but if WU continues to be less
than reliable then perhaps other solutions might be viable?
Thanks for the reply, perhaps a new thread needs to be started by someone
smarter than me about historical data search.
Good luck with your research
32 matches
Mail list logo
