I have a very similar problem.
Rpi4 & Buster.

After Micks emails, I did try to remove & purge my ow-shell and owserver,
the only thing that starts is the fake sensors.
I have not been able to access my sensors on my Buster install, I don't
understand what's wrong and how I can get it working again.

I did have a thunder strike that grilled my Raspberry Pi (3?) but the 1wire
board and the RPI is brand new.

Does anyone have any ideas how I can access my sensors again?

*ls /dev/i2c**
/dev/i2c-1

*ofws.conf:*
! server: server = localhost:4304
server: i2c = /dev/i2c-1
http: port = 2121
ftp: port = 2120
server: port = localhost:4304

*sudo /usr/bin/owserver -c /etc/owfs.conf --debug*
DEBUG MODE
libow version:
        3.2p3
  DEBUG: ow_daemon.c:(170) main thread id = 3069411056
CONNECT: ow_dnssd.c:(81) Zeroconf/Bonjour is disabled since dnssd library
isn't found
   CALL: ow_parsename.c:(174) path=[]
  DEBUG: owlib.c:(77) Global temp limit 0C to 100C (for fake and mock
adapters)
  DEBUG: ow_regex.c:(24) Reg Ex expression <^$> compiled to 0xb6efd60c
  DEBUG: ow_regex.c:(24) Reg Ex expression <^all$> compiled to 0xb6efd62c
  DEBUG: ow_regex.c:(24) Reg Ex expression <^scan$> compiled to 0xb6efd64c
  DEBUG: ow_regex.c:(24) Reg Ex expression <^\*$> compiled to 0xb6efd66c
  DEBUG: ow_regex.c:(24) Reg Ex expression
<^[[:digit:]]{1,3}\.[[:digit:]]{1,3}\.[[:digit:]]{1,3}\.[[:digit:]]{1,3}$>
compiled to 0xb6efd68c
  DEBUG: ow_regex.c:(24) Reg Ex expression <^-?[[:digit:]]+$> compiled to
