OWFS & PI4

[vigilancewx]

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

[Glenn McKechnie]

This sounds familiar.
Reviewing an older post shows some similarities with this info.

https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!searchin/weewx-
user/exNoController|sort:date/weewx-user/CfhGLIF8aaU/Cbjjo4wvBAAJ

Not all of that will apply to your situation but I think the first part will.

If it does, skip to the last post in that thread where Howard Walter
gives an excellent outline of the steps required to implement the
newer method.

If that solves it for you, confirm the fix here and we'll post Howards
outline on the wiki.

> --
> 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+...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/91744861-af7c-4378-8190-c1fc6ae425ca%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>


--


Cheers
Glenn

rorpi - read only raspberry pi & various weewx addons
https://github.com/glennmckechnie

[vigilancewx]

Thank you for the information

yes that appears to be the problem

http://203.213.243.61/weewx/owpkg/owpkg.tar.gz

the link has expired so unable to update the relevant packages.

  above seems to easier fix  as i am unsure how to implement the final section added by Howard  

i have followed the steps as you can see below

pi@raspberrypi:~ $ sudo apt install owserver ow-shell
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
  libftdi1-2 libow-3.2-3 owfs-common
The following NEW packages will be installed:
  libftdi1-2 libow-3.2-3 ow-shell owfs-common owserver
0 upgraded, 5 newly installed, 0 to remove and 2 not upgraded.
Need to get 375 kB of archives.
After this operation, 1,348 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://archive-bm.raspbian.org/raspbian buster/main armhf libftdi1-2 armhf 1.4-1+b2 [27.7 kB]
Get:2 http://archive-bm.raspbian.org/raspbian buster/main armhf owfs-common all 3.2p3+dfsg1-2 [17.6 kB]
Get:3 http://archive-bm.raspbian.org/raspbian buster/main armhf libow-3.2-3 armhf 3.2p3+dfsg1-2 [269 kB]
Get:4 http://archive-bm.raspbian.org/raspbian buster/main armhf ow-shell armhf 3.2p3+dfsg1-2 [29.8 kB]
Get:5 http://archive-bm.raspbian.org/raspbian buster/main armhf owserver armhf 3.2p3+dfsg1-2 [30.8 kB]
Fetched 375 kB in 1s (370 kB/s)
Selecting previously unselected package libftdi1-2:armhf.
(Reading database ... 134162 files and directories currently installed.)
Preparing to unpack .../libftdi1-2_1.4-1+b2_armhf.deb ...
Unpacking libftdi1-2:armhf (1.4-1+b2) ...
Selecting previously unselected package owfs-common.
Preparing to unpack .../owfs-common_3.2p3+dfsg1-2_all.deb ...
Unpacking owfs-common (3.2p3+dfsg1-2) ...
Selecting previously unselected package libow-3.2-3:armhf.
Preparing to unpack .../libow-3.2-3_3.2p3+dfsg1-2_armhf.deb ...
Unpacking libow-3.2-3:armhf (3.2p3+dfsg1-2) ...
Selecting previously unselected package ow-shell.
Preparing to unpack .../ow-shell_3.2p3+dfsg1-2_armhf.deb ...
Unpacking ow-shell (3.2p3+dfsg1-2) ...
Selecting previously unselected package owserver.
Preparing to unpack .../owserver_3.2p3+dfsg1-2_armhf.deb ...
Unpacking owserver (3.2p3+dfsg1-2) ...
Setting up libftdi1-2:armhf (1.4-1+b2) ...
Setting up owfs-common (3.2p3+dfsg1-2) ...

Creating config file /etc/owfs.conf with new version
Setting up ow-shell (3.2p3+dfsg1-2) ...
Setting up libow-3.2-3:armhf (3.2p3+dfsg1-2) ...
Setting up owserver (3.2p3+dfsg1-2) ...
Job for owserver.service failed because the service did not take the steps required by its unit configuration.
See "systemctl status owserver.service" and "journalctl -xe" for details.
invoke-rc.d: initscript owserver, action "start" failed.
● owserver.service - Backend server for 1-wire control
   Loaded: loaded (/lib/systemd/system/owserver.service; disabled; vendor preset: enabled)
   Active: activating (auto-restart) (Result: protocol) since Thu 2019-07-18 12:53:41 BST; 29ms ago
     Docs: man:owserver(1)
  Process: 1193 ExecStart=/usr/bin/owserver -c /etc/owfs.conf (code=exited, status=0/SUCCESS)
 Main PID: 1193 (code=exited, status=0/SUCCESS)
dpkg: error processing package owserver (--configure):
 installed owserver package post-installation script subprocess returned error exit status 1
Processing triggers for man-db (2.8.5-2) ...
Processing triggers for libc-bin (2.28-10+rpi1) ...
Processing triggers for systemd (241-5+rpi1) ...
Errors were encountered while processing:
 owserver
E: Sub-process /usr/bin/dpkg returned an error code (1)
pi@raspberrypi:~ $


 owserver
E: Sub-process /usr/bin/dpkg returned an error code (1)
pi@raspberrypi:~ $ ^C
pi@raspberrypi:~ $ sudo  /etc/owfs.conf
sudo: /etc/owfs.conf: command not found
pi@raspberrypi:~ $ sudo  nano /etc/owfs.conf
pi@raspberrypi:~ $ sudo  nano /etc/owfs.conf
pi@raspberrypi:~ $  sudo systemctl stop owserver
pi@raspberrypi:~ $ sudo systemctl enable owserver
Synchronizing state of owserver.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable owserver
Created symlink /etc/systemd/system/multi-user.target.wants/owserver.service → /lib/systemd/system/owserver.service.
Created symlink /etc/systemd/system/sockets.target.wants/owserver.socket → /lib/systemd/system/owserver.socket.
pi@raspberrypi:~ $ sudo systemctl start owserver
Job for owserver.service failed because the service did not take the steps required by its unit configuration.
See "systemctl status owserver.service" and "journalctl -xe" for details.
pi@raspberrypi:~ $

[Glenn McKechnie]

Don't worry about owpkg.tar.gz. It was relevant at the time, it's not now.

dpkg didn't finish the installation of owserver, it failed for some
reason. Possibly a version mismatch? Try refreshing the package
database with...

sudo apt update

then redo the installation...

sudo apt install owserver ow-shell

Hopefully you'll have a successful install this time around.

I assume /etc/owfs.conf has been edited to have just the 2 lines
mentioned? Check it.

server: usb = all
server: port = 4304

Try a systemctl 'restart', or better yet 'stop' then 'start'. and it
never hurts to do a 'status' check.

Fingers are crossed for you.



what does /etc/init.d/owserver status return - or the equivalent with systemctl.

On 18/07/2019, vigilancewx <vigil...@gmail.com> wrote:

> Thank you for the information
>
> yes that appears to be the problem
>
> http://203.213.243.61/weewx/owpkg/owpkg.tar.gz

> <http://www.google.com/url?q=http%3A%2F%2F203.213.243.61%2Fweewx%2Fowpkg%2Fowpkg.tar.gz&sa=D&sntz=1&usg=AFQjCNGchfIwPGp0wUYAWpve_0JFLYIzxg>

> --
> 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+...@googlegroups.com.
> To view this discussion on the web visit

> https://groups.google.com/d/msgid/weewx-user/bd9c940d-5507-4968-8582-7fe7f3d7c868%40googlegroups.com.

[vigilancewx]

Hi Glenn

thanks for helping out

Tried the following but still getting errors

sudo apt upate

sudo apt upgrade

sudo apt install owserver ow-shell

/etc/owfs.conf

file updated

pi@raspberrypi:~ $ sudo apt install owserver ow-shell
Reading package lists... Done
Building dependency tree
Reading state information... Done

The following packages were automatically installed and are no longer required:
  libboost-system1.62.0 libboost-thread1.62.0 libreoffice-gtk2
Use 'sudo apt autoremove' to remove them.

The following additional packages will be installed:
  libftdi1-2 libow-3.2-3 owfs-common
The following NEW packages will be installed:
  libftdi1-2 libow-3.2-3 ow-shell owfs-common owserver

0 upgraded, 5 newly installed, 0 to remove and 0 not upgraded.

Need to get 375 kB of archives.
After this operation, 1,348 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://archive-bm.raspbian.org/raspbian buster/main armhf libftdi1-2 armhf 1.4-1+b2 [27.7 kB]
Get:2 http://archive-bm.raspbian.org/raspbian buster/main armhf owfs-common all 3.2p3+dfsg1-2 [17.6 kB]
Get:3 http://archive-bm.raspbian.org/raspbian buster/main armhf libow-3.2-3 armhf 3.2p3+dfsg1-2 [269 kB]
Get:4 http://archive-bm.raspbian.org/raspbian buster/main armhf ow-shell armhf 3.2p3+dfsg1-2 [29.8 kB]
Get:5 http://archive-bm.raspbian.org/raspbian buster/main armhf owserver armhf 3.2p3+dfsg1-2 [30.8 kB]

Fetched 375 kB in 6s (59.2 kB/s)

Selecting previously unselected package libftdi1-2:armhf.

(Reading database ... 140620 files and directories currently installed.)

   Active: activating (auto-restart) (Result: protocol) since Thu 2019-07-18 15:55:14 BST; 28ms ago
     Docs: man:owserver(1)
  Process: 8854 ExecStart=/usr/bin/owserver -c /etc/owfs.conf (code=exited, status=0/SUCCESS)
 Main PID: 8854 (code=exited, status=0/SUCCESS)

dpkg: error processing package owserver (--configure):
 installed owserver package post-installation script subprocess returned error exit status 1
Processing triggers for man-db (2.8.5-2) ...
Processing triggers for libc-bin (2.28-10+rpi1) ...
Processing triggers for systemd (241-5+rpi1) ...
Errors were encountered while processing:
 owserver
E: Sub-process /usr/bin/dpkg returned an error code (1)

pi@raspberrypi:~ $ sudo nano /etc/owfs.conf/

pi@raspberrypi:~ $ sudo nano /etc/owfs.conf

then

/etc/init.d/owserver status return

pi@raspberrypi:~ $ /etc/init.d/owserver status

● owserver.service - Backend server for 1-wire control
   Loaded: loaded (/lib/systemd/system/owserver.service; disabled; vendor preset: enabled)

   Active: failed (Result: protocol) since Thu 2019-07-18 16:02:44 BST; 1min 45s ago
     Docs: man:owserver(1)
  Process: 9530 ExecStart=/usr/bin/owserver -c /etc/owfs.conf (code=exited, status=0/SUCCESS)
 Main PID: 9530 (code=exited, status=0/SUCCESS)

Jul 18 16:02:44 raspberrypi systemd[1]: owserver.service: Service RestartSec=100ms expired, scheduling restart.
Jul 18 16:02:44 raspberrypi systemd[1]: owserver.service: Scheduled restart job, restart counter is at 5.
Jul 18 16:02:44 raspberrypi systemd[1]: Stopped Backend server for 1-wire control.
Jul 18 16:02:44 raspberrypi systemd[1]: owserver.service: Start request repeated too quickly.
Jul 18 16:02:44 raspberrypi systemd[1]: owserver.service: Failed with result 'protocol'.
Jul 18 16:02:44 raspberrypi systemd[1]: Failed to start Backend server for 1-wire control.
pi@raspberrypi:~ $ ^C

On Thursday, July 18, 2019 at 8:55:42 AM UTC+1, vigilancewx wrote:

[Glenn McKechnie]

I don't run mine under systemd, however; If I run through the same
install process as above, on a machine that has systemd installed I
get the same error as you IF I don't have the USB module plugged in
when I attempt to start it.

So, is yours plugged in when you do the install or attempt the restart?

If it is plugged in, I'm out of ideas as googling "owserver.service:
Failed with result 'protocol'." doesn't turn up much that appears
relevant.

> --
> 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+...@googlegroups.com.
> To view this discussion on the web visit

> https://groups.google.com/d/msgid/weewx-user/9fb91704-7d3f-4c57-b16c-ec4065b70552%40googlegroups.com.

[Glenn McKechnie]

Given that you had the dongle installed (per your first post) and that
I'm out of ideas. The following list posting at owfs.org may prove
interesting? In particular the last post by the OP.

https://sourceforge.net/p/owfs/mailman/owfs-developers/thread/8b89c145-3f72-6b2b-d992-36f1666a52d6%40kky.zcu.cz/#msg36719234

It's not the sort of solution you can nail on the wall, or take to the
boss, but it does suggest gremlins do exist.
For me, the bonus is that it worked once and, is no vaguer than some
of my suggestions!

[vigilancewx]

OK I figured it out with your help something wrong with python-ow 3-xxx

get a clean install with regards to 1 wire ie python-ow

the idea is to install python-ow2.9

download the deb packages

i copied them to my /var/cache/apt/archives/partia/

dont know if that matters

and installed them

works fine now

sudo dpkg -i /var/cache/apt/archives/partial/libusb-0.1-4_0.1.12-25_armhf.deb

sudo dpkg -i /var/cache/apt/archives/partial/owfs-common_2.9p8-6_all.deb

sudo dpkg -i /var/cache/apt/archives/partial/libow-2.9-8__2.9p8-6_armhf.deb

sudo dpkg -i /var/cache/apt/archives/partial/python-ow_2.9p8-6_armhf.deb

sudo /home/weewx/bin/wee_extension --install weewx-owfs-0.21.tgz

On Thursday, July 18, 2019 at 8:55:42 AM UTC+1, vigilancewx wrote:

[vigilancewx]

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:

[Glenn McKechnie]

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.

> --
> 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+...@googlegroups.com.
> To view this discussion on the web visit

> https://groups.google.com/d/msgid/weewx-user/61e04a56-7e35-4029-81f4-2440defe6107%40googlegroups.com.

[vigilancewx]

Glenn

Thanks for the detailed information very informative

i guess i will keep a good working .img file nice and safe

If and when i do any upgrade i have something to fall back on

I know if we never upgraded we would still be using DOS or win 3.1 but sometimes its a headache

thanks again

On Thursday, July 18, 2019 at 8:55:42 AM UTC+1, vigilancewx wrote: