Re: [weewx-development] Re: V4.0.0b4 is up

(update) Please, disregard my previous posting as Year now showing. After much do and starting over, WeeWX 4.0.0b5 now working with no issues on RPi4 2.7 python. Will leave for a while, and later try python 3. X -- You received this message because you are subscribed to the Google Groups

Re: [weewx-development] Re: V4.0.0b4 is up

Just FYI, the cmon skin is one of the skins that uses the imaging library's default font. On my Pi 3, this causes a slow increase in memory usage. See, https://groups.google.com/forum/#!topic/weewx-user/qeVSNzy7Zck for any additional information I might discover. - Rich On Saturday, 14

Re: [weewx-development] Re: V4.0.0b4 is up

"Baby steps" here and started from scratch all over again for RPi4... 1) RPi 3b+ / stable On the side, in parallel, and working fine with WeeWX 3.9.2 & Bskin 1.1b7 2) RPi 4 / bench test Transposed the above to RPi4 (ie, adjust previous 3.9.2 with Seasons skin to RPi 4, rebuild db, etc).

Re: [weewx-development] Re: V4.0.0b4 is up

Ralph, Try this version of cmon.py. I did a quick port to Python 3. It should work with Python 2 or 3, and under either WeeWX V3.9, or 4.0. -tk On Mon, Dec 16, 2019 at 6:53 PM Ralph Underwood wrote: > I found most of those items, but I was still getting a bunch of errors. My > system running

Re: [weewx-development] Re: V4.0.0b4 is up

I found most of those items, but I was still getting a bunch of errors. My system running 3.?? died a few days ago and my backups were not good so I was installing the version 4 as a replacement - consequently I had less that 24 hours data on the system I mistakenly installed cmon on. I am

Re: [weewx-development] Re: V4.0.0b4 is up

Appreciate you have managed to disable cmon but for future reference manual uninstallation of an extension is fairly easy once you know what to look for. There is no simple 'find this and do this', the amount of work involved and where to work depends on the extension. A skin/report based

Re: [weewx-development] Re: V4.0.0b4 is up

On Monday, December 16, 2019 at 1:42:58 PM UTC-8, Ralph Underwood wrote: > > I commented out various cmon stuff in weewx.conf and have whew running > again. > > > HA - I'm not the only person that Google is auto-correcting 'weewx' to be 'whew' on ! You could 'try' to edit cmon to make it

Re: [weewx-development] Re: V4.0.0b4 is up

I commented out various cmon stuff in weewx.conf and have whew running again. Thanks, Ralph On Monday, December 16, 2019 at 1:29:23 PM UTC-8, Ralph Underwood wrote: > > OK. I tried doing a wee-extension uninstall with no success. Any hints on > how/where to remove it? May be simpler to

Re: [weewx-development] Re: V4.0.0b4 is up

OK. I tried doing a wee-extension uninstall with no success. Any hints on how/where to remove it? May be simpler to just start with another install of WeeWx. I did manage to update my program that reads the mqtt data and write to file pile.txt without those 'b's. On Monday, December

Re: [weewx-development] Re: V4.0.0b4 is up

cmon has not been ported to Python 3. On Mon, Dec 16, 2019 at 2:17 PM Ralph Underwood wrote: > I tried to install the cmon extension with the version 4 and got this > error. > > I had just restarted my tail of the log so I hope this is enough. > > Dec 16 13:02:16 JV-Wx weewx[27906] CRITICAL

Re: [weewx-development] Re: V4.0.0b4 is up

I tried to install the cmon extension with the version 4 and got this error. I had just restarted my tail of the log so I hope this is enough. Dec 16 13:02:16 JV-Wx weewx[27906] CRITICAL weewx.engine: obj = weeutil.weeutil.get_object(svc)(self,config_dict) Dec 16 13:02:16 JV-Wx

Re: [weewx-development] Re: V4.0.0b4 is up

Thanks Tom. WeeWx appears to be running - I'm getting output to home/weewx/public_html/index.html . Now to tackle the damn 'b's, should keep me busy for a few hours. I plan on waiting a bit before adding cmom, I have been having trouble with the old system stopping, I suspect because of a

Re: [weewx-development] Re: V4.0.0b4 is up

Silly me. I forgot to save the characters to the buffer! Try the attached. Those damn 'b's are because you are printing bytes or bytearrays, not strings. If you want to get rid of them, you need to convert to a string (which is unicode under Python3). This illustrates: >>> print(b'abc) b'abc'

Re: [weewx-development] Re: V4.0.0b4 is up

This is the result with latest ultimeter.py and debug_serial = 1 Dec 14 10:06:36 JV-Wx weewx[12591] INFO weewx.engine: retrying... Dec 14 10:06:36 JV-Wx weewx[12591] INFO weewx.engine: Using configuration file /home/weewx/weewx.conf Dec 14 10:06:36 JV-Wx weewx[12591] DEBUG weewx.engine: Debug

Re: [weewx-development] Re: V4.0.0b4 is up

I think this problem may be related to this thread , which was never resolved. Hopefully, we'll get it this time. Try this version, but before you do, not only set debug=1 at the top of weewx.conf, but also set debug_serial

Re: [weewx-development] Re: V4.0.0b4 is up

This is the result with the new driver. I let it go several times with same result. Dec 13 18:23:16 JV-Wx weewx[3658] INFO weewx.engine: retrying... Dec 13 18:23:16 JV-Wx weewx[3658] INFO weewx.engine: Using configuration file /home/weewx/weewx.conf Dec 13 18:23:16 JV-Wx weewx[3658] DEBUG

Re: [weewx-development] Re: V4.0.0b4 is up

On Thursday, December 12, 2019 at 8:13:30 PM UTC-8, gjr80 wrote: > > As far as I am aware development versions are generally distributed as > setup.py installs only and not as a (deb or rpm) package. For setup.py > installs you need to manually install the service files. Refer to the Run >

Re: [weewx-development] Re: V4.0.0b4 is up

As far as I am aware development versions are generally distributed as setup.py installs only and not as a (deb or rpm) package. For setup.py installs you need to manually install the service files. Refer to the Run section of the setup.py install instructions http://weewx.com/docs/setup.htm

Re: [weewx-development] Re: V4.0.0b4 is up

It seems a simple path setup, but it beats me... root@RPi4:/etc/systemd# systemctl start weewx Failed to start weewx.service: Unit weewx.service not found. Must declare path somewhere? Shouldn't install take care of that? -- You received this message because you are subscribed to the Google

Re: [weewx-development] Re: V4.0.0b4 is up

On Thursday, December 12, 2019 at 12:44:20 PM UTC-8, Xant wrote: > > root@RPi4:/etc/weewx# service weewx start > Failed to start weewx.service: Unit weewx.service not found. > > I'd try "systemctl start weewx" and use full systemd syntax, just in case. -- You received this message because you

Re: [weewx-development] Re: V4.0.0b4 is up

On Thursday, December 12, 2019 at 12:44:20 PM UTC-8, Xant wrote: > > Vince > It seems you using WFlow and running. Any to patch? > > > Yes - you need to run it through 2to3 if you want to use python3. https://github.com/captain-coredump/weatherflow-udp/pull/9 Diffs are at

Re: [weewx-development] Re: V4.0.0b4 is up

Please, disregard previous weewx.conf (mistaken upload). 1) Starting as: "service weewx start" (RPi4, python 2x) 2) Weewx.conf re-attached. Thx, X -- You received this message because you are subscribed to the Google Groups "weewx-development" group. To unsubscribe from this group and stop

Re: [weewx-development] Re: V4.0.0b4 is up

weewx.service is the systemd configuration file. You'll find it under util/systemd. It's used when starting weewx as a daemon. One other thing: the weewx.conf file you enclosed is a V3.9.2 file. Are you sure you're running v4.0.0? -tk On Thu, Dec 12, 2019 at 1:44 PM Xant wrote: > > Starting

Re: [weewx-development] Re: V4.0.0b4 is up

