Windspeed/windgust (UDP) seems not okay. radiation, uv, et, extratemp are
NULL (but I think thats because you still need to implement that, right)?
With WLLDriver, I got:
mysql> select
datetime,from_unixtime(datetime),outtemp,windspeed,windgust,radiation,uv,et,rain,extratemp1
from archive order by datetime desc limit 5;
+------------+-------------------------+---------+--------------------+----------+-----------+------+------+------+------------+
| datetime | from_unixtime(datetime) | outtemp | windspeed |
windgust | radiation | uv | et | rain | extratemp1 |
+------------+-------------------------+---------+--------------------+----------+-----------+------+------+------+------------+
| 1593864000 | 2020-07-04 14:00:00 | 16.5 | 5.6156250000000005
| 16 | NULL | NULL | NULL | 0 | NULL |
| 1593863940 | 2020-07-04 13:59:00 | 16.5 | 6.9475
| 16 | NULL | NULL | NULL | 0 | NULL |
| 1593863880 | 2020-07-04 13:58:00 | 16.5 | 6.0440625
| 16 | NULL | NULL | NULL | 0 | NULL |
| 1593863820 | 2020-07-04 13:57:00 | 16.5 | 7.158125000000002
| 17 | NULL | NULL | NULL | 0 | NULL |
| 1593863760 | 2020-07-04 13:56:00 | 16.5 | 5.956874999999999
| 17 | NULL | NULL | NULL | 0 | NULL |
+------------+-------------------------+---------+--------------------+----------+-----------+------+------+------+------------+
5 rows in set (0.00 sec)
In my other virtual machine (hooked with a WeatherLink IP, my production
environment), I got for the same datetime.
mysql> select
datetime,from_unixtime(datetime),outtemp,windspeed,windgust,radiation,uv,et,rain,extratemp1
from weewx.archive order by datetime desc limit 5;
+------------+-------------------------+--------------------+-----------+----------+-----------+------+--------+------+--------------------+
| datetime | from_unixtime(datetime) | outtemp | windspeed |
windgust | radiation | uv | et | rain | extratemp1 |
+------------+-------------------------+--------------------+-----------+----------+-----------+------+--------+------+--------------------+
| 1593864000 | 2020-07-04 14:00:00 | 16.555555555555557 | 4.4704 |
5.81152 | 123 | 1.1 | 0.0762 | 0 | 16.666666666666668 |
| 1593863940 | 2020-07-04 13:59:00 | 16.555555555555557 | 5.36448 |
6.7056 | 138 | 1.1 | 0 | 0 | 16.666666666666668 |
| 1593863880 | 2020-07-04 13:58:00 | 16.555555555555557 | 4.4704 |
7.15264 | 127 | 1 | 0 | 0 | 16.666666666666668 |
| 1593863820 | 2020-07-04 13:57:00 | 16.555555555555557 | 5.36448 |
7.15264 | 116 | 0.9 | 0 | 0 | 16.666666666666668 |
| 1593863760 | 2020-07-04 13:56:00 | 16.555555555555557 | 4.4704 |
6.25856 | 107 | 0.9 | 0 | 0 | 16.666666666666668 |
+------------+-------------------------+--------------------+-----------+----------+-----------+------+--------+------+--------------------+
5 rows in set (0.01 sec)
I've got my wanted units set in weewx.conf:
[[[Units]]]
# The following section sets what unit to use for each unit
group.
# NB: The unit is always in the singular. I.e., 'mile_per_hour',
# NOT 'miles_per_hour'
[[[[Groups]]]]
group_altitude = meter # Options are 'foot' or 'meter'
group_degree_day = degree_C_day # Options are
'degree_F_day' or 'degree_C_day'
group_distance = km # Options are 'mile' or 'km'
group_pressure = mbar # Options are 'inHg', 'mmHg',
'mbar', or 'hPa'
group_rain = mm # Options are 'inch', 'cm', or 'mm'
group_rainrate = mm_per_hour # Options are
'inch_per_hour', 'cm_per_hour', or 'mm_per_hour'
group_speed = meter_per_second # Options are
'mile_per_hour', 'km_per_hour', 'knot', or 'meter_per_second'
group_speed2 = meter_per_second2 # Options are
'mile_per_hour2', 'km_per_hour2', 'knot2', or 'meter_per_second2'
group_temperature = degree_C # Options are 'degree_F' or
'degree_C'
Op zaterdag 4 juli 2020 13:44:15 UTC+2 schreef Maarten van der Hoeven:
>
> Some findings
>
> I cannot stop the weewx process by ' /etc/init.d/weewx stop', it keeps
> running for several minutes (and keeps on going). I need to find the
> process ID, and kill it by
>
> root@ubuntu:/etc/weewx# ps -ef | grep weewx
> root 17394 1 17 13:27 ? 00:01:59 python3
> /usr/share/weewx/weewxd --daemon --pidfile=/var/run/weewx.pid
> /etc/weewx/weewx.conf
> root 17899 1 0 13:37 ? 00:00:00 /bin/sh
> /etc/init.d/weewx stop
> root 18084 13623 0 13:38 pts/0 00:00:00 grep --color=auto weewx
> root@ubuntu:/etc/weewx# kill -9 17394
>
>
> Question: why do you have the WLLArchive placed into StdReport-services?
> And not in StdArchive-service? Reading the Weewx-architecture (see
> http://www.weewx.com/docs/customizing.htm#The_WeeWX_service_architecture),
> it should have its place as an archive_service, dont you agree? Quote:
> "weewx.engine.StdArchive Archive any new data to the SQL databases."
>
> [Engine]
> [[Services]]
> # This section specifies the services that should be run. They are
> # grouped by type, and the order of services within each group
> # determines the order in which the services will be run.
> prep_services = weewx.engine.StdTimeSynch
> data_services = ,
> process_services = weewx.engine.StdConvert,
> weewx.engine.StdCalibrate, weewx.engine.StdQC,
> weewx.wxservices.StdWXCalculate, user.calcdrought.CalcDrought
> archive_services = weewx.engine.StdArchive
> restful_services = weewx.restx.StdStationRegistry,
> weewx.restx.StdWunderground, weewx.restx.StdPWSweather,
> weewx.restx.StdCWOP, weewx.restx.StdWOW, weewx.restx.StdAWEKAS,
> user.mqtt.MQTT
> report_services = weewx.engine.StdPrint, weewx.engine.StdReport,
> user.WLLArchive.WLLArchive
>
>
>
> Op zaterdag 4 juli 2020 13:28:16 UTC+2 schreef Maarten van der Hoeven:
>>
>> Yes, apologies. Working now. I had the 'old' config of WLL still in
>> place. Did only change WLLArchive according to the readme...
>>
>> It is getting archive records, will test it today!
>>
>>
>> Op zaterdag 4 juli 2020 om 12:35:04 UTC+2 schreef [email protected]:
>>
>>> Hi,
>>>
>>> Like in Readme on Github, you've to set device id like this 1:iss. Or if
>>> you have iss on id 2, set this : 2:iss.
>>>
>>> I make this to implement extra sensor in future.
>>>
>>>
--
You received this message because you are subscribed to the Google Groups
"weewx-development" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/weewx-development/f9421618-fb78-4bf3-aebe-58319d4e355ao%40googlegroups.com.
