n Raspian), feel free reaching out to me off-alias.
The weewx_watchdog is over here, for now:
https://github.com/UberEclectic/weewx/tree/master/examples/watchdog
Regards,
\Leon
--
Leon Shaner :: Dearborn, Michigan (iPad Pro)
--
You received this message because you are subscribed to the Goog
issue.
Sorry I don't know how those inTemp mappings work. I'm sure someone on the
alias will know...
You do realize all those China / Swiss ones are commented out, right?
So you really only have the one inTemp set:
> inTemp = temperature.*.*
Regards,
Leon
--
Leon Shaner ::
thon3 /var/tmp/maxsize.py
File "/var/tmp/maxsize.py", line 2
print sys.maxsize
^
SyntaxError: Missing parentheses in call to 'print'
pi@nixie:~ $ cat /var/tmp/maxsize3.py
import sys
print (sys.maxsize)
pi@nixie:~ $ python3 /var/tmp/maxsize3.py
2147483647
Reg
t to a point where it is quiet for long periods. You can stop
the strace after you see those a couple of times.
The output could be quite large so you may want to compress it:
$ gzip /tmp/weewxd_strace.txt
Regards,
Leon
--
Leon Shaner :: Dearborn, Michigan (iPad Pro)
> On Apr 25, 2019, at 10
a "third-party" and your switch has no reason to think the
conversation between the weather station and the server should be "shared" with
your weewx host.
Regards,
Leon
--
Leon Shaner :: Dearborn, Michigan (iPad Pro)
> On Apr 24, 2019, at 3:54 PM, Kev D wrote:
>
>
rst...
Regards,
Leon
--
Leon Shaner :: Dearborn, Michigan (iPad Pro)
> On Apr 24, 2019, at 6:20 AM, Damjan Hajsek wrote:
>
> Hi
> What I did is first use some old weewx.conf file from last year and doesn't
> work either.
> So I tried to reconfigure it but can't
>
Damian,
These logs still do not state debug = 1.
It still could be that the weewx.conf isn't being parsed correctly, and isn't
even able to read the debug = 1 setting.
Did you try my suggestions for how to "rebuild" the conf file?
Regards,
Leon
--
Leon Shaner :: Dearbo
ye. :-/
>From that, my takeaway is you probably need to factor in a UV sensor to
>account for transparency.
That forum I quoted would probably be a great place to get more input. Plenty
of PhD types over there. =D
Good luck! =D
Regards,
Leon
--
Leon Shaner :: Dearborn, Michigan
resting lead:
https://www.researchgate.net/post/How_can_we_compute_solar_position_at_a_given_place_on_a_given_day_and_time
Regards,
\Leon
--
Leon Shaner :: Dearborn, Michigan (iPad Pro)
Regards,
Leon
--
Leon Shaner :: Dearborn, Michigan (iPad Pro)
> On Apr 21, 2019, at 10:00 AM, kobuki wro
y.
HTH
Regards,
Leon
--
Leon Shaner :: Dearborn, Michigan (iPhone)
> On Apr 21, 2019, at 9:47 AM, kobuki wrote:
>
> Sorry if it might seem a bit off topic, but since I want to integrate this
> service in WeeWx, too, I thought it's the appropriate place after all. I'd
> like
to only put the
important parameters and to not reintroduce corruption.
Regards,
Leon
--
Leon Shaner :: Dearborn, Michigan (iPad Pro)
> On Apr 20, 2019, at 6:16 AM, AsgeirK wrote:
>
> I have of course tried to reverse the changes, but missing something (I
> haven't kept a cop
FWIW, I think WU is overloaded.
I manually run wunderfixer a couple of times a day here and there.
It routinely complains that WU is unavailable.
I'll try it up to 10 times before it finally "gets through."
Regards,
\Leon
--
Leon Shaner :: Dearborn, Michigan (iPad Pro)
Regard
one hand,
and being referenced in a later pass for the windDir and windGustDir changes.
So, I guess it is time for me to climb the roof, lower the pole, and push the
actual button on the wind-vane to physically calibrate it. :-/
Regards,
\Leon
--
Leon Shaner :: Dearborn, Michigan (iPad Pro)
R
0 if windGustDirMod < 0 else windGustDirMod)
if windGustDir is not None else None
Regards,
Leon
--
Leon Shaner :: Dearborn, Michigan (iPad Pro)
> On Apr 15, 2019, at 3:36 PM, Leon Shaner wrote:
>
> Hey, WeeWX'ers! =D
>
> I am baffled by a weewx.conf parsing er
0 else windGustDir) if
windGustDir is not None else None
print ("OUTPUT: windDir =", windDir, "windGustDir =", windGustDir)
Regards,
\Leon
--
Leon Shaner :: Dearborn, Michigan (iPad Pro)
--
You received this message because you are subscribed to the Google Gro
0.
We can see that 32736+32 is 32768, a "magic" power of 2, so even the empty
memory must contain 32 reserved records.
Anyway, I've set a reminder to check the history every two weeks in case the
automatic clearing via weewx isn't working. :S
Regards,
Leon
--
Leon Shaner :
Wow! Good show, Matt! =D
Regards,
\Leon
--
Leon Shaner :: Dearborn, Michigan (iPad Pro)
Regards,
Leon
--
Leon Shaner :: Dearborn, Michigan (iPad Pro)
> On Apr 14, 2019, at 6:58 PM, mwall wrote:
>
>> On Sunday, April 14, 2019 at 2:27:36 PM UTC-4, Leon Shaner wrote:
>>
hen, a user extension and an alarm would probably be the preferred
approach here, but the one example I saw for handling e-mail natively seemed
overly complicated, when all I really needed to do was call mailx. :-/
Regards,
\Leon
--
Leon Shaner :: Dearborn, Michigan (iPad Pro)
--
You received th
ck -- cool
enough, but even cooler now that it does something truly useful with the energy
it burns. =D
https://www.reddit.com/r/raspberry_pi/comments/awvfkq/enhanced_gra_afch_raspberry_pi_nixie_tube_clock/
Regards,
\Leon
--
Leon Shaner :: Dearborn, Michigan (iPhone)
--
You received this messa
w HHH ACCUM, (for which I presume "HHH" means
"High High High").
Then I held the MEM button and that cleared the RAIN display to 0.00 in. ACCUM.
I think that should solve this one! Thanks for all the help!
Regards,
Leon
--
Leon Shaner :: Dearborn, Michigan (iPad Pro)
>
humidex=prefer_hardware,
pressure=prefer_hardware, inDewpoint=prefer_hardware, ET=prefer_hardware,
altimeter=prefer_hardware, cloudbase=prefer_hardware
I ran that through "fmt -1 | sort -u" and these are the only references to
rain(.*) seen:
'rain_rate',
'rainRa
;t mind because I want both.
Meanwhile, I noticed that weewx was telling me that my maximum rain counter was
exceeded and that I should reset the data, so I did that on the 9th or 10th.
It rained for the first time since on the 12th.
Thanks again for all the insights.
Regards,
Leon
--
Leon Shaner :
Hey, TK,
Sorry. I did query for rain already and it's all 0.0, except as shown in the
second output I pasted.
Regards,
Leon
--
Leon Shaner :: Dearborn, Michigan (iPad Pro)
> On Apr 13, 2019, at 11:06 AM, Thomas Keffer wrote:
>
> You can't look for rain where rainRate i
1|0.489995002
2016-07-12|0.00998|0.509994798
2016-07-12|0.00998|0.659993268
2016-07-12|0.0101|0.07184
2016-07-13|0.02|0.0
2016-07-13|0.00998|0.279997144
2016-07-13|0.00998|0.539994492
Regards,
Leon
-
5
0.0 31500
2019-04-11 0.0 2019-04-11 00:00:01 0.0 2019-04-11 00:00:01 0.0 288
0.0 86400
2019-04-12 0.0 2019-04-12 00:00:01 0.419995716 2019-04-12
08:46:14 1.40269840736274 173 420.809522208823 51900
Regards,
\Leon
--
Leon Shaner :: Dearborn, Michigan (iPad Pro)
--
9 02:37:20 UTC+10, Damjan Hajsek wrote:
>>> Hi
>>>
>>>
>>> Yes I really changed debug to 1 in conf file. I am from GMT +2
>>> And I tested, date shows real date and time as it should be
>>> Why there is no logs I don't know, that i
s?
See here:
https://medium.com/python-pandemonium/debugging-an-inactive-python-process-2b11f88730c7
Meanwhile, perhaps consider upgrading to 1.3.9-1 (from your 1.3.8) and try
again?
Regards,
Leon
--
Leon Shaner :: Dearborn, Michigan (iPad Pro)
> On Apr 11, 2019, at 12:55 PM, Damjan Hajsek wrote:
&
a copy to share, it would be something like:
$ grep weewx /var/log/syslog > /var/tmp/weewx.log
(And you could upload /var/tmp/weewx.log, but only if it actually has recent
log entries).
Regards,
Leon
--
Leon Shaner :: Dearborn, Michigan (iPad Pro)
> On Apr 11, 2019, at 12:37 PM, Damjan Ha
erground-PWS on.
The setting to do that is in the Wunderground section and you can try adding it
right under the rapidfire = True a la:
archive_post = True
I'm on 1.3.9-1 and you're on 1.3.8, so while it is worth a shot, it might not
be the issue in your case.
Regards,
Leon
-
ire to actually work.
Probably a bug, but I'm going to give it a rest, because I want both
enabled anyway. =D
On Wednesday, April 10, 2019 at 5:02:26 PM UTC-4, Leon Shaner wrote:
>
> [snip]
>
>
> *I'm still stuck with needing both to be set to True for rapid fire to
>
If you wish to do this, set the option 'enable' to true,
> # and specify a station (e.g., 'KORHOODR3') and password.
> # To guard against parsing errors, put the password in quotes.
> enable = true
> station = KALALBER13
> password = X
>
> -
> Tom
>
&g
t, ALL the data reset. Which is fine by me.
I probably should have reset the data at least once a year and certainly
before trying out weewx with the unit (since it was taking forever to
process data going back to 2016).
On Wednesday, April 10, 2019 at 10:54:53 AM UTC-4, Leon Shaner wrote:
>
t, ALL the data reset. Which is fine by me.
I probably should have reset the data at least once a year and certainly
before trying out weewx with the unit (since it was taking forever to
process data going back to 2016).
On Wednesday, April 10, 2019 at 3:51:26 PM UTC-4, Leon Shaner wrote:
>
Hey, wall,
Thanks for the reply. I never did install their very old Windows XP
software, since I only have Mac, Linux, Raspian available.
Interestingly enough, I did just notice that they now sell for $60 some
software that claims to run on RPI, but the say the software is sold as is,
no refun
thout archive_post also
enabled, since the default behavior is for those two post methods to be
mutually exclusive. :-/
On Wednesday, April 10, 2019 at 3:14:52 PM UTC-4, Leon Shaner wrote:
>
> On Wednesday, April 10, 2019 at 2:41:24 PM UTC-4, Leon Shaner wrote:
>>
>> [snip]
>>
Yes, Tom, I have "rapidfire = True" as confirmed by:
Apr 10 14:53:23 nixie weewx[371]: restx: Wunderground-RF: Data for station
KMIDEARB5 will be posted
Thanks! =D
On Wednesday, April 10, 2019 at 3:02:37 PM UTC-4, Tom Robertson wrote:
>
> Did you set rapidfire = true in the [StdRESTful] [[Wund
On Wednesday, April 10, 2019 at 2:41:24 PM UTC-4, Leon Shaner wrote:
>
> [snip]
> I'm just happy that Rapidfire is now working! =D
>
> But can anybody explain why forcing PWS mode on was necessary for RF to
> start working?
>
> Or could it be that RF wasn'
Working my way through one issue at a time with my new setup on RPI.
With yesterday's fix for the the "non-positive" interval, my weewx started
processing archive data from the WMR300A unit (going back to 2016), with
the occasional datapoint from 2012 (which I suppose come from times that
the u
While setting up weewx 3.9.1-1 for the first time ever, yesterday on a RPI,
I saw some discrepant dates being reported.
That prompted me to check the date/time on the actual WMR300A, which I
found to be more than an hour off of actual.
My RPI has the current date/time taken from NTP.
So my questi
On Tuesday, April 9, 2019 at 5:09:02 PM UTC-4, mwall wrote:
>
> On Tuesday, April 9, 2019 at 4:42:17 PM UTC-4, Leon Shaner wrote:
>>
>>
>> On Tuesday, April 9, 2019 at 4:06:26 PM UTC-4, Leon Shaner wrote:
>>>
>>> Seeing several recent posts with a simila
On Tuesday, April 9, 2019 at 4:06:26 PM UTC-4, Leon Shaner wrote:
>
> Seeing several recent posts with a similar message with WMR200, but mine
> is on a new install with an WMR300A.
> Any solutions?
>
>
My guess is that there is some kind of a date issue.
I put in a hack in wmr
Seeing several recent posts with a similar message with WMR200, but mine is
on a new install with an WMR300A.
Any solutions?
Apr 9 16:03:20 nixie systemd[1]: Starting LSB: weewx weather system...
Apr 9 16:03:22 nixie weewx[807]: engine: Initializing weewx version 3.9.1
Apr 9 16:03:22 nixie wee
101 - 142 of 142 matches
Mail list logo
