On Wednesday, June 12, 2019 at 6:01:34 AM UTC-4, Olivier Payrastre wrote:
>
> So if someone can help me cause I understand a bit of code, but not at all
> python :( Just what I think, is that channel isn't improved in original
> code, so, what is send to weewx is all channels from the interceptor driver
> to outTemp and outHumid
>
when you use the lw30x station and the interceptor driver, use the
`sensor_map` to distinguish sensors. the default sensor map puts the
temperature and humidity values from all sensors into the 'outTemp' and
'outHumidity' fields.
this is how you would define a sensor map for a configuration with 4
sensors:
[Interceptor]
...
[[sensor_map]]
pressure = baro.*.*
outTemp = ot.1:*.*
outHumidity = oh.1:*.*
windSpeed = ws.?:*.*
windGust = wg.?:*.*
windDir = wd.?:*.*
rainRate = rr.?:*.*
rain = rain.?:*.*
UV = uvh.?:*.*
extraTemp1 = ot.2:*.* # office
extraHumid1 = oh.2:*.*
extraTemp2 = ot.3.*.* # garage
extraHumid2 = oh.3:*.*
extraTemp3 = ot.4:*.* # pool
extraHumid3 = oh.4:*.*
the label on the left is the name of a database field (e.g., outTemp), and
the pattern on the right is a tuple with glob-style pattern matching. each
tuple is a pattern of the form:
<observation_name>.<channel_id>:<rid>.<mac>
typically you only need to distinguish using the 'channel_id' - you only
need to specify the 'rid' and 'mac' if you have multiple sensors of the
same type using the same channel.
this sensor_map pattern is used in most weewx drivers that have extensible
sensors. the tuple syntax varies depending on the hardware.
m
--
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/weewx-user/985d52b5-a4fa-47ec-96ea-1e793a6a9064%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
