*I'm following this because one of my weewx stations rely heavily on OW
sensors to augment the data from my Davis Vantage pro2. *
*I'd upgrade to weewx 4.x but really can't lose owfs operability*.
Thx/mp
On Tuesday, May 26, 2020 at 10:06:04 AM UTC+2, Gazza wrote:
>
>
> If you are running the owfs.py from my fork, the syslog message will
>> tell you what module it has opted to run under. That message occurs in
>> the first few log entries after weewx initializes. It's an INFO
>> message
>>
>
> So with python-ow installed I get this in the INFO:
>
> May 26 17:43:02 GazPi4 weewx[1159] INFO user.owfs: service version is 0.23
> (ow)
> May 26 17:43:02 GazPi4 weewx[1159] INFO user.owfs: interface is localhost:
> 4304
>
> With python-ow removed I get this:
>
> May 26 17:50:52 GazPi4 weewx[1259] INFO user.owfs: service version is 0.23
> (pyownet)
> May 26 17:50:52 GazPi4 weewx[1259] INFO user.owfs: interface is localhost:
> 4304
> May 26 17:50:52 GazPi4 weewx[1259] INFO user.owfs: sensor map is {u
> 'extraTemp5': u'/uncached/28.E10441040000/temperature'}
>
>
> I have waited for a REC to be generated and the 1wire sensor allocated to
> extraTemp5 is being reported OK, so it does look like it is working fine
> with either method.
>
> I think I was thrown off track when running direct failed, does that mean
> the broken _main_ section is not called when it is running from weewx ?
>
>
> Gaz
>
>
>
--
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/e7e9f9b7-4388-48d0-ac7d-776b91c59dd7%40googlegroups.com.
