Re: [weewx-user] Weewx mqtt

an item timestamped 21:10:05 belongs to the reporting period after 21:10 - it doesn’t matter when the report is actually generated ⊣GE⊢ > On 14 Sep 2023, at 11:35 am, kufuu wrote: > > I reboot the pi zero-w and seen it didnt add the files to database till it > ran the second payload > > >

Re: [weewx-user] Weewx mqtt

I reboot the pi zero-w and seen it didnt add the files to database till it ran the second payload Sep 13 21:10:09 zero-wx weewx[532] DEBUG user.MQTTSubscribe: (Driver) MessageCallbackProvider data-> incoming topic: enviro/river-wx, QOS: 0, retain: 0, payload: b'{"readings": {"pressure":

Re: [weewx-user] Weewx mqtt

ok, my weather station is a pico enviro weather, I have it to send the data every 10 mins to a pi zero-w using weewx and is up to date along with raspberry os, here is a packet Sep 13 20:10:09 zero-wx weewx[9676] DEBUG user.MQTTSubscribe: (Driver) MessageCallbackProvider data-> incoming topic:

Re: [weewx-user] Weewx mqtt

kufuu writes: > I just found that weewx mqtt if it takes a reading at 1:00pm and another at > 1:10pm and at 1:20, it wont post the data from 1:00pm till it reads the > 1:20pm , its always 1 reading behind, station sends the packet every 10 > mins. Can that be changed ? Probably, but it might

[weewx-user] Weewx mqtt

I just found that weewx mqtt if it takes a reading at 1:00pm and another at 1:10pm and at 1:20, it wont post the data from 1:00pm till it reads the 1:20pm , its always 1 reading behind, station sends the packet every 10 mins. Can that be changed ? -- You received this message because you are

[weewx-user] Diagrams of readings of the DWD weather stations

By now this applies to Germany only. So I describe it in german. Die WeeWX-Erweiterung weewx-DWD kann die Meßwerte der Stationen verschiedener staatlicher Wetterdienste abrufen. Bisher konnte man damit nur aktuelle Werte mittels $current als Zahlenwerte

[weewx-user] Re: Observation Types

Thanks Karen, that is an incredibly useful document. Craig On Thursday, September 14, 2023 at 8:21:08 AM UTC+12 Karen K wrote: > I would suggest to look into obs_group_dict in > /usr/share/weewx/weewx/units.py for a list of pre-defined observation types > and their unit groups. > > -- You

[weewx-user] Re: Observation Types

I would suggest to look into obs_group_dict in /usr/share/weewx/weewx/units.py for a list of pre-defined observation types and their unit groups. -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving

[weewx-user] Re: Observation Types

Thanks Matthew, I understand now. I also did some reading of the 'customization' section in the wiki and it ties together nicely with what you have posted. So my next step is to setup the database, load all of my archive data and then update the driver to match the schema. Craig On

Re: [weewx-user] NOAA data mixed (F and C)

Yves, did you resolve this? On Fri, Sep 8, 2023 at 3:59 PM Tom Keffer wrote: > Not much information here. > > Which skin? Which version? > > Which values were in C, which in F? > > In weewx.conf, under [StdReport] / [[Defaults]] what settings did you use > for unit_system? Did you override

Re: [weewx-user] Problems importing wview.sdb

Yes. The classic wview database has 52 columns. The "wview-extended" database has 114. You're mixing the two. You're also making this harder than it needs to be. 1, Stop weewxd. 2. Then simply copy your wview database into place. Don't dump anything, nor read anything. Just copy it. 3. Then, in

[weewx-user] Problems importing wview.sdb

I plan to change from wview to weewx. First I started weewx in simulator mode. I copied the database from wview and transferred it to a dump file using sqlitre3 commands. After that I merged the databases of weewx in simulator mode and wview with the .read command. This worked without errors.

[weewx-user] Re: Observation Types

On Wednesday, September 13, 2023 at 6:51:17 AM UTC-4 craig.y...@gmail.com wrote: Where can I find the list of observation types? within the driver code, use names that match whatever the hardware uses. then you can map those onto the weewx observation types when you generate a LOOP or

[weewx-user] Observation Types

Where can I find the list of observation types? I am writing a new driver for my hardware and need to map the physical data to the corresponding observation types to create the loop packet. Craig -- You received this message because you are subscribed to the Google Groups "weewx-user"