[weewx-user] Re: Error trying to upgrade from 5.1b4 to 5.1 on Fedora 40

[Mark Jenks]

Okay, even though it thought 5.1 is the latest version, I could find 
5.1.0-2, and install that one.  Hopefully it stays out of the Beta ones 
now, until I need to go back.

# dnf search --showduplicates weewx
Last metadata expiration check: 4:06:56 ago on Sun 28 Jul 2024 03:09:53 PM 
CDT.
= Name Exactly Matched: weewx 
==
weewx-5.1.0b4-1.el9.noarch : weather software
weewx-5.0.0-1.el9.noarch : weather software
weewx-5.0.1-1.el9.noarch : weather software
weewx-5.0.1-2.el9.noarch : weather software
weewx-5.0.1-3.el9.noarch : weather software
weewx-5.0.2-1.el9.noarch : weather software
weewx-5.1.0-1.el9.noarch : weather software
weewx-5.1.0-2.el9.noarch : weather software

# dnf install weewx-5.1.0-2.el9.noarch
On Sunday, July 28, 2024 at 11:34:46 AM UTC-5 vince wrote:

> el40 ?   I suspect you have an error in your repo.d file.
>
> Look at the note on https://www.weewx.com/docs/5.1/quickstarts/redhat/
>
> On Sunday, July 28, 2024 at 8:44:50 AM UTC-7 Mark Jenks wrote:
>
>> Installed it back with Fedora 38, but have since gone to 40.
>> Changed the repo.d from weewx-test to the normal repo.d.
>>
>> Getting this error while trying to do an upgrade.  Seems there is no el40 
>> yet.
>>
>> Thanks!
>>
>> -Mark
>>
>> Errors during downloading metadata for repository 'weewx':
>>   - Status code: 404 for 
>> http://weewx.com/yum/weewx/el40/repodata/repomd.xml (IP: 
>> 2600:1f14:287:7600:4a94:1d06:d3ae:db92)
>> Error: Failed to download metadata for repo 'weewx': Cannot download 
>> repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried
>>
>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/3e7469ff-c643-44ae-aa87-9451c3a5cadcn%40googlegroups.com.

[weewx-user] Re: Error trying to upgrade from 5.1b4 to 5.1 on Fedora 40

[Mark Jenks]

Okay, looks like might need a Fedora page out here.  The redhat releases 
don't align with the fedora ones.Fedora 40, is still Redhat EL9.

So, I fixed the repo file to el9, and it looks like it can see it. 

But 5.1b4 is what it sees and says it's up to date, even though 5.1 (non 
beta) is the latest.   I'll look into this later.


On Sunday, July 28, 2024 at 11:34:46 AM UTC-5 vince wrote:

> el40 ?   I suspect you have an error in your repo.d file.
>
> Look at the note on https://www.weewx.com/docs/5.1/quickstarts/redhat/
>
> On Sunday, July 28, 2024 at 8:44:50 AM UTC-7 Mark Jenks wrote:
>
>> Installed it back with Fedora 38, but have since gone to 40.
>> Changed the repo.d from weewx-test to the normal repo.d.
>>
>> Getting this error while trying to do an upgrade.  Seems there is no el40 
>> yet.
>>
>> Thanks!
>>
>> -Mark
>>
>> Errors during downloading metadata for repository 'weewx':
>>   - Status code: 404 for 
>> http://weewx.com/yum/weewx/el40/repodata/repomd.xml (IP: 
>> 2600:1f14:287:7600:4a94:1d06:d3ae:db92)
>> Error: Failed to download metadata for repo 'weewx': Cannot download 
>> repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried
>>
>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/27c2788d-86ff-428a-b918-19b983d5e0e7n%40googlegroups.com.

[weewx-user] Re: Error trying to upgrade from 5.1b4 to 5.1 on Fedora 40

[Mark Jenks]

# more weewx.repo
[weewx]
name=weewx
baseurl=http://weewx.com/yum/weewx/el$releasever
enabled=1
gpgcheck=1

# cat /etc/redhat-release
Fedora release 40 (Forty)


On Sunday, July 28, 2024 at 11:34:46 AM UTC-5 vince wrote:

> el40 ?   I suspect you have an error in your repo.d file.
>
> Look at the note on https://www.weewx.com/docs/5.1/quickstarts/redhat/
>
> On Sunday, July 28, 2024 at 8:44:50 AM UTC-7 Mark Jenks wrote:
>
>> Installed it back with Fedora 38, but have since gone to 40.
>> Changed the repo.d from weewx-test to the normal repo.d.
>>
>> Getting this error while trying to do an upgrade.  Seems there is no el40 
>> yet.
>>
>> Thanks!
>>
>> -Mark
>>
>> Errors during downloading metadata for repository 'weewx':
>>   - Status code: 404 for 
>> http://weewx.com/yum/weewx/el40/repodata/repomd.xml (IP: 
>> 2600:1f14:287:7600:4a94:1d06:d3ae:db92)
>> Error: Failed to download metadata for repo 'weewx': Cannot download 
>> repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried
>>
>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/d2fa72f6-b0c2-4016-bfcc-3ed14e64078bn%40googlegroups.com.

[weewx-user] Error trying to upgrade from 5.1b4 to 5.1 on Fedora 40

[Mark Jenks]

Installed it back with Fedora 38, but have since gone to 40.
Changed the repo.d from weewx-test to the normal repo.d.

Getting this error while trying to do an upgrade.  Seems there is no el40 
yet.

Thanks!

-Mark

Errors during downloading metadata for repository 'weewx':
  - Status code: 404 for 
http://weewx.com/yum/weewx/el40/repodata/repomd.xml (IP: 
2600:1f14:287:7600:4a94:1d06:d3ae:db92)
Error: Failed to download metadata for repo 'weewx': Cannot download 
repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/2e9a7cf2-7662-4ec6-8219-d3a90e28abe0n%40googlegroups.com.

[weewx-user] Re: Belchertown and MQTT configuration error

[Mark Jenks]

Make sure MQTT is running correctly. You can test it via CLI. This page 
goes into configuring a cert, you can stop reading at that point.

https://medium.com/gravio-edge-iot-platform/how-to-set-up-a-mosquitto-mqtt-broker-securely-using-client-certificates-82b2aaaef9c8


On Thursday, July 25, 2024 at 10:27:54 PM UTC-5 M&M wrote:

> Also I tried commenting out all of the MQTT lines in weewx.conf so that I 
> could get the service running again but it isn't running at all.  Giving me 
> the same error as I posted above.
>
> On Thursday, July 25, 2024 at 11:11:15 PM UTC-4 M&M wrote:
>
>> I'm getting closer.  Mosquito service is running but weewx gives me the 
>> follow error in journalctl:
>>
>> Jul 25 22:59:55 raspberrypi weewxd[25852]: INFO __main__: Terminating 
>> weewx version 5.0.2
>> Jul 25 22:59:55 raspberrypi systemd[1]: weewx.service: Succeeded.
>> Jul 25 22:59:55 raspberrypi systemd[1]: Stopped WeeWX.
>> Jul 25 22:59:55 raspberrypi systemd[1]: weewx.service: Consumed 3h 44min 
>> 13.462s CPU time.
>> Jul 25 23:00:51 raspberrypi systemd[1]: Started WeeWX.
>> Jul 25 23:00:53 raspberrypi weewxd[28347]: INFO __main__: Initializing 
>> weewxd version 5.0.2
>> Jul 25 23:00:53 raspberrypi weewxd[28347]: INFO __main__: Command line: 
>> /usr/share/weewx/weewxd.py /etc/weewx/weewx.conf
>> Jul 25 23:00:53 raspberrypi weewxd[28347]: Traceback (most recent call 
>> last):
>> Jul 25 23:00:53 raspberrypi weewxd[28347]:   File 
>> "/usr/share/weewx/weewxd.py", line 265, in 
>> Jul 25 23:00:53 raspberrypi weewxd[28347]: main()
>> Jul 25 23:00:53 raspberrypi weewxd[28347]:   File 
>> "/usr/share/weewx/weewxd.py", line 107, in main
>> Jul 25 23:00:53 raspberrypi weewxd[28347]: weewx_root, user_module = 
>> weeutil.startup.initialize(config_dict)
>> Jul 25 23:00:53 raspberrypi weewxd[28347]:   File 
>> "/usr/share/weewx/weeutil/startup.py", line 67, in initialize
>> Jul 25 23:00:53 raspberrypi weewxd[28347]: 
>> importlib.import_module('user.extensions')
>> Jul 25 23:00:53 raspberrypi weewxd[28347]:   File 
>> "/usr/lib/python3.9/importlib/__init__.py", line 127, in import_module
>> Jul 25 23:00:53 raspberrypi weewxd[28347]: return 
>> _bootstrap._gcd_import(name[level:], package, level)
>> Jul 25 23:00:53 raspberrypi weewxd[28347]:   File "> importlib._bootstrap>", line 1030, in _gcd_import
>> Jul 25 23:00:53 raspberrypi weewxd[28347]:   File "> importlib._bootstrap>", line 1007, in _find_and_load
>> Jul 25 23:00:53 raspberrypi weewxd[28347]:   File "> importlib._bootstrap>", line 986, in _find_and_load_unlocked
>> Jul 25 23:00:53 raspberrypi weewxd[28347]:   File "> importlib._bootstrap>", line 680, in _load_unlocked
>> Jul 25 23:00:53 raspberrypi weewxd[28347]:   File "> importlib._bootstrap_external>", line 790, in exec_module
>> Jul 25 23:00:53 raspberrypi weewxd[28347]:   File "> importlib._bootstrap>", line 228, in _call_with_frames_removed
>> Jul 25 23:00:53 raspberrypi weewxd[28347]:   File 
>> "/etc/weewx/bin/user/extensions.py", line 18, in 
>> Jul 25 23:00:53 raspberrypi weewxd[28347]: 
>> locale.setlocale(locale.LC_ALL, '')
>> Jul 25 23:00:53 raspberrypi weewxd[28347]:   File 
>> "/usr/lib/python3.9/locale.py", line 610, in setlocale
>> Jul 25 23:00:53 raspberrypi weewxd[28347]: return 
>> _setlocale(category, locale)
>> Jul 25 23:00:53 raspberrypi weewxd[28347]: locale.Error: unsupported 
>> locale setting
>> Jul 25 23:00:53 raspberrypi systemd[1]: weewx.service: Main process 
>> exited, code=exited, status=1/FAILURE
>> Jul 25 23:00:53 raspberrypi systemd[1]: weewx.service: Failed with result 
>> 'exit-code'.
>> Jul 25 23:00:53 raspberrypi systemd[1]: weewx.service: Consumed 2.050s 
>> CPU time.
>>
>> On Thursday, July 25, 2024 at 1:47:21 PM UTC-4 vince wrote:
>>
>>> Pat's docs are authoritative for Belchertown and the MQTT stuff looks ok 
>>> to me.  Just follow that.
>>>
>>> https://github.com/weewx/weewx/wiki/mqtt has Tom's instructions for 
>>> installing the MQTT extension.  You can check it at least minimally by 
>>> running "weectl extension list" and it should show up in the list of 
>>> installed extensions.
>>>
>>> Your config file stuff for weewx that you posted looked ok to me.
>>>
>>> On Thursday, July 25, 2024 at 9:54:13 AM UTC-7 M&M wrote:
>>>
 That is correct that I have the MQTT installed as an extension for 
 weewx which is running on the pi.  I checked for a mqtt.service and I'm 
 not 
 seeing one on there.  I'm also not seeing a mosquitto_sub or pub installed 
 so I think I must have missed anothe page to get this installed and 
 working.  From searching around right now, it looks like I need to follow 
 this page:  https://obrienlabs.net/how-to-setup-your-own-mqtt-broker/

 I'm hoping to get this on a website that doesn't cost anything but one 
 step at a time.

 Am I on the right track?  

 On Wednesday, July 24, 2024 at 10:50:45 PM UTC-4 vince wrote:

> Connection refused generally means th

Re: [weewx-user] Re: can't seem to find epel-release for fedora fc38

[Mark Jenks]

That's where I am now.  Was fc38 until last night and now on fc40.   5.1 
beta is working great.

On Saturday, June 15, 2024 at 8:49:23 PM UTC-5 Tom Keffer wrote:

> Would you be willing to try the V5.1 beta? More information 
> .
>
> On Sat, Jun 15, 2024 at 6:42 PM Jonathan Ryshpan  
> wrote:
>
>> On Sun, 2024-02-11 at 09:41 -0800, matthew wall wrote:
>>
>> the epel-release dependency has been removed for the redhat el8 and el9 
>> packages.  this will appear in the next weewx release (probably 5.0.3, but 
>> perhaps 5.1).
>> meanwhile, you can tell rpm to ignore that dependency, since you already 
>> have installed the prereqs that weewx actually uses.
>>
>> rpm --nodeps
>>
>> for yum/dnf, you could try the skip broken option
>> yum --skip-broken
>>
>>
>> It looks like the problem remains. I am trying to upgrade weewx to 
>> prepare for installing Fedora-40, and get the following errors (slightly 
>> edited).. It may be a good idea to download the rpm and install it using 
>> rpm --nodeps weewx
>> but I am suspicious, since python3-importlib-resources is missing as well 
>> as epel-release, and I don't want to break my weather station. 
>>
>> jonrysh@OaklandWeather:~$ sudo dnf upgrade --refresh
>> [sudo] password for jonrysh: 
>> Fedora 39 - x86_64 71 kB/s | 30 kB 00:00 
>> Fedora 39 openh264 (From Cisco) - x86_64 8.9 kB/s | 989 B 00:00 
>> Fedora 39 - x86_64 - Updates 203 kB/s | 26 kB 00:00 
>> google-chrome 7.8 kB/s | 1.3 kB 00:00 
>> weewx 48 kB/s | 3.0 kB 00:00 
>> Dependencies resolved.
>>
>> Problem: cannot install the best update candidate for package 
>> weewx-4.10.2-1.el8.noarch
>> - nothing provides epel-release needed by weewx-5.0.2-1.el8.noarch from 
>> weewx
>> - nothing provides python3-importlib-resources needed by 
>> weewx-5.0.2-1.el8.noarch from weewx
>>
>> =
>> Package Architecture Version Repository Size
>>
>> 
>> Skipping packages with broken dependencies:
>> weewx noarch 5.0.2-1.el8 weewx 1.2 M
>>
>> Transaction Summary
>>
>> ===
>> Skip 1 Package
>>
>> Nothing to do.
>> Complete!
>> jonrysh@OaklandWeather:~$ sudo dnf upgrade --skip-broken 
>> [sudo] password for jonrysh: 
>> Last metadata expiration check: 0:23:39 ago on Sat 15 Jun 2024 04:19:32 
>> PM PDT.
>> Dependencies resolved.
>>
>> Problem: cannot install the best update candidate for package 
>> weewx-4.10.2-1.el8.noarch
>> - nothing provides epel-release needed by weewx-5.0.2-1.el8.noarch from 
>> weewx
>> - nothing provides python3-importlib-resources needed by 
>> weewx-5.0.2-1.el8.noarch from weewx
>>
>> ==
>> Package Architecture Version Repository Size
>>
>> ==
>> Skipping packages with broken dependencies:
>> weewx noarch 5.0.2-1.el8 weewx 1.2 M
>>
>> Transaction Summary
>>
>> ===
>> Skip 1 Package
>>
>> Nothing to do.
>> Complete!
>>
>> -- 
>>
>> Sincerely Jonathan Ryshpan 
>>
>>  Fiat justitia, ruant coelis!
>>
>> -- 
>> 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+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/f59606c02cbf1e3482b13ab412daf07cd986362a.camel%40pacbell.net
>>  
>> 
>> .
>>
>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/aaa61747-f530-4972-8d5b-6f009b2103can%40googlegroups.com.

Re: [weewx-user] Belchertown not running under Ubuntu 24.04

[Mark Jenks]

I just got this error after updating to Fedora 40 last night.   Updating 
belchertown.py from the github fixed it for me.

-Mark

On Saturday, June 22, 2024 at 10:23:33 AM UTC-5 MaKi68 wrote:

> I've seen, that belchertown.py was changed yesterday. I'll try ;).
>
> MaKi68 schrieb am Samstag, 22. Juni 2024 um 16:48:13 UTC+2:
>
>> Thanks for your reply.
>> I try to downgrade Python.
>>
>> Tom Keffer schrieb am Samstag, 22. Juni 2024 um 16:44:34 UTC+2:
>>
>>> locale.format() has been deprecated since Python 3.7, and was removed in 
>>> Python 3.12. It has been replaced with local.format_string().
>>>
>>> I believe that there was a pull request submitted to the Belchertown 
>>> repository to fix this. I don't know if Pat has done a new release to 
>>> reflect the fix. 
>>>
>>> Alternatively, you could downgrade your version of Python.
>>>
>>> On Sat, Jun 22, 2024 at 7:11 AM MaKi68  wrote:
>>>
 Hello,
 I installed weewx 5.02 with the Belchertown skin on Ubuntu 24.04.
 I installed weewx in Debian and pip as a test.
 Unfortunately, both versions produce an error message

 Debian:
 2024-06-22T14:52:16.564778+02:00 weewx-ubuntu weectl[11523]: INFO 
 user.belchertown: version 1.3.1
 2024-06-22T14:52:16.574267+02:00 weewx-ubuntu weectl[11523]: ERROR 
 weewx.reportengine: Caught unrecoverable exception in generator 
 'weewx.cheetahgenerator.CheetahGenerator'
 2024-06-22T14:52:16.574381+02:00 weewx-ubuntu weectl[11523]: ERROR 
 weewx.reportengine:   module 'locale' has no attribute 'format'
 2024-06-22T14:52:16.579307+02:00 weewx-ubuntu weectl[11523]: ERROR 
 weewx.reportengine:   Traceback (most recent call last):
 2024-06-22T14:52:16.579411+02:00 weewx-ubuntu weectl[11523]: ERROR 
 weewx.reportengine: File 
 "/usr/share/weewx/weewx/reportengine.py", line 220, in run
 2024-06-22T14:52:16.579478+02:00 weewx-ubuntu weectl[11523]: ERROR 
 weewx.reportengine:   obj.start()
 2024-06-22T14:52:16.579544+02:00 weewx-ubuntu weectl[11523]: ERROR 
 weewx.reportengine: File 
 "/usr/share/weewx/weewx/reportengine.py", line 409, in start
 2024-06-22T14:52:16.579613+02:00 weewx-ubuntu weectl[11523]: ERROR 
 weewx.reportengine:   self.run()
 2024-06-22T14:52:16.579674+02:00 weewx-ubuntu weectl[11523]: ERROR 
 weewx.reportengine: File 
 "/usr/share/weewx/weewx/cheetahgenerator.py", line 166, in run
 2024-06-22T14:52:16.579748+02:00 weewx-ubuntu weectl[11523]: ERROR 
 weewx.reportengine:   ngen = 
 self.generate(gen_dict[section_name], section_name, self.gen_ts)
 2024-06-22T14:52:16.579821+02:00 weewx-ubuntu weectl[11523]: ERROR 
 weewx.reportengine:  
 
 2024-06-22T14:52:16.579893+02:00 weewx-ubuntu weectl[11523]: ERROR 
 weewx.reportengine: File 
 "/usr/share/weewx/weewx/cheetahgenerator.py", line 226, in generate
 2024-06-22T14:52:16.579981+02:00 weewx-ubuntu weectl[11523]: ERROR 
 weewx.reportengine:   ngen += 
 self.generate(section[subsection], subsection, gen_ts)
 2024-06-22T14:52:16.580055+02:00 weewx-ubuntu weectl[11523]: ERROR 
 weewx.reportengine:  
  ^^
 2024-06-22T14:52:16.580124+02:00 weewx-ubuntu weectl[11523]: ERROR 
 weewx.reportengine: File 
 "/usr/share/weewx/weewx/cheetahgenerator.py", line 226, in generate
 2024-06-22T14:52:16.580191+02:00 weewx-ubuntu weectl[11523]: ERROR 
 weewx.reportengine:   ngen += 
 self.generate(section[subsection], subsection, gen_ts)
 2024-06-22T14:52:16.580257+02:00 weewx-ubuntu weectl[11523]: ERROR 
 weewx.reportengine:  
  ^^
 2024-06-22T14:52:16.580323+02:00 weewx-ubuntu weectl[11523]: ERROR 
 weewx.reportengine: File 
 "/usr/share/weewx/weewx/cheetahgenerator.py", line 309, in generate
 2024-06-22T14:52:16.580394+02:00 weewx-ubuntu weectl[11523]: ERROR 
 weewx.reportengine:   searchList = 
 self._getSearchList(encoding, timespan,
 2024-06-22T14:52:16.580471+02:00 weewx-ubuntu weectl[11523]: ERROR 
 weewx.reportengine:    
 ^^^
 2024-06-22T14:52:16.580541+02:00 weewx-ubuntu weectl[11523]: ERROR 
 weewx.reportengine: File 
 "/usr/share/weewx/weewx/cheetahgenerator.py", line 401, in _getSearchList
 2024-06-22T14:52:16.580613+02:00 weewx-ubuntu weectl[11523]: ERROR 
 weewx.reportengine:   search_list += 
 obj.get_extension_list(timespan, db_lookup)
 2024-06-22T14:52:16.580682+02:

Re: IRe: [weewx-user] High CPU on 5.10

[Mark Jenks]

Yes, that was it.

On Thursday, May 30, 2024 at 12:56:18 AM UTC-5 Ian Millard wrote:

> Should the last command be: -
> weectl database calc-missing 
> Sent from my iPad.
>
> On 30 May 2024, at 03:28, Mark Jenks  wrote:
>
>  I ran this, and did the recalc-missing, and it seems to be running 
> better.   Except there is only one record in those tables.
>
>
>
> Not sure why that would cause that issue.
>
> weectl database add-column appTemp
> weectl database add-column cloudbase
> weectl database add-column visibility
> weectl database add-column windrun
> weectl database add-column cloud_cover
> weectl database add-column aqi
> weectl calc-missing
>
>
> On Tuesday, May 28, 2024 at 8:10:45 PM UTC-5 Mark Jenks wrote:
>
>> Seasons itself doesn't do it, and Belchertown with no settings on it is 
>> doing it.   
>> So, I'm adding those columns now and recalculating now.
>>
>>
>> On Tuesday, May 28, 2024 at 1:15:56 PM UTC-5 mh081...@gmail.com wrote:
>>
>>> I think this was the Problem with missing Database extended schema 
>>> object. I had the same problem as i upgraded from weewx 4 to 5. I solved 
>>> this with.
>>>
>>> weectl database add-column appTemp
>>> weectl database add-column cloudbase
>>> weectl database add-column visibility
>>> weectl database add-column windrun
>>> weectl database add-column cloud_cover
>>> weectl database add-column aqi
>>> weectl calc-missing
>>> weectl calc-missing appTemp
>>>
>>> vince schrieb am Dienstag, 28. Mai 2024 um 19:38:07 UTC+2:
>>>
>>>> The other test would be to disable belchertown, enable seasons, and see 
>>>> if that’s ok. That would check the db vs. the v5 calculated aka synthetic 
>>>> readings feature that slowed some folks down.
>>>>
>>>> On Tuesday, May 28, 2024 at 10:25:10 AM UTC-7 Tom Keffer wrote:
>>>>
>>>>> I thought of the appTemp angle, but those queries involve thousands of 
>>>>> small aggregate intervals, not one query over 4 years. 
>>>>>
>>>>> Still, it's worth a try.
>>>>>
>>>>> On Tue, May 28, 2024 at 9:07 AM vince  wrote:
>>>>>
>>>>>> You seem to be hacking randomly and praying.  I'd suggest deleting 
>>>>>> Belchertown at this point, verifying it is deleted, then add it back in. 
>>>>>>  
>>>>>> Do not customize it yet.  Just run the default setup, it works.  Really.
>>>>>>
>>>>>> My guess is you are missing the appTemp element in the db.  There are 
>>>>>> a bunch of threads on this re: Belchertown and v5 weewx.
>>>>>>
>>>>>> Check your mariadb schema and see if it is missing appTemp.  If you 
>>>>>> have the old wview-compatible db you'd have about 50 elements in it.  If 
>>>>>> you later switched to the v4 and above bigger wview-extended schema, 
>>>>>> you'd 
>>>>>> have 114 elements in it.  Sorry but I don't know the mariadb commands to 
>>>>>> count them nor check.
>>>>>>
>>>>>> For sqlite3 it would be:  'echo ".schema" | sqlite3 mydbname  | wc 
>>>>>> -l'
>>>>>>
>>>>>> On Tuesday, May 28, 2024 at 3:59:19 AM UTC-7 Mark Jenks wrote:
>>>>>>
>>>>>>> I removed the last two from skin.conf, and it still does the large 
>>>>>>> query.   I'll keep digging tonight.
>>>>>>>
>>>>>>> generator_list = weewx.cheetahgenerator.CheetahGenerator, 
>>>>>>> weewx.reportengine.CopyGenerator, 
>>>>>>> user.belchertown.HighchartsJsonGenerator
>>>>>>>
>>>>>>> On Monday, May 27, 2024 at 10:06:02 PM UTC-5 Mark Jenks wrote:
>>>>>>>
>>>>>>>> false alarm so far.  mqtt is tied to belchertown.So, seems to 
>>>>>>>> be belchertown like you suspected.   
>>>>>>>>
>>>>>>>> Digging more tomorrow.
>>>>>>>>
>>>>>>>>
>>>>>>>> On Monday, May 27, 2024 at 10:00:15 PM UTC-5 Mark Jenks wrote:
>>>>>>>>
>>>>>>>>> I just ripped mqtt out also.  I'll check it in the morning and see 
>>>>>>>>> if that makes a differ

IRe: [weewx-user] High CPU on 5.10

[Mark Jenks]

 I ran this, and did the recalc-missing, and it seems to be running 
better.   Except there is only one record in those tables.

Not sure why that would cause that issue.

weectl database add-column appTemp
weectl database add-column cloudbase
weectl database add-column visibility
weectl database add-column windrun
weectl database add-column cloud_cover
weectl database add-column aqi
weectl calc-missing


On Tuesday, May 28, 2024 at 8:10:45 PM UTC-5 Mark Jenks wrote:

> Seasons itself doesn't do it, and Belchertown with no settings on it is 
> doing it.   
> So, I'm adding those columns now and recalculating now.
>
>
> On Tuesday, May 28, 2024 at 1:15:56 PM UTC-5 mh081...@gmail.com wrote:
>
>> I think this was the Problem with missing Database extended schema 
>> object. I had the same problem as i upgraded from weewx 4 to 5. I solved 
>> this with.
>>
>> weectl database add-column appTemp
>> weectl database add-column cloudbase
>> weectl database add-column visibility
>> weectl database add-column windrun
>> weectl database add-column cloud_cover
>> weectl database add-column aqi
>> weectl calc-missing
>> weectl calc-missing appTemp
>>
>> vince schrieb am Dienstag, 28. Mai 2024 um 19:38:07 UTC+2:
>>
>>> The other test would be to disable belchertown, enable seasons, and see 
>>> if that’s ok. That would check the db vs. the v5 calculated aka synthetic 
>>> readings feature that slowed some folks down.
>>>
>>> On Tuesday, May 28, 2024 at 10:25:10 AM UTC-7 Tom Keffer wrote:
>>>
>>>> I thought of the appTemp angle, but those queries involve thousands of 
>>>> small aggregate intervals, not one query over 4 years. 
>>>>
>>>> Still, it's worth a try.
>>>>
>>>> On Tue, May 28, 2024 at 9:07 AM vince  wrote:
>>>>
>>>>> You seem to be hacking randomly and praying.  I'd suggest deleting 
>>>>> Belchertown at this point, verifying it is deleted, then add it back in.  
>>>>> Do not customize it yet.  Just run the default setup, it works.  Really.
>>>>>
>>>>> My guess is you are missing the appTemp element in the db.  There are 
>>>>> a bunch of threads on this re: Belchertown and v5 weewx.
>>>>>
>>>>> Check your mariadb schema and see if it is missing appTemp.  If you 
>>>>> have the old wview-compatible db you'd have about 50 elements in it.  If 
>>>>> you later switched to the v4 and above bigger wview-extended schema, 
>>>>> you'd 
>>>>> have 114 elements in it.  Sorry but I don't know the mariadb commands to 
>>>>> count them nor check.
>>>>>
>>>>> For sqlite3 it would be:  'echo ".schema" | sqlite3 mydbname  | wc -l'
>>>>>
>>>>> On Tuesday, May 28, 2024 at 3:59:19 AM UTC-7 Mark Jenks wrote:
>>>>>
>>>>>> I removed the last two from skin.conf, and it still does the large 
>>>>>> query.   I'll keep digging tonight.
>>>>>>
>>>>>> generator_list = weewx.cheetahgenerator.CheetahGenerator, 
>>>>>> weewx.reportengine.CopyGenerator, 
>>>>>> user.belchertown.HighchartsJsonGenerator
>>>>>>
>>>>>> On Monday, May 27, 2024 at 10:06:02 PM UTC-5 Mark Jenks wrote:
>>>>>>
>>>>>>> false alarm so far.  mqtt is tied to belchertown.So, seems to be 
>>>>>>> belchertown like you suspected.   
>>>>>>>
>>>>>>> Digging more tomorrow.
>>>>>>>
>>>>>>>
>>>>>>> On Monday, May 27, 2024 at 10:00:15 PM UTC-5 Mark Jenks wrote:
>>>>>>>
>>>>>>>> I just ripped mqtt out also.  I'll check it in the morning and see 
>>>>>>>> if that makes a difference.
>>>>>>>>
>>>>>>>>
>>>>>>>> On Monday, May 27, 2024 at 9:52:21 PM UTC-5 Mark Jenks wrote:
>>>>>>>>
>>>>>>>>> Bad news?  I uninstalled belchertown, and it's still hitting high 
>>>>>>>>> CPU on mariadb and python3.  This is the hit to the DB.
>>>>>>>>>
>>>>>>>>> SELECT 
>>>>>>>>> <http://phpmyadmin.mjenks.net/url.php?url=https://dev.mysql.com/doc/refman/8.0/en/select.html>
>>>>>>>>>  * FROM

Re: [weewx-user] High CPU on 5.10

[Mark Jenks]

Seasons itself doesn't do it, and Belchertown with no settings on it is 
doing it.   
So, I'm adding those columns now and recalculating now.


On Tuesday, May 28, 2024 at 1:15:56 PM UTC-5 mh081...@gmail.com wrote:

> I think this was the Problem with missing Database extended schema object. 
> I had the same problem as i upgraded from weewx 4 to 5. I solved this with.
>
> weectl database add-column appTemp
> weectl database add-column cloudbase
> weectl database add-column visibility
> weectl database add-column windrun
> weectl database add-column cloud_cover
> weectl database add-column aqi
> weectl calc-missing
> weectl calc-missing appTemp
>
> vince schrieb am Dienstag, 28. Mai 2024 um 19:38:07 UTC+2:
>
>> The other test would be to disable belchertown, enable seasons, and see 
>> if that’s ok. That would check the db vs. the v5 calculated aka synthetic 
>> readings feature that slowed some folks down.
>>
>> On Tuesday, May 28, 2024 at 10:25:10 AM UTC-7 Tom Keffer wrote:
>>
>>> I thought of the appTemp angle, but those queries involve thousands of 
>>> small aggregate intervals, not one query over 4 years. 
>>>
>>> Still, it's worth a try.
>>>
>>> On Tue, May 28, 2024 at 9:07 AM vince  wrote:
>>>
>>>> You seem to be hacking randomly and praying.  I'd suggest deleting 
>>>> Belchertown at this point, verifying it is deleted, then add it back in.  
>>>> Do not customize it yet.  Just run the default setup, it works.  Really.
>>>>
>>>> My guess is you are missing the appTemp element in the db.  There are a 
>>>> bunch of threads on this re: Belchertown and v5 weewx.
>>>>
>>>> Check your mariadb schema and see if it is missing appTemp.  If you 
>>>> have the old wview-compatible db you'd have about 50 elements in it.  If 
>>>> you later switched to the v4 and above bigger wview-extended schema, you'd 
>>>> have 114 elements in it.  Sorry but I don't know the mariadb commands to 
>>>> count them nor check.
>>>>
>>>> For sqlite3 it would be:  'echo ".schema" | sqlite3 mydbname  | wc -l'
>>>>
>>>> On Tuesday, May 28, 2024 at 3:59:19 AM UTC-7 Mark Jenks wrote:
>>>>
>>>>> I removed the last two from skin.conf, and it still does the large 
>>>>> query.   I'll keep digging tonight.
>>>>>
>>>>> generator_list = weewx.cheetahgenerator.CheetahGenerator, 
>>>>> weewx.reportengine.CopyGenerator, user.belchertown.HighchartsJsonGenerator
>>>>>
>>>>> On Monday, May 27, 2024 at 10:06:02 PM UTC-5 Mark Jenks wrote:
>>>>>
>>>>>> false alarm so far.  mqtt is tied to belchertown.So, seems to be 
>>>>>> belchertown like you suspected.   
>>>>>>
>>>>>> Digging more tomorrow.
>>>>>>
>>>>>>
>>>>>> On Monday, May 27, 2024 at 10:00:15 PM UTC-5 Mark Jenks wrote:
>>>>>>
>>>>>>> I just ripped mqtt out also.  I'll check it in the morning and see 
>>>>>>> if that makes a difference.
>>>>>>>
>>>>>>>
>>>>>>> On Monday, May 27, 2024 at 9:52:21 PM UTC-5 Mark Jenks wrote:
>>>>>>>
>>>>>>>> Bad news?  I uninstalled belchertown, and it's still hitting high 
>>>>>>>> CPU on mariadb and python3.  This is the hit to the DB.
>>>>>>>>
>>>>>>>> SELECT 
>>>>>>>> <http://phpmyadmin.mjenks.net/url.php?url=https://dev.mysql.com/doc/refman/8.0/en/select.html>
>>>>>>>>  * FROM archive WHERE dateTime > 1704088800 AND 
>>>>>>>> <http://phpmyadmin.mjenks.net/url.php?url=https://dev.mysql.com/doc/refman/8.0/en/logical-operators.html%23operator_and>
>>>>>>>>  dateTime <= 1735711200 ORDER BY dateTime ASC
>>>>>>>>
>>>>>>>>
>>>>>>>> On Monday, May 27, 2024 at 7:16:36 PM UTC-5 Tom Keffer wrote:
>>>>>>>>
>>>>>>>>> That query is asking for every single record over 4 years of data 
>>>>>>>>> --- about 400,000+ records with a 5 minute archive interval. That's 
>>>>>>>>> not the 
>>>>>>>>> use pattern when an xtype is causing the problem 
>>>>>&

Re: [weewx-user] High CPU on 5.10

[Mark Jenks]

Here is my Archive table;

localhost/weewx/ 
http://phpmyadmin.mjenks.net/index.php?route=/database/sql&db=weewx
Your SQL query has been executed successfully.

show columns from archive;



dateTime int(11) NO PRI NULL 
usUnits int(11) NO NULL 
interval int(11) NO NULL 
barometer double YES NULL 
pressure double YES NULL 
altimeter double YES NULL 
inTemp double YES NULL 
outTemp double YES NULL 
inHumidity double YES NULL 
outHumidity double YES NULL 
windSpeed double YES NULL 
windDir double YES NULL 
windGust double YES NULL 
windGustDir double YES NULL 
rainRate double YES NULL 
rain double YES NULL 
dewpoint double YES NULL 
windchill double YES NULL 
heatindex double YES NULL 
ET double YES NULL 
radiation double YES NULL 
UV double YES NULL 
extraTemp1 double YES NULL 
extraTemp2 double YES NULL 
extraTemp3 double YES NULL 
soilTemp1 double YES NULL 
soilTemp2 double YES NULL 
soilTemp3 double YES NULL 
soilTemp4 double YES NULL 
leafTemp1 double YES NULL 
leafTemp2 double YES NULL 
extraHumid1 double YES NULL 
extraHumid2 double YES NULL 
soilMoist1 double YES NULL 
soilMoist2 double YES NULL 
soilMoist3 double YES NULL 
soilMoist4 double YES NULL 
leafWet1 double YES NULL 
leafWet2 double YES NULL 
rxCheckPercent double YES NULL 
txBatteryStatus double YES NULL 
consBatteryVoltage double YES NULL 
hail double YES NULL 
hailRate double YES NULL 
heatingTemp double YES NULL 
heatingVoltage double YES NULL 
supplyVoltage double YES NULL 
referenceVoltage double YES NULL 
windBatteryStatus double YES NULL 
rainBatteryStatus double YES NULL 
outTempBatteryStatus double YES NULL 
inTempBatteryStatus double YES NULL 

On Tuesday, May 28, 2024 at 7:35:56 PM UTC-5 Mark Jenks wrote:

> Ripping out Belchertown completely.  I did it before, but didn't let it 
> sit for very long.Will see if the problem exists with Seasons.
>
>
> On Tuesday, May 28, 2024 at 1:15:56 PM UTC-5 mh081...@gmail.com wrote:
>
>> I think this was the Problem with missing Database extended schema 
>> object. I had the same problem as i upgraded from weewx 4 to 5. I solved 
>> this with.
>>
>> weectl database add-column appTemp
>> weectl database add-column cloudbase
>> weectl database add-column visibility
>> weectl database add-column windrun
>> weectl database add-column cloud_cover
>> weectl database add-column aqi
>> weectl calc-missing
>> weectl calc-missing appTemp
>>
>> vince schrieb am Dienstag, 28. Mai 2024 um 19:38:07 UTC+2:
>>
>>> The other test would be to disable belchertown, enable seasons, and see 
>>> if that’s ok. That would check the db vs. the v5 calculated aka synthetic 
>>> readings feature that slowed some folks down.
>>>
>>> On Tuesday, May 28, 2024 at 10:25:10 AM UTC-7 Tom Keffer wrote:
>>>
>>>> I thought of the appTemp angle, but those queries involve thousands of 
>>>> small aggregate intervals, not one query over 4 years. 
>>>>
>>>> Still, it's worth a try.
>>>>
>>>> On Tue, May 28, 2024 at 9:07 AM vince  wrote:
>>>>
>>>>> You seem to be hacking randomly and praying.  I'd suggest deleting 
>>>>> Belchertown at this point, verifying it is deleted, then add it back in.  
>>>>> Do not customize it yet.  Just run the default setup, it works.  Really.
>>>>>
>>>>> My guess is you are missing the appTemp element in the db.  There are 
>>>>> a bunch of threads on this re: Belchertown and v5 weewx.
>>>>>
>>>>> Check your mariadb schema and see if it is missing appTemp.  If you 
>>>>> have the old wview-compatible db you'd have about 50 elements in it.  If 
>>>>> you later switched to the v4 and above bigger wview-extended schema, 
>>>>> you'd 
>>>>> have 114 elements in it.  Sorry but I don't know the mariadb commands to 
>>>>> count them nor check.
>>>>>
>>>>> For sqlite3 it would be:  'echo ".schema" | sqlite3 mydbname  | wc -l'
>>>>>
>>>>> On Tuesday, May 28, 2024 at 3:59:19 AM UTC-7 Mark Jenks wrote:
>>>>>
>>>>>> I removed the last two from skin.conf, and it still does the large 
>>>>>> query.   I'll keep digging tonight.
>>>>>>
>>>>>> generator_list = weewx.cheetahgenerator.CheetahGenerator, 
>>>>>> weewx.reportengine.CopyGenerator, 
>>>>>> user.belchertown.HighchartsJsonGenerator
>>>>>>
>>>>>> On Monday, May 27, 2024 at 10:06:02 PM UTC-5 Mark Jenks wrote:
>>>>>>
>

Re: [weewx-user] High CPU on 5.10

[Mark Jenks]

Not sure what you think I am changing within Belchertown.  Other than MQTT, 
I'm just throwing in some settings to make it work.

   [[[Extras]]]
site_title = Jenks Weather Website
theme = dark
logo_image = http://weather.mjenks.net/weather.jpg
radar_marker = 1
forecast_enabled = 1
forecast_api_id = xc
forecast_api_secret = lx
about_page_header = About This Weather Station
footer_copyright_text = The Jenks Weather Website
footer_disclaimer_text = ""
facebook_enabled = 1
twitter_enabled = 1
googleAnalyticsId = "xxx"
social_share_html = http://weather.mjenks.net
twitter_text = Check out my website: Mark's Weather Conditions
twitter_owner = xxx
twitter_hashtags = "weewx #weather"
mqtt_websockets_enabled = 1
mqtt_websockets_host = 
mqtt_websockets_port = 9001
mqtt_websockets_ssl = 0
mqtt_websockets_topic = weather/weewx/loop
mqtt_websockets_username = "weather"
mqtt_websockets_password = ""

On Tuesday, May 28, 2024 at 11:07:01 AM UTC-5 vince wrote:

> You seem to be hacking randomly and praying.  I'd suggest deleting 
> Belchertown at this point, verifying it is deleted, then add it back in. 
>  Do not customize it yet.  Just run the default setup, it works.  Really.
>
> My guess is you are missing the appTemp element in the db.  There are a 
> bunch of threads on this re: Belchertown and v5 weewx.
>
> Check your mariadb schema and see if it is missing appTemp.  If you have 
> the old wview-compatible db you'd have about 50 elements in it.  If you 
> later switched to the v4 and above bigger wview-extended schema, you'd have 
> 114 elements in it.  Sorry but I don't know the mariadb commands to count 
> them nor check.
>
> For sqlite3 it would be:  'echo ".schema" | sqlite3 mydbname  | wc -l'
>
> On Tuesday, May 28, 2024 at 3:59:19 AM UTC-7 Mark Jenks wrote:
>
>> I removed the last two from skin.conf, and it still does the large 
>> query.   I'll keep digging tonight.
>>
>> generator_list = weewx.cheetahgenerator.CheetahGenerator, 
>> weewx.reportengine.CopyGenerator, user.belchertown.HighchartsJsonGenerator
>>
>> On Monday, May 27, 2024 at 10:06:02 PM UTC-5 Mark Jenks wrote:
>>
>>> false alarm so far.  mqtt is tied to belchertown.So, seems to be 
>>> belchertown like you suspected.   
>>>
>>> Digging more tomorrow.
>>>
>>>
>>> On Monday, May 27, 2024 at 10:00:15 PM UTC-5 Mark Jenks wrote:
>>>
>>>> I just ripped mqtt out also.  I'll check it in the morning and see if 
>>>> that makes a difference.
>>>>
>>>>
>>>> On Monday, May 27, 2024 at 9:52:21 PM UTC-5 Mark Jenks wrote:
>>>>
>>>>> Bad news?  I uninstalled belchertown, and it's still hitting high CPU 
>>>>> on mariadb and python3.  This is the hit to the DB.
>>>>>
>>>>> SELECT 
>>>>> <http://phpmyadmin.mjenks.net/url.php?url=https://dev.mysql.com/doc/refman/8.0/en/select.html>
>>>>>  * FROM archive WHERE dateTime > 1704088800 AND 
>>>>> <http://phpmyadmin.mjenks.net/url.php?url=https://dev.mysql.com/doc/refman/8.0/en/logical-operators.html%23operator_and>
>>>>>  dateTime <= 1735711200 ORDER BY dateTime ASC
>>>>>
>>>>>
>>>>> On Monday, May 27, 2024 at 7:16:36 PM UTC-5 Tom Keffer wrote:
>>>>>
>>>>>> That query is asking for every single record over 4 years of data --- 
>>>>>> about 400,000+ records with a 5 minute archive interval. That's not the 
>>>>>> use 
>>>>>> pattern when an xtype is causing the problem 
>>>>>> <https://github.com/weewx/weewx/wiki/XTypes-performance>.
>>>>>>
>>>>>> It's hard to imagine why the Belchertown skin would need data at that 
>>>>>> density. Try isolating the problem by shutting off the imagegenerator, 
>>>>>> then 
>>>>>> the cheetahgenerator (you can do that by modifying generator_list in 
>>>>>> skin.conf).
>>>>>>
>>>>>> Then once you know which one is the culprit, then start trimming 
>>>>>> their respective sections in skin.conf until you isolate the plot or tag 
>>>>>> that is causing th

Re: [weewx-user] High CPU on 5.10

[Mark Jenks]

Ripping out Belchertown completely.  I did it before, but didn't let it sit 
for very long.Will see if the problem exists with Seasons.


On Tuesday, May 28, 2024 at 1:15:56 PM UTC-5 mh081...@gmail.com wrote:

> I think this was the Problem with missing Database extended schema object. 
> I had the same problem as i upgraded from weewx 4 to 5. I solved this with.
>
> weectl database add-column appTemp
> weectl database add-column cloudbase
> weectl database add-column visibility
> weectl database add-column windrun
> weectl database add-column cloud_cover
> weectl database add-column aqi
> weectl calc-missing
> weectl calc-missing appTemp
>
> vince schrieb am Dienstag, 28. Mai 2024 um 19:38:07 UTC+2:
>
>> The other test would be to disable belchertown, enable seasons, and see 
>> if that’s ok. That would check the db vs. the v5 calculated aka synthetic 
>> readings feature that slowed some folks down.
>>
>> On Tuesday, May 28, 2024 at 10:25:10 AM UTC-7 Tom Keffer wrote:
>>
>>> I thought of the appTemp angle, but those queries involve thousands of 
>>> small aggregate intervals, not one query over 4 years. 
>>>
>>> Still, it's worth a try.
>>>
>>> On Tue, May 28, 2024 at 9:07 AM vince  wrote:
>>>
>>>> You seem to be hacking randomly and praying.  I'd suggest deleting 
>>>> Belchertown at this point, verifying it is deleted, then add it back in.  
>>>> Do not customize it yet.  Just run the default setup, it works.  Really.
>>>>
>>>> My guess is you are missing the appTemp element in the db.  There are a 
>>>> bunch of threads on this re: Belchertown and v5 weewx.
>>>>
>>>> Check your mariadb schema and see if it is missing appTemp.  If you 
>>>> have the old wview-compatible db you'd have about 50 elements in it.  If 
>>>> you later switched to the v4 and above bigger wview-extended schema, you'd 
>>>> have 114 elements in it.  Sorry but I don't know the mariadb commands to 
>>>> count them nor check.
>>>>
>>>> For sqlite3 it would be:  'echo ".schema" | sqlite3 mydbname  | wc -l'
>>>>
>>>> On Tuesday, May 28, 2024 at 3:59:19 AM UTC-7 Mark Jenks wrote:
>>>>
>>>>> I removed the last two from skin.conf, and it still does the large 
>>>>> query.   I'll keep digging tonight.
>>>>>
>>>>> generator_list = weewx.cheetahgenerator.CheetahGenerator, 
>>>>> weewx.reportengine.CopyGenerator, user.belchertown.HighchartsJsonGenerator
>>>>>
>>>>> On Monday, May 27, 2024 at 10:06:02 PM UTC-5 Mark Jenks wrote:
>>>>>
>>>>>> false alarm so far.  mqtt is tied to belchertown.So, seems to be 
>>>>>> belchertown like you suspected.   
>>>>>>
>>>>>> Digging more tomorrow.
>>>>>>
>>>>>>
>>>>>> On Monday, May 27, 2024 at 10:00:15 PM UTC-5 Mark Jenks wrote:
>>>>>>
>>>>>>> I just ripped mqtt out also.  I'll check it in the morning and see 
>>>>>>> if that makes a difference.
>>>>>>>
>>>>>>>
>>>>>>> On Monday, May 27, 2024 at 9:52:21 PM UTC-5 Mark Jenks wrote:
>>>>>>>
>>>>>>>> Bad news?  I uninstalled belchertown, and it's still hitting high 
>>>>>>>> CPU on mariadb and python3.  This is the hit to the DB.
>>>>>>>>
>>>>>>>> SELECT 
>>>>>>>> <http://phpmyadmin.mjenks.net/url.php?url=https://dev.mysql.com/doc/refman/8.0/en/select.html>
>>>>>>>>  * FROM archive WHERE dateTime > 1704088800 AND 
>>>>>>>> <http://phpmyadmin.mjenks.net/url.php?url=https://dev.mysql.com/doc/refman/8.0/en/logical-operators.html%23operator_and>
>>>>>>>>  dateTime <= 1735711200 ORDER BY dateTime ASC
>>>>>>>>
>>>>>>>>
>>>>>>>> On Monday, May 27, 2024 at 7:16:36 PM UTC-5 Tom Keffer wrote:
>>>>>>>>
>>>>>>>>> That query is asking for every single record over 4 years of data 
>>>>>>>>> --- about 400,000+ records with a 5 minute archive interval. That's 
>>>>>>>>> not the 
>>>>>>>>> use pattern when an xtype is causing the problem 
>>>>>>&g

Re: [weewx-user] High CPU on 5.10

[Mark Jenks]

I removed the last two from skin.conf, and it still does the large query.  
 I'll keep digging tonight.

generator_list = weewx.cheetahgenerator.CheetahGenerator, 
weewx.reportengine.CopyGenerator, user.belchertown.HighchartsJsonGenerator

On Monday, May 27, 2024 at 10:06:02 PM UTC-5 Mark Jenks wrote:

> false alarm so far.  mqtt is tied to belchertown.So, seems to be 
> belchertown like you suspected.   
>
> Digging more tomorrow.
>
>
> On Monday, May 27, 2024 at 10:00:15 PM UTC-5 Mark Jenks wrote:
>
>> I just ripped mqtt out also.  I'll check it in the morning and see if 
>> that makes a difference.
>>
>>
>> On Monday, May 27, 2024 at 9:52:21 PM UTC-5 Mark Jenks wrote:
>>
>>> Bad news?  I uninstalled belchertown, and it's still hitting high CPU on 
>>> mariadb and python3.  This is the hit to the DB.
>>>
>>> SELECT 
>>> <http://phpmyadmin.mjenks.net/url.php?url=https://dev.mysql.com/doc/refman/8.0/en/select.html>
>>>  * FROM archive WHERE dateTime > 1704088800 AND 
>>> <http://phpmyadmin.mjenks.net/url.php?url=https://dev.mysql.com/doc/refman/8.0/en/logical-operators.html%23operator_and>
>>>  dateTime <= 1735711200 ORDER BY dateTime ASC
>>>
>>>
>>> On Monday, May 27, 2024 at 7:16:36 PM UTC-5 Tom Keffer wrote:
>>>
>>>> That query is asking for every single record over 4 years of data --- 
>>>> about 400,000+ records with a 5 minute archive interval. That's not the 
>>>> use 
>>>> pattern when an xtype is causing the problem 
>>>> <https://github.com/weewx/weewx/wiki/XTypes-performance>.
>>>>
>>>> It's hard to imagine why the Belchertown skin would need data at that 
>>>> density. Try isolating the problem by shutting off the imagegenerator, 
>>>> then 
>>>> the cheetahgenerator (you can do that by modifying generator_list in 
>>>> skin.conf).
>>>>
>>>> Then once you know which one is the culprit, then start trimming their 
>>>> respective sections in skin.conf until you isolate the plot or tag that is 
>>>> causing the problem.
>>>>
>>>> On Mon, May 27, 2024 at 4:47 PM Mark Jenks  wrote:
>>>>
>>>>> Just built a new weewx on my Fedora 38 this morning, and attached it 
>>>>> to my mariadb.  It has 13 years worth of data in it.
>>>>>
>>>>> I am running Belchertown and mqtt, and installed Windy.  But I just 
>>>>> removed Windy to see if that was it, but still does it.  Python and/or 
>>>>> moriadb goes to 100% CPU.
>>>>> Mariadb says the high query during that time is:  SELECT * FROM 
>>>>> archive WHERE dateTime > 1320346500 AND dateTime <= 1716824400 ORDER BY 
>>>>> dateTime ASC
>>>>> But that makes no sense, since I can query my entire archive table 
>>>>> (select *) in about 3 seconds.
>>>>>
>>>>> Any thoughts on how to catch what is going on?   I could enable debug, 
>>>>> but hoping for a better way other that looking at a ton of logs.
>>>>>
>>>>> Thanks!
>>>>>
>>>>>
>>>>>
>>>>> -- 
>>>>> 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+...@googlegroups.com.
>>>>> To view this discussion on the web visit 
>>>>> https://groups.google.com/d/msgid/weewx-user/a882fb44-d36b-4bf4-8588-41199524b5f7n%40googlegroups.com
>>>>>  
>>>>> <https://groups.google.com/d/msgid/weewx-user/a882fb44-d36b-4bf4-8588-41199524b5f7n%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>>> .
>>>>>
>>>>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/a9b9a2b1-a032-4c86-9879-ea097589db91n%40googlegroups.com.

Re: [weewx-user] High CPU on 5.10

[Mark Jenks]

false alarm so far.  mqtt is tied to belchertown.So, seems to be 
belchertown like you suspected.   

Digging more tomorrow.


On Monday, May 27, 2024 at 10:00:15 PM UTC-5 Mark Jenks wrote:

> I just ripped mqtt out also.  I'll check it in the morning and see if that 
> makes a difference.
>
>
> On Monday, May 27, 2024 at 9:52:21 PM UTC-5 Mark Jenks wrote:
>
>> Bad news?  I uninstalled belchertown, and it's still hitting high CPU on 
>> mariadb and python3.  This is the hit to the DB.
>>
>> SELECT 
>> <http://phpmyadmin.mjenks.net/url.php?url=https://dev.mysql.com/doc/refman/8.0/en/select.html>
>>  * FROM archive WHERE dateTime > 1704088800 AND 
>> <http://phpmyadmin.mjenks.net/url.php?url=https://dev.mysql.com/doc/refman/8.0/en/logical-operators.html%23operator_and>
>>  dateTime <= 1735711200 ORDER BY dateTime ASC
>>
>>
>> On Monday, May 27, 2024 at 7:16:36 PM UTC-5 Tom Keffer wrote:
>>
>>> That query is asking for every single record over 4 years of data --- 
>>> about 400,000+ records with a 5 minute archive interval. That's not the use 
>>> pattern when an xtype is causing the problem 
>>> <https://github.com/weewx/weewx/wiki/XTypes-performance>.
>>>
>>> It's hard to imagine why the Belchertown skin would need data at that 
>>> density. Try isolating the problem by shutting off the imagegenerator, then 
>>> the cheetahgenerator (you can do that by modifying generator_list in 
>>> skin.conf).
>>>
>>> Then once you know which one is the culprit, then start trimming their 
>>> respective sections in skin.conf until you isolate the plot or tag that is 
>>> causing the problem.
>>>
>>> On Mon, May 27, 2024 at 4:47 PM Mark Jenks  wrote:
>>>
>>>> Just built a new weewx on my Fedora 38 this morning, and attached it to 
>>>> my mariadb.  It has 13 years worth of data in it.
>>>>
>>>> I am running Belchertown and mqtt, and installed Windy.  But I just 
>>>> removed Windy to see if that was it, but still does it.  Python and/or 
>>>> moriadb goes to 100% CPU.
>>>> Mariadb says the high query during that time is:  SELECT * FROM archive 
>>>> WHERE dateTime > 1320346500 AND dateTime <= 1716824400 ORDER BY dateTime 
>>>> ASC
>>>> But that makes no sense, since I can query my entire archive table 
>>>> (select *) in about 3 seconds.
>>>>
>>>> Any thoughts on how to catch what is going on?   I could enable debug, 
>>>> but hoping for a better way other that looking at a ton of logs.
>>>>
>>>> Thanks!
>>>>
>>>>
>>>>
>>>> -- 
>>>> 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+...@googlegroups.com.
>>>> To view this discussion on the web visit 
>>>> https://groups.google.com/d/msgid/weewx-user/a882fb44-d36b-4bf4-8588-41199524b5f7n%40googlegroups.com
>>>>  
>>>> <https://groups.google.com/d/msgid/weewx-user/a882fb44-d36b-4bf4-8588-41199524b5f7n%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>> .
>>>>
>>>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/f7dd0de8-fc41-4294-bb66-eada9b33eae2n%40googlegroups.com.

Re: [weewx-user] High CPU on 5.10

[Mark Jenks]

I just ripped mqtt out also.  I'll check it in the morning and see if that 
makes a difference.


On Monday, May 27, 2024 at 9:52:21 PM UTC-5 Mark Jenks wrote:

> Bad news?  I uninstalled belchertown, and it's still hitting high CPU on 
> mariadb and python3.  This is the hit to the DB.
>
> SELECT 
> <http://phpmyadmin.mjenks.net/url.php?url=https://dev.mysql.com/doc/refman/8.0/en/select.html>
>  * FROM archive WHERE dateTime > 1704088800 AND 
> <http://phpmyadmin.mjenks.net/url.php?url=https://dev.mysql.com/doc/refman/8.0/en/logical-operators.html%23operator_and>
>  dateTime <= 1735711200 ORDER BY dateTime ASC
>
>
> On Monday, May 27, 2024 at 7:16:36 PM UTC-5 Tom Keffer wrote:
>
>> That query is asking for every single record over 4 years of data --- 
>> about 400,000+ records with a 5 minute archive interval. That's not the use 
>> pattern when an xtype is causing the problem 
>> <https://github.com/weewx/weewx/wiki/XTypes-performance>.
>>
>> It's hard to imagine why the Belchertown skin would need data at that 
>> density. Try isolating the problem by shutting off the imagegenerator, then 
>> the cheetahgenerator (you can do that by modifying generator_list in 
>> skin.conf).
>>
>> Then once you know which one is the culprit, then start trimming their 
>> respective sections in skin.conf until you isolate the plot or tag that is 
>> causing the problem.
>>
>> On Mon, May 27, 2024 at 4:47 PM Mark Jenks  wrote:
>>
>>> Just built a new weewx on my Fedora 38 this morning, and attached it to 
>>> my mariadb.  It has 13 years worth of data in it.
>>>
>>> I am running Belchertown and mqtt, and installed Windy.  But I just 
>>> removed Windy to see if that was it, but still does it.  Python and/or 
>>> moriadb goes to 100% CPU.
>>> Mariadb says the high query during that time is:  SELECT * FROM archive 
>>> WHERE dateTime > 1320346500 AND dateTime <= 1716824400 ORDER BY dateTime ASC
>>> But that makes no sense, since I can query my entire archive table 
>>> (select *) in about 3 seconds.
>>>
>>> Any thoughts on how to catch what is going on?   I could enable debug, 
>>> but hoping for a better way other that looking at a ton of logs.
>>>
>>> Thanks!
>>>
>>>
>>>
>>> -- 
>>> 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+...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/weewx-user/a882fb44-d36b-4bf4-8588-41199524b5f7n%40googlegroups.com
>>>  
>>> <https://groups.google.com/d/msgid/weewx-user/a882fb44-d36b-4bf4-8588-41199524b5f7n%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>>
>>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/351e96df-94cb-489f-997c-eca60442430en%40googlegroups.com.

Re: [weewx-user] High CPU on 5.10

[Mark Jenks]

Bad news?  I uninstalled belchertown, and it's still hitting high CPU on 
mariadb and python3.  This is the hit to the DB.

SELECT 
<http://phpmyadmin.mjenks.net/url.php?url=https://dev.mysql.com/doc/refman/8.0/en/select.html>
 * FROM archive WHERE dateTime > 1704088800 AND 
<http://phpmyadmin.mjenks.net/url.php?url=https://dev.mysql.com/doc/refman/8.0/en/logical-operators.html%23operator_and>
 dateTime <= 1735711200 ORDER BY dateTime ASC


On Monday, May 27, 2024 at 7:16:36 PM UTC-5 Tom Keffer wrote:

> That query is asking for every single record over 4 years of data --- 
> about 400,000+ records with a 5 minute archive interval. That's not the use 
> pattern when an xtype is causing the problem 
> <https://github.com/weewx/weewx/wiki/XTypes-performance>.
>
> It's hard to imagine why the Belchertown skin would need data at that 
> density. Try isolating the problem by shutting off the imagegenerator, then 
> the cheetahgenerator (you can do that by modifying generator_list in 
> skin.conf).
>
> Then once you know which one is the culprit, then start trimming their 
> respective sections in skin.conf until you isolate the plot or tag that is 
> causing the problem.
>
> On Mon, May 27, 2024 at 4:47 PM Mark Jenks  wrote:
>
>> Just built a new weewx on my Fedora 38 this morning, and attached it to 
>> my mariadb.  It has 13 years worth of data in it.
>>
>> I am running Belchertown and mqtt, and installed Windy.  But I just 
>> removed Windy to see if that was it, but still does it.  Python and/or 
>> moriadb goes to 100% CPU.
>> Mariadb says the high query during that time is:  SELECT * FROM archive 
>> WHERE dateTime > 1320346500 AND dateTime <= 1716824400 ORDER BY dateTime ASC
>> But that makes no sense, since I can query my entire archive table 
>> (select *) in about 3 seconds.
>>
>> Any thoughts on how to catch what is going on?   I could enable debug, 
>> but hoping for a better way other that looking at a ton of logs.
>>
>> Thanks!
>>
>>
>>
>> -- 
>> 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+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/a882fb44-d36b-4bf4-8588-41199524b5f7n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/a882fb44-d36b-4bf4-8588-41199524b5f7n%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/cc69056f-bc36-4bf2-9cc3-54046420b8edn%40googlegroups.com.

Re: [weewx-user] 4.10 to 5.1 upgrade observations

[Mark Jenks]

See my new post..  :)

On Monday, May 27, 2024 at 12:24:33 PM UTC-5 vince wrote:

> Why do you think you need to update your database ?
>
> If your skins process in a reasonable couple/few second time without 
> errors, you're good as is.
>
> On Monday, May 27, 2024 at 8:20:57 AM UTC-7 Mark Jenks wrote:
>
>> Is there a schema change?  Or am I good with just running weectl database 
>> update?  I did that before I started it too, but didn't seem like it did 
>> much?
>>
>> -Mark
>>
>>
>> On Monday, May 27, 2024 at 9:08:12 AM UTC-5 Tom Keffer wrote:
>>
>>> Thanks for your report.
>>>
>>> The library pyephem is not available as a package under RH, so you have 
>>> to install it using pip. 
>>>
>>> The creation of a new database with suffix "_new" by "weectl database 
>>> reconfigure" is normal behavior. See the docs 
>>> <https://www.weewx.com/docs/5.1/utilities/weectl-database/#reconfigure-a-database>
>>> .
>>>
>>> On Mon, May 27, 2024 at 6:40 AM Mark Jenks  wrote:
>>>
>>>> I just did a fresh install of 5.1 from yum-test, and migrated 
>>>> everything from my 4.10 over to it.   Everything went as expected, except 
>>>> a 
>>>> few things I noticed.
>>>>
>>>> One thing to note, is to install the extensions, before start editing 
>>>> the data in them.  I'm running Belchertown, and coping the skins folder 
>>>> over first was a bad idea.  Just let them install and them tweak the 
>>>> folder 
>>>> as needed.
>>>>
>>>> Seems this is supposed to come with v5?  But did not for me.  I did a 
>>>> dnf install, which was never done before on my system.
>>>> INFO weewx.engine: 'pyephem' not detected, extended almanac data is not 
>>>> available
>>>>
>>>> Also, when I do a weectl database reconfigure, it doesn't use what is 
>>>> already in weewx.conf (like what configuring the hardware does), but wants 
>>>> to create a weewx_new database?  That threw me for a loop, because I was 
>>>> trying to make sure everything was right, before I started it up for the 
>>>> first time.
>>>>
>>>> Otherwise, all back up and running and can now archive my /home/weewx 
>>>> install.
>>>>
>>>> Thanks!
>>>>
>>>> -- 
>>>> 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+...@googlegroups.com.
>>>> To view this discussion on the web visit 
>>>> https://groups.google.com/d/msgid/weewx-user/1f1f3fa0-e3c7-4000-b461-4293453be1e0n%40googlegroups.com
>>>>  
>>>> <https://groups.google.com/d/msgid/weewx-user/1f1f3fa0-e3c7-4000-b461-4293453be1e0n%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>> .
>>>>
>>>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/91592f2a-477a-4263-89fa-fc7cf3a279c4n%40googlegroups.com.

[weewx-user] High CPU on 5.10

[Mark Jenks]

Just built a new weewx on my Fedora 38 this morning, and attached it to my 
mariadb.  It has 13 years worth of data in it.

I am running Belchertown and mqtt, and installed Windy.  But I just removed 
Windy to see if that was it, but still does it.  Python and/or moriadb goes 
to 100% CPU.
Mariadb says the high query during that time is:  SELECT * FROM archive 
WHERE dateTime > 1320346500 AND dateTime <= 1716824400 ORDER BY dateTime ASC
But that makes no sense, since I can query my entire archive table (select 
*) in about 3 seconds.

Any thoughts on how to catch what is going on?   I could enable debug, but 
hoping for a better way other that looking at a ton of logs.

Thanks!



-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/a882fb44-d36b-4bf4-8588-41199524b5f7n%40googlegroups.com.

Re: [weewx-user] 4.10 to 5.1 upgrade observations

[Mark Jenks]

Is there a schema change?  Or am I good with just running weectl database 
update?  I did that before I started it too, but didn't seem like it did 
much?

-Mark


On Monday, May 27, 2024 at 9:08:12 AM UTC-5 Tom Keffer wrote:

> Thanks for your report.
>
> The library pyephem is not available as a package under RH, so you have to 
> install it using pip. 
>
> The creation of a new database with suffix "_new" by "weectl database 
> reconfigure" is normal behavior. See the docs 
> <https://www.weewx.com/docs/5.1/utilities/weectl-database/#reconfigure-a-database>
> .
>
> On Mon, May 27, 2024 at 6:40 AM Mark Jenks  wrote:
>
>> I just did a fresh install of 5.1 from yum-test, and migrated everything 
>> from my 4.10 over to it.   Everything went as expected, except a few things 
>> I noticed.
>>
>> One thing to note, is to install the extensions, before start editing the 
>> data in them.  I'm running Belchertown, and coping the skins folder over 
>> first was a bad idea.  Just let them install and them tweak the folder as 
>> needed.
>>
>> Seems this is supposed to come with v5?  But did not for me.  I did a dnf 
>> install, which was never done before on my system.
>> INFO weewx.engine: 'pyephem' not detected, extended almanac data is not 
>> available
>>
>> Also, when I do a weectl database reconfigure, it doesn't use what is 
>> already in weewx.conf (like what configuring the hardware does), but wants 
>> to create a weewx_new database?  That threw me for a loop, because I was 
>> trying to make sure everything was right, before I started it up for the 
>> first time.
>>
>> Otherwise, all back up and running and can now archive my /home/weewx 
>> install.
>>
>> Thanks!
>>
>> -- 
>> 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+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/1f1f3fa0-e3c7-4000-b461-4293453be1e0n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/1f1f3fa0-e3c7-4000-b461-4293453be1e0n%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/dccb4917-c5aa-4d27-b963-181808410a1fn%40googlegroups.com.

[weewx-user] 4.10 to 5.1 upgrade observations

[Mark Jenks]

I just did a fresh install of 5.1 from yum-test, and migrated everything 
from my 4.10 over to it.   Everything went as expected, except a few things 
I noticed.

One thing to note, is to install the extensions, before start editing the 
data in them.  I'm running Belchertown, and coping the skins folder over 
first was a bad idea.  Just let them install and them tweak the folder as 
needed.

Seems this is supposed to come with v5?  But did not for me.  I did a dnf 
install, which was never done before on my system.
INFO weewx.engine: 'pyephem' not detected, extended almanac data is not 
available

Also, when I do a weectl database reconfigure, it doesn't use what is 
already in weewx.conf (like what configuring the hardware does), but wants 
to create a weewx_new database?  That threw me for a loop, because I was 
trying to make sure everything was right, before I started it up for the 
first time.

Otherwise, all back up and running and can now archive my /home/weewx 
install.

Thanks!

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/1f1f3fa0-e3c7-4000-b461-4293453be1e0n%40googlegroups.com.

[weewx-user] Fedora Weewx RPM install

[Mark Jenks]

Good morning!

I was going to do PIP for the new 5.x install, instead of using the 
setup.py like I have for years.
Then I saw the RPM, and figured I was take a look at that, except the rpm 
doesn't work for Fedora.
Fedora is not Enterprise Linux, so you can not install EPEL-Repo for it, 
but all packages that are in the EPEL, are already avail for Fedora.

Looking at the RPM, epel-release is a dependency which is required by the 
RPM.  So either you create a new RPM for Fedora only, or the dependency 
needs to be removed.

-Mark

#
dnf install weewx
Last metadata expiration check: 0:25:37 ago on Wed 06 Mar 2024 05:30:57 AM 
CST.
Dependencies resolved.

 Problem: cannot install the best candidate for the job
  - nothing provides epel-release needed by weewx-5.0.2-1.el9.noarch from 
weewx


rpm -qpR weewx-5.0.2-1.el9.noarch.rpm
/bin/sh
/bin/sh
/bin/sh
/usr/bin/getent
/usr/sbin/groupadd
/usr/sbin/useradd
*epel-release*
python3
python3-cheetah
python3-configobj
python3-pillow
python3-pyserial
python3-pyusb
rpmlib(CompressedFileNames) <= 3.0.4-1
rpmlib(FileDigests) <= 4.6.0-1
rpmlib(PayloadFilesHavePrefix) <= 4.0-1
rpmlib(PayloadIsXz) <= 5.2-1

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/b8af8921-dcb7-4bfa-9e21-dfdbfb26682cn%40googlegroups.com.

Re: [weewx-user] How to upgrade from setup.py v4 install to pip v5 install

[Mark Jenks]

I think that is the direction I am going to go in also.   I've been using 
setup.py since the beginning since there was no rpm yet.

I'm going to do the pip install, move all my files around to the new format 
and restart it there.   Running mariadb, so all my data is in one place 
already.

Been here since 2011, and it's time to clean up the install anyways.

On Thursday, February 22, 2024 at 9:13:16 AM UTC-6 Tom Keffer wrote:

> There's nothing special about /home/weewx. You could do
>
> *cp -rp /home/weewx ~/weewx-data*
> *cd ~/weewx-data*
> *mv bin bin.old*
> *mkdir bin*
> *cp -r ./bin.old/user bin *
>
>
> You'll have to adjust your systemd service file to reflect the new 
> location.
>
> -tk
>
> On Thu, Feb 22, 2024 at 6:28 AM gary@gmail.com  
> wrote:
>
>> Thanks for the options.
>>
>> I don't want to have a "hybrid" so won't be following the migration guide 
>> method.
>> Makes more sense to me to install new, install extensions and skins, edit 
>> in my config from the existing (old) weewx.conf, copy the database over, 
>> remove the old systemd service file, add the new systemd service, move the 
>> old install to weewx.old, run the new.
>>
>> May be a tiny bit more effort but then should be easier for me to 
>> maintain/update in the future.
>>
>>
>>
>> On Wednesday, February 21, 2024 at 11:07:46 AM UTC-5 Tom Keffer wrote:
>>
>>> Oh, I thought we were talking about upgrading from an alpha version of 
>>> v5.
>>>
>>> Not much difference. Just set up a V5 virtual environment, then point it 
>>> at /home/weewx. Follow the directions in the migration guide 
>>> . 
>>>
>>> On Wed, Feb 21, 2024 at 7:44 AM gary@gmail.com  
>>> wrote:
>>>
 I understand coming from v5 that would be a way.
 I need to upgrade my v4 setup.py to v5 though.


 On Wednesday, February 21, 2024 at 10:39:47 AM UTC-5 Tom Keffer wrote:

 The pip installs are super easy to back up. Just copy ~/weewx-venv and 
 ~/weewx-data and you have everything you need.

 Then activate the virtual environment, then "pip install weewx 
 --upgrade". It should be that easy. If something fails, just roll things 
 back.

 On Wed, Feb 21, 2024 at 7:15 AM gary@gmail.com  
 wrote:

 I've had a test install of v5 since early alphas. Now, it is time to 
 upgrade my production install.
 I have a relatively simple install, Vantage Pro IP driver, weewx-mqtt. 
 A couple of additional internet uploaders (Windy and WeatherCloud). I run 
 two skins, Belchertown and weewx-wdc

 All is and has been quite stable. So, I hesitate to poke at it. But, v5 
 is the new standard, so I need to get this done.

 I don't see many who have trod this path. How to go about this?

 -- 
 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+...@googlegroups.com.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/weewx-user/b2d73a89-3432-4ad4-8971-34ea51167f24n%40googlegroups.com
  
 
 .

 -- 
 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+...@googlegroups.com.

>>> To view this discussion on the web visit 
 https://groups.google.com/d/msgid/weewx-user/68e9b77e-5d25-492f-bfa5-448ac39b8cedn%40googlegroups.com
  
 
 .

>>> -- 
>> 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+...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/fbb6b339-9284-4e54-a97b-85d99d787a61n%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/7fc3fd17-fc7f-422a-b7b7-05b51a9a6a76n%40googlegroups.com.