0xb6efd6ac
]*$> compiled to 0xb6efd6ccg Ex expression <^ *([^ ]+)[
]*$> compiled to 0xb6efd6ecg Ex expression <^ *([^ ]+) *: *([^ ]+)[
]*$> compiled to 0xb6efd70cg Ex expression <^ *([^ ]+) *: *([^ ]+) *: *([^
]+)[
  DEBUG: ow_regex.c:(53) Not found
  DEBUG: ow_regex.c:(53) Not found
  DEBUG: ow_regex.c:(100) 0: 0->10 found <></dev/i2c-1><>
  DEBUG: ow_regex.c:(100) 1: 0->10 found <></dev/i2c-1><>
  DEBUG: ow_parse_address.c:(87) Text </dev/i2c-1>
  DEBUG: ow_parse_address.c:(142) First </dev/i2c-1>
CONNECT: ow_ds2482.c:(396) Found an i2c device at /dev/i2c-1 address 18
CONNECT: ow_ds2482.c:(422) i2c device at /dev/i2c-1 address 18 cannot be
reset. Not a DS2482.
CONNECT: ow_ds2482.c:(396) Found an i2c device at /dev/i2c-1 address 19
CONNECT: ow_ds2482.c:(422) i2c device at /dev/i2c-1 address 19 cannot be
reset. Not a DS2482.
CONNECT: ow_ds2482.c:(396) Found an i2c device at /dev/i2c-1 address 1A
CONNECT: ow_ds2482.c:(422) i2c device at /dev/i2c-1 address 1A cannot be
reset. Not a DS2482.
CONNECT: ow_ds2482.c:(396) Found an i2c device at /dev/i2c-1 address 1B
  DEBUG: ow_ds2482.c:(516) ok
CONNECT: ow_ds2482.c:(422) i2c device at /dev/i2c-1 address 1B cannot be
reset. Not a DS2482.
CONNECT: ow_ds2482.c:(396) Found an i2c device at /dev/i2c-1 address 1C
CONNECT: ow_ds2482.c:(422) i2c device at /dev/i2c-1 address 1C cannot be
reset. Not a DS2482.
CONNECT: ow_ds2482.c:(396) Found an i2c device at /dev/i2c-1 address 1D
CONNECT: ow_ds2482.c:(422) i2c device at /dev/i2c-1 address 1D cannot be
reset. Not a DS2482.
CONNECT: ow_ds2482.c:(396) Found an i2c device at /dev/i2c-1 address 1E
CONNECT: ow_ds2482.c:(422) i2c device at /dev/i2c-1 address 1E cannot be
reset. Not a DS2482.
CONNECT: ow_ds2482.c:(396) Found an i2c device at /dev/i2c-1 address 1F
CONNECT: ow_ds2482.c:(422) i2c device at /dev/i2c-1 address 1F cannot be
reset. Not a DS2482.
  DEBUG: ow_com_close.c:(42) Unimplemented!!!
CONNECT: owlib.c:(145) Cannot detect an i2c DS2482-x00 on /dev/i2c-1
DEFAULT: owlib.c:(52) No valid 1-wire buses found
  DEBUG: ow_exit.c:(17) Exit code = 1
   CALL: ow_lib_close.c:(21) Starting Library cleanup
   CALL: ow_lib_stop.c:(22) Clear Cache
  DEBUG: ow_cache.c:(295) Flipping cache tree (purging timed-out data)
  DEBUG: ow_cache.c:(313) flip cache. tdestroy() will be called.
  DEBUG: ow_cache.c:(295) Flipping cache tree (purging timed-out data)
  DEBUG: ow_cache.c:(313) flip cache. tdestroy() will be called.
   CALL: ow_lib_stop.c:(24) Closing input devices
   CALL: ow_lib_stop.c:(26) Closing output devices
   CALL: ow_lib_close.c:(42) Finished Library cleanup
  DEBUG: ow_lib_close.c:(50) Libraries closed

I'm able to see the i2c device:
sudo i2cdetect -y 1
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:          -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- 1b -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
....

I had it working on my last install with a Rpi3 with this conf:
(cropping commented lines)

! server: server = localhost:4304
server: i2c = ALL:ALL
http: port = 2121
ftp: port = 2120
server: port = localhost:4304

Any ideas are welcome!
Thanks!

[image: Linkedin] <http://de.linkedin.com/in/rlagus> *Robert Lagus*

+358 (0)40 662 44 99

rob...@lagus.net



On Sun, 15 Sep 2019 at 21:08, Mick Sulley <m...@sulley.info> wrote:

> Many thanks Colin.
>
> The log had many lines like
>
> Sep 15 18:01:27 pi-solar-old kernel: [ 3631.364529] w1_master_driver
> w1_bus_master1: Attaching one wire slave 00.a20000000000 crc 13
> Sep 15 18:01:27 pi-solar-old kernel: [ 3631.383280] w1_master_driver
> w1_bus_master1: Family 0 for 00.a20000000000.13 is not registered.
> After a bit of head scratching I looked at /etc/owfs.config and that did
> not make much sense, so I deleted it and created a new one.  It is now
> working!
>
> What I don't understand is how owfs.conf gets created in the first place.
> I uninstalled and purged owserver and ow-shell, but owfs.conf was still
> there so I deleted it.  I then reinstalled but it didn't create owfs.conf,
> don't understand why.
>
> Anyway, now I can get back to testing :)
>
> Mick
>
> On 15/09/2019 16:57, Colin Law wrote:
>
> Check in the owserver log (likely /var/log/syslog) to see if it is showing
> errors.
>
> Colin
>
> On Sun, 15 Sep 2019, 12:08 Mick Sulley, <m...@sulley.info> wrote:
>
>> I am having trouble getting owfs to work on Raspbian Buster.  I have
>> posted on the Pi forum
>>
>>
>> https://www.raspberrypi.org/forums/viewtopic.php?f=28&t=251702&p=1536228#p1536228
>>
>> Someone said they had the same problem but no suggestions to fix it, so I
>> wonder if anyone here can give me a clue.
>>
>> I have just done a fresh install of Buster and updated. I ran
>> raspi-config and enabled 1-wire and i2c.
>> I have installed owserver ow-shell
>> At first it worked, I could see devices with owdir, but it has stopped
>> working, owdir returns nothing
>> I have run "sudo systemctl enable owserver.service"
>> but I see -
>>
>> pi@pi-solar-old:~ $ sudo systemctl status owserver.service
>> ● owserver.service - Backend server for 1-wire control
>>    Loaded: loaded (/lib/systemd/system/owserver.service; enabled; vendor 
>> preset: enabled)
>>    Active: failed (Result: protocol) since Fri 2019-09-13 21:47:16 BST; 48s 
>> ago
>>      Docs: man:owserver(1)
>>  Main PID: 493 (code=exited, status=0/SUCCESS)
>>
>> Sep 13 21:47:16 pi-solar-old systemd[1]: owserver.service: Service 
>> RestartSec=100ms expired, scheduling
>> Sep 13 21:47:16 pi-solar-old systemd[1]: owserver.service: Scheduled restart 
>> job, restart counter is at
>> Sep 13 21:47:16 pi-solar-old systemd[1]: Stopped Backend server for 1-wire 
>> control.
>> Sep 13 21:47:16 pi-solar-old systemd[1]: owserver.service: Start request 
>> repeated too quickly.
>> Sep 13 21:47:16 pi-solar-old systemd[1]: owserver.service: Failed with 
>> result 'protocol'.
>> Sep 13 21:47:16 pi-solar-old systemd[1]: Failed to start Backend server for 
>> 1-wire control.
>> pi@pi-solar-old:~ $
>>
>> I have tried disable, enable, restart for the service, I have removed and
>> reinstalled owserver and ow-shell but nothing helps.
>>
>> Any ideas?
>> _______________________________________________
>> Owfs-developers mailing list
>> Owfs-developers@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/owfs-developers
>>
>
>
> _______________________________________________
> Owfs-developers mailing 
> listOwfs-developers@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/owfs-developers
>
> _______________________________________________
> Owfs-developers mailing list
> Owfs-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/owfs-developers
>
_______________________________________________
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Reply via email to