Re: [weewx-user] Weewx mqtt

[Graham Eddy]

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
> 
> 
> 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": 952.05, "rain": 0, 
> "wind_speed": 0, "temperature": 17.41, "humidity": 90.31, "wind_direction": 
> 90, "rain_per_second": 0.0, "luminance": 0.0}, "nickname": "river-wx", 
> "model": "weather", "uid": "e6614c311b62b034", "timestamp": 
> "2023-09-14T01:10:05Z"}'

-- 
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/58E01E41-D861-4364-B941-17B92C84C120%40geddy.au.

Re: [weewx-user] Weewx mqtt

[kufuu]

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": 952.05, "rain": 0, 
"wind_speed": 0, "temperature": 17.41, "humidity": 90.31, "wind_direction": 
90, "rain_per_second": 0.0, "luminance": 0.0}, "nickname": "river-wx", 
"model": "weather", "uid": "e6614c311b62b034", "timestamp": 
"2023-09-14T01:10:05Z"}'
Sep 13 21:10:10 zero-wx weewx[532] DEBUG user.MQTTSubscribe: (Driver) 
TopicManager data-> incoming enviro/river-wx: 'luminance': '0.0', 
'outHumidity': '90.31', 'outTemp': '17.41', 'pressure': '952.05', 'rain': 
'0.0', 'rainPersecond': '0.0', 'windDir': '90.0', 'windSpeed': '0.0'
Sep 13 21:10:11 zero-wx weewx[532] DEBUG user.MQTTSubscribe: (Driver) 
TopicManager data-> outgoing enviro/river-wx: 'dateTime': 
'1694653810.0253491', 'luminance': '0.0', 'outHumidity': '90.31', 
'outTemp': '17.41', 'pressure': '952.05', 'rain': '0.0', 'rainPersecond': 
'0.0', 'usUnits': '17', 'windDir': '90.0', 'windSpeed': '0.0'
Sep 13 21:10:11 zero-wx weewx[532] DEBUG user.MQTTSubscribe: (Driver) 
data-> final loop packet is enviro/river-wx 2023-09-13 21:10:10 EDT 
(1694653810): 'dateTime': '1694653810.0253491', 'luminance': '0.0', 
'outHumidity': '90.31', 'outTemp': '17.41', 'pressure': '952.05', 'rain': 
'0.0', 'rainPersecond': '0.0', 'usUnits': '17', 'windDir': '90.0', 
'windSpeed': '0.0'
Sep 13 21:17:01 zero-wx CRON[839]: (root) CMD (   cd / && run-parts 
--report /etc/cron.hourly)
Sep 13 21:20:10 zero-wx weewx[532] DEBUG user.MQTTSubscribe: (Driver) 
MessageCallbackProvider data-> incoming topic: enviro/river-wx, QOS: 0, 
retain: 0, payload: b'{"readings": {"pressure": 952.19, "rain": 0, 
"wind_speed": 0, "temperature": 17.12, "humidity": 91.01, "wind_direction": 
90, "rain_per_second": 0.0, "luminance": 0.0}, "nickname": "river-wx", 
"model": "weather", "uid": "e6614c311b62b034", "timestamp": 
"2023-09-14T01:20:05Z"}'
Sep 13 21:20:10 zero-wx weewx[532] DEBUG user.MQTTSubscribe: (Driver) 
TopicManager data-> incoming enviro/river-wx: 'luminance': '0.0', 
'outHumidity': '91.01', 'outTemp': '17.12', 'pressure': '952.19', 'rain': 
'0.0', 'rainPersecond': '0.0', 'windDir': '90.0', 'windSpeed': '0.0'
Sep 13 21:20:10 zero-wx weewx[532] DEBUG user.MQTTSubscribe: (Driver) 
TopicManager data-> outgoing enviro/river-wx: 'dateTime': 
'1694654410.1346781', 'luminance': '0.0', 'outHumidity': '91.01', 
'outTemp': '17.12', 'pressure': '952.19', 'rain': '0.0', 'rainPersecond': 
'0.0', 'usUnits': '17', 'windDir': '90.0', 'windSpeed': '0.0'
Sep 13 21:20:10 zero-wx weewx[532] DEBUG user.MQTTSubscribe: (Driver) 
data-> final loop packet is enviro/river-wx 2023-09-13 21:20:10 EDT 
(1694654410): 'dateTime': '1694654410.1346781', 'luminance': '0.0', 
'outHumidity': '91.01', 'outTemp': '17.12', 'pressure': '952.19', 'rain': 
'0.0', 'rainPersecond': '0.0', 'usUnits': '17', 'windDir': '90.0', 
'windSpeed': '0.0'
Sep 13 21:20:10 zero-wx weewx[532] DEBUG user.MQTTSubscribe: (Driver) No 
archive topic configured.
Sep 13 21:20:11 zero-wx weewx[532] INFO weewx.manager: Added record 
2023-09-13 21:15:00 EDT (1694654100) to database 'weewx.sdb'
Sep 13 21:20:11 zero-wx weewx[532] INFO weewx.manager: Added record 
2023-09-13 21:15:00 EDT (1694654100) to daily summary in 'weewx.sdb'
Sep 13 21:20:12 zero-wx weewx[532] DEBUG weewx.reportengine: Running 
reports for latest time in the database.
Sep 13 21:20:12 zero-wx weewx[532] DEBUG weewx.reportengine: Running report 
'SeasonsReport'
Sep 13 21:20:13 zero-wx weewx[532] DEBUG weewx.reportengine: Found 
configuration file /etc/weewx/skins/Seasons/skin.conf for report 
'SeasonsReport'
Sep 13 21:20:15 zero-wx weewx[532] DEBUG weewx.cheetahgenerator: Using 
search list ['weewx.cheetahgenerator.Almanac', 
'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.DisplayOptions', 
'weewx.cheetahgenerator.Extras', 'weewx.cheetahgenerator.Gettext', 
'weewx.cheetahgenerator.JSONHelpers', 'weewx.cheetahgenerator.PlotInfo', 
'weewx.cheetahgenerator.SkinInfo', 'weewx.cheetahgenerator.Station', 
'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo']
Sep 13 21:20:15 zero-wx weewx[532] DEBUG weewx.manager: Daily summary 
version is 4.0
Sep 13 21:20:39 zero-wx weewx[532] INFO weewx.cheetahgenerator: Generated 9 
files for report SeasonsReport in 24.59 seconds
Sep 13 21:20:40 zero-wx weewx[532] DEBUG weewx.manager: Daily summary 
version is 4.0
Sep 13 21:21:07 zero-wx weewx[532] INFO weewx.imagegenerator: Generated 31 
images for report SeasonsReport in 27.13 seconds
Sep 13 21:21:07 zero-wx weewx[532] INFO weewx.reportengine: Copied 5 files 
to /var/weewx/reports
Sep 13 21:21:07 zero-wx weewx[532] DEBUG weewx.reportengine: Report 
'SmartphoneReport' not enabled. Skipping.
Sep 13 21:21:07 zero-wx weewx[532] DEBUG weewx.reportengine: Report 
'MobileReport' not enabled. 

Re: [weewx-user] Weewx mqtt

[kufuu]

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: enviro/river-wx, QOS: 0, 
retain: 0, payload: b'{"readings": {"pressure": 951.19, "rain": 0, 
"wind_speed": 0, "temperature": 19.1, "humidity": 84.97, "wind_direction": 
90, "rain_per_second": 0.0, "luminance": 0.0}, "nickname": "river-wx", 
"model": "weather", "uid": "e6614c311b62b034", "timestamp": 
"2023-09-14T00:10:05Z"}'
Sep 13 20:10:09 zero-wx weewx[9676] DEBUG user.MQTTSubscribe: (Driver) 
TopicManager data-> incoming enviro/river-wx: 'luminance': '0.0', 
'outHumidity': '84.97', 'outTemp': '19.1', 'pressure': '951.19', 'rain': 
'0.0', 'rainPersecond': '0.0', 'windDir': '90.0', 'windSpeed': '0.0'
Sep 13 20:10:10 zero-wx weewx[9676] DEBUG user.MQTTSubscribe: (Driver) 
TopicManager data-> outgoing enviro/river-wx: 'dateTime': 
'1694650209.7946532', 'luminance': '0.0', 'outHumidity': '84.97', 
'outTemp': '19.1', 'pressure': '951.19', 'rain': '0.0', 'rainPersecond': 
'0.0', 'usUnits': '17', 'windDir': '90.0', 'windSpeed': '0.0'
Sep 13 20:10:10 zero-wx weewx[9676] DEBUG user.MQTTSubscribe: (Driver) 
data-> final loop packet is enviro/river-wx 2023-09-13 20:10:09 EDT 
(1694650209): 'dateTime': '1694650209.7946532', 'luminance': '0.0', 
'outHumidity': '84.97', 'outTemp': '19.1', 'pressure': '951.19', 'rain': 
'0.0', 'rainPersecond': '0.0', 'usUnits': '17', 'windDir': '90.0', 
'windSpeed': '0.0'
Sep 13 20:10:10 zero-wx weewx[9676] DEBUG user.MQTTSubscribe: (Driver) No 
archive topic configured.
Sep 13 20:10:10 zero-wx weewx[9676] INFO weewx.manager: Added record 
2023-09-13 20:05:00 EDT (1694649900) to database 'weewx.sdb'
Sep 13 20:10:11 zero-wx weewx[9676] INFO weewx.manager: Added record 
2023-09-13 20:05:00 EDT (1694649900) to daily summary in 'weewx.sdb'
Sep 13 20:10:11 zero-wx weewx[9676] DEBUG weewx.reportengine: Running 
reports for latest time in the database.
Sep 13 20:10:11 zero-wx weewx[9676] DEBUG weewx.reportengine: Running 
report 'SeasonsReport'
Sep 13 20:10:12 zero-wx weewx[9676] DEBUG weewx.reportengine: Found 
configuration file /etc/weewx/skins/Seasons/skin.conf for report 
'SeasonsReport'
Sep 13 20:10:12 zero-wx weewx[9676] DEBUG weewx.cheetahgenerator: Using 
search list ['weewx.cheetahgenerator.Almanac', 
'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.DisplayOptions', 
'weewx.cheetahgenerator.Extras', 'weewx.cheetahgenerator.Gettext', 
'weewx.cheetahgenerator.JSONHelpers', 'weewx.cheetahgenerator.PlotInfo', 
'weewx.cheetahgenerator.SkinInfo', 'weewx.cheetahgenerator.Station', 
'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo']
Sep 13 20:10:12 zero-wx weewx[9676] DEBUG weewx.manager: Daily summary 
version is 4.0
Sep 13 20:10:22 zero-wx weewx[9676] INFO weewx.cheetahgenerator: Generated 
8 files for report SeasonsReport in 10.49 seconds
Sep 13 20:10:23 zero-wx weewx[9676] DEBUG weewx.manager: Daily summary 
version is 4.0
Sep 13 20:10:28 zero-wx weewx[9676] INFO weewx.imagegenerator: Generated 7 
images for report SeasonsReport in 5.69 seconds
Sep 13 20:10:28 zero-wx weewx[9676] INFO weewx.reportengine: Copied 0 files 
to /var/weewx/reports
Sep 13 20:10:28 zero-wx weewx[9676] DEBUG weewx.reportengine: Report 
'SmartphoneReport' not enabled. Skipping.
Sep 13 20:10:28 zero-wx weewx[9676] DEBUG weewx.reportengine: Report 
'MobileReport' not enabled. Skipping.
Sep 13 20:10:28 zero-wx weewx[9676] DEBUG weewx.reportengine: Report 
'StandardReport' not enabled. Skipping.
Sep 13 20:10:28 zero-wx weewx[9676] DEBUG weewx.reportengine: Report 'FTP' 
not enabled. Skipping.
Sep 13 20:10:28 zero-wx weewx[9676] DEBUG weewx.reportengine: Report 
'RSYNC' not enabled. Skipping.

On Wednesday, September 13, 2023 at 7:02:42 PM UTC-4 Greg Troxel wrote:

> 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 be your system. Make sure you are up to date,
> and post again with what you are really doing, and details. including a
> mosquitto_sub command and debug output. Not trying to be unkind, but if
> you can debug it you can fix it, and if not, it will likely stay broken
> until somebody who can debug does so. I haven't seen other reports, and
> this doesn't happen to me, so it is also possible there is something
> else locally wrong, in which case nobody else will debug it.
>
> In Davis, there is the idea that archive records are generated at 15s
> past the time, to deal with station clock skew. You need to be clear on
> that happening vs just mqtt.
>

-- 
You received this message because you are subscribed to the Google Groups 

Re: [weewx-user] Weewx mqtt

[Greg Troxel]

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 be your system.  Make sure you are up to date,
and post again with what you are really doing, and details.  including a
mosquitto_sub command and debug output.  Not trying to be unkind, but if
you can debug it you can fix it, and if not, it will likely stay broken
until somebody who can debug does so.  I haven't seen other reports, and
this doesn't happen to me, so it is also possible there is something
else locally wrong, in which case nobody else will debug it.

In Davis, there is the idea that archive records are generated at 15s
past the time, to deal with station clock skew.  You need to be clear on
that happening vs just mqtt.

-- 
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/rmiv8cd8ynn.fsf%40s1.lexort.com.

[weewx-user] Weewx mqtt

[kufuu]

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 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/d66a8bab-1c40-4e99-adc8-4710cd6204dan%40googlegroups.com.

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

[Karen K]

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 
darstellen.

Nun habe ich ein Modul ergänzt, daß die Werte in eine Datenbank speichert, 
die von WeeWX verarbeitet werden kann. Vorerst funktioniert das nur mit 
CDC-Werten vom DWD.

Durch das Speichern der Werte ist es nun auch möglich, die Werte in 
Diagrammen anzuzeigen.

Der Grund, warum hierfür ein extra Modul notwendig war und nicht die 
Speicherroutinen von WeeWX genutzt werden konnten, ist, daß die Werte vom 
DWD mit Verzögerung bereitgestellt werden, so daß man andere Zeitstempel 
hat.

-- 
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/a1d69785-4e50-4e76-bd04-2dac586c19dfn%40googlegroups.com.

[weewx-user] Re: Observation Types

[Craig Young]

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 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/4817fd96-3951-41b9-9bf6-13323f27addan%40googlegroups.com.

[weewx-user] Re: Observation Types

[Karen K]

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 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/5ffd9234-3017-44e0-924a-271b53b5bb4bn%40googlegroups.com.

[weewx-user] Re: Observation Types

[Craig Young]

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 Wednesday, September 13, 2023 at 11:07:28 PM UTC+12 matthew wall wrote:

> 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 ARCHIVE dict.  for example, the hardware documentation might use 
> 'inside_temperature', but the weewx equivalent is 'inTemp'.
>
> the weewx observation types are defined by the database schema. 
> 'wview_extended' is the default schema, but weewx also ships with the 
> legacy 'wview' and 'wview_small' schemas.
>
> https://github.com/weewx/weewx/blob/master/bin/schemas/wview_extended.py
>
> you can see what other drivers have done by browsing the 'Station data' 
> section for each driver in the hardware guide:
>
> http://weewx.com/docs/hardware.htm
>
> for power/solar/battery monitoring, or hardware that emits observations 
> that are not easily mapped to the weather-based schemas, it is typical to 
> ship a bespoke schema with the driver.
>
>  
>

-- 
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/ed0abb3f-cbdd-40ab-a890-de10b9f22d35n%40googlegroups.com.

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

[Tom Keffer]

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 group_temperature? Did you override for
> the specific skin?
>
> How did you manage the mixed unit systems? With separate reports, each
> using a different value for unit_system? Some other way?
>
> It might be easiest if you post your [StdReport] section.
>
> -tk
>
> On Fri, Sep 8, 2023 at 1:07 PM Yves Martin  wrote:
>
>> Hi,
>>
>> I have a bilingual web site, English and French.
>> When I upgraded weewx, the NOAA data were mixed-up for the French version
>> in F and C !
>>
>> How to re-generate all the NOAA data in C (For the French side) from the
>> database?
>>
>> Regards,
>> Yves, YMartin.com/meteo
>>
>> --
>> 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/430ac885-d7c9-4dec-8108-98106719375en%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/CAPq0zEANUvE55VybDPeNOgrYg5ngpQcL_nTiYrkQFTXQ54_noA%40mail.gmail.com.

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

[Tom Keffer]

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.conf specify a  classic database.

[DataBindings]
  [[wx_binding]]
...
schema = schemas.wview.schema


4. Then start weewxd. Because your old wview database will not have a daily
summary in it, one will be built automatically. Should take a couple minutes

-tk

On Wed, Sep 13, 2023 at 9:13 AM Karl Napp  wrote:

> 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.  And weewx started with the additional data.
>
> After that I changed the driver from weewx to Vantage, connected the
> Vantage Pro and restarted weewx. After reading all data from the Vantage I
> closed weewx and tried to merge the data from wview with the database
> weex.sdb also with read. Unfortunately this did not work I get the error
> message with the .read command with each line:
>
> Error: near line x: table archive has 114 columns but 52 values were
> supplied
>
> No data was added to weewx - does anyone know the cause ?
>
> --
> 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/6495e247-a027-48d2-91da-544affbaaf15n%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/CAPq0zEBxJf4icL5dMfYCF65Pz4nt4UUrWXc2YcotPUD1TRf7CA%40mail.gmail.com.

[weewx-user] Problems importing wview.sdb

[Karl Napp]

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.  And weewx started with the additional data.

After that I changed the driver from weewx to Vantage, connected the 
Vantage Pro and restarted weewx. After reading all data from the Vantage I 
closed weewx and tried to merge the data from wview with the database 
weex.sdb also with read. Unfortunately this did not work I get the error 
message with the .read command with each line:

Error: near line x: table archive has 114 columns but 52 values were 
supplied

No data was added to weewx - does anyone know the cause ?

-- 
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/6495e247-a027-48d2-91da-544affbaaf15n%40googlegroups.com.

[weewx-user] Re: Observation Types

[matthew wall]

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 ARCHIVE dict.  for example, the hardware documentation might use 
'inside_temperature', but the weewx equivalent is 'inTemp'.

the weewx observation types are defined by the database schema. 
'wview_extended' is the default schema, but weewx also ships with the 
legacy 'wview' and 'wview_small' schemas.

https://github.com/weewx/weewx/blob/master/bin/schemas/wview_extended.py

you can see what other drivers have done by browsing the 'Station data' 
section for each driver in the hardware guide:

http://weewx.com/docs/hardware.htm

for power/solar/battery monitoring, or hardware that emits observations 
that are not easily mapped to the weather-based schemas, it is typical to 
ship a bespoke schema with the driver.

 

-- 
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/694d4c47-9075-4f32-af71-cdc42afcfb83n%40googlegroups.com.

[weewx-user] Observation Types

[Craig Young]

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" 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/21db9689-3aa4-4a6b-ba26-6425bcb9e577n%40googlegroups.com.