I’ve got an extension that can be installed as either a driver or service.
Depending on which, the updates to WeeWX configuration is different.
Currently I instruct people to set an environment variable to control the
install. I’m wondering if passing in an option to wee_extension would make
02,"h2":.0002} (for whatever value I have)
>
> That plus what's in the add_archive_type link is all that's required?
>
> Earl
>
>
> On Wednesday, July 1, 2020 at 2:05:44 PM UTC-4 bell...@gmail.com wrote:
>
>> This is what I was thinking needs to be done to accumulate
This is what I was thinking needs to be done to accumulate loop data into
archive data
https://github.com/weewx/weewx/wiki/Accumulators
rich
On Wednesday, 1 July 2020 14:02:22 UTC-4, Rich Bell wrote:
>
> Woops, my bad... I think I remember there might bevanother step to tell
> Wee
Earl,
I’ll take a first crack at this, and the WeeWX experts can clarify/help as
needed. WeeWX really does all the heavily lifting. Whatever name/values are
in the loop data that MQTTSubscribe generates will be accumulated into an
archive record. You should see this happening if you run WeeWX
Till,
Thanks. I’ve had it on my list to learn tox. Seems like now is the time.
rich
On Sunday, 10 May 2020 11:55:40 UTC-4, Till Maas wrote:
>
> Hi,
>
> On Sun, May 10, 2020 at 07:50:04AM -0700, Rich Bell wrote:
>
> > 2. Extension development
> > 1. Download set
I know am a bit late to the party. I am also no Python expert and I know
that I will be able to work with any new packaging/install. But, I want to
note my workflows that are super easy with today's packaging/install
1. Debugging base WeeWx code
1. Git fork and clone
2. Copy known
I've been experimenting/learning about the logging in v4. I am very excited
and impressed! Reading
https://github.com/weewx/weewx/wiki/WeeWX-v4-and-logging, the example of
quieting a chatty module seems to be the opposite of what I, as an
extension writer, would want. Meaning, most like likely
'decode' here and there a month ago a
> suggestion from Tom K.
> DEBUG user.MQTTSubscribe: MessageCallbackProvider For weather has QOS of 0
> and retain of 0 received:* b*'TIME:0,soilTemp3:14.68,INHU:40.00'
>
> Thanks for the help!
>
>
> On Tuesday, January 14, 2020 at 4:
Or since a comma is the default, comment it out for now.
Rich
On Tuesday, 14 January 2020 19:37:56 UTC-5, Rich Bell wrote:
>
> Ralph,
> My first guess is that it doesn’t like the comma in the config for the
> delimiter. This is based on this line the log.
> Jan 14 15:39:40 Te
Ralph,
My first guess is that it doesn’t like the comma in the config for the
delimiter. This is based on this line the log.
Jan 14 15:39:40 TestPi weewx[5256] INFO user.MQTTSubscribe: Message
callback config is {'type': 'keyword', 'keyword_delimiter': [],
'keyword_separator': ':', 'label_map':
Ralph,
What version of WeeWX and MQTTSubscribe? Did you install via wee_extension?
If you post a copy of your config (making sure to remove any sensitive
information), I’d be happy to take a look.
We should probably move this out of the wxMesh thread...
Rich
On Tuesday, 14 January 2020 14:48:03
I think you can find it here
https://github.com/matthewwall/weewx-forecast
-rich
On Sunday, 12 January 2020 20:14:51 UTC-5, Vince Skahan wrote:
>
> On Sunday, January 12, 2020 at 4:26:47 PM UTC-8, John Kline wrote:
>>
>> mwall has this extension in github now with weewx 4/py3 changes.
>>
>
>
>
Oops, here
https://github.com/bellrichm/WeeWX-MQTTSubscribe/blob/master/bin/user/MQTTSubscribe.py
On Sunday, 5 January 2020 19:25:30 UTC-5, Rich Bell wrote:
>
> It has to do with the different way strings are handled in python 3 vs 2.
> If you look at the on_message _keyword method (ap
It has to do with the different way strings are handled in python 3 vs 2.
If you look at the on_message _keyword method (approx line 576), you will
see that I decode the payload under python 3.
- rich
On Sunday, 5 January 2020 17:59:20 UTC-5, KSKENYON wrote:
>
> I'm stumped. wxMesh.py v0.2
Just FYI, the cmon skin is one of the skins that uses the imaging library's
default font. On my Pi 3, this causes a slow increase in memory usage. See,
https://groups.google.com/forum/#!topic/weewx-user/qeVSNzy7Zck for any
additional information I might discover.
- Rich
On Saturday, 14
ithmetic got neglected as well. I think I got it all
> fixed in commit 073be00. You can just download xtypes.py if you want to patch
> your copy, or do a pull on the repository.
>
>
> On Tue, Nov 19, 2019 at 1:25 PM Rich Bell wrote:
>
> I'm throwing various extensions that I ha
Working great. Thanks!
- rich
On Tuesday, 19 November 2019 11:41:44 UTC-5, Tom Keffer wrote:
>
> Fixed in commit 178114d
> <https://github.com/weewx/weewx/commit/178114d0ba3a235a8f2f6b4a77d21c4f9135a9f0>
> .
>
> Thanks, Rich!
>
> -tk
>
> On Tue, Nov 19,
Should have added, running under python 2.
On Tuesday, 19 November 2019 10:16:31 UTC-5, Rich Bell wrote:
>
> With this in weewx.conf
>
> [ComputerMonitor]
> max_age = None
>
> Getting the following error:
> Traceback (most recent call last):
> F
>
> With this in weewx.conf
[ComputerMonitor]
max_age = None
Getting the following error:
Traceback (most recent call last):
File "./bin/weewxd", line 64, in
weewx.engine.main(options, args)
File "/home/pi/4.0.0b1/bin/weewx/engine.py", line 883, in main
engine =
I have a VP2. It’s been hooked up to WeeWX via the usb logger for about 2
years. I spent some time before that struggling to get a robust set up
(hw, not WeeWX) and life got in the way, etc. I’ve been lurking on the
groups during those years. Currently everything is not public. But I have
been
20 matches
Mail list logo
