Can anyone shed light on these matters from the Weewx-Weather34 skin;
1. Position 4, in the easyW34skinsetup.php only gives the options of of
advisory_rw, _eu,_uk. Is this the only options for position 4? Some
previous versions on the internet are showing Position 4 with more options
Sorry for the wrong answer!
On Fri, Apr 9, 2021 at 3:05 PM Tom Keffer wrote:
> You had the right idea, but we have to be careful about values that are
> encoded in only two bytes.
>
> Try this version.
>
> -tk
>
> On Fri, Apr 9, 2021 at 8:50 AM Chris Thompstone <
> chris.thompst...@gmail.com>
Converting the wview DB to the extended schema made everything happy. Took
a while.
--Richard
On Friday, April 9, 2021 at 3:08:33 PM UTC-7 tke...@gmail.com wrote:
> Alternatively, V4.5.1 allows you to add new data types one-by-one. See the
> section *Adding a new type to an existing
What type of hardware?
Did you change the kind of record generation?
On Fri, Apr 9, 2021 at 10:46 AM 'Tom' via weewx-user <
weewx-user@googlegroups.com> wrote:
> Hi,
>
> I have updated WeeWX from version 3.8 to the current version. Now I have
> the problem that the wind direction is only
Alternatively, V4.5.1 allows you to add new data types one-by-one. See the
section *Adding a new type to an existing database
* in
the Customizing Guide.
On Fri, Apr 9, 2021 at 2:12 PM vince wrote:
> Not a great problem description for us to work on, but my guess is that
> your old db is the
You had the right idea, but we have to be careful about values that are
encoded in only two bytes.
Try this version.
-tk
On Fri, Apr 9, 2021 at 8:50 AM Chris Thompstone
wrote:
> Don't worry, I think I may have patched it. I'm not really much of a
> coder (although can do some stuff)...
>
Not a great problem description for us to work on, but my guess is that
your old db is the old wview-compatible schema and the new software expects
the newer wview-extended schema.
Easiest way to check your db is see how many tables are in your db:
echo ".schema" | sqlite3
Probably not worth sweating, as Weewx seems to have stitched everything
back together except earlier today...and that's fine. However, after
switching to the wview SDB file, I am seeing an error every cycle from
WeeWX in the log:
Apr 9 13:50:24 minix weewx[6296] ERROR weewx.reportengine:
WeeWX and I are getting along well. We had a wview installation that had
accumulated 7+ years of readings from a TE923W. The recent WeeWX data is
only a week or two. I have done the DB shuflle and WeeWX is creating
summary data and such for the pile of wview data.
It's not a huge loss if
Hi,
I have updated WeeWX from version 3.8 to the current version. Now I have
the problem that the wind direction is only written into the SQLite
database with a resolution of 22.5 degrees. I took over the old
configuration file weewx.conf during the update.
Previously, the wind direction was
Don't worry, I think I may have patched it. I'm not really much of a coder
(although can do some stuff)...
Modded your file. see line 345 onwards.
See attached
On Friday, 9 April 2021 at 16:36:35 UTC+1 tke...@gmail.com wrote:
> Sorry. I’ll try to get an update out later today.
>
> On Fri, Apr
Sorry. I’ll try to get an update out later today.
On Fri, Apr 9, 2021 at 8:18 AM Chris Thompstone
wrote:
>
> just tried that and get:
> Apr 9 16:17:18 weewx weewx[1719] DEBUG weewx.drivers.ultimeter: Close
> serial port /dev/ttyUSB0
> Apr 9 16:17:19 weewx weewx[1719] CRITICAL __main__: Caught
just tried that and get:
Apr 9 16:17:18 weewx weewx[1719] DEBUG weewx.drivers.ultimeter: Close
serial port /dev/ttyUSB0
Apr 9 16:17:19 weewx weewx[1719] CRITICAL __main__: Caught unrecoverable
exception:
Apr 9 16:17:19 weewx weewx[1719] CRITICAL __main__: startswith
first arg must
The driver should work fine with Python 3.
However, the driver has a small, non-functional bug that causes it to emit
that error message when it encounters a "dash" value. It's non-functional
because it emits the right value ("None"). It just shouldn't log an error.
Try this version. I've taken
Oh, the ultimeter isn't supported on Python 3 and ver 4 weewx ?
Is that what your saying?
Oh, had not planned on that.
I found some sort of error in my template, which I've kind of resolved.
But the Ultimeter driver... not sure on this one.
Thanks
Chris
On Friday, 9 April 2021 at 15:20:41 UTC+1
Looks like you switched to Python 3 from Python 2.7 and the driver isn't
compatible, based on the error message.
On Fri, Apr 9, 2021 at 6:56 AM Chris Thompstone
wrote:
> Hi Guys,
> I have been trying to upgrade to version 4 since my Pi decided to throw a
> strop.
> Anyway, it's been fairly
Hi Guys,
I have been trying to upgrade to version 4 since my Pi decided to throw a
strop.
Anyway, it's been fairly hardwork.
I have this message continuous in the logs:
DEBUG weewx.drivers.ultimeter: Decode failed for '': invalid literal
for int() with base 16: ''
just coming every 1s
should this still work with weewx 4.5.1 ?
i updated and my full day charts are gone
Manfred Maier schrieb am Montag, 15. Juni 2020 um 11:12:27 UTC+2:
> Thanks, Gary, for this comprehensive explanation.
>
> Based on what you wrote I was now able to plot an entire day.
>
> [image: Bildschirmfoto
18 matches
Mail list logo