[weewx-user] Re: Belchertown not generating forecast

[Mark Jenks]

Works different for me.  But it is getting downloaded.
[root@fedora json]# date --date="@1685959229"
Mon Jun  5 05:00:29 AM CDT 2023


On Monday, June 5, 2023 at 5:54:40 AM UTC-5 Mark Jenks wrote:

> date -d doesn't do that for me, but inside the json, I found the current 
> date and time.  So it's downloading, but not generating the HTML.
>
>  "dateTimeISO": "2023-06-05T07:00:00-05:00"
>
>
> On Sunday, June 4, 2023 at 11:06:51 PM UTC-5 vince wrote:
>
>> Your syslog should show something like
>> Jun  4 21:00:20 pi4 weewx[10457] INFO user.belchertown: New forecast file 
>> downloaded to 
>> /home/pi/weewx-data/public_html/weewx_belchertown/json/forecast.json
>>
>> And the timestamp of the first record of that forecast.json file should 
>> match that date
>> {"timestamp": 1685937620, "current": [{"success": true, "error": null, 
>> "response": {"id": "KSEA", "dataSource": "METAR_NOAA", "loc": {"long": 
>> -122.317, "lat": 47.45}, "place"
>> : {"name": "seattle/metro", "city": "seattle/metro",
>>
>> pi@pi4:/var/www/html/weewx/weewx_belchertown $ date -d @1685937620
>> Sun 04 Jun 2023 09:00:20 PM PDT
>>
>>
>> On Sunday, June 4, 2023 at 6:12:47 PM UTC-7 Mark Jenks wrote:
>>
>>> It's downloading it form aeris and I see it in the API as being 
>>> queries.  Also I see it in the logs and the json is downloaded.
>>>
>>> Jun  4 20:00:27 fedora journal[3171401]: weewx[3171401] INFO 
>>> user.belchertown: New forecast file downloaded to 
>>> /var/www/html/weewx/belchertown/json/forecast.json
>>>
>>> But I have no forecast on the webpage, and don't see any errors.
>>>
>>> Not sure where to look next.. 
>>>
>>> [[Belchertown]]
>>> skin = Belchertown
>>> HTML_ROOT = /var/www/html/weewx/belchertown
>>> enable = true
>>> #HTML_ROOT = /var/www/html/weewx/belchertown
>>> [[[Extras]]]
>>> forecast_enabled = 1
>>> forecast_api_id = 
>>> forecast_api_secret = x
>>>
>>>
>>>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/7298f395-5195-4982-9201-d8b5ab584374n%40googlegroups.com.

[weewx-user] Re: Belchertown not generating forecast

[Mark Jenks]

date -d doesn't do that for me, but inside the json, I found the current 
date and time.  So it's downloading, but not generating the HTML.

 "dateTimeISO": "2023-06-05T07:00:00-05:00"


On Sunday, June 4, 2023 at 11:06:51 PM UTC-5 vince wrote:

> Your syslog should show something like
> Jun  4 21:00:20 pi4 weewx[10457] INFO user.belchertown: New forecast file 
> downloaded to 
> /home/pi/weewx-data/public_html/weewx_belchertown/json/forecast.json
>
> And the timestamp of the first record of that forecast.json file should 
> match that date
> {"timestamp": 1685937620, "current": [{"success": true, "error": null, 
> "response": {"id": "KSEA", "dataSource": "METAR_NOAA", "loc": {"long": 
> -122.317, "lat": 47.45}, "place"
> : {"name": "seattle/metro", "city": "seattle/metro",
>
> pi@pi4:/var/www/html/weewx/weewx_belchertown $ date -d @1685937620
> Sun 04 Jun 2023 09:00:20 PM PDT
>
>
> On Sunday, June 4, 2023 at 6:12:47 PM UTC-7 Mark Jenks wrote:
>
>> It's downloading it form aeris and I see it in the API as being queries.  
>> Also I see it in the logs and the json is downloaded.
>>
>> Jun  4 20:00:27 fedora journal[3171401]: weewx[3171401] INFO 
>> user.belchertown: New forecast file downloaded to 
>> /var/www/html/weewx/belchertown/json/forecast.json
>>
>> But I have no forecast on the webpage, and don't see any errors.
>>
>> Not sure where to look next.. 
>>
>> [[Belchertown]]
>> skin = Belchertown
>> HTML_ROOT = /var/www/html/weewx/belchertown
>> enable = true
>> #HTML_ROOT = /var/www/html/weewx/belchertown
>> [[[Extras]]]
>> forecast_enabled = 1
>> forecast_api_id = 
>> forecast_api_secret = x
>>
>>
>>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/68586c3a-3775-42cd-828c-ca6d6db30407n%40googlegroups.com.

[weewx-user] Belchertown not generating forecast

[Mark Jenks]

It's downloading it form aeris and I see it in the API as being queries.  
Also I see it in the logs and the json is downloaded.

Jun  4 20:00:27 fedora journal[3171401]: weewx[3171401] INFO 
user.belchertown: New forecast file downloaded to 
/var/www/html/weewx/belchertown/json/forecast.json

But I have no forecast on the webpage, and don't see any errors.

Not sure where to look next.. 

[[Belchertown]]
skin = Belchertown
HTML_ROOT = /var/www/html/weewx/belchertown
enable = true
#HTML_ROOT = /var/www/html/weewx/belchertown
[[[Extras]]]
forecast_enabled = 1
forecast_api_id = 
forecast_api_secret = x


-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/88e4c23f-5f48-44ba-946b-32d33105a766n%40googlegroups.com.

[weewx-user] Re: Wmr 200 rain gauge replacement

[Mark Jenks]

I had the worst luck with the WMR rain gauge.  The antenna reception is 
just terrible at best. 
II tried this and it helped some..  
 https://images37.fotosik.pl/164/db3fd6d70e345043med.jpg

I just kept it closer to the house than the weather station.


On Tuesday, January 19, 2021 at 5:34:47 AM UTC-6 jdest...@gmail.com wrote:

> Hi everyone,
> I am using Weewx on an rpi3 and my WMR200 station for a while now. The 
> WMR200 station is working quite well exept the rain gauge who don't want to 
> work outside. I figure it out to sync correctly inside my house but outside 
> the station lose sync after few hours.
>
> I looked for a replacement but I think the rain gauge PCR800 is no longuer 
> manufactured by Oregon scientific. I am look for a rain gauge who can work 
> with my actual setup, I read that the Natatmo rain gauge is OK with Weewx. 
>
> Is that true ? and is there another solution to record rain ?
>
> Thanks in advance! 
> Sorry for my poor English
> --
> Johann
>
>
>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/4756fd84-c814-42e2-b9a0-2c71dd6fc038n%40googlegroups.com.

Re: [weewx-user] NWS Radar Changes

[Mark Jenks]

If you go up a level, the ones not in the folders are the current ones.

https://www.aviationweather.gov/data/obs/radar/rad_rala_lws.gif


On Monday, January 11, 2021 at 10:07:55 PM UTC-6 ral...@gmail.com wrote:

> Anybody able to make the new and improved NWS radar work?  Has anyone 
> written code to build a dynamic link for the aviation weather radar? It 
> appears to me that we need to enter date and time into the url for the 
> radar. I copied the aviation radar link into my skin.conf and it appeared 
> to work, then after a week I noticed that its showing Dec 31 data.   
> https://www.aviationweather.gov/data/obs/radar/20201231/20/20201231_2038_rad_rala_lws.gif
>
> On Friday, January 1, 2021 at 5:28:07 AM UTC-8 messyp...@gmail.com wrote:
>
>> I just found out why my "
>> http://radar.weather.gov/ridge/lite/N0R/HTX_loop.gif"; is broke, and, why 
>> I can't find the replacement. They redesigned the entire system (from 
>> something that was working fine) to what could be described as "the new 
>> Coke" of NWS radar services. This article explains it succinctly:
>>
>> https://www.washingtonpost.com/weather/2020/12/21/nws-new-radar-website-slow/
>> Really disappointing. 
>> --MP
>>
>> On Thursday, December 31, 2020 at 9:44:39 PM UTC+1 tke...@gmail.com 
>> wrote:
>>
>>> Here's another option: NOAA's aviation radar. 
>>> https://www.aviationweather.gov/data/obs/radar/20201231/20/20201231_2038_rad_rala_lws.gif
>>>
>>> The images load fast and cover the entire USA.
>>>
>>> [image: image.png]
>>>
>>> On Wed, Dec 30, 2020 at 9:52 AM John Mora  wrote:
>>>
>>>> I have been using these links:
>>>> https://radblast.wunderground.com/cgi-bin/radar/WUNIDS_map?station=ILN&;
>>>> brand=wui&num=18&delay=15&type=N0R&frame=0&scale=1.000&noclutter=0&sho
>>>> wstorms=1&showlabels=1&severe=1&rainsnow=1&lightning=1&smooth=1 
>>>>
>>>> https://www.wunderground.com/radar/us/oh/cincinnati/iln
>>>>
>>>> Just replace the station with the one you desire.
>>>>
>>>> To me they are an adequate replacement until a better one is found
>>>>
>>>> Cheers!
>>>>
>>>> On Wednesday, December 30, 2020 at 12:40:17 PM UTC-5 
>>>> jo...@johnkline.com wrote:
>>>>
>>>>> >  I haven't see this link listed anywhere yet.
>>>>> It’s listed in this thread.
>>>>>
>>>>> On Dec 30, 2020, at 8:35 AM, Mark Jenks  wrote:
>>>>>
>>>>> Finally got an answer back from NOAA.  I haven't see this link listed 
>>>>> anywhere yet.   Images aren't the best, but it's something better than 
>>>>> the 
>>>>> .gz's and straight .gif files
>>>>>
>>>>>
>>>>>
>>>>> https://radar.weather.gov/ridge/lite/
>>>>>
>>>>>
>>>>> On Wednesday, December 23, 2020 at 7:12:15 AM UTC-6 Mark Jenks wrote:
>>>>>
>>>>>> Email contact information here:
>>>>>> https://www.weather.gov/radarfaq
>>>>>>
>>>>>> On Wednesday, December 23, 2020 at 7:10:50 AM UTC-6 Mark Jenks wrote:
>>>>>>
>>>>>>> I just sent an email to NWS.  I'll let you know the response if I 
>>>>>>> get one..
>>>>>>>
>>>>>>> 
>>>>>>>
>>>>>>> Good Morning!
>>>>>>>
>>>>>>> For years, there have been many many people who have linked your 
>>>>>>> radar images and loops to their PWS (Personal weather station) 
>>>>>>> websites.  I 
>>>>>>> currently use weewx @ http://weather.mjenks.net
>>>>>>> With the new radar, this is no longer possible, and the .gz versions 
>>>>>>> just aren't good enough quality.  So I have to use someone else's radar 
>>>>>>> now.
>>>>>>>
>>>>>>> It sure would be nice if you could provide an iframe code snipped 
>>>>>>> that we could embed into our webpages.Or at least recreate the 
>>>>>>> images 
>>>>>>> and loops.
>>>>>>>
>>>>>>> This is what I have been using that no longer works.
>>>>>>>
>>>>

Re: [weewx-user] Re: CentOS is on shakey ground

[Mark Jenks]

Go back and look at Fedora again if you haven't used it in the last few 
years.It's better than it used to be and is worth a look.

On Sunday, January 3, 2021 at 4:56:37 PM UTC-6 WindnFog wrote:

> I suspect a lot of web hosting companies use CentOS.  The outfit I was 
> with in Florida sure did. No doubt there’s going to be a scramble to get 
> Rocky Linux or equivalent going quickly. 
>
> I am now hosting my weewx website on a VPS now using Ubuntu and Apache. 
>  That way I have full control and don’t have to pay a fortune for someone 
> else to do it.  It cost me $50 USD for the TLS certificate alone! Now I get 
> my own and install it for free.  I used to use Fedora, but it’s really a 
> beta version for RedHat and I got tired of the incessant bug fixes and 
> updates.  CentOS was a great solution as it was familiar and mature. 
>
> Anyway, I guess this is not really weewx related. 
>
> - Paul VE1DX 
>
> On Jan 3, 2021, at 6:20 PM, Mark Jenks  wrote:
>
> I use CentOS for everything, except my home server.At home I use 
> Fedora, since it's RedHat based..
>
>
>
> On Sunday, January 3, 2021 at 12:48:56 PM UTC-6 WindnFog wrote:
>
>> I may have been the only one using CentOS for weewx (before switching to 
>> a Raspberry Pi about a year ago.)  I note it's still mentioned as a distro 
>> in the weewx documentation, with RedHat and Fedora.  CentOS was to be 
>> supported until 31 May 2029. 
>>
>> Since the takeover of RedHat by IBM, this has been shortened to 31 
>> December 2021.  If anyone is still using CentOS for weewx, it's probably a 
>> good idea to migrate to another distro soon.  There's a movement to replace 
>> CentOS with "Rocky Linux", but there's no timeframe for its deployment:
>>
>> https://wiki.rockylinux.org/
>>
>> The "strength" of CentOS was stability because it is a clone of RedHat.  
>> I still use CentOS for other things than weewx, and rather than wait to see 
>> if Rocky Linux is successful, I'm moving to Ubuntu LTS 2020, which has at 
>> least 5 years of support/stability.
>>
>> - Paul VE1DX
>>
> -- 
> You received this message because you are subscribed to a topic in the 
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/weewx-user/0xzffO8ddEE/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to 
> weewx-user+...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/d86315f0-d75f-4ff6-924f-aa023c28a8fcn%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/weewx-user/d86315f0-d75f-4ff6-924f-aa023c28a8fcn%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/128b4862-b0a3-49d0-ba43-8d12b49f7f44n%40googlegroups.com.

[weewx-user] Re: CentOS is on shakey ground

[Mark Jenks]

I use CentOS for everything, except my home server.At home I use 
Fedora, since it's RedHat based..

On Sunday, January 3, 2021 at 12:48:56 PM UTC-6 WindnFog wrote:

> I may have been the only one using CentOS for weewx (before switching to a 
> Raspberry Pi about a year ago.)  I note it's still mentioned as a distro in 
> the weewx documentation, with RedHat and Fedora.  CentOS was to be 
> supported until 31 May 2029. 
>
> Since the takeover of RedHat by IBM, this has been shortened to 31 
> December 2021.  If anyone is still using CentOS for weewx, it's probably a 
> good idea to migrate to another distro soon.  There's a movement to replace 
> CentOS with "Rocky Linux", but there's no timeframe for its deployment:
>
> https://wiki.rockylinux.org/
>
> The "strength" of CentOS was stability because it is a clone of RedHat.  I 
> still use CentOS for other things than weewx, and rather than wait to see 
> if Rocky Linux is successful, I'm moving to Ubuntu LTS 2020, which has at 
> least 5 years of support/stability.
>
> - Paul VE1DX
>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/d86315f0-d75f-4ff6-924f-aa023c28a8fcn%40googlegroups.com.

[weewx-user] Re: best way to use weewx with a Davis station

[Mark Jenks]

You can still find the 6510USB for sale online.

On Thursday, December 31, 2020 at 2:41:01 PM UTC-6 pedal...@gmail.com wrote:

> Yes you can. I have a Davis Vantage Vue and Weatherlink Live and have that 
> ability with weewx
>
> On Thursday, December 31, 2020 at 12:45:40 PM UTC-5 Juan Antonio Mosquera 
> wrote:
>
>> ok ... and with weatherlink cloud weewx gets all current and historical 
>> data (I have seen that there is a weewx extension for weatherlink live to 
>> work). QUESTION: can I buy a davis vantage pro2 with weatherlink live and 
>> have historical data with weewx? (using the extension)
>>
>> O xoves, 31 de decembro de 2020 á/s 14:59:22 UTC+1, kk44...@gmail.com 
>> escribiu:
>>
>>> The adaptors for the console are discontinued. Davis now sells the 
>>> WeatherLinkLive device, only. 
>>>
>>> To use WeatherLinkLive you do not need a console at all. Unfortunately 
>>> you cannot use the device without setting it up by connecting it to the 
>>> cloud of Davis.
>>>
>>> The drivers for the old adaptors can read data saved in the device. 
>>> That's why you do not loose data if weewx is down for some time. The 
>>> drivers for WeatherLinkLive cannot read those data. Davis prevents it.
>>>
>>> Juan Antonio Mosquera schrieb am Donnerstag, 31. Dezember 2020 um 
>>> 10:16:20 UTC+1:
>>>

 hi, what is the best way to use weewx with a davis vantage vue2 or 
 davis vantage pro2 ?. weatherlink live? or ... USB console and datalogger?

 thanks.

>>>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/163dcd18-796a-4fbd-83a7-179220fda00en%40googlegroups.com.

Re: [weewx-user] NWS Radar Changes

[Mark Jenks]

Finally got an answer back from NOAA.  I haven't see this link listed 
anywhere yet.   Images aren't the best, but it's something better than the 
.gz's and straight .gif files

https://radar.weather.gov/ridge/lite/


On Wednesday, December 23, 2020 at 7:12:15 AM UTC-6 Mark Jenks wrote:

> Email contact information here:
> https://www.weather.gov/radarfaq
>
> On Wednesday, December 23, 2020 at 7:10:50 AM UTC-6 Mark Jenks wrote:
>
>> I just sent an email to NWS.  I'll let you know the response if I get 
>> one..
>>
>> 
>>
>> Good Morning!
>>
>> For years, there have been many many people who have linked your radar 
>> images and loops to their PWS (Personal weather station) websites.  I 
>> currently use weewx @ http://weather.mjenks.net
>> With the new radar, this is no longer possible, and the .gz versions just 
>> aren't good enough quality.  So I have to use someone else's radar now.
>>
>> It sure would be nice if you could provide an iframe code snipped that we 
>> could embed into our webpages.Or at least recreate the images and loops.
>>
>> This is what I have been using that no longer works.
>>
>> radar_img = http://radar.weather.gov/ridge/lite/N0R/GRB_loop.gif
>> radar_url = 
>> http://radar.weather.gov/ridge/radar.php?product=NCR&rid=GRB&loop=yes
>>
>> Thank you!
>>
>> Mark Jenks
>> Station ID - DW7584
>>
>> On Tuesday, December 22, 2020 at 4:20:17 PM UTC-6 chri...@gmail.com 
>> wrote:
>>
>>> Thank you for looking into this folks. It sounds as though they have 
>>> gone the same route as Environment Canada did a long time ago now.  No more 
>>> animated gifs available, instead they build the animations on the fly with 
>>> overlays and a repository of images. The best I could do for Environment 
>>> Canada radars was to create a shell script that runs on the web server cron 
>>> that guesses at the current time stamp for the latest image and saves it to 
>>> my webserver.
>>>
>>> Less than great.
>>>
>>> It sure would be nice if they could just provide an iframe code snipped 
>>> that we could embed into our webpages.
>>> Alas.
>>> Cheers
>>> Chris
>>> On Saturday, December 19, 2020 at 9:59:31 AM UTC-8 peterq...@gmail.com 
>>> wrote:
>>>
>>>> I hooked up the NWS gif and it's worse than useless. It's hours old and 
>>>> shows nothing, flashes clutter, and repeats. Now, it should show nothing 
>>>> but the flashing of clutter is super annoying. 
>>>>
>>>> As much as I'm pissed at WU, I'm going to use their gif while it's 
>>>> available.
>>>>
>>>> On Sat, Dec 19, 2020 at 7:17 AM wfs...@gmail.com  
>>>> wrote:
>>>>
>>>>> Yes John kind of crummy images and I just tried mine for KILX and it 
>>>>> is two hours behind the current UTC.
>>>>>
>>>>> On Friday, December 18, 2020 at 11:56:56 AM UTC-6 jo...@johnkline.com 
>>>>> wrote:
>>>>>
>>>>>> The loops in https://radar.weather.gov/ridge/lite/ 
>>>>>> <https://radar.weather.gov/ridge/lite/KMUX_loop.gif> seem to be up 
>>>>>> to date today.
>>>>>>
>>>>>> For example:
>>>>>> https://radar.weather.gov/ridge/lite/KMUX_loop.gif
>>>>>>
>>>>>> As such, that’s also an option, although these gifs are tough to get 
>>>>>> used to.
>>>>>>
>>>>>> On Dec 18, 2020, at 9:38 AM, John Kline  wrote:
>>>>>>
>>>>>> 
>>>>>>
>>>>>> This thread has a nice solution (see URL below):
>>>>>>
>>>>>> https://www.wxforum.net/index.php?topic=40980.0
>>>>>>
>>>>>> Terms of use:
>>>>>> https://www.wunderground.com/company/legal
>>>>>>
>>>>>> (In the following URL, substitute your radar station for OAX.  Set 
>>>>>> weewx.conf’s Seasons radar_img value to this.)
>>>>>>
>>>>>>
>>>>>> https://radblast.wunderground.com/cgi-bin/radar/WUNIDS_map?station=OAX&brand=wui&num=18&delay=15&type=N0R&frame=0&scale=1.000&noclutter=0&showstorms=0&showlabels=1&severe=1&rainsnow=0&lightning=0&smooth=0
>>>>>>
>>>

Re: [weewx-user] NWS Radar Changes

[Mark Jenks]

Email contact information here:
https://www.weather.gov/radarfaq

On Wednesday, December 23, 2020 at 7:10:50 AM UTC-6 Mark Jenks wrote:

> I just sent an email to NWS.  I'll let you know the response if I get one..
>
> 
>
> Good Morning!
>
> For years, there have been many many people who have linked your radar 
> images and loops to their PWS (Personal weather station) websites.  I 
> currently use weewx @ http://weather.mjenks.net
> With the new radar, this is no longer possible, and the .gz versions just 
> aren't good enough quality.  So I have to use someone else's radar now.
>
> It sure would be nice if you could provide an iframe code snipped that we 
> could embed into our webpages.Or at least recreate the images and loops.
>
> This is what I have been using that no longer works.
>
> radar_img = http://radar.weather.gov/ridge/lite/N0R/GRB_loop.gif
> radar_url = 
> http://radar.weather.gov/ridge/radar.php?product=NCR&rid=GRB&loop=yes
>
> Thank you!
>
> Mark Jenks
> Station ID - DW7584
>
> On Tuesday, December 22, 2020 at 4:20:17 PM UTC-6 chri...@gmail.com wrote:
>
>> Thank you for looking into this folks. It sounds as though they have gone 
>> the same route as Environment Canada did a long time ago now.  No more 
>> animated gifs available, instead they build the animations on the fly with 
>> overlays and a repository of images. The best I could do for Environment 
>> Canada radars was to create a shell script that runs on the web server cron 
>> that guesses at the current time stamp for the latest image and saves it to 
>> my webserver.
>>
>> Less than great.
>>
>> It sure would be nice if they could just provide an iframe code snipped 
>> that we could embed into our webpages.
>> Alas.
>> Cheers
>> Chris
>> On Saturday, December 19, 2020 at 9:59:31 AM UTC-8 peterq...@gmail.com 
>> wrote:
>>
>>> I hooked up the NWS gif and it's worse than useless. It's hours old and 
>>> shows nothing, flashes clutter, and repeats. Now, it should show nothing 
>>> but the flashing of clutter is super annoying. 
>>>
>>> As much as I'm pissed at WU, I'm going to use their gif while it's 
>>> available.
>>>
>>> On Sat, Dec 19, 2020 at 7:17 AM wfs...@gmail.com  
>>> wrote:
>>>
>>>> Yes John kind of crummy images and I just tried mine for KILX and it is 
>>>> two hours behind the current UTC.
>>>>
>>>> On Friday, December 18, 2020 at 11:56:56 AM UTC-6 jo...@johnkline.com 
>>>> wrote:
>>>>
>>>>> The loops in https://radar.weather.gov/ridge/lite/ 
>>>>> <https://radar.weather.gov/ridge/lite/KMUX_loop.gif> seem to be up to 
>>>>> date today.
>>>>>
>>>>> For example:
>>>>> https://radar.weather.gov/ridge/lite/KMUX_loop.gif
>>>>>
>>>>> As such, that’s also an option, although these gifs are tough to get 
>>>>> used to.
>>>>>
>>>>> On Dec 18, 2020, at 9:38 AM, John Kline  wrote:
>>>>>
>>>>> 
>>>>>
>>>>> This thread has a nice solution (see URL below):
>>>>>
>>>>> https://www.wxforum.net/index.php?topic=40980.0
>>>>>
>>>>> Terms of use:
>>>>> https://www.wunderground.com/company/legal
>>>>>
>>>>> (In the following URL, substitute your radar station for OAX.  Set 
>>>>> weewx.conf’s Seasons radar_img value to this.)
>>>>>
>>>>>
>>>>> https://radblast.wunderground.com/cgi-bin/radar/WUNIDS_map?station=OAX&brand=wui&num=18&delay=15&type=N0R&frame=0&scale=1.000&noclutter=0&showstorms=0&showlabels=1&severe=1&rainsnow=0&lightning=0&smooth=0
>>>>>
>>>>>
>>>>> On Dec 17, 2020, at 10:00 PM, John Kline  wrote:
>>>>>
>>>>> 
>>>>> Although the directory listing here shows old timestamps:
>>>>> https://radar.weather.gov/ridge/lite/
>>>>>
>>>>> The loop is being updated (albeit still a few hours old and I’m not a 
>>>>> fan of this radar imagery):
>>>>> https://radar.weather.gov/ridge/lite/KMUX_loop.gif
>>>>>
>>>>> Although not part of the loop, this image is only about 30m old:
>>>>> https://radar.weather.gov/ridge/lite/KMUX_1.gif
>>>>>
>>>>> I

Re: [weewx-user] NWS Radar Changes

[Mark Jenks]

I just sent an email to NWS.  I'll let you know the response if I get one..



Good Morning!

For years, there have been many many people who have linked your radar 
images and loops to their PWS (Personal weather station) websites.  I 
currently use weewx @ http://weather.mjenks.net
With the new radar, this is no longer possible, and the .gz versions just 
aren't good enough quality.  So I have to use someone else's radar now.

It sure would be nice if you could provide an iframe code snipped that we 
could embed into our webpages.Or at least recreate the images and loops.

This is what I have been using that no longer works.

radar_img = http://radar.weather.gov/ridge/lite/N0R/GRB_loop.gif
radar_url = 
http://radar.weather.gov/ridge/radar.php?product=NCR&rid=GRB&loop=yes

Thank you!

Mark Jenks
Station ID - DW7584

On Tuesday, December 22, 2020 at 4:20:17 PM UTC-6 chri...@gmail.com wrote:

> Thank you for looking into this folks. It sounds as though they have gone 
> the same route as Environment Canada did a long time ago now.  No more 
> animated gifs available, instead they build the animations on the fly with 
> overlays and a repository of images. The best I could do for Environment 
> Canada radars was to create a shell script that runs on the web server cron 
> that guesses at the current time stamp for the latest image and saves it to 
> my webserver.
>
> Less than great.
>
> It sure would be nice if they could just provide an iframe code snipped 
> that we could embed into our webpages.
> Alas.
> Cheers
> Chris
> On Saturday, December 19, 2020 at 9:59:31 AM UTC-8 peterq...@gmail.com 
> wrote:
>
>> I hooked up the NWS gif and it's worse than useless. It's hours old and 
>> shows nothing, flashes clutter, and repeats. Now, it should show nothing 
>> but the flashing of clutter is super annoying. 
>>
>> As much as I'm pissed at WU, I'm going to use their gif while it's 
>> available.
>>
>> On Sat, Dec 19, 2020 at 7:17 AM wfs...@gmail.com  
>> wrote:
>>
>>> Yes John kind of crummy images and I just tried mine for KILX and it is 
>>> two hours behind the current UTC.
>>>
>>> On Friday, December 18, 2020 at 11:56:56 AM UTC-6 jo...@johnkline.com 
>>> wrote:
>>>
>>>> The loops in https://radar.weather.gov/ridge/lite/ 
>>>> <https://radar.weather.gov/ridge/lite/KMUX_loop.gif> seem to be up to 
>>>> date today.
>>>>
>>>> For example:
>>>> https://radar.weather.gov/ridge/lite/KMUX_loop.gif
>>>>
>>>> As such, that’s also an option, although these gifs are tough to get 
>>>> used to.
>>>>
>>>> On Dec 18, 2020, at 9:38 AM, John Kline  wrote:
>>>>
>>>> 
>>>>
>>>> This thread has a nice solution (see URL below):
>>>>
>>>> https://www.wxforum.net/index.php?topic=40980.0
>>>>
>>>> Terms of use:
>>>> https://www.wunderground.com/company/legal
>>>>
>>>> (In the following URL, substitute your radar station for OAX.  Set 
>>>> weewx.conf’s Seasons radar_img value to this.)
>>>>
>>>>
>>>> https://radblast.wunderground.com/cgi-bin/radar/WUNIDS_map?station=OAX&brand=wui&num=18&delay=15&type=N0R&frame=0&scale=1.000&noclutter=0&showstorms=0&showlabels=1&severe=1&rainsnow=0&lightning=0&smooth=0
>>>>
>>>>
>>>> On Dec 17, 2020, at 10:00 PM, John Kline  wrote:
>>>>
>>>> 
>>>> Although the directory listing here shows old timestamps:
>>>> https://radar.weather.gov/ridge/lite/
>>>>
>>>> The loop is being updated (albeit still a few hours old and I’m not a 
>>>> fan of this radar imagery):
>>>> https://radar.weather.gov/ridge/lite/KMUX_loop.gif
>>>>
>>>> Although not part of the loop, this image is only about 30m old:
>>>> https://radar.weather.gov/ridge/lite/KMUX_1.gif
>>>>
>>>> It’s not clear one could determine which file has the latest image.  
>>>> Maybe this will improve over time and the _0.gif will have the latest gif 
>>>> (and/or the loop will be updated regularly).
>>>>
>>>> On Dec 17, 2020, at 4:18 PM, John Kline  wrote:
>>>>
>>>> 
>>>> I’ve been grappling with this.  It is annoying.  The “new site” is 
>>>> maddening to interact with: https://radar.weather.gov/
>>>>
>>>> There’s a FAQ about the change he

Re: [weewx-user] Belchertown skin with MQTT not working?

[Mark Jenks]

UGH, Thanks Tim.   :)

I usually don't run a firewall, because I use my home one.  But 6 months 
ago, I enabled it to stop all of the excess hacking attempted to 
ssh/http/etc/etc.  I started blocking countries, and repeat failures.

And that's what it was in the end.  Looks like I had multiple issues, but 
that was the last one.

On Tuesday, December 22, 2020 at 1:15:21 PM UTC-6 ti...@skybase.net wrote:

> Hi Mark,
>
> Have you configured the operating system's firewall to permit the 
> connection ?
>
> thanks
>
> Tim
>
>
> On 23/12/20 1:31 am, Mark Jenks wrote:
> > Okay, I cleaned it up per that link, and it doesn't seem to be working 
> > yet.
> >
> > mqtt_websockets_enabled = 1
> > mqtt_websockets_host = weather.mjenks.net
> > mqtt_websockets_port = 9001
> > mqtt_websockets_ssl = 0
> > mqtt_websockets_topic = "weather/weewx/loop"
> >
> > It looks like it's listening correctly...
> >
> > # netstat -tulpen|grep mosquitto
> > tcp0  0 0.0.0.0:18830.0.0.0:*  LISTEN  
> > 0  27106828   2136787/mosquitto
> > tcp6   0  0 :::9001 :::* LISTEN  
> > 0  27106831   2136787/mosquitto
> > tcp6   0  0 :::1883 :::* LISTEN  
> > 0  27106829   2136787/mosquitto
> >
> > # nc -4 -v weather.mjenks.net 9001
> > Ncat: Version 7.80 ( https://nmap.org/ncat )
> > Ncat: Connected to 192.168.10.10:9001.
> >
>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/ae870736-ca70-4c83-a33b-093f801a1189n%40googlegroups.com.

Re: [weewx-user] Belchertown skin with MQTT not working?

[Mark Jenks]

Okay, I cleaned it up per that link, and it doesn't seem to be working yet.

mqtt_websockets_enabled = 1
mqtt_websockets_host = weather.mjenks.net
mqtt_websockets_port = 9001
mqtt_websockets_ssl = 0
mqtt_websockets_topic = "weather/weewx/loop"

It looks like it's listening correctly...

# netstat -tulpen|grep mosquitto
tcp0  0 0.0.0.0:18830.0.0.0:*   LISTEN  
0  27106828   2136787/mosquitto
tcp6   0  0 :::9001 :::*LISTEN  
0  27106831   2136787/mosquitto
tcp6   0  0 :::1883 :::*LISTEN  
0  27106829   2136787/mosquitto

# nc -4 -v weather.mjenks.net 9001
Ncat: Version 7.80 ( https://nmap.org/ncat )
Ncat: Connected to 192.168.10.10:9001.


On Monday, December 21, 2020 at 6:18:10 PM UTC-6 vince wrote:

> Old thread where I battled the same thing a year ago, with solution...
>
> https://groups.google.com/g/weewx-user/c/w8aSTyX1UVo/m/eU52eJReCAAJ
>
>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/22480930-4d22-4703-a061-75b7182fb9cfn%40googlegroups.com.

Re: [weewx-user] Belchertown skin with MQTT not working?

[Mark Jenks]

I guess I should have included this...

# more mosquitto.conf
persistence false

# mqtt
listener 1883 127.0.0.1
protocol mqtt

# websockets
listener 9001 127.0.0.1
protocol websockets


On Monday, December 21, 2020 at 5:28:48 PM UTC-6 Greg Troxel wrote:

>
> Mark Jenks  writes:
>
> > Failed connecting to the weather station. Please try again later! 
> >
> > [StdRESTful]
> > [[MQTT]]
> > server_url = mqtt://weather:passwordx@localhost:1883/
> > topic = "weather/weewx"
> > unit_system = US
> > binding = archive, loop
> > aggregation = aggregate
> >
> > [[Belchertown]]
> > skin = Belchertown
> > # HTML_ROOT = /var/www/html/weewx/belchertown
> > [[[Extras]]]
> > mqtt_websockets_enabled = 1
> > mqtt_websockets_host = "127.0.0.1"
> > mqtt_websockets_port = 1883
> > mqtt_websockets_topic = "weather/weewx/loop"
> >
> > I see data when I run this, so it's getting populated.
> > #mosquitto_sub -h localhost -t weather/weewx/loop
>
> I have not set this up, but I think what you are missing is that 1883 is
> MQTT and you need to set up "mqtt over websockets" in mosquitto and
> point the skin at that. And if you are using a browswer on the same
> machine as the broker, ok, but really the mqtt_websockets_host needs to
> be the global name and reachable.
>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/740e546b-0acb-4afc-ba84-6bd1a6f7c8een%40googlegroups.com.

[weewx-user] Belchertown skin with MQTT not working?

[Mark Jenks]

What am I missing?  I can't seem to get this to work.  The website won't 
connect to mqtt to get the data.  Even though I can see it when I watch the 
topic.

Failed connecting to the weather station. Please try again later!  

[StdRESTful]
[[MQTT]]
server_url = mqtt://weather:passwordx@localhost:1883/
topic = "weather/weewx"
unit_system = US
binding = archive, loop
aggregation = aggregate

[[Belchertown]]
skin = Belchertown
#HTML_ROOT = /var/www/html/weewx/belchertown
[[[Extras]]]
mqtt_websockets_enabled = 1
mqtt_websockets_host = "127.0.0.1"
mqtt_websockets_port = 1883
mqtt_websockets_topic = "weather/weewx/loop"

I see data when I run this, so it's getting populated.
#mosquitto_sub -h localhost -t weather/weewx/loop

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/594e29e7-6a7e-4b32-9f00-4e8e668d3de2n%40googlegroups.com.

Re: [weewx-user] Probleme WMR200

[Mark Jenks]

Mine did it with Python 2, HTPC Intel MB with Fedora on it.  I never did 
notice the USB changing, but it's very possible.

I'd go back and check, but I'm now on a Vantage Vue..  :)

On Tuesday, December 15, 2020 at 6:11:45 AM UTC-6 tke...@gmail.com wrote:

> Issue #578  addresses this 
> problem with the WMR200. Unfortunately, no fix has been found.
>
> What kind of computer are you using? A Raspberry Pi? Something else?
>
> On Tue, Dec 15, 2020 at 2:36 AM mtev...@gmail.com  
> wrote:
>
>> Hello.
>> I have a problem. Weewx crashes regularly. Here are the log.
>> Do you have any ideas ?
>>
>> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.drivers.wmr200: 
>> open_device() Unable to claim USB interface. Reason: [Errno 16] Resource 
>> busy 
>> Dec 15 21:30:42 Nas weewx[495153] ERROR weewx.engine: Import of driver 
>> failed: [Errno 16] Resource busy () 
>> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine:  
>>  Traceback (most recent call last): 
>> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine: File 
>> "/usr/share/weewx/weewx/drivers/wmr200.py", line 193, in open_device 
>> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine:  
>>  self.handle.claimInterface(self.interface) 
>> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine: File 
>> "/usr/lib/python3/dist-packages/usb/legacy.py", line 230, in claimInterface 
>> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine:  
>>  util.claim_interface(self.dev, interface) 
>> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine: File 
>> "/usr/lib/python3/dist-packages/usb/util.py", line 205, in claim_interface 
>> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine:  
>>  device._ctx.managed_claim_interface(device, interface) 
>> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine: File 
>> "/usr/lib/python3/dist-packages/usb/core.py", line 102, in wrapper 
>> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine:  
>>  return f(self, *args, **kwargs) 
>> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine: File 
>> "/usr/lib/python3/dist-packages/usb/core.py", line 167, in 
>> managed_claim_interface 
>> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine:  
>>  self.backend.claim_interface(self.handle, i) 
>> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine: File 
>> "/usr/lib/python3/dist-packages/usb/backend/libusb1.py", line 811, in 
>> claim_interface 
>> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine:  
>>  _check(self.lib.libusb_claim_interface(dev_handle.handle, intf)) 
>> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine: File 
>> "/usr/lib/python3/dist-packages/usb/backend/libusb1.py", line 595, in 
>> _check 
>> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine:  
>>  raise USBError(_strerror(ret), ret, _libusb_errno[ret]) 
>> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine:  
>>  usb.core.USBError: [Errno 16] Resource busy 
>> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine:    
>> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine:   During 
>> handling of the above exception, another exception occurred: 
>> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine:    
>> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine:  
>>  Traceback (most recent call last): 
>> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine: File 
>> "/usr/share/weewx/weewx/engine.py", line 109, in setupStation 
>> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine:  
>>  self.console = loader_function(config_dict, self) 
>> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine: File 
>> "/usr/share/weewx/weewx/drivers/wmr200.py", line 58, in loader 
>> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine:  
>>  return WMR200(**config_dict[DRIVER_NAME]) 
>> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine: File 
>> "/usr/share/weewx/weewx/drivers/wmr200.py", line 1468, in __init__ 
>> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine:  
>>  self.usb_device.open_device() 
>> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine: File 
>> "/usr/share/weewx/weewx/drivers/wmr200.py", line 196, in open_device 
>> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine:  
>>  raise weewx.WakeupError(exception) 
>> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine:  
>>  weewx.WakeupError: [Errno 16] Resource busy 
>> Dec 15 21:30:42 Nas weewx[495153] CRITICAL __main__: Unable to load 
>> driver: [Errno 16] Resource busy 
>> Dec 15 21:30:42 Nas weewx[495153] CRITICAL __main__:   Exiting...
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups

[weewx-user] Re: Probleme WMR200

[Mark Jenks]

Mine did that once in awhile, and I never did figure out why..  I just 
wrote a script to watch it and restart it, if it saw "Exiting.."

# more watch-weewx.sh
#!/bin/bash
service=weewx.service
if (( $(/usr/bin/systemctl status $service | grep running | wc -l) < 1 ))
then
echo “$service was down and was restarted!!!”
systemctl stop $service
systemctl start $service
fi
if (( $(/usr/bin/systemctl status $service | grep "Exiting..." | wc -l) > 0 
))
then
echo “$service Exited and was restarted!!!”
systemctl stop $service
systemctl start $service
fi


On Tuesday, December 15, 2020 at 4:36:36 AM UTC-6 mtev...@gmail.com wrote:

> Hello.
> I have a problem. Weewx crashes regularly. Here are the log.
> Do you have any ideas ?
>
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.drivers.wmr200: 
> open_device() Unable to claim USB interface. Reason: [Errno 16] Resource 
> busy 
> Dec 15 21:30:42 Nas weewx[495153] ERROR weewx.engine: Import of driver 
> failed: [Errno 16] Resource busy () 
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine:  
>  Traceback (most recent call last): 
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine: File 
> "/usr/share/weewx/weewx/drivers/wmr200.py", line 193, in open_device 
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine:  
>  self.handle.claimInterface(self.interface) 
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine: File 
> "/usr/lib/python3/dist-packages/usb/legacy.py", line 230, in claimInterface 
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine:  
>  util.claim_interface(self.dev, interface) 
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine: File 
> "/usr/lib/python3/dist-packages/usb/util.py", line 205, in claim_interface 
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine:  
>  device._ctx.managed_claim_interface(device, interface) 
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine: File 
> "/usr/lib/python3/dist-packages/usb/core.py", line 102, in wrapper 
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine:  
>  return f(self, *args, **kwargs) 
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine: File 
> "/usr/lib/python3/dist-packages/usb/core.py", line 167, in 
> managed_claim_interface 
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine:  
>  self.backend.claim_interface(self.handle, i) 
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine: File 
> "/usr/lib/python3/dist-packages/usb/backend/libusb1.py", line 811, in 
> claim_interface 
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine:  
>  _check(self.lib.libusb_claim_interface(dev_handle.handle, intf)) 
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine: File 
> "/usr/lib/python3/dist-packages/usb/backend/libusb1.py", line 595, in 
> _check 
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine:  
>  raise USBError(_strerror(ret), ret, _libusb_errno[ret]) 
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine:  
>  usb.core.USBError: [Errno 16] Resource busy 
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine:    
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine:   During 
> handling of the above exception, another exception occurred: 
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine:    
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine:  
>  Traceback (most recent call last): 
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine: File 
> "/usr/share/weewx/weewx/engine.py", line 109, in setupStation 
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine:  
>  self.console = loader_function(config_dict, self) 
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine: File 
> "/usr/share/weewx/weewx/drivers/wmr200.py", line 58, in loader 
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine:  
>  return WMR200(**config_dict[DRIVER_NAME]) 
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine: File 
> "/usr/share/weewx/weewx/drivers/wmr200.py", line 1468, in __init__ 
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine:  
>  self.usb_device.open_device() 
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine: File 
> "/usr/share/weewx/weewx/drivers/wmr200.py", line 196, in open_device 
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine:  
>  raise weewx.WakeupError(exception) 
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL weewx.engine:  
>  weewx.WakeupError: [Errno 16] Resource busy 
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL __main__: Unable to load 
> driver: [Errno 16] Resource busy 
> Dec 15 21:30:42 Nas weewx[495153] CRITICAL __main__:   Exiting...
>

-- 
You rece

Re: [weewx-user] Re: Upgrade from 3.9.2 to 4.1.1 issues

[Mark Jenks]

Ugh, I looked right at it and didn't even see it.  I looked into 
/home/weewx, but only glanced into bin.
Removed and it's working!   

Thank you!

-Mark

On Sunday, October 25, 2020 at 8:07:49 PM UTC-5 tke...@gmail.com wrote:

> Did you look in /home/weewx/bin? 
>
> On Sun, Oct 25, 2020 at 6:02 PM Mark Jenks  wrote:
>
>> I completely removed pyserial using pip and dnf.
>> Same thing.  Maybe something to do with rules.d?  I tried tty and usb 
>> both, and get the same thing.
>>
>> [root@server ~]# systemctl status weewx.service
>> ● weewx.service - weewx weather system
>>Loaded: loaded (/usr/lib/systemd/system/weewx.service; enabled; vendor 
>> preset: disabled)
>>Active: failed (Result: exit-code) since Sun 2020-10-25 20:00:20 CDT; 
>> 2s ago
>>   Process: 11717 ExecStart=/home/weewx/bin/weewxd /home/weewx/weewx.conf 
>> (code=exited, status=4)
>>  Main PID: 11717 (code=exited, status=4)
>>   CPU: 221ms
>>
>> Oct 25 20:00:20 server.mjenks.net weewxd[11717]: weewx[11717] CRITICAL 
>> weewx.engine:   Vantage.__init__(self, 
>> **config_dict[DRIVER_NAME])
>> Oct 25 20:00:20 server.mjenks.net weewxd[11717]: weewx[11717] CRITICAL 
>> weewx.engine: File "/home/weewx/bin/weewx/drivers/vantage.py", 
>> line 511, >
>> Oct 25 20:00:20 server.mjenks.net weewxd[11717]: weewx[11717] CRITICAL 
>> weewx.engine:   self.port.openPort()
>> Oct 25 20:00:20 server.mjenks.net weewxd[11717]: weewx[11717] CRITICAL 
>> weewx.engine: File "/home/weewx/bin/weewx/drivers/vantage.py", 
>> line 307, >
>> Oct 25 20:00:20 server.mjenks.net weewxd[11717]: weewx[11717] CRITICAL 
>> weewx.engine:   self.serial_port = serial.Serial(self.port, 
>> self.baudrate>
>> Oct 25 20:00:20 server.mjenks.net weewxd[11717]: weewx[11717] CRITICAL 
>> weewx.engine:   AttributeError: module 'serial' has no attribute 
>> 'Serial'
>> Oct 25 20:00:20 server.mjenks.net weewxd[11717]: weewx[11717] CRITICAL 
>> __main__: Unable to load driver: module 'serial' has no attribute 'Serial'
>> Oct 25 20:00:20 server.mjenks.net weewxd[11717]: weewx[11717] CRITICAL 
>> __main__:   Exiting...
>> Oct 25 20:00:20 server.mjenks.net systemd[1]: weewx.service: Main 
>> process exited, code=exited, status=4/NOPERMISSION
>> Oct 25 20:00:20 server.mjenks.net systemd[1]: weewx.service: Failed with 
>> result 'exit-code'.
>> [root@server ~]# more /etc/udev/rules.d/vantage.rules
>> # udev rules for davis vantage connected via usb
>> #ACTION=="add", SUBSYSTEM=="tty", ATTRS{idVendor}=="10c4", 
>> ATTRS{idProduct}=="ea60", SYMLINK+="vantage"
>>
>> # use this rule if you are using systemd
>> ACTION=="add", SUBSYSTEM=="tty", ATTRS{idVendor}=="10c4", 
>> ATTRS{idProduct}=="ea60", SYMLINK+="vantage", TAG+="systemd", 
>> ENV{SYSTEMD_WANTS}="weewx.service"
>> #ACTION=="add", SUBSYSTEM=="usb", ATTRS{idVendor}=="10c4", 
>> ATTRS{idProduct}=="ea60", SYMLINK+="vantage", TAG+="systemd", 
>> ENV{SYSTEMD_WANTS}="weewx.service"
>>  
>>
>>
>> On Sunday, October 25, 2020 at 7:31:36 PM UTC-5 tke...@gmail.com wrote:
>>
>>> If you use pip to install things while in the WeeWX directory 
>>> /home/weewx, it will see the setup.cfg file there, then try and install 
>>> things in the WeeWX directory system. Take a look in /home/weewx/bin 
>>> and see if serial ended up in there.
>>>
>>> If so, delete it, then cd to some other directory, such as your home 
>>> directory, then try installing. Make sure you use the python3 version of 
>>> pip:
>>>
>>> *cd ~*
>>> *python3 -m pip install pyserial*
>>>
>>> -tk
>>>
>>> On Sun, Oct 25, 2020 at 3:38 PM Mark Jenks  wrote:
>>>
>>>> Never had to do that before..   But just added weewx go dialout group 
>>>> and no change.
>>>>
>>>> On Sunday, October 25, 2020 at 5:16:31 PM UTC-5 ti...@skybase.net 
>>>> wrote:
>>>>
>>>>> Hi Mark, 
>>>>>
>>>>> Does the user, that weewx is running as, belong to the group dialout ? 
>>>>>
>>>>> On linux, a user that wants to use a serial port must belong to the 
>>>>> dialout group. 
>>>>>
>>>>> This

Re: [weewx-user] Re: Upgrade from 3.9.2 to 4.1.1 issues

[Mark Jenks]

I completely removed pyserial using pip and dnf.
Same thing.  Maybe something to do with rules.d?  I tried tty and usb both, 
and get the same thing.

[root@server ~]# systemctl status weewx.service
● weewx.service - weewx weather system
   Loaded: loaded (/usr/lib/systemd/system/weewx.service; enabled; vendor 
preset: disabled)
   Active: failed (Result: exit-code) since Sun 2020-10-25 20:00:20 CDT; 2s 
ago
  Process: 11717 ExecStart=/home/weewx/bin/weewxd /home/weewx/weewx.conf 
(code=exited, status=4)
 Main PID: 11717 (code=exited, status=4)
  CPU: 221ms

Oct 25 20:00:20 server.mjenks.net weewxd[11717]: weewx[11717] CRITICAL 
weewx.engine:   Vantage.__init__(self, 
**config_dict[DRIVER_NAME])
Oct 25 20:00:20 server.mjenks.net weewxd[11717]: weewx[11717] CRITICAL 
weewx.engine: File "/home/weewx/bin/weewx/drivers/vantage.py", 
line 511, >
Oct 25 20:00:20 server.mjenks.net weewxd[11717]: weewx[11717] CRITICAL 
weewx.engine:   self.port.openPort()
Oct 25 20:00:20 server.mjenks.net weewxd[11717]: weewx[11717] CRITICAL 
weewx.engine: File "/home/weewx/bin/weewx/drivers/vantage.py", 
line 307, >
Oct 25 20:00:20 server.mjenks.net weewxd[11717]: weewx[11717] CRITICAL 
weewx.engine:   self.serial_port = serial.Serial(self.port, 
self.baudrate>
Oct 25 20:00:20 server.mjenks.net weewxd[11717]: weewx[11717] CRITICAL 
weewx.engine:   AttributeError: module 'serial' has no attribute 
'Serial'
Oct 25 20:00:20 server.mjenks.net weewxd[11717]: weewx[11717] CRITICAL 
__main__: Unable to load driver: module 'serial' has no attribute 'Serial'
Oct 25 20:00:20 server.mjenks.net weewxd[11717]: weewx[11717] CRITICAL 
__main__:   Exiting...
Oct 25 20:00:20 server.mjenks.net systemd[1]: weewx.service: Main process 
exited, code=exited, status=4/NOPERMISSION
Oct 25 20:00:20 server.mjenks.net systemd[1]: weewx.service: Failed with 
result 'exit-code'.
[root@server ~]# more /etc/udev/rules.d/vantage.rules
# udev rules for davis vantage connected via usb
#ACTION=="add", SUBSYSTEM=="tty", ATTRS{idVendor}=="10c4", 
ATTRS{idProduct}=="ea60", SYMLINK+="vantage"

# use this rule if you are using systemd
ACTION=="add", SUBSYSTEM=="tty", ATTRS{idVendor}=="10c4", 
ATTRS{idProduct}=="ea60", SYMLINK+="vantage", TAG+="systemd", 
ENV{SYSTEMD_WANTS}="weewx.service"
#ACTION=="add", SUBSYSTEM=="usb", ATTRS{idVendor}=="10c4", 
ATTRS{idProduct}=="ea60", SYMLINK+="vantage", TAG+="systemd", 
ENV{SYSTEMD_WANTS}="weewx.service"
 


On Sunday, October 25, 2020 at 7:31:36 PM UTC-5 tke...@gmail.com wrote:

> If you use pip to install things while in the WeeWX directory /home/weewx, 
> it will see the setup.cfg file there, then try and install things in the 
> WeeWX directory system. Take a look in /home/weewx/bin and see if serial 
> ended up in there.
>
> If so, delete it, then cd to some other directory, such as your home 
> directory, then try installing. Make sure you use the python3 version of 
> pip:
>
> *cd ~*
> *python3 -m pip install pyserial*
>
> -tk
>
> On Sun, Oct 25, 2020 at 3:38 PM Mark Jenks  wrote:
>
>> Never had to do that before..   But just added weewx go dialout group and 
>> no change.
>>
>> On Sunday, October 25, 2020 at 5:16:31 PM UTC-5 ti...@skybase.net wrote:
>>
>>> Hi Mark, 
>>>
>>> Does the user, that weewx is running as, belong to the group dialout ? 
>>>
>>> On linux, a user that wants to use a serial port must belong to the 
>>> dialout group. 
>>>
>>> This still applies even if the serial port is via a USB interface. 
>>>
>>> regards 
>>>
>>> Tim 
>>>
>>> On 26/10/20 7:06 am, Mark Jenks wrote: 
>>> > I just did a full stop and start, and I get this.   Permissions? 
>>> > 
>>> > Oct 25 15:04:18 server.mjenks.net weewxd[20245]: weewx[20245] 
>>> CRITICAL 
>>> > weewx.engine:   Vantage.__init__(self, 
>>> > **config_dict[DRIVER_NAM> 
>>> > Oct 25 15:04:18 server.mjenks.net weewxd[20245]: weewx[20245] 
>>> CRITICAL 
>>> > weewx.engine: File 
>>> > "/home/weewx/bin/weewx/drivers/vantage.py", > 
>>> > Oct 25 15:04:18 server.mjenks.net weewxd[20245]: weewx[20245] 
>>> CRITICAL 
>>> > weewx.engine:   self.port.openPort() 
>>> > Oct 25 15:04:18 server.mjenks.net weewxd[20245]: weewx[20245] 
>>> CRITICAL 
>>> > weewx.engine: File 
>>> > 

Re: [weewx-user] Re: Upgrade from 3.9.2 to 4.1.1 issues

[Mark Jenks]

Never had to do that before..   But just added weewx go dialout group and 
no change.

On Sunday, October 25, 2020 at 5:16:31 PM UTC-5 ti...@skybase.net wrote:

> Hi Mark,
>
> Does the user, that weewx is running as, belong to the group dialout ?
>
> On linux, a user that wants to use a serial port must belong to the 
> dialout group.
>
> This still applies even if the serial port is via a USB interface.
>
> regards
>
> Tim
>
> On 26/10/20 7:06 am, Mark Jenks wrote:
> > I just did a full stop and start, and I get this.   Permissions?
> >
> > Oct 25 15:04:18 server.mjenks.net weewxd[20245]: weewx[20245] CRITICAL 
> > weewx.engine:   Vantage.__init__(self, 
> > **config_dict[DRIVER_NAM>
> > Oct 25 15:04:18 server.mjenks.net weewxd[20245]: weewx[20245] CRITICAL 
> > weewx.engine: File 
> > "/home/weewx/bin/weewx/drivers/vantage.py", >
> > Oct 25 15:04:18 server.mjenks.net weewxd[20245]: weewx[20245] CRITICAL 
> > weewx.engine:   self.port.openPort()
> > Oct 25 15:04:18 server.mjenks.net weewxd[20245]: weewx[20245] CRITICAL 
> > weewx.engine: File 
> > "/home/weewx/bin/weewx/drivers/vantage.py", >
> > Oct 25 15:04:18 server.mjenks.net weewxd[20245]: weewx[20245] CRITICAL 
> > weewx.engine:   self.serial_port = 
> > serial.Serial(self.port, sel>
> > Oct 25 15:04:18 server.mjenks.net weewxd[20245]: weewx[20245] CRITICAL 
> > weewx.engine:   AttributeError: module 'serial' has no 
> > attribute 'S>
> > Oct 25 15:04:18 server.mjenks.net weewxd[20245]: weewx[20245] CRITICAL 
> > __main__: Unable to load driver: module 'serial' has no attribute 
> 'Serial'
> > Oct 25 15:04:18 server.mjenks.net weewxd[20245]: weewx[20245] CRITICAL 
> > __main__:   Exiting...
> > Oct 25 15:04:18 server.mjenks.net systemd[1]: weewx.service: Main 
> > process exited, code=exited, status=4/NOPERMISSION
> > Oct 25 15:04:18 server.mjenks.net systemd[1]: weewx.service: Failed 
> > with result 'exit-code'.
> >
> >
>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/e874ea1c-7ca8-41a8-b5c5-043799a7836bn%40googlegroups.com.

Re: [weewx-user] Re: Upgrade from 3.9.2 to 4.1.1 issues

[Mark Jenks]

I just did a full stop and start, and I get this.   Permissions?

Oct 25 15:04:18 server.mjenks.net weewxd[20245]: weewx[20245] CRITICAL 
weewx.engine:   Vantage.__init__(self, **config_dict[DRIVER_NAM>
Oct 25 15:04:18 server.mjenks.net weewxd[20245]: weewx[20245] CRITICAL 
weewx.engine: File "/home/weewx/bin/weewx/drivers/vantage.py", >
Oct 25 15:04:18 server.mjenks.net weewxd[20245]: weewx[20245] CRITICAL 
weewx.engine:   self.port.openPort()
Oct 25 15:04:18 server.mjenks.net weewxd[20245]: weewx[20245] CRITICAL 
weewx.engine: File "/home/weewx/bin/weewx/drivers/vantage.py", >
Oct 25 15:04:18 server.mjenks.net weewxd[20245]: weewx[20245] CRITICAL 
weewx.engine:   self.serial_port = serial.Serial(self.port, sel>
Oct 25 15:04:18 server.mjenks.net weewxd[20245]: weewx[20245] CRITICAL 
weewx.engine:   AttributeError: module 'serial' has no attribute 'S>
Oct 25 15:04:18 server.mjenks.net weewxd[20245]: weewx[20245] CRITICAL 
__main__: Unable to load driver: module 'serial' has no attribute 'Serial'
Oct 25 15:04:18 server.mjenks.net weewxd[20245]: weewx[20245] CRITICAL 
__main__:   Exiting...
Oct 25 15:04:18 server.mjenks.net systemd[1]: weewx.service: Main process 
exited, code=exited, status=4/NOPERMISSION
Oct 25 15:04:18 server.mjenks.net systemd[1]: weewx.service: Failed with 
result 'exit-code'.


I have this set..  I tried tty and usb for SUBSYSTEM..


[root@server rules.d]# more vantage.rules
# udev rules for davis vantage connected via usb
#ACTION=="add", SUBSYSTEM=="tty", ATTRS{idVendor}=="10c4", 
ATTRS{idProduct}=="ea60", SYMLINK+="vantage"

# use this rule if you are using systemd
#ACTION=="add", SUBSYSTEM=="tty", ATTRS{idVendor}=="10c4", 
ATTRS{idProduct}=="ea60", SYMLINK+="vantage", TAG+="systemd", 
ENV{SYSTEMD_WANTS}="weewx.service"
ACTION=="add", SUBSYSTEM=="usb", ATTRS{idVendor}=="10c4", 
ATTRS{idProduct}=="ea60", SYMLINK+="vantage", TAG+="systemd", 
ENV{SYSTEMD_WANTS}="weewx.service"


On Sunday, October 25, 2020 at 3:02:34 PM UTC-5 Mark Jenks wrote:

> That works.  See above.   It's python3
>
> On Sunday, October 25, 2020 at 2:48:58 PM UTC-5 jo...@johnkline.com wrote:
>
>>
>> I’m not sure what OS you are on, but would you try:
>>
>> python3
>> import serial
>>
>> On Oct 25, 2020, at 12:40 PM, Mark Jenks  wrote:
>>
>> This works...
>>
>>
>>
>> [weewx@server ~]$ python
>> Python 3.7.6 (default, Jan 30 2020, 09:44:41)
>> [GCC 9.2.1 20190827 (Red Hat 9.2.1-1)] on linux
>> Type "help", "copyright", "credits" or "license" for more information.
>> >>> import serial
>> >>>
>>
>>
>> On Sunday, October 25, 2020 at 2:10:28 PM UTC-5 Mark Jenks wrote:
>>
>>> I just did this.  No change..
>>>
>>> dnf install python3-pyserial
>>>
>>>
>>> On Sunday, October 25, 2020 at 1:59:28 PM UTC-5 Mark Jenks wrote:
>>>
>>>> pip install pyserial
>>>>
>>>> On Sunday, October 25, 2020 at 1:28:02 PM UTC-5 tke...@gmail.com wrote:
>>>>
>>>>> How did you install pyserial?
>>>>>
>>>>> On Sun, Oct 25, 2020 at 10:00 AM Mark Jenks  
>>>>> wrote:
>>>>>
>>>>>> # The station model, e.g., WMR200, WMR200A, Radio Shack W200
>>>>>> model = Vantage
>>>>>>
>>>>>> # The driver to use:
>>>>>> driver = weewx.drivers.vantage
>>>>>> type = Serial
>>>>>> port = /dev/ttyUSB0
>>>>>>
>>>>>> # The type of LOOP packet to request: 1 = LOOP1; 2 = LOOP2; 3 = 
>>>>>> both
>>>>>> loop_request = 1
>>>>>>
>>>>>>
>>>>>> On Sunday, October 25, 2020 at 11:58:59 AM UTC-5 Mark Jenks wrote:
>>>>>>
>>>>>>> I was running python 2 before, and upgraded to python 3.   Never had 
>>>>>>> an issue until I upgraded to 4.1.1.  
>>>>>>>
>>>>>>> What am I missing?
>>>>>>>
>>>>>>> # python --version
>>>>>>> Python 3.7.6
>>>>>>>
>>>>>>> pyserial is installed.
>>>>>>>
>>>>>>> [root@server bin]# ./wee_device
>>>>>

Re: [weewx-user] Re: Upgrade from 3.9.2 to 4.1.1 issues

[Mark Jenks]

That works.  See above.   It's python3

On Sunday, October 25, 2020 at 2:48:58 PM UTC-5 jo...@johnkline.com wrote:

>
> I’m not sure what OS you are on, but would you try:
>
> python3
> import serial
>
> On Oct 25, 2020, at 12:40 PM, Mark Jenks  wrote:
>
> This works...
>
>
>
> [weewx@server ~]$ python
> Python 3.7.6 (default, Jan 30 2020, 09:44:41)
> [GCC 9.2.1 20190827 (Red Hat 9.2.1-1)] on linux
> Type "help", "copyright", "credits" or "license" for more information.
> >>> import serial
> >>>
>
>
> On Sunday, October 25, 2020 at 2:10:28 PM UTC-5 Mark Jenks wrote:
>
>> I just did this.  No change..
>>
>> dnf install python3-pyserial
>>
>>
>> On Sunday, October 25, 2020 at 1:59:28 PM UTC-5 Mark Jenks wrote:
>>
>>> pip install pyserial
>>>
>>> On Sunday, October 25, 2020 at 1:28:02 PM UTC-5 tke...@gmail.com wrote:
>>>
>>>> How did you install pyserial?
>>>>
>>>> On Sun, Oct 25, 2020 at 10:00 AM Mark Jenks  wrote:
>>>>
>>>>> # The station model, e.g., WMR200, WMR200A, Radio Shack W200
>>>>> model = Vantage
>>>>>
>>>>>     # The driver to use:
>>>>> driver = weewx.drivers.vantage
>>>>> type = Serial
>>>>> port = /dev/ttyUSB0
>>>>>
>>>>> # The type of LOOP packet to request: 1 = LOOP1; 2 = LOOP2; 3 = 
>>>>> both
>>>>> loop_request = 1
>>>>>
>>>>>
>>>>> On Sunday, October 25, 2020 at 11:58:59 AM UTC-5 Mark Jenks wrote:
>>>>>
>>>>>> I was running python 2 before, and upgraded to python 3.   Never had 
>>>>>> an issue until I upgraded to 4.1.1.  
>>>>>>
>>>>>> What am I missing?
>>>>>>
>>>>>> # python --version
>>>>>> Python 3.7.6
>>>>>>
>>>>>> pyserial is installed.
>>>>>>
>>>>>> [root@server bin]# ./wee_device
>>>>>> Using configuration file /home/weewx/weewx.conf
>>>>>> Using Vantage driver version 3.2.1 (weewx.drivers.vantage)
>>>>>> Traceback (most recent call last):
>>>>>>   File "./wee_device", line 78, in 
>>>>>> main()
>>>>>>   File "./wee_device", line 74, in main
>>>>>> device.configure(config_dict)
>>>>>>   File "/home/weewx/bin/weewx/drivers/__init__.py", line 67, in 
>>>>>> configure
>>>>>> self.do_options(options, parser, config_dict, not 
>>>>>> options.noprompt)
>>>>>>   File "/home/weewx/bin/weewx/drivers/vantage.py", line 2055, in 
>>>>>> do_options
>>>>>> station = Vantage(**config_dict[DRIVER_NAME])
>>>>>>   File "/home/weewx/bin/weewx/drivers/vantage.py", line 511, in 
>>>>>> __init__
>>>>>> self.port.openPort()
>>>>>>   File "/home/weewx/bin/weewx/drivers/vantage.py", line 307, in 
>>>>>> openPort
>>>>>> self.serial_port = serial.Serial(self.port, self.baudrate, 
>>>>>> timeout=self.timeout)
>>>>>> AttributeError: module 'serial' has no attribute 'Serial'
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> -- 
>>>>>
>>>>>
>>>>> 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+...@googlegroups.com.
>>>>>
>>>>>
>>>>> To view this discussion on the web visit 
>>>>> https://groups.google.com/d/msgid/weewx-user/77253bab-92be-417c-956d-1fcdc0876293n%40googlegroups.com
>>>>>  
>>>>> <https://groups.google.com/d/msgid/weewx-user/77253bab-92be-417c-956d-1fcdc0876293n%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>>> .
>>>>>
>>>>>
>>>>> -- 
>>>> -tk
>>>>
>>> -- 
> 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+...@googlegroups.com.
>
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/3761c9ce-55d7-44b8-8530-53dceebe7ea6n%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/weewx-user/3761c9ce-55d7-44b8-8530-53dceebe7ea6n%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/732714bf-423d-4e84-8577-d0ea44ac2c78n%40googlegroups.com.

Re: [weewx-user] Re: Upgrade from 3.9.2 to 4.1.1 issues

[Mark Jenks]

This works...

[weewx@server ~]$ python
Python 3.7.6 (default, Jan 30 2020, 09:44:41)
[GCC 9.2.1 20190827 (Red Hat 9.2.1-1)] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import serial
>>>


On Sunday, October 25, 2020 at 2:10:28 PM UTC-5 Mark Jenks wrote:

> I just did this.  No change..
>
> dnf install python3-pyserial
>
>
> On Sunday, October 25, 2020 at 1:59:28 PM UTC-5 Mark Jenks wrote:
>
>> pip install pyserial
>>
>> On Sunday, October 25, 2020 at 1:28:02 PM UTC-5 tke...@gmail.com wrote:
>>
>>> How did you install pyserial?
>>>
>>> On Sun, Oct 25, 2020 at 10:00 AM Mark Jenks  wrote:
>>>
>>>> # The station model, e.g., WMR200, WMR200A, Radio Shack W200
>>>> model = Vantage
>>>>
>>>> # The driver to use:
>>>> driver = weewx.drivers.vantage
>>>> type = Serial
>>>> port = /dev/ttyUSB0
>>>>
>>>> # The type of LOOP packet to request: 1 = LOOP1; 2 = LOOP2; 3 = both
>>>> loop_request = 1
>>>>
>>>>
>>>> On Sunday, October 25, 2020 at 11:58:59 AM UTC-5 Mark Jenks wrote:
>>>>
>>>>> I was running python 2 before, and upgraded to python 3.   Never had 
>>>>> an issue until I upgraded to 4.1.1.  
>>>>>
>>>>> What am I missing?
>>>>>
>>>>> # python --version
>>>>> Python 3.7.6
>>>>>
>>>>> pyserial is installed.
>>>>>
>>>>> [root@server bin]# ./wee_device
>>>>> Using configuration file /home/weewx/weewx.conf
>>>>> Using Vantage driver version 3.2.1 (weewx.drivers.vantage)
>>>>> Traceback (most recent call last):
>>>>>   File "./wee_device", line 78, in 
>>>>> main()
>>>>>   File "./wee_device", line 74, in main
>>>>> device.configure(config_dict)
>>>>>   File "/home/weewx/bin/weewx/drivers/__init__.py", line 67, in 
>>>>> configure
>>>>> self.do_options(options, parser, config_dict, not options.noprompt)
>>>>>   File "/home/weewx/bin/weewx/drivers/vantage.py", line 2055, in 
>>>>> do_options
>>>>> station = Vantage(**config_dict[DRIVER_NAME])
>>>>>   File "/home/weewx/bin/weewx/drivers/vantage.py", line 511, in 
>>>>> __init__
>>>>> self.port.openPort()
>>>>>   File "/home/weewx/bin/weewx/drivers/vantage.py", line 307, in 
>>>>> openPort
>>>>> self.serial_port = serial.Serial(self.port, self.baudrate, 
>>>>> timeout=self.timeout)
>>>>> AttributeError: module 'serial' has no attribute 'Serial'
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> -- 
>>>>
>>>>
>>>> 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+...@googlegroups.com.
>>>>
>>>>
>>>> To view this discussion on the web visit 
>>>> https://groups.google.com/d/msgid/weewx-user/77253bab-92be-417c-956d-1fcdc0876293n%40googlegroups.com
>>>>  
>>>> <https://groups.google.com/d/msgid/weewx-user/77253bab-92be-417c-956d-1fcdc0876293n%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>> .
>>>>
>>>>
>>>> -- 
>>> -tk
>>>
>>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/3761c9ce-55d7-44b8-8530-53dceebe7ea6n%40googlegroups.com.

Re: [weewx-user] Re: Upgrade from 3.9.2 to 4.1.1 issues

[Mark Jenks]

I just did this.  No change..

dnf install python3-pyserial


On Sunday, October 25, 2020 at 1:59:28 PM UTC-5 Mark Jenks wrote:

> pip install pyserial
>
> On Sunday, October 25, 2020 at 1:28:02 PM UTC-5 tke...@gmail.com wrote:
>
>> How did you install pyserial?
>>
>> On Sun, Oct 25, 2020 at 10:00 AM Mark Jenks  wrote:
>>
>>> # The station model, e.g., WMR200, WMR200A, Radio Shack W200
>>> model = Vantage
>>>
>>> # The driver to use:
>>> driver = weewx.drivers.vantage
>>> type = Serial
>>> port = /dev/ttyUSB0
>>>
>>> # The type of LOOP packet to request: 1 = LOOP1; 2 = LOOP2; 3 = both
>>> loop_request = 1
>>>
>>>
>>> On Sunday, October 25, 2020 at 11:58:59 AM UTC-5 Mark Jenks wrote:
>>>
>>>> I was running python 2 before, and upgraded to python 3.   Never had an 
>>>> issue until I upgraded to 4.1.1.  
>>>>
>>>> What am I missing?
>>>>
>>>> # python --version
>>>> Python 3.7.6
>>>>
>>>> pyserial is installed.
>>>>
>>>> [root@server bin]# ./wee_device
>>>> Using configuration file /home/weewx/weewx.conf
>>>> Using Vantage driver version 3.2.1 (weewx.drivers.vantage)
>>>> Traceback (most recent call last):
>>>>   File "./wee_device", line 78, in 
>>>> main()
>>>>   File "./wee_device", line 74, in main
>>>> device.configure(config_dict)
>>>>   File "/home/weewx/bin/weewx/drivers/__init__.py", line 67, in 
>>>> configure
>>>> self.do_options(options, parser, config_dict, not options.noprompt)
>>>>   File "/home/weewx/bin/weewx/drivers/vantage.py", line 2055, in 
>>>> do_options
>>>> station = Vantage(**config_dict[DRIVER_NAME])
>>>>   File "/home/weewx/bin/weewx/drivers/vantage.py", line 511, in __init__
>>>> self.port.openPort()
>>>>   File "/home/weewx/bin/weewx/drivers/vantage.py", line 307, in openPort
>>>> self.serial_port = serial.Serial(self.port, self.baudrate, 
>>>> timeout=self.timeout)
>>>> AttributeError: module 'serial' has no attribute 'Serial'
>>>>
>>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> -- 
>>>
>>>
>>> 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+...@googlegroups.com.
>>>
>>>
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/weewx-user/77253bab-92be-417c-956d-1fcdc0876293n%40googlegroups.com
>>>  
>>> <https://groups.google.com/d/msgid/weewx-user/77253bab-92be-417c-956d-1fcdc0876293n%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>>
>>>
>>> -- 
>> -tk
>>
>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/075ce5e6-e220-43c9-8598-9689bfc6825en%40googlegroups.com.

Re: [weewx-user] Re: Upgrade from 3.9.2 to 4.1.1 issues

[Mark Jenks]

pip install pyserial

On Sunday, October 25, 2020 at 1:28:02 PM UTC-5 tke...@gmail.com wrote:

> How did you install pyserial?
>
> On Sun, Oct 25, 2020 at 10:00 AM Mark Jenks  wrote:
>
>> # The station model, e.g., WMR200, WMR200A, Radio Shack W200
>> model = Vantage
>>
>> # The driver to use:
>> driver = weewx.drivers.vantage
>> type = Serial
>> port = /dev/ttyUSB0
>>
>> # The type of LOOP packet to request: 1 = LOOP1; 2 = LOOP2; 3 = both
>> loop_request = 1
>>
>>
>> On Sunday, October 25, 2020 at 11:58:59 AM UTC-5 Mark Jenks wrote:
>>
>>> I was running python 2 before, and upgraded to python 3.   Never had an 
>>> issue until I upgraded to 4.1.1.  
>>>
>>> What am I missing?
>>>
>>> # python --version
>>> Python 3.7.6
>>>
>>> pyserial is installed.
>>>
>>> [root@server bin]# ./wee_device
>>> Using configuration file /home/weewx/weewx.conf
>>> Using Vantage driver version 3.2.1 (weewx.drivers.vantage)
>>> Traceback (most recent call last):
>>>   File "./wee_device", line 78, in 
>>> main()
>>>   File "./wee_device", line 74, in main
>>> device.configure(config_dict)
>>>   File "/home/weewx/bin/weewx/drivers/__init__.py", line 67, in configure
>>> self.do_options(options, parser, config_dict, not options.noprompt)
>>>   File "/home/weewx/bin/weewx/drivers/vantage.py", line 2055, in 
>>> do_options
>>> station = Vantage(**config_dict[DRIVER_NAME])
>>>   File "/home/weewx/bin/weewx/drivers/vantage.py", line 511, in __init__
>>> self.port.openPort()
>>>   File "/home/weewx/bin/weewx/drivers/vantage.py", line 307, in openPort
>>> self.serial_port = serial.Serial(self.port, self.baudrate, 
>>> timeout=self.timeout)
>>> AttributeError: module 'serial' has no attribute 'Serial'
>>>
>>>
>>
>>
>>
>>
>>
>>
>>
>> -- 
>>
>>
>> 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+...@googlegroups.com.
>>
>>
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/77253bab-92be-417c-956d-1fcdc0876293n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/77253bab-92be-417c-956d-1fcdc0876293n%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>>
>> -- 
> -tk
>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/c2df37aa-a5b2-4534-8583-4e28c0f2c69en%40googlegroups.com.

[weewx-user] Re: Upgrade from 3.9.2 to 4.1.1 issues

[Mark Jenks]

# The station model, e.g., WMR200, WMR200A, Radio Shack W200
model = Vantage

# The driver to use:
driver = weewx.drivers.vantage
type = Serial
port = /dev/ttyUSB0

# The type of LOOP packet to request: 1 = LOOP1; 2 = LOOP2; 3 = both
loop_request = 1


On Sunday, October 25, 2020 at 11:58:59 AM UTC-5 Mark Jenks wrote:

> I was running python 2 before, and upgraded to python 3.   Never had an 
> issue until I upgraded to 4.1.1.  
>
> What am I missing?
>
> # python --version
> Python 3.7.6
>
> pyserial is installed.
>
> [root@server bin]# ./wee_device
> Using configuration file /home/weewx/weewx.conf
> Using Vantage driver version 3.2.1 (weewx.drivers.vantage)
> Traceback (most recent call last):
>   File "./wee_device", line 78, in 
> main()
>   File "./wee_device", line 74, in main
> device.configure(config_dict)
>   File "/home/weewx/bin/weewx/drivers/__init__.py", line 67, in configure
> self.do_options(options, parser, config_dict, not options.noprompt)
>   File "/home/weewx/bin/weewx/drivers/vantage.py", line 2055, in do_options
> station = Vantage(**config_dict[DRIVER_NAME])
>   File "/home/weewx/bin/weewx/drivers/vantage.py", line 511, in __init__
> self.port.openPort()
>   File "/home/weewx/bin/weewx/drivers/vantage.py", line 307, in openPort
> self.serial_port = serial.Serial(self.port, self.baudrate, 
> timeout=self.timeout)
> AttributeError: module 'serial' has no attribute 'Serial'
>
>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/77253bab-92be-417c-956d-1fcdc0876293n%40googlegroups.com.

[weewx-user] Upgrade from 3.9.2 to 4.1.1 issues

[Mark Jenks]

I was running python 2 before, and upgraded to python 3.   Never had an 
issue until I upgraded to 4.1.1.  

What am I missing?

# python --version
Python 3.7.6

pyserial is installed.

[root@server bin]# ./wee_device
Using configuration file /home/weewx/weewx.conf
Using Vantage driver version 3.2.1 (weewx.drivers.vantage)
Traceback (most recent call last):
  File "./wee_device", line 78, in 
main()
  File "./wee_device", line 74, in main
device.configure(config_dict)
  File "/home/weewx/bin/weewx/drivers/__init__.py", line 67, in configure
self.do_options(options, parser, config_dict, not options.noprompt)
  File "/home/weewx/bin/weewx/drivers/vantage.py", line 2055, in do_options
station = Vantage(**config_dict[DRIVER_NAME])
  File "/home/weewx/bin/weewx/drivers/vantage.py", line 511, in __init__
self.port.openPort()
  File "/home/weewx/bin/weewx/drivers/vantage.py", line 307, in openPort
self.serial_port = serial.Serial(self.port, self.baudrate, 
timeout=self.timeout)
AttributeError: module 'serial' has no attribute 'Serial'

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/9dd3cff9-1660-4d09-a7d3-2ee80ebc93a5n%40googlegroups.com.

[weewx-user] Re: Seasons Skin timestamps

[Mark Jenks]

Thanks, I didn't even see those things.  Now I do.

As for the other one, If I click on month, it shows me the daily.  It's 
been so long I forgot about it.  :)

On Tuesday, April 9, 2019 at 6:51:13 PM UTC-5, mwall wrote:
>
>
>
> On Tuesday, April 9, 2019 at 7:43:24 PM UTC-4, Mark Jenks wrote:
>>
>> Why was the time removed from daily for the highs and lows?   Any way to 
>> bring them back without going back to Standard?
>>
>  
> put the cursor over the value.  or click on the 'High/Low' text to see it 
> all at once.
>
>
> Also, is there a way to see hourly stats instead of just Weekly or Monthly?
>>
>
>  not sure what you're asking for.  the 'day' plots show that information - 
> just look at the vertical line above each hour.
>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Seasons Skin timestamps

[Mark Jenks]

Also, the Wind only shows degrees.   In Standard it show SSW, SW, W, etc 
next to it.



On Tuesday, April 9, 2019 at 6:43:24 PM UTC-5, Mark Jenks wrote:
>
> Why was the time removed from daily for the highs and lows?   Any way to 
> bring them back without going back to Standard?
>
> Also, is there a way to see hourly stats instead of just Weekly or Monthly?
>
> -Mark
>
> High Temperature
> Low Temperature 55.5°F at 02:15:21 PM
> 37.4°F at 04:51:05 AM
> High Heat Index
> Low Wind Chill 55.5°F at 02:15:21 PM
> 31.8°F at 05:58:24 AM
> High Humidity
> Low Humidity 90% at 04:04:59 AM
> 45% at 02:02:54 PM
> High Dewpoint
> Low Dewpoint 41.6°F at 11:39:02 AM
> 25.6°F at 06:34:09 PM
> High Barometer
> Low Barometer 29.945 inHg at 06:29:03 PM
> 29.801 inHg at 01:07:02 PM
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Seasons Skin timestamps

[Mark Jenks]

Why was the time removed from daily for the highs and lows?   Any way to 
bring them back without going back to Standard?

Also, is there a way to see hourly stats instead of just Weekly or Monthly?

-Mark

High Temperature
Low Temperature 55.5°F at 02:15:21 PM
37.4°F at 04:51:05 AM
High Heat Index
Low Wind Chill 55.5°F at 02:15:21 PM
31.8°F at 05:58:24 AM
High Humidity
Low Humidity 90% at 04:04:59 AM
45% at 02:02:54 PM
High Dewpoint
Low Dewpoint 41.6°F at 11:39:02 AM
25.6°F at 06:34:09 PM
High Barometer
Low Barometer 29.945 inHg at 06:29:03 PM
29.801 inHg at 01:07:02 PM

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: New Station Question

[Mark Jenks]

That last issue cleared up today. It must not generate the Sensor Status as 
much as the other stuff on the page.

-Mark

On Saturday, March 30, 2019 at 7:44:00 PM UTC-5, Mark Jenks wrote:
>
> Looks like it so far.   It's creating Day.png files that are accurate now.
>
> Only thing I still see is, but I don't know if it's normal.:
> Transmitter Battery OK
> Wind Battery LOW
> Rain Battery LOW
> Outside Temperature Battery LOW 
> On Saturday, March 30, 2019 at 5:55:12 PM UTC-5, gjr80 wrote:
>>
>> So it's working as it should?
>>
>> Gary
>>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: New Station Question

[Mark Jenks]

Looks like it so far.   It's creating Day.png files that are accurate now.

Only thing I still see is, but I don't know if it's normal.:
Transmitter Battery OK
Wind Battery LOW
Rain Battery LOW
Outside Temperature Battery LOW 
On Saturday, March 30, 2019 at 5:55:12 PM UTC-5, gjr80 wrote:
>
> So it's working as it should?
>
> Gary
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: New Station Question

[Mark Jenks]

Okay, update!I changed the station to 300 with wee_device and removed 
day*.png.  Then I restarted Weewx..

It's not generating daily graphs.So, guessing it was setting both to 
300.

Thanks!

-Mark


On Saturday, March 30, 2019 at 5:21:24 PM UTC-5, Mark Jenks wrote:
>
> weewx.conf was 300.  I just did the wee_device to change the other side.  
>   I will remove the plot images and see what is created now.
>
> -Mark
>
>
> On Saturday, March 30, 2019 at 4:47:06 PM UTC-5, gjr80 wrote:
>>
>> Hi ,
>>
>> Davis stations ship with a default 30 minute archive period, that means 
>> archive records are saved and reports/images generated every 30 minutes, 
>> probably not want you want. If so,  you need to change the archive interval 
>> under [StdArchive] in weewx.conf. You also need to change the archive 
>> interval on the console to match. 5 minutes is commonly used. This can be 
>> done either via the console front panel or via the utility wee_device using 
>> the --set-interval action (
>> http://www.weewx.com/docs/hardware.htm#vantage_notes).
>>
>> Davis stations emit loop packets every 2.5 odd seconds so what you see is 
>> expected. The plots will be updated at different rates; day plots should be 
>> updated each report cycle, week every hour, month every 3 hours and year 
>> every 24 hours. You can force all plots to be regenerated on the next 
>> report cycle by deleteing the plot image files.
>>
>> I suggest you get a reasonable archive interval in place then delete the 
>> plot image files and take it from there.
>>
>> Gary
>>
>>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: New Station Question

[Mark Jenks]

weewx.conf was 300.  I just did the wee_device to change the other side.
I will remove the plot images and see what is created now.

-Mark


On Saturday, March 30, 2019 at 4:47:06 PM UTC-5, gjr80 wrote:
>
> Hi ,
>
> Davis stations ship with a default 30 minute archive period, that means 
> archive records are saved and reports/images generated every 30 minutes, 
> probably not want you want. If so,  you need to change the archive interval 
> under [StdArchive] in weewx.conf. You also need to change the archive 
> interval on the console to match. 5 minutes is commonly used. This can be 
> done either via the console front panel or via the utility wee_device using 
> the --set-interval action (
> http://www.weewx.com/docs/hardware.htm#vantage_notes).
>
> Davis stations emit loop packets every 2.5 odd seconds so what you see is 
> expected. The plots will be updated at different rates; day plots should be 
> updated each report cycle, week every hour, month every 3 hours and year 
> every 24 hours. You can force all plots to be regenerated on the next 
> report cycle by deleteing the plot image files.
>
> I suggest you get a reasonable archive interval in place then delete the 
> plot image files and take it from there.
>
> Gary
>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: New Station Question

[Mark Jenks]

Okay, more information.I am getting a imagegenerator every 30 mins, and 
only seems to be updating the week graphs.

The Daily's are not getting updated.

-Mark


On Saturday, March 30, 2019 at 10:45:44 AM UTC-5, Mark Jenks wrote:
>
> I just changed from the WMR200 and bought a Davis Vantage.
>
> I changed weewx.conf to use the right driver and I'm getting data on the 
> html in the current section, but...
>
> It's not generating graphs at all with the new data.  Do I need to change 
> something else?
>
> Also, I noticed that this seems to reading wrong too?  Lists the 
> individual WMR components still, along with the new ones.
>
> -Mark
>
> Sensor Status <http://weather.mjenks.net/telemetry.html>♦
> Connectivity
> Signal Quality 100%
> Battery Status
> Transmitter Battery OK
> Wind Battery LOW
> Rain Battery LOW
> Outside Temperature Battery LOW
> Voltage
> Console Battery 4.9 V
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: New Station Question

[Mark Jenks]

Also, I am getting a packet every 2 seconds.  Not sure how normal that is 
with the Vantage?

Mar 30 11:17:16 server weewx[10304]: engine: Initializing weewx version 
3.9.1
Mar 30 11:17:16 server weewx[10304]: engine: Using Python 2.7.5 (default, 
Apr 10 2015, 08:09:05)
[GCC 4.8.3 20140911 (Red Hat 4.8.3-7)]
Mar 30 11:17:16 server weewx[10304]: engine: Platform 
Linux-3.19.8-100.fc20.x86_64-x86_64-with-fedora-20-Heisenbug
Mar 30 11:17:16 server weewx[10304]: engine: Locale is 'en_US.UTF-8'
Mar 30 11:17:16 server weewx[10304]: engine: Using configuration file 
/home/weewx/weewx.conf
Mar 30 11:17:16 server weewx[10304]: engine: Loading station type Vantage 
(weewx.drivers.vantage)
Mar 30 11:17:16 server weewx[10304]: engine: StdConvert target unit is 0x1
Mar 30 11:17:16 server weewx[10304]: wxcalculate: The following values will 
be calculated: barometer=prefer_hardware, windchill=software, 
dewpoint=prefer_hardware, appTemp=prefer_hardware, 
rainRate=prefer_hardware, windrun=prefer_hardware, 
heatindex=prefer_hardware, maxSolarRad=prefer_hardware, 
humidex=prefer_hardware, pressure=prefer_hardware, 
inDewpoint=prefer_hardware, ET=prefer_hardware, altimeter=prefer_hardware, 
cloudbase=prefer_hardware
Mar 30 11:17:16 server weewx[10304]: wxcalculate: The following algorithms 
will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
Mar 30 11:17:16 server weewx[10304]: engine: Archive will use data binding 
wx_binding
Mar 30 11:17:16 server weewx[10304]: engine: Record generation will be 
attempted in 'hardware'
Mar 30 11:17:16 server weewx[10304]: engine: The archive interval in the 
configuration file (300) does not match the station hardware interval 
(1800).
Mar 30 11:17:16 server weewx[10304]: engine: Using archive interval of 1800 
seconds (specified by hardware)
Mar 30 11:17:16 server weewx[10304]: engine: Using binding 'wx_binding' to 
database 'weewx'
Mar 30 11:17:16 server weewx[10304]: manager: Starting backfill of daily 
summaries
Mar 30 11:17:16 server weewx[10304]: restx: StationRegistry: Station will 
be registered.
Mar 30 11:17:16 server weewx[10304]: restx: Wunderground-PWS: Data for 
station KWISEYMO2 will be posted
Mar 30 11:17:16 server weewx[10304]: restx: PWSWeather: Data for station 
SEYMOURWI will be posted
Mar 30 11:17:16 server weewx[10304]: restx: CWOP: Data for station DW7584 
will be posted
Mar 30 11:17:16 server weewx[10304]: restx: WOW: Posting not enabled.
Mar 30 11:17:16 server weewx[10304]: restx: AWEKAS: Data will be uploaded 
for user markjenks
Mar 30 11:17:16 server weewx[10304]: engine: Starting up weewx version 3.9.1
Mar 30 11:17:16 server weewx[10304]: engine: Clock error is 0.32 seconds 
(positive is fast)
Mar 30 11:17:16 server weewx[10304]: engine: Starting main packet loop.


On Saturday, March 30, 2019 at 11:09:24 AM UTC-5, peterq...@gmail.com wrote:
>
> What does the log show?
>
> tail -f /var/log/syslog
>
>
> On Saturday, March 30, 2019 at 8:45:44 AM UTC-7, Mark Jenks wrote:
>>
>> I just changed from the WMR200 and bought a Davis Vantage.
>>
>> I changed weewx.conf to use the right driver and I'm getting data on the 
>> html in the current section, but...
>>
>> It's not generating graphs at all with the new data.  Do I need to change 
>> something else?
>>
>> Also, I noticed that this seems to reading wrong too?  Lists the 
>> individual WMR components still, along with the new ones.
>>
>> -Mark
>>
>> Sensor Status <http://weather.mjenks.net/telemetry.html>♦
>> Connectivity
>> Signal Quality 100%
>> Battery Status
>> Transmitter Battery OK
>> Wind Battery LOW
>> Rain Battery LOW
>> Outside Temperature Battery LOW
>> Voltage
>> Console Battery 4.9 V
>>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: New Station Question

[Mark Jenks]

I don't show imagegenerator running for the last 45 mins..

-Mark


On Saturday, March 30, 2019 at 11:09:24 AM UTC-5, peterq...@gmail.com wrote:
>
> What does the log show?
>
> tail -f /var/log/syslog
>
>
> On Saturday, March 30, 2019 at 8:45:44 AM UTC-7, Mark Jenks wrote:
>>
>> I just changed from the WMR200 and bought a Davis Vantage.
>>
>> I changed weewx.conf to use the right driver and I'm getting data on the 
>> html in the current section, but...
>>
>> It's not generating graphs at all with the new data.  Do I need to change 
>> something else?
>>
>> Also, I noticed that this seems to reading wrong too?  Lists the 
>> individual WMR components still, along with the new ones.
>>
>> -Mark
>>
>> Sensor Status <http://weather.mjenks.net/telemetry.html>♦
>> Connectivity
>> Signal Quality 100%
>> Battery Status
>> Transmitter Battery OK
>> Wind Battery LOW
>> Rain Battery LOW
>> Outside Temperature Battery LOW
>> Voltage
>> Console Battery 4.9 V
>>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] New Station Question

[Mark Jenks]

I just changed from the WMR200 and bought a Davis Vantage.

I changed weewx.conf to use the right driver and I'm getting data on the 
html in the current section, but...

It's not generating graphs at all with the new data.  Do I need to change 
something else?

Also, I noticed that this seems to reading wrong too?  Lists the individual 
WMR components still, along with the new ones.

-Mark

Sensor Status ♦
Connectivity
Signal Quality 100%
Battery Status
Transmitter Battery OK
Wind Battery LOW
Rain Battery LOW
Outside Temperature Battery LOW
Voltage
Console Battery 4.9 V

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Weewx crash catcher

[Mark Jenks]

Crashing has a different message now.   Before a week ago, I was still 
running 3.8.1, and was still catching crashes with my script. 

I don't know if I can go back that far, but I think this is closer to my 
problem why I wrote the script.

-Mark


Mar  3 04:44:37 server weewx[7844]: wmr200: Thread-2: E read_device() USB 
Error Reason:[Errno 110] Operation timed out
Mar  3 04:44:37 server weewx[7844]: wmr200: Thread-2: E USB device read 
error
Mar  3 04:44:37 server weewxd: LOOP:   2019-03-03 04:43:50 CST 
(1551609Exception in thread Thread-2:
Mar  3 04:44:37 server weewxd: Traceback (most recent call last):
Mar  3 04:44:37 server weewxd: File "/usr/lib64/python2.7/threading.py", 
line 811, in __bootstrap_inner
Mar  3 04:44:37 server weewxd: self.run()
Mar  3 04:44:37 server weewxd: File 
"/home/weewx/bin/weewx/drivers/wmr200.py", line 1278, in run
Mar  3 04:44:37 server weewxd: buf = self.usb_device.read_device()
Mar  3 04:44:37 server weewxd: File 
"/home/weewx/bin/weewx/drivers/wmr200.py", line 285, in read_device
Mar  3 04:44:37 server weewxd: raise weewx.WeeWxIOError(msg)
Mar  3 04:44:37 server weewxd: WeeWxIOError: read_device() USB Error 
Reason:[Errno 110] Operation timed out
Mar  3 04:44:38 server weewx[7844]: wmr200: MainThread: E USB polling 
thread unexpectedly terminated
Mar  3 04:44:38 server weewx[7844]: engine: Main loop exiting. Shutting 
engine down.
Mar  3 04:44:38 server weewx[7844]: engine: Shutting down StdReport thread


On Friday, March 1, 2019 at 5:11:13 PM UTC-6, Thomas Keffer wrote:
>
> OK, see this post 
> <https://groups.google.com/d/msg/weewx-user/69RvQnD_OQc/M_8q8sDoAgAJ>.
>
> -tk
>
> On Fri, Mar 1, 2019 at 1:53 PM Mark Jenks  > wrote:
>
>> Yes, it is a WMR200.   Eventually changed for something newer in a few 
>> months.
>>
>> -Mark
>>
>>
>> On Tuesday, February 26, 2019 at 6:49:13 AM UTC-6, Thomas Keffer wrote:
>>>
>>> Is this, by any chance, a WMR200 or WS28xx?
>>>
>>> -tk
>>>
>>> On Tue, Feb 26, 2019 at 4:30 AM Mark Jenks  wrote:
>>>
>>>> Got one last night
>>>>
>>>> Feb 25 22:29:41 server weewx[7721]: wmr200: MainThread: I Driver 
>>>> gracefully exiting
>>>> Feb 25 22:29:41 server weewx[7721]: engine: Caught unrecoverable 
>>>> exception in engine:
>>>> Feb 25 22:29:41 server weewx[7721]:   Non-positive value for record 
>>>> field 'interval': 0
>>>> Feb 25 22:29:41 server weewx[7721]:   Traceback (most recent call 
>>>> last):
>>>> Feb 25 22:29:41 server weewx[7721]: File 
>>>> "/home/weewx/bin/weewx/engine.py", line 890, in main
>>>> Feb 25 22:29:41 server weewx[7721]:   engine.run()
>>>> Feb 25 22:29:41 server weewx[7721]: File 
>>>> "/home/weewx/bin/weewx/engine.py", line 160, in run
>>>> Feb 25 22:29:41 server weewx[7721]:   
>>>> self.dispatchEvent(weewx.Event(weewx.STARTUP))
>>>> Feb 25 22:29:41 server weewx[7721]: File 
>>>> "/home/weewx/bin/weewx/engine.py", line 224, in dispatchEvent
>>>> Feb 25 22:29:41 server weewx[7721]:   callback(event)
>>>> Feb 25 22:29:41 server weewx[7721]: File 
>>>> "/home/weewx/bin/weewx/engine.py", line 520, in startup
>>>> Feb 25 22:29:41 server weewx[7721]:   
>>>> self._catchup(self.engine.console.genStartupRecords)
>>>> Feb 25 22:29:41 server weewx[7721]: File 
>>>> "/home/weewx/bin/weewx/engine.py", line 635, in _catchup
>>>> Feb 25 22:29:41 server weewx[7721]:   origin='hardware'))
>>>> Feb 25 22:29:41 server weewx[7721]: File 
>>>> "/home/weewx/bin/weewx/engine.py", line 224, in dispatchEvent
>>>> Feb 25 22:29:41 server weewx[7721]:   callback(event)
>>>> Feb 25 22:29:41 server weewx[7721]: File 
>>>> "/home/weewx/bin/weewx/engine.py", line 601, in new_archive_record
>>>> Feb 25 22:29:41 server weewx[7721]:   
>>>> dbmanager.addRecord(event.record, accumulator=self.old_accumulator)
>>>> Feb 25 22:29:41 server weewx[7721]: File 
>>>> "/home/weewx/bin/weewx/manager.py", line 246, in addRecord
>>>> Feb 25 22:29:41 server weewx[7721]:   
>>>> self._addSingleRecord(record, cursor, log_level)
>>>> Feb 25 22:29:41 server weewx[7721]: File 
>>>> "/home/weewx/bin/weewx/manager.py", line 1212, in _addSingleRecord
>>>> Feb 25

Re: [weewx-user] Re: Weewx crash catcher

[Mark Jenks]

Yes, it is a WMR200.   Eventually changed for something newer in a few 
months.

-Mark


On Tuesday, February 26, 2019 at 6:49:13 AM UTC-6, Thomas Keffer wrote:
>
> Is this, by any chance, a WMR200 or WS28xx?
>
> -tk
>
> On Tue, Feb 26, 2019 at 4:30 AM Mark Jenks  > wrote:
>
>> Got one last night
>>
>> Feb 25 22:29:41 server weewx[7721]: wmr200: MainThread: I Driver 
>> gracefully exiting
>> Feb 25 22:29:41 server weewx[7721]: engine: Caught unrecoverable 
>> exception in engine:
>> Feb 25 22:29:41 server weewx[7721]:   Non-positive value for record 
>> field 'interval': 0
>> Feb 25 22:29:41 server weewx[7721]:   Traceback (most recent call 
>> last):
>> Feb 25 22:29:41 server weewx[7721]: File 
>> "/home/weewx/bin/weewx/engine.py", line 890, in main
>> Feb 25 22:29:41 server weewx[7721]:   engine.run()
>> Feb 25 22:29:41 server weewx[7721]: File 
>> "/home/weewx/bin/weewx/engine.py", line 160, in run
>> Feb 25 22:29:41 server weewx[7721]:   
>> self.dispatchEvent(weewx.Event(weewx.STARTUP))
>> Feb 25 22:29:41 server weewx[7721]: File 
>> "/home/weewx/bin/weewx/engine.py", line 224, in dispatchEvent
>> Feb 25 22:29:41 server weewx[7721]:   callback(event)
>> Feb 25 22:29:41 server weewx[7721]: File 
>> "/home/weewx/bin/weewx/engine.py", line 520, in startup
>> Feb 25 22:29:41 server weewx[7721]:   
>> self._catchup(self.engine.console.genStartupRecords)
>> Feb 25 22:29:41 server weewx[7721]: File 
>> "/home/weewx/bin/weewx/engine.py", line 635, in _catchup
>> Feb 25 22:29:41 server weewx[7721]:   origin='hardware'))
>> Feb 25 22:29:41 server weewx[7721]: File 
>> "/home/weewx/bin/weewx/engine.py", line 224, in dispatchEvent
>> Feb 25 22:29:41 server weewx[7721]:   callback(event)
>> Feb 25 22:29:41 server weewx[7721]: File 
>> "/home/weewx/bin/weewx/engine.py", line 601, in new_archive_record
>> Feb 25 22:29:41 server weewx[7721]:   
>> dbmanager.addRecord(event.record, accumulator=self.old_accumulator)
>> Feb 25 22:29:41 server weewx[7721]: File 
>> "/home/weewx/bin/weewx/manager.py", line 246, in addRecord
>> Feb 25 22:29:41 server weewx[7721]:   
>> self._addSingleRecord(record, cursor, log_level)
>> Feb 25 22:29:41 server weewx[7721]: File 
>> "/home/weewx/bin/weewx/manager.py", line 1212, in _addSingleRecord
>> Feb 25 22:29:41 server weewx[7721]:   _weight = 
>> self._calc_weight(record)
>> Feb 25 22:29:41 server weewx[7721]: File 
>> "/home/weewx/bin/weewx/manager.py", line 1582, in _calc_weight
>> Feb 25 22:29:41 server weewx[7721]:   raise 
>> ValueError("Non-positive value for record field 'interval': %s" % 
>> (record['interval'], ))
>> Feb 25 22:29:41 server weewx[7721]:   ValueError: Non-positive value 
>> for record field 'interval': 0
>> Feb 25 22:29:41 server weewx[7721]:   Exiting.
>>
>>
>> On Saturday, February 23, 2019 at 4:34:06 PM UTC-6, mwall wrote:
>>>
>>> On Saturday, February 23, 2019 at 10:36:45 AM UTC-5, Mark Jenks wrote:
>>>>
>>>> I've been running this for a few years now, and once and awhile weewx 
>>>> just falls over for no good reason.   To deal with this, I wrote a script 
>>>> that I run in cron to check to make sure it's running, and if not, start 
>>>> it 
>>>> over again.
>>>>
>>>
>>> mark,
>>>
>>> systemctl is supposed to do that for you.
>>>
>>> in fact, this thread shows that it does, at least in one case:
>>>
>>> https://groups.google.com/forum/#!topic/weewx-user/bspZEoGqpyY
>>>
>>> but as tom points out, we really want to know when weewx stops running 
>>> so that we can fix it.
>>>
>>> if you need to use a script (or systemctl) to ensure that weewx is 
>>> automatically restarted, perhaps you could figure out some way to capture 
>>> and report the log leading up to the crash?
>>>
>>> m
>>>
>>> -- 
>> 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+...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Weewx crash catcher

[Mark Jenks]

Got one last night

Feb 25 22:29:41 server weewx[7721]: wmr200: MainThread: I Driver gracefully 
exiting
Feb 25 22:29:41 server weewx[7721]: engine: Caught unrecoverable exception 
in engine:
Feb 25 22:29:41 server weewx[7721]:   Non-positive value for record 
field 'interval': 0
Feb 25 22:29:41 server weewx[7721]:   Traceback (most recent call last):
Feb 25 22:29:41 server weewx[7721]: File 
"/home/weewx/bin/weewx/engine.py", line 890, in main
Feb 25 22:29:41 server weewx[7721]:   engine.run()
Feb 25 22:29:41 server weewx[7721]: File 
"/home/weewx/bin/weewx/engine.py", line 160, in run
Feb 25 22:29:41 server weewx[7721]:   
self.dispatchEvent(weewx.Event(weewx.STARTUP))
Feb 25 22:29:41 server weewx[7721]: File 
"/home/weewx/bin/weewx/engine.py", line 224, in dispatchEvent
Feb 25 22:29:41 server weewx[7721]:   callback(event)
Feb 25 22:29:41 server weewx[7721]: File 
"/home/weewx/bin/weewx/engine.py", line 520, in startup
Feb 25 22:29:41 server weewx[7721]:   
self._catchup(self.engine.console.genStartupRecords)
Feb 25 22:29:41 server weewx[7721]: File 
"/home/weewx/bin/weewx/engine.py", line 635, in _catchup
Feb 25 22:29:41 server weewx[7721]:   origin='hardware'))
Feb 25 22:29:41 server weewx[7721]: File 
"/home/weewx/bin/weewx/engine.py", line 224, in dispatchEvent
Feb 25 22:29:41 server weewx[7721]:   callback(event)
Feb 25 22:29:41 server weewx[7721]: File 
"/home/weewx/bin/weewx/engine.py", line 601, in new_archive_record
Feb 25 22:29:41 server weewx[7721]:   
dbmanager.addRecord(event.record, accumulator=self.old_accumulator)
Feb 25 22:29:41 server weewx[7721]: File 
"/home/weewx/bin/weewx/manager.py", line 246, in addRecord
Feb 25 22:29:41 server weewx[7721]:   self._addSingleRecord(record, 
cursor, log_level)
Feb 25 22:29:41 server weewx[7721]: File 
"/home/weewx/bin/weewx/manager.py", line 1212, in _addSingleRecord
Feb 25 22:29:41 server weewx[7721]:   _weight = 
self._calc_weight(record)
Feb 25 22:29:41 server weewx[7721]: File 
"/home/weewx/bin/weewx/manager.py", line 1582, in _calc_weight
Feb 25 22:29:41 server weewx[7721]:   raise 
ValueError("Non-positive value for record field 'interval': %s" % 
(record['interval'], ))
Feb 25 22:29:41 server weewx[7721]:   ValueError: Non-positive value 
for record field 'interval': 0
Feb 25 22:29:41 server weewx[7721]:   Exiting.


On Saturday, February 23, 2019 at 4:34:06 PM UTC-6, mwall wrote:
>
> On Saturday, February 23, 2019 at 10:36:45 AM UTC-5, Mark Jenks wrote:
>>
>> I've been running this for a few years now, and once and awhile weewx 
>> just falls over for no good reason.   To deal with this, I wrote a script 
>> that I run in cron to check to make sure it's running, and if not, start it 
>> over again.
>>
>
> mark,
>
> systemctl is supposed to do that for you.
>
> in fact, this thread shows that it does, at least in one case:
>
> https://groups.google.com/forum/#!topic/weewx-user/bspZEoGqpyY
>
> but as tom points out, we really want to know when weewx stops running so 
> that we can fix it.
>
> if you need to use a script (or systemctl) to ensure that weewx is 
> automatically restarted, perhaps you could figure out some way to capture 
> and report the log leading up to the crash?
>
> m
>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: New weather station opinions?

[Mark Jenks]

I've had my WMR for 8-9 years.  It looks horrid.  lol


On Saturday, February 23, 2019 at 12:57:27 PM UTC-6, vince wrote:
>
> On Saturday, February 23, 2019 at 9:37:41 AM UTC-8, rich T wrote:
>>
>> Might to check here:
>>
>>
>> https://www.scaledinstruments.com/product-category/davis-instruments/complete-weather-stations/
>>
>>>
>>>
> Yup - they're the other great 3rd party seller.   I bought my replacement 
> VP2 anemometer there.  (oooh - replacement solar panel for $25 now - I'm on 
> it.  My VP2 panel is pretty horrid looking after 10+ years in service, 
> although it works great)
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Weewx crash catcher

[Mark Jenks]

It doesn't do it often, but I think it had a hardware issue with the usb.  
It could be the OS that I'm on also..

Better 

On Saturday, February 23, 2019 at 10:00:49 AM UTC-6, Thomas Keffer wrote:
>
> Mark,
>
> WeeWX should not crash. If it does, it's a bug. I have successfully run it 
> for 2 years at a time.
>
> The next time it does, please post the system log. Far better to engineer 
> out the point of failure.
>
> -tk
>
> On Sat, Feb 23, 2019 at 7:36 AM Mark Jenks  > wrote:
>
>> I've been running this for a few years now, and once and awhile weewx 
>> just falls over for no good reason.   To deal with this, I wrote a script 
>> that I run in cron to check to make sure it's running, and if not, start it 
>> over again.
>>
>> Here it is for everyone to use
>>
>> -Mark
>>
>> [root@server bin]# crontab -l
>> 0 * * * * /usr/local/bin/watch-weewx.sh
>>
>>
>> [root@server bin]# cat watch-weewx.sh
>> #!/bin/bash
>> service=weewx.service
>> if (( $(/usr/bin/systemctl status $service | grep running | wc -l) < 1 ))
>> then
>> echo “$service was down and was restarted!!!”
>> systemctl stop $service
>> systemctl start $service
>> fi
>> if (( $(/usr/bin/systemctl status $service | grep "Exiting..." | wc -l) > 
>> 0 ))
>> then
>> echo “$service Exited and was restarted!!!”
>> systemctl stop $service
>> systemctl start $service
>> fi
>>
>> -- 
>> 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+...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] New weather station opinions?

[Mark Jenks]

Currently, I have a WMR200, but it originally started out as a WMR100.  The 
console died and I found a good used 200 on Ebay.

But the years have taken its toll and I have replaced just about everything 
once.   I'm just limping it along right now with extra parts I've gotten 
over the years.  But most of the plastic is old and fragile..

Now I'm looking at replacing it with something similar or even better.

What does everyone recommend?  I'd like to keep it under $300 if possible.

-Mark

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Weewx crash catcher

[Mark Jenks]

I've been running this for a few years now, and once and awhile weewx just 
falls over for no good reason.   To deal with this, I wrote a script that I 
run in cron to check to make sure it's running, and if not, start it over 
again.

Here it is for everyone to use

-Mark

[root@server bin]# crontab -l
0 * * * * /usr/local/bin/watch-weewx.sh


[root@server bin]# cat watch-weewx.sh
#!/bin/bash
service=weewx.service
if (( $(/usr/bin/systemctl status $service | grep running | wc -l) < 1 ))
then
echo “$service was down and was restarted!!!”
systemctl stop $service
systemctl start $service
fi
if (( $(/usr/bin/systemctl status $service | grep "Exiting..." | wc -l) > 0 
))
then
echo “$service Exited and was restarted!!!”
systemctl stop $service
systemctl start $service
fi

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Windchill generated wrong.

[Mark Jenks]

20 miles NW from Green Bay, WI.  Frozen Tundra!


On Tuesday, December 26, 2017 at 3:21:28 PM UTC-6, vince wrote:
>
> On Monday, December 25, 2017 at 10:24:36 PM UTC-8, Mark Jenks wrote:
>>
>> Yes, I live somewhere where the air hurts my face..  But that being said, 
>> when windchill hits -25, it calculates it wrong.
>>
>> Outside Temperature -9.4°F
>> Wind Chill -24.6°F
>> Heat Index -9.4°F
>> Dewpoint -34.2°F
>> Humidity 27%
>>
>>
> ok - I have to ask.where are you ?
>  
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Windchill generated wrong.

[Mark Jenks]

Correct.


On Tuesday, December 26, 2017 at 1:44:41 PM UTC-6, gjr80 wrote:
>
> So when weeWX was displaying the nonsense windchill at the same time the 
> console was displaying the correct windchill?
>
> Gary
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Windchill generated wrong.

[Mark Jenks]

Yes, software seems to be working fine now.

Outside Temperature -9.6°F
Wind Chill -26.9°F
Heat Index -9.6°F
Dewpoint -34.3°F
Humidity 27%
Barometer 30.599 inHg
Barometer Trend (3 hours) 0.057 inHg
Wind 9 mph from 270° (W)
Rain Rate 0.00 in/hr
Inside Temperature 62.1°F
Inside Humidity 25%


On Tuesday, December 26, 2017 at 7:45:12 AM UTC-6, Mark Jenks wrote:
>
> Yes, windchill is correct on the station.  Says -30F right now.
>
> I'm going to try switching it to software to see if it fixes it for now.
>
> I have a feeling that the driver isn't grabbing it correctly.
>
> -Mark
>
> On Tuesday, December 26, 2017 at 3:54:03 AM UTC-6, gjr80 wrote:
>>
>> Hmm, accoding to the Hardware Guide (
>> http://weewx.com/docs/hardware.htm#wmr200_notes) the WMR200 calculates 
>> and provides windchill to weeWX. So it's likely either the WMR200 driver is 
>> decoding windchill incorrectly or the station is outputting nonsense 
>> windchill now and then. Does windchill always display correctly on the 
>> station? Probably need a WMR200 expert I suspect.
>>
>> You could force weeWX to calculate windchill by setting 
>> windchill=software under StdWXCalculate in weewx.conf but this will only 
>> give you a windchill value when you have non-None values for outTemp AND 
>> windSpeed in the packet/record. Arguably this is only masking the issue 
>> rather than fixing it.
>>
>> Gary
>>
>>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Windchill generated wrong.

[Mark Jenks]

Yes, windchill is correct on the station.  Says -30F right now.

I'm going to try switching it to software to see if it fixes it for now.

I have a feeling that the driver isn't grabbing it correctly.

-Mark

On Tuesday, December 26, 2017 at 3:54:03 AM UTC-6, gjr80 wrote:
>
> Hmm, accoding to the Hardware Guide (
> http://weewx.com/docs/hardware.htm#wmr200_notes) the WMR200 calculates 
> and provides windchill to weeWX. So it's likely either the WMR200 driver is 
> decoding windchill incorrectly or the station is outputting nonsense 
> windchill now and then. Does windchill always display correctly on the 
> station? Probably need a WMR200 expert I suspect.
>
> You could force weeWX to calculate windchill by setting windchill=software 
> under StdWXCalculate in weewx.conf but this will only give you a windchill 
> value when you have non-None values for outTemp AND windSpeed in the 
> packet/record. Arguably this is only masking the issue rather than fixing 
> it.
>
> Gary
>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Windchill generated wrong.

[Mark Jenks]

WMR200.   Weewx 3.8.0


On Tuesday, December 26, 2017 at 12:35:44 AM UTC-6, gjr80 wrote:
>
> Also, what type of station?
>
> Gary
>


Dec 26 03:19:28 server weewxd: LOOP:   2017-12-26 03:19:03 CST (1514279943) 
altimeter: None, appTemp: None, barometer: None, cloudbase: None, dateTime: 
1514279943, dewpoint: None, heatindex: None, humidex: None, inDewpoint: 
26.4423483272, inHeatindex: None, inHumidity: 25, inTemp: 62.78, 
maxSolarRad: None, pressure: None, rainRate: 0, usUnits: 1, windchill: 
None, windDir: None, windGustDir: None
Dec 26 03:19:28 server weewxd: LOOP:   2017-12-26 03:19:13 CST (1514279953) 
altimeter: None, appTemp: None, barometer: None, cloudbase: None, dateTime: 
1514279953, dewpoint: None, heatindex: None, humidex: None, inDewpoint: 
26.4423483272, inHeatindex: None, inHumidity: 25, inTemp: 62.78, 
maxSolarRad: None, pressure: None, rainRate: 0, usUnits: 1, windchill: 
None, windDir: None, windGustDir: None
Dec 26 03:19:28 server weewxd: LOOP:   2017-12-26 03:19:14 CST (1514279954) 
altimeter: None, appTemp: None, barometer: None, cloudbase: None, dateTime: 
1514279954, dewpoint: None, heatindex: None, humidex: None, inDewpoint: 
None, maxSolarRad: None, pressure: None, rainRate: 0, usUnits: 1, 
windchill: 3302.8, windDir: 270.0, windGust: 8.05299066698, windSpeed: 
7.60560229659
Dec 26 03:19:28 server weewxd: LOOP:   2017-12-26 03:19:23 CST (1514279963) 
altimeter: None, appTemp: None, barometer: None, cloudbase: None, dateTime: 
1514279963, dewpoint: None, heatindex: None, humidex: None, inDewpoint: 
26.4423483272, inHeatindex: None, inHumidity: 25, inTemp: 62.78, 
maxSolarRad: None, pressure: None, rainRate: 0, usUnits: 1, windchill: 
None, windDir: None, windGustDir: None
 

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Windchill generated wrong.

[Mark Jenks]

Yes, I live somewhere where the air hurts my face..  But that being said, 
when windchill hits -25, it calculates it wrong.

Outside Temperature -9.4°F
Wind Chill -24.6°F
Heat Index -9.4°F
Dewpoint -34.2°F
Humidity 27%
Barometer 30.507 inHg
Barometer Trend (3 hours) 0.038 inHg
Wind 8 mph from 288° (WNW)
Rain Rate 0.00 in/hr
Inside Temperature 62.2°F
Inside Humidity 26%


Outside Temperature -9.4°F
Wind Chill 641.2°F
Heat Index -9.4°F
Dewpoint -34.2°F
Humidity 27%
Barometer 30.507 inHg
Barometer Trend (3 hours) 0.038 inHg
Wind 8 mph from 270° (W)
Rain Rate 0.00 in/hr
Inside Temperature 62.2°F
Inside Humidity 26%

Here is the dump of data right before the bad calculation.

Dec 26 00:20:15 server weewxd: LOOP:   2017-12-26 00:19:33 CST (1514269173) 
altimeter: None, appTemp: None, barometer: None, cloudbase: None, dateTime: 
1514269173, dewpoint: None, heatindex: None, hourRain: 0.0, humidex: None, 
inDewpoint: None, maxSolarRad: None, pressure: None, rain: 0.0, rain24: 
0.0, rainRate: 0.0, rainTotal: 1.778, usUnits: 1, windchill: None, windDir: 
None, windGustDir: None
Dec 26 00:20:15 server weewxd: LOOP:   2017-12-26 00:19:33 CST (1514269173) 
altimeter: None, appTemp: None, barometer: None, cloudbase: None, dateTime: 
1514269173, dewpoint: None, heatindex: None, humidex: None, inDewpoint: 
26.9311557969, inHeatindex: None, inHumidity: 26, inTemp: 62.24, 
maxSolarRad: None, pressure: None, rainRate: 0, usUnits: 1, windchill: 
None, windDir: None, windGustDir: None
Dec 26 00:20:15 server weewxd: LOOP:   2017-12-26 00:19:33 CST (1514269173) 
altimeter: None, appTemp: None, barometer: None, cloudbase: None, dateTime: 
1514269173, dewpoint: None, heatindex: None, humidex: None, inDewpoint: 
None, maxSolarRad: None, pressure: None, rainRate: 0, usUnits: 1, 
windchill: -24.0, windDir: 270.0, windGust: None, windGustDir: None, 
windSpeed: 8.05299066698
Dec 26 00:20:15 server weewxd: LOOP:   2017-12-26 00:19:41 CST (1514269181) 
altimeter: None, appTemp: None, barometer: None, cloudbase: None, dateTime: 
1514269181, dewpoint: None, heatindex: None, humidex: None, inDewpoint: 
None, maxSolarRad: None, pressure: None, rainRate: 0, usUnits: 1, 
windchill: -24.0, windDir: 270.0, windGust: None, windGustDir: None, 
windSpeed: 8.05299066698
Dec 26 00:20:15 server weewxd: LOOP:   2017-12-26 00:19:41 CST (1514269181) 
altimeter: None, appTemp: None, barometer: None, cloudbase: 6459.19655848, 
dateTime: 1514269181, dewpoint: -34.1684648573, heatindex: -9.4, humidex: 
-9.4, inDewpoint: None, maxSolarRad: None, outHumidity: 27, outTemp: -9.4, 
pressure: None, rainRate: 0, usUnits: 1, windchill: None, windDir: None, 
windGustDir: None
Dec 26 00:20:15 server weewxd: LOOP:   2017-12-26 00:19:43 CST (1514269183) 
altimeter: None, appTemp: None, barometer: None, cloudbase: None, dateTime: 
1514269183, dewpoint: None, heatindex: None, humidex: None, inDewpoint: 
26.9311557969, inHeatindex: None, inHumidity: 26, inTemp: 62.24, 
maxSolarRad: None, pressure: None, rainRate: 0, usUnits: 1, windchill: 
None, windDir: None, windGustDir: None
Dec 26 00:20:15 server weewxd: LOOP:   2017-12-26 00:19:47 CST (1514269187) 
altimeter: None, appTemp: None, barometer: None, cloudbase: None, dateTime: 
1514269187, dewpoint: None, heatindex: None, humidex: None, inDewpoint: 
None, maxSolarRad: None, pressure: None, rainRate: 0, usUnits: 1, 
windchill: -25.0, windDir: 270.0, windGust: 8.05299066698, windSpeed: 
8.05299066698
Dec 26 00:20:15 server weewxd: LOOP:   2017-12-26 00:19:53 CST (1514269193) 
altimeter: None, appTemp: None, barometer: None, cloudbase: None, dateTime: 
1514269193, dewpoint: None, heatindex: None, humidex: None, inDewpoint: 
26.9311557969, inHeatindex: None, inHumidity: 26, inTemp: 62.24, 
maxSolarRad: None, pressure: None, rainRate: 0, usUnits: 1, windchill: 
None, windDir: None, windGustDir: None
Dec 26 00:20:15 server weewxd: LOOP:   2017-12-26 00:20:01 CST (1514269201) 
altimeter: None, appTemp: None, barometer: None, cloudbase: None, dateTime: 
1514269201, dewpoint: None, heatindex: None, humidex: None, inDewpoint: 
None, maxSolarRad: None, pressure: None, rainRate: 0, usUnits: 1, 
windchill: -24.0, windDir: 315.0, windGust: None, windGustDir: None, 
windSpeed: 8.05299066698
Dec 26 00:20:15 server weewxd: LOOP:   2017-12-26 00:20:13 CST (1514269213) 
altimeter: None, appTemp: None, barometer: None, cloudbase: None, dateTime: 
1514269213, dewpoint: None, heatindex: None, humidex: None, inDewpoint: 
26.9311557969, inHeatindex: None, inHumidity: 26, inTemp: 62.24, 
maxSolarRad: None, pressure: None, rainRate: 0, usUnits: 1, windchill: 
None, windDir: None, windGustDir: None
Dec 26 00:20:15 server weewxd: LOOP:   2017-12-26 00:20:15 CST (1514269215) 
altimeter: None, appTemp: None, barometer: None, cloudbase: None, dateTime: 
1514269215, dewpoint: None, heatindex: None, humidex: None, inDewpoint: 
None, maxSolarRad: None, pressure: None, rainRate: 0, usUnits: 1, 
windchill: -24.0, windDir: 270.0, windGust: 7.82929648179, wind