On 26/05/2020, Gazza <gazc...@gmail.com> wrote:
> OK, I have done some more tests, first I have removed python-ow and now the
> owfs service in weewx is not working.
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
This is from my current session, I'm running with (pyownet)....
INFO user.owfs-dallas: driver version is 0.23.6 (pyownet)
Have a look in the last log, before you removed python-ow and see
which one it picked up, it will be either (ow) or (pyownet).
Might as well have a look at what it's using after you deleted
python-ow (ie: now) and see what it's running with..
to get pyownet installed, how was that done? Through pip?
A quick check to see if python can find them...
$ python2.7
Python 2.7.13 (default, Sep 26 2018, 18:42:22)
[GCC 6.3.0 20170516] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import ow
>>> import pyownet
>>> import arflegarflegloop
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
ImportError: No module named arflegarflegloop
>>>
If the module isn't present it will throw the ImportError message above.
> When I run systemctl status owserver it shows that it is enabled and
> running.
>
> pi@GazPi4:~ $ systemctl status owserver
> * owserver.service - Backend server for 1-wire control
> Loaded: loaded (/lib/systemd/system/owserver.service; enabled; vendor
> preset: enabled)
> Active: active (running) since Tue 2020-05-26 15:08:43 AEST; 34min ago
> Docs: man:owserver(1)
> Main PID: 365 (owserver)
> Tasks: 3 (limit: 4915)
> Memory: 2.8M
> CGroup: /system.slice/owserver.service
> `-365 /usr/bin/owserver -c /etc/owfs.conf
>
> May 26 15:08:43 GazPi4 systemd[1]: Starting Backend server for 1-wire
> control...
> May 26 15:08:43 GazPi4 owserver[365]: DEFAULT: ow_opt.c:(670) systemd mode
> -- ignore 'p' option
> May 26 15:08:43 GazPi4 systemd[1]: Started Backend server for 1-wire
> control.
So far so good.
> When I run owdir, the sensor is detected but I get no readings.
>
> pi@GazPi4:~ $ owdir
> /28.E10441040000
> /bus.0
> /uncached
> /settings
> /system
> /statistics
> /structure
> /simultaneous
> /alarm
try running...
owdir /28.E10441040000
and you should get the tree for that sensor, of which temperature
should be included in it.
I'm assuming that /28.E10441040000 is your DS1820, in which case the
following is the command to reveal it's temperature reading...
owget /28.E10441040000/temperature
> When I try to to run weewx owfs direct command it fails.
>
>
> pi@GazPi4:~ $ sudo PYTHONPATH=/home/weewx/bin python /home/weewx/bin/user/
> owfs.py --sensors --iface=localhost:4304
> Traceback (most recent call last):
> File "/home/weewx/bin/user/owfs.py", line 713, in <module>
> main()
> File "/home/weewx/bin/user/owfs.py", line 674, in main
> traverse(ow.Sensor('/'), identify_sensor)
> File "/home/weewx/bin/user/owfs.py", line 264, in Sensor
> return self.proxy.Sensor(path)
> AttributeError: '_Proxy' object has no attribute 'Sensor'
That doesn't surprise me.
I have a note on my fork that the _main_ section is broken if you are
using pyownet.
Mathews revision is a work in progress, as is mine. If memory serves
they can only pickup python-ow, not pyownet and the Sensor tree isn't
functioning , so yes. broken but a work in progress.
(In my fork, owfs-dallas.py is further advanced - it works under
python3,, but I'm not suggesting to swap to that either.)
> It seems that even though I had changed the weewx.conf from =/dec/i2c-1 to
> =localhost:4304 it was still using pyownet.
When you run weewx, take note of that INFO version message. Then we'll
know which module one to focus on.
--
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/CAAraAzgjTtuirS734zZvyefCjk20oCk-coTCvCHhbrOx%2B7dg-g%40mail.gmail.com.