Starting from scratch (again). PWS is WeatherFlow. 1) RPi3 WeeWX release w Bskin - all is well and running 2) RPi4 WeeWX - python 2x for now; got the following error msg: root@RPi4:/etc/weewx# service weewx start Failed to start weewx.service: Unit weewx.service not found. Only place I see

Re: [weewx-development] Re: V4.0.0b4 is up

On Friday, December 6, 2019 at 2:12:40 PM UTC-8, Tom Keffer wrote: > > Were you using Python 3? If so, the problem is almost surely because the > Belchertown skin has not been ported yet. > >> >> fyi - the development branch for Belchertown works nicely on python3, but changing multiple things

Re: [weewx-development] Re: V4.0.0b4 is up

I don't think so. It's definitely a problem. Fixed in commit 55f9cb3 . Uploaded V4.0.0b5 . -tk On Fri, Dec 6, 2019 at 7:17 AM Armando Esteves wrote: > Tom > >

Re: [weewx-development] Re: V4.0.0b4 is up

Tom Hold-on on this issue, as it might not be WeeWX/DB related, but Rpi version/OS conflict (https://groups.google.com/d/msg/weewx-development/ZXChMjAGUjM/RGlnAUzYBAAJ). Will inform back upon new developments and when ready for further b-Tests. X -- You received this message because you are

Re: [weewx-development] Re: V4.0.0b4 is up

A... thank you Thomas. Your note is a relief, as didn't want to make a "noobie" mistake in the Dev League (debated much prior to posting). That said, I'm your new "b-Tester" and glad to help for any. To note, now handling two SD Rpi cards: 1. Functional 3.9.2 2. "half-way" v4 (open

Re: [weewx-development] Re: V4.0.0b4 is up

You're doing things right! It's just that how a schema is specified has changed in V4.0. However, the intention was to make it backwards compatible, which I obviously failed at. Let me think about this case and I'll get back to you. -tk On Thu, Dec 5, 2019 at 6:01 PM Armando Esteves wrote: >

Re: [weewx-development] Re: V4.0.0b4 is up

Xant here, trying to jump into the "Big Boys league" (aka, development) :P Since jumping to next up, went to duplicate and upgrade everything: - Rpi3 to Rpi4 - check! - Bskin 1.1b7 to Bskin 1.1b8 - check! - WeeWX 3.9.2 to WeeWX 4.0.0b4 -error (ufff...) NOT reportingas a bug, but

Re: [weewx-development] Re: V4.0.0b4 is up

Fixed in commit d60c154 . -tk On Wed, Nov 27, 2019 at 9:25 AM Hartmut Schweidler wrote: > Hallo Tom > > the driver fousb.py at line addr1 = (address // 256) & 0xff not addr1 = > (address / 256) & 0xff > > the

Re: [weewx-development] Re: V4.0.0b4 is up

Running with SDR root@weewx-01:/home/weewx/weewx-4.0.0b4# uname -a && cat /etc/debian_version Linux weewx-01 4.19.0-6-amd64 #1 SMP Debian 4.19.67-2+deb10u1 (2019-09-20) x86_64 GNU/Linux 10.2 Nov 27 15:04:02 weewx-01 weewx[12624] INFO weewx.engine: Starting up weewx version 4.0.0b4 Nov 27

Re: [weewx-development] Re: V4.0.0b4 is up

Thanks, Hartmut! Alternatively, how about addr1 = (address >> 8) & 0xff which makes the bit arithmetic more explicit. -tk On Wed, Nov 27, 2019 at 9:25 AM Hartmut Schweidler wrote: > Hallo Tom > > the driver fousb.py at line addr1 = (address // 256) & 0xff not addr1 = > (address / 256)

[weewx-development] Re: V4.0.0b4 is up

On Tuesday, November 26, 2019 at 5:24:07 PM UTC-8, Tom Keffer wrote: > > What we really need is testing of the drivers, particularly under Python > 3. If you have something other than a Vantage, please install and check it > out! > > Tests fine on a pi4 with current Raspbian using: -