>> 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) [...]
> With python-ow removed I get this: > > May 26 17:50:52 GazPi4 weewx[1259] INFO user.owfs: service version is 0.23 > (pyownet) [...] > 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. That's good news. For you and me ;-) > 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 ? Correct. It's a separate section quite distinct from the Driver/Service side. It does need to be, and will be fixed as it's required to sort out the system_map. Thankfully you knew yours already. When it starts raining again, or we get locked up again :) I'll get back to it and see if inspiration strikes. It borrows a few functions from the main script, but the rest of it is fairly unique. Made more difficult at the moment as ow and pyownet approach things in different ways. Almost had it working on mine but I have a 1-wire hub which complicates a simple directory walk with pyownet. -- Cheers Glenn rorpi - read only raspberry pi & various weewx addons https://github.com/glennmckechnie -- 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/CAAraAzjCqdYpu5nC%3D%3DYo5qwWrcs11g8djVnvgHjsDyXDiQ-OuQ%40mail.gmail.com.
