I'd say they will be overwritten on the next upgrade. As it's Debian at heart there is a method to lock a package version (search for : debian lock package version ) and prevent upgrades but the problem still exists in that other upgrades and their dependencies, eg weewx's eventual move from python2.7 to python3 , may no longer work with those packages.
Further to the above: Recapping for my own benefit and future searches, because the issue is not fully resolved yet. Reviewing the previous links in this thread and dredging up my memories of the original event that started the move to owserver, a quick summary is... As you note, python-ow 3-xxx on Debian Raspian (perhaps others) is broken. This causes upgrades and new installs of weewx and weewx-owfs to fail. Reverting to a 2.xxx version restores the installation and everything works again. Howard Walter was burnt by this, confirmed it was a python-ow problem, and took that to the owfs list. The developers there responded that as it was with the python-ow package and that the build relied on the swig bindings, which were no longer being supported upstream, a fix was not worth the effort. Understandable as abandonware is by definition unsupported. They suggested the owserver installation method to allow python-ow to work, not only as it had before but via the preferred method of communicating directly with a running owserver. The suggestion was also made to stop using python-ow altogether (more on that later). The method provided by the developers on the owfs list, and proved by Howard, works with owserver and, I'm assuming?, python-ow 3xx. Howard posted his working method to the weewx list. However, going by your recent problem, It appears that besides python-ow 3x still being broken, that the installation of owserver, under systemd? on Debian Buster (Raspian) is also broken. There doesn't appear to be a solution for the new owserver problem as the post I referred to previously said it just "comes good after awhile". Good for the Original Poster, but not a fix that's portable :-) https://sourceforge.net/p/owfs/mailman/owfs-developers/thread/8b89c145-3f72-6b2b-d992-36f1666a52d6%40kky.zcu.cz/#msg36719234 It seems like it's possibly a systemd problem but I don't have a Buster install, nor the time to do one and test it. My weewx installation here uses init.d, owserver and ownet (pyownet). It doesn't use python-ow, instead it uses a modified version of Mathew Walls owfs.py script. That modified script is no secret, it can be made available if required but you need a working owserver, and while the python-ow binding method still works it is not necessary. On 20/07/2019, vigilancewx <[email protected]> wrote: > Hi > > Just tried this method and it has worked on 3 separate installs > > one question when i update or upgrade the pi will it over write these > files?? causing it to fail again > > > > > On Thursday, July 18, 2019 at 8:55:42 AM UTC+1, vigilancewx wrote: >> >> I have used OWFS service for a few years and its worked flawlessly >> >> I am trying to get it to work on a new PI4 but i cant get to read any >> sensors >> >> >> I have followed the owfs service installation guide as in the past >> >> >> >> >> pi@raspberrypi:~/Myideas $ sudo PYTHONPATH=/home/weewx/bin python >> /home/weewx/bin/user/owfs.py --sensors >> Traceback (most recent call last): >> File "/home/weewx/bin/user/owfs.py", line 618, in <module> >> main() >> File "/home/weewx/bin/user/owfs.py", line 578, in main >> ow.init(iface) >> File "/usr/lib/python2.7/dist-packages/ow/__init__.py", line 221, in >> init >> raise exNoController >> ow.exNoController >> >> Previously i think the only time i have had the above error is when i >> have forgotten to plug the dalas adapter in to a USB port >> >> it appears the service cant read my usb port >> >> from the syslog file >> Jul 18 08:29:44 raspberrypi OWFS[3132]: DEFAULT: owlib.c:(208) Cannot open >> >> USB bus master >> Jul 18 08:29:44 raspberrypi OWFS[3132]: DEFAULT: owlib.c:(52) No valid >> 1-wire buses found >> >> but the device is connected >> >> >> pi@raspberrypi:~/Myideas $ lsusb >> Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub >> Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub >> Bus 001 Device 003: ID 04fa:2490 Dallas Semiconductor DS1490F 2-in-1 Fob, >> >> 1-Wire adapter >> Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub >> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub >> pi@raspberrypi:~/Myideas $ >> >> >> any ideas how to read the senors?? >> >> thanks for any help >> >> >> > > -- > 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/61e04a56-7e35-4029-81f4-2440defe6107%40googlegroups.com. > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/CAAraAzhKpVT88u3%2BdsVnc7OUEsxLsPaTEMzmCvKhh9ZNgLf%3D9A%40mail.gmail.com.
