I wonder if "cp -pr" was used? Permissions and subdirs may have complicated
matters...
--
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
On Tuesday, December 11, 2018 at 9:53:25 PM UTC-6, Louis De Lange wrote:
>
> I recently came across a really excellent solution for putting together
> your own weather station on the cheap with high quality sensors - and most
> importantly a very useful weather HAT to use with a Raspberry PI
After update to 3.9.0b2, anacron logged this:
/etc/cron.daily/logrotate:
error: Ignoring weewx because of bad file mode - must be 0644 or 0444.
No other anomalies noted at this time.
Thanks!
Paul
--
You received this message because you are subscribed to the Google Groups
"weewx-user"
On Sunday, January 27, 2019 at 11:21:05 AM UTC-6, Thomas Keffer wrote:
>
> Take a look at permissions in /etc/logrotate.d:
>
> *ls -l /etc/logrotate.d*
>
> On Sun, Jan 27, 2019 at 9:06 AM P Simmons >
> wrote:
>
>> After update to 3.9.0b2, anacron logged this
Updated to db1b41e, problem solved.
Thanks!
Paul
--
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
Howdy! I had no problems using v4.0.0b6 but decided to upgrade to v4.0.0b9.
I'm now having problems with report generation.
Here are my (sanitized) conf and log files.
Thank you,
Paul
--
You received this message because you are subscribed to the Google Groups
"weewx-user" group.
To
On Wednesday, January 22, 2020 at 8:20:57 PM UTC-6, Thomas Keffer wrote:
>
> Thanks, Paul
>
> Could you temporarily replace your copy of units.py with the attached? It
> will log some clues about what's causing the decode error.
>
>
>
>
TK: Wilco - but tomorrow (sorry for delay).
Thanks!
P.
On Wednesday, February 5, 2020 at 9:03:44 AM UTC-6, Thomas Keffer wrote:
>
> Could you please go into the file ws23xx.py and change the global variable
> DEBUG_SERIAL to True (line 803)? Then try running the driver directly. For
> example:
>
> *PYTHONPATH=bin python3
On Wednesday, February 5, 2020 at 6:54:41 PM UTC-6, Thomas Keffer wrote:
>
> /var/log/weewx.log? What's that? Did you try /var/log/syslog?
>
> On Wed, Feb 5, 2020 at 4:46 PM P Simmons >
> wrote:
>
>>
>>
>> On Wednesday, February 5, 2020 at 5:53:34 PM UTC-
Appended a "testing bookmark" in /var/log/syslog with "echo". Repeated
testing command series. No additional entries in /var/log/syslog either.
--
You received this message because you are subscribed to the Google Groups
"weewx-user" group.
To unsubscribe from this group and stop receiving
On Wednesday, February 5, 2020 at 5:53:34 PM UTC-6, Thomas Keffer wrote:
>
> Guess I forgot to mention one important detail: send the log!
>
> -tk
>
>
Repeated test... no log entries in /var/log/weewx.log during driver runs...
only console results. Next?
--
You received this message because
# PYTHONPATH=bin python3 bin/weewx/drivers/ws23xx.py --readings
--port=/dev/ttyS0
Traceback (most recent call last):
File "bin/weewx/drivers/ws23xx.py", line 2120, in
data = s.get_raw_data(SENSOR_IDS)
File "bin/weewx/drivers/ws23xx.py", line 790, in get_raw_data
raw_data =
On Thursday, February 6, 2020 at 11:13:28 AM UTC-6, Thomas Keffer wrote:
>
> I guess that's progress. Try this one.
>
> I'm just blinding replacing python 2 idioms with six idioms. No idea about
> the underlying logic.
>
> -tk
>
>
Result:
# PYTHONPATH=bin python3 bin/weewx/drivers/ws23xx.py
On Thursday, February 6, 2020 at 10:20:53 AM UTC-6, Thomas Keffer wrote:
>
> This remote debugging is hard!
>
> Give this version a try.
>
> -tk
>
>
>
I can appreciate the difficulty, having done remote development (in
assembly language, on an obscure Sharp platform, in the distant past).
On Thursday, February 6, 2020 at 11:36:40 AM UTC-6, Thomas Keffer wrote:
>
> Steady progress.
>
>
>
> # PYTHONPATH=bin python3 bin/weewx/drivers/ws23xx.py --readings
--port=/dev/ttyS0
Traceback (most recent call last):
File "bin/weewx/drivers/ws23xx.py", line 2117, in
data =
I've attempted to move from Python2 to Python3, and have encountered a
problem with ws23xx.py
Thank you,
Paul
--
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
Sorry for delay, needed a nap. |-)
# PYTHONPATH=bin python3 bin/weewx/drivers/ws23xx.py --readings
--port=/dev/ttyS0
Traceback (most recent call last):
File "bin/weewx/drivers/ws23xx.py", line 2117, in
data = s.get_raw_data(SENSOR_IDS)
File "bin/weewx/drivers/ws23xx.py", line 790, in
On Friday, February 7, 2020 at 6:46:40 AM UTC-6, Thomas Keffer wrote:
>
> I'm going to need an aspirin.
>
>
> On Thu, Feb 6, 2020 at 3:01 PM P Simmons >
> wrote:
>
>> Sorry for delay, needed a nap. |-)
>>
>> # PYTHONPATH=bin python3 bin/weewx/drivers/
On Friday, February 7, 2020 at 6:46:40 AM UTC-6, Thomas Keffer wrote:
>
> I'm going to need an aspirin.
>
>
>
>
Hold the aspirin... methinks you've found/fixed it!
The driver output looks normal (to me), and the reports are updating.
Kudos!
Paul
--
You received this message because you are
On Friday, February 7, 2020 at 2:28:34 PM UTC-6, mwall wrote:
>
> confirmed that the ws23xx driver is now working with both python3 and
> python2. tested with:
>
> station: lacrosse 2310
> os: debian7
> python: 3.7.4 and 2.7.3
> weewx: 4.0.0b11
> ws23xx driver: 0.41
>
> i just bumped the
On Friday, February 7, 2020 at 4:13:03 PM UTC-6, Thomas Keffer wrote:
>
> Thank goodness it's not that common a station!
>
>
>
Yeah, mine was a gift from a neighbor, received a few years ago. He
doesn't live out here full time. I watch over his property, and he wants
me to keep him apprised
On Friday, January 24, 2020 at 5:34:14 PM UTC-6, Thomas Keffer wrote:
>
> Could you all do a pull and give it another try? The flow path between
> byte strings and unicode are more controlled now, making the results less
> prone to decode errors.
>
> At least, that's the theory!
>
> -tk
>
My
Well, weewx doesn't terminate with the new driver under Python3, but there
seems to be another issue. The reports don't update under Python3.
It's been a long time since I modified the weewx.conf (and I'm sure I have
done so); don't discount the possibility that I've munged something!
Here
23 matches
Mail list logo
