Glenn:
Well, some progress (perhaps), but not enough.To make things easier to
read, responses from a command are in BLUE and configuration files are in
RED.
I followed your suggestions and "service weewx status" came back with the
following:
pi@raspberrypi:~ $ service weewx status
● weewx.service - LSB: weewx weather system
Loaded: loaded (/etc/init.d/weewx; generated)
Active: active (exited) since Thu 2020-04-16 21:30:28 EDT; 1min 38s ago
Docs: man:systemd-sysv-generator(8)
Process: 2565 ExecStart=/etc/init.d/weewx start (code=exited,
status=0/SUCCESS)
Apr 16 21:30:28 raspberrypi weewx[2580]: owfs: driver version is 0.21
Apr 16 21:30:28 raspberrypi weewx[2580]: owfs: interface is localhost:4304
Apr 16 21:30:28 raspberrypi weewx[2580]: owfs: sensor map is {'outTemp':
'/uncached/28.6E175D040000/temperature'}
Apr 16 21:30:28 raspberrypi weewx[2580]: owfs: sensor type map is {}
Apr 16 21:30:28 raspberrypi weewx[2580]: owfs: polling interval is 10
Apr 16 21:30:28 raspberrypi weewx[2580]: owfs: sensor unit system is metric
Apr 16 21:30:33 raspberrypi OWFS[2580]: DEFAULT: owlib.c:(52) No valid
1-wire buses found
Apr 16 21:30:33 raspberrypi OWFS[2580]: engine: Import of driver failed:
(<class 'ow.exNoController'>)
Apr 16 21:30:33 raspberrypi OWFS[2580]: engine: Unable to load driver:
Apr 16 21:30:33 raspberrypi OWFS[2580]: **** Exiting...
This is somewhat better than the previous result (one less error). Still
cannot find a "valid 1-Wire bus".
RUNNING THE FOLLOWING:
pi@raspberrypi:~ $ sudo systemctl status owserver
● owserver.service - Backend server for 1-wire control
Loaded: loaded (/lib/systemd/system/owserver.service; enabled; vendor
preset: enabled)
Active: failed (Result: signal) since Wed 2020-04-15 22:58:23 EDT; 22h
ago
Docs: man:owserver(1)
Process: 549 ExecStart=/usr/bin/owserver -c /etc/owfs.conf (code=killed,
signal=SEGV)
Main PID: 549 (code=killed, signal=SEGV)
Apr 15 22:58:23 raspberrypi systemd[1]: owserver.service: Service
RestartSec=100ms expired, scheduling restart.
Apr 15 22:58:23 raspberrypi systemd[1]: owserver.service: Scheduled restart
job, restart counter is at 5.
Apr 15 22:58:23 raspberrypi systemd[1]: Stopped Backend server for 1-wire
control.
Apr 15 22:58:23 raspberrypi systemd[1]: owserver.service: Start request
repeated too quickly.
Apr 15 22:58:23 raspberrypi systemd[1]: owserver.service: Failed with
result 'signal'.
Apr 15 22:58:23 raspberrypi systemd[1]: Failed to start Backend server for
1-wire control.
Throws the error above, Failed to start Backend server for 1-wire control.
I then stopped, enabled and started the owserver.
"Starting" fails as below:
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
pi@raspberrypi:~ $ sudo systemctl start owserver
Job for owserver.service failed because a fatal signal was delivered to the
control process.
See "systemctl status owserver.service" and "journalctl -xe" for details.
OWFS.CONF Follows:
# Sample configuration file for the OWFS suite for Debian GNU/Linux.
#
#
# This is the main OWFS configuration file. You should read the
# owfs.conf(5) manual page in order to understand the options listed
# here.
######################## SOURCES ########################
#
# With this setup, any client (but owserver) uses owserver on the
# local machine...
###! server: server = localhost:4304
#
# ...and owserver uses the real hardware, by default fake devices
# This part must be changed on real installation
## server: FAKE = DS18S20,DS2405
#
#### USB device: DS9490
server: usb = all
#
# Serial port: DS9097
#server: device = /dev/ttyS1
#
# owserver tcp address
#server: server = 192.168.10.1:3131
#
# random simulated device
#server: FAKE = DS18S20,DS2405
#
######################### OWFS ##########################
#
#mountpoint = /mnt/1wire
#allow_other
#
####################### OWHTTPD #########################
###http: port = 2121
####################### OWFTPD ##########################
###ftp: port = 2120
####################### OWSERVER ########################
#
######################### OWFS ##########################
#
#mountpoint = /mnt/1wire
#allow_other
#
####################### OWHTTPD #########################
###http: port = 2121
####################### OWFTPD ##########################
###ftp: port = 2120
####################### OWSERVER ########################
###server: port = localhost:4304
server: port = 4304
WEEWX.CONF follows:
Options for extension 'owfs'
[OWFS]
interface = localhost:4304
driver = user.owfs
[[sensor_type]]
[[sensor_map]]
outTemp = /uncached/28.6E175D040000/temperature
Again, thank you for all of your help. I really appreciate it. The thing
that confuses me is that everything works on a PC running Ubuntu but not on
the Pi.
On Thursday, April 16, 2020 at 8:15:01 PM UTC-4, Glenn McKechnie wrote:
>
> On 17/04/2020, michael form <[email protected] <javascript:>> wrote:
> > Glenn:
> >
> > Thank you for your response.
> >
> > apt show ow-python <<< does not show anything
>
> Ah, that's just me and the keyboard having issues again!
>
> > apt show python-ow <<< returns 3.2p3+dfg1-2
> >
> > apt show owserver returns info so I assume that owserver is installed.
>
> Ah, actually. I've given you the wrong command. To list installed
> packages try the following
>
> apt list --installed | grep owserver
> apt list --installed | grep python-ow
>
> Post the results of those commands
>
> > Do I need to uninstall things as per the referred post??
> >
> > - Start from a fresh system (no other owfs components installed) and
> > install owserver and ow-shell:
> > $ sudo apt install owserver ow-shell
>
> Nope. For a start, just give it try with...
> sudo apt install owserver ow-shell
>
> That should replace anything stale, or that's considered to clash.
>
> > - Delete (as root) the hyper-verbose default debian /etc/owfs.conf
> file
> > and use this minimal config:
> > server: usb = all
> > server: port = 4304
>
> Definitely do the above.
> Those 2 lines are all that needs to be in the /etc/owfs.conf file for
> this configuration to work.
>
> > - Enable and start the owserver
> > $ sudo systemctl stop owserver
> > $ sudo systemctl enable owserver
> > $ sudo systemctl start owserver
> >
>
> You could add a status check just to make sure it's all good
>
> sudo systemctl status owserver # that should work, but I'm not a systemctl
> user.
>
>
> > Current {OWFS}
> > interface = u
> > driver = user.owfs
> > [[sensor map]]
> > outTemp = /uncached/28.6E175D040000/temperature
> >
> >
> > Do I just need to change the "u" to localhost:4304 or any other changes
> > need to be made??
>
> That's it
> [OWFS]
> interface = localhost:4304
> driver = user.owfs
> [[sensor map]]
> outTemp = /uncached/28.6E175D040000/temperature
>
> (Although I have had one configuration baulk at localhost, using
> 127.0.0.1 worked ? interface = 127.0.0.1:4304)
>
> > Sorry for all of the questions as I said that I design hardware and am
> > familiar with Windows. Linux is a new experience for me.
> > Then again, I might as well spend the time at home learning new things.
> :)
>
> Agreed. An opportunity for us all :-)
>
>
> --
>
>
> 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/308ceb2b-730a-4a2e-860b-60fb14d5fb16%40googlegroups.com.
