Just as a final conclusion - during this night the weekwindvec diagram has
been created also at 3:00 as expected (no longer error messages within
journalctl).
[image: weekwindvec.png]
Its timestamp 03:00:00 proves it (to be compared with 23:00:00 some posts
ago without the xtypes.py fix).
Micha
Assuming you didn't want to pm me:
> I'll go through and tag names to them. I tried with making "name =
Wind", etc. in a prior attempt, but apparently I can't be arbitrary with
FieldName?
You need to map the individual value to an existing database column,
depending on the schema you use the
I think you need something like this, to map the values to obs_types:
# The topics to subscribe to.
[[topics]]
unit_system = METRICWX
[[[rtl_433/pi4b8/devices/Acurite-5n1/A/3030/humidity]]]
name = outHumidity
[[[rtl_433/pi4b8/devices/Acurite-5n1/A/3030/r
journal logs:
root@weewx:~# journalctl -u weewx.service -f
Nov 18 11:10:32 weewx python3[848]: weewx[848] INFO weewx.manager: Added
record 2023-11-18 11:10:00 EST (1700323800) to database 'weewx.sdb'
Nov 18 11:10:32 weewx python3[848]: weewx[848] INFO weewx.manager: Added
record 2023-11-18 11:10
I'm new in trying to get weewx set up to use as a replacement for my
acurite display on the wall. I have a server running rtl_433 that is
outputting my weather sensor in mqtt form (ExecStart=/usr/bin/rtl_433 -C si
-F mqtt) which for my other mqtt-based weather plugins, works fine. For
weewx,
