Here's the problem: when a browser renders a document, it needs to know
what encoding it is in. For HTML documents, this is specified by a meta tag
However, with a plain text document, there is no way to specify the
encoding, so, instead, browsers must use a default. From what I can tell,
Hi Tom
At #1 you wrote:
NOAA reports now use a 'utf8' encoding instead of 'strict_ascii'. This will
only
affect new installations. Fixes issue #644.
When I look at the skin.conf, utf8 has disappeared as a choice:
# Possible encodings include 'html_entities', 'strict_ascii',
My first upgrade of Wewwx (after years on wview). Upgraded from 4.1.1 to
4.4.0 with Belchertown 1.2 on a Ubuntu 20.04 VM using the setup.py method.
Wow that was smooth... Great software and wonderful community.
On Thursday, February 4, 2021 at 7:14:28 AM UTC-7 kk44...@gmail.com wrote:
>
Meanwhile I would add, that the update was without problems in my case
(Ubuntu apt-get upgrade). I use Belchertown skin and some additional
uploaders.
Vetti52 schrieb am Donnerstag, 4. Februar 2021 um 11:04:43 UTC+1:
> Hi,
> maybe a new thread would be helpful, because the issue is/was very
Hi,
maybe a new thread would be helpful, because the issue is/was very special
and might not be a problem with version 4.4.0:
After I realized, that weewx could be run manually, I was inspecting, what
was the difference. I had updated to version 4.4.0 and also had an update
for my Zigbee
Ok, can you please set debug=1, restart WeeWX as a daemon and post in a new
thread the log through until the failure occurs.
Gary
On Thursday, 4 February 2021 at 05:28:00 UTC+10 Vetti52 wrote:
> just to narrow down my problem:
>
> When starting manually
> weewxd /etc/weewx/weewx.conf
> it
Hi,
It appears there is a network/connectivity issue preventing the gw1000
driver connecting to your GW1000 device. Can you connect to the GW1000 via
the WS View app on your mobile device? If so is your WeeWX machine properly
connecting to the same network? Can you ping the WeeWX machine from
just to narrow down my problem:
When starting manually
weewxd /etc/weewx/weewx.conf
it works. Starting with
systemctl start weewx,
it fails.
Maybe, I will find out, what makes the difference. But, just in case,
someone knows the trick, please tell!
Thanks
-Peter
Vetti52 schrieb am Mittwoch,
Typo: Upgrade from 4.3.0 to 4.4.0.
Version 4.3.0 had no issues so far.
Vetti52 schrieb am Mittwoch, 3. Februar 2021 um 18:17:46 UTC+1:
> Just upgraded from 4.4.3 to 4.4.0, but it fails.
> got this in systemctl status weewx.service:
> Feb 03 16:44:25 RaspBee python3[629]: weewx[629] CRITICAL
>
Just upgraded from 4.4.3 to 4.4.0, but it fails.
got this in systemctl status weewx.service:
Feb 03 16:44:25 RaspBee python3[629]: weewx[629] CRITICAL weewx.engine:
debug_wind=self.debug_wind)
Feb 03 16:44:25 RaspBee python3[629]: weewx[629] CRITICAL weewx.engine:
File
Updated this morning on Debian 10.7 and after several minutes of
updating the DB, everything came up working smooth as silk.
Good show!
- Nate
--
"The optimist proclaims that we live in the best of all
possible worlds. The pessimist fears this is true."
Web: https://www.n0nb.us
Projects:
Updated here as well with standard and Weather34 skins on macOS 11.1. Flawless.
> On Jan 31, 2021, at 19:58, Neville Davis wrote:
>
> I am also now at 4.4.0 and Belchertown 1.2... everything working fine..
>
> Thanks very much
>
> On Sunday, January 31, 2021 at 10:04:09 AM UTC+10
This version fixes a bug that was introduced by fixing yet another bug. It
only affects vector wind plots.
4.4.0 01/30/2021
StdWXCalculate can now do calculations for only LOOP packets, only archive
records, or both. PR #630. Thanks to user g-eddy!
Introduced aggregate types "avg_ge" and
13 matches
Mail list logo
