Hi all Forum users I'm trying to get fhem (v 5.9.18775) working on a RPI (Linux raspberrypi 4.14.98+ #1200 Tue Feb 12 20:11:02 GMT 2019 armv6l GNU/Linux) with the w1 kernel modules and owserver(owserver version: 3.1p5 libow version: 3.1p5).
I check that w1-kernel modules works -> OK root@raspberrypi:/etc# ls /sys/bus/w1/devices/ 28-0115835a14ff 29-0000001d489d w1_bus_master1 I use following /etc/owfs.conf root@raspberrypi:/etc# grep -v '^#' /etc/owfs.conf !server: server = localhost:4304 server: w1 server: timeout_w1 = 10 server: port = localhost:4304 I start the owserver with root@raspberrypi:~# systemctl start owserver I check that this also works with owfs like root@raspberrypi:/etc# owfs -m /mnt/1wire root@raspberrypi:/etc# ls /mnt/1wire/ 28.FF145A831501 29.9D481D000000 bus.0 simultaneous structure uncached 29.9D481D000000 alarm settings statistics system I kill owfs I visit then fhem on http://192.168..:8083 and begin defining things define myOWServer OWServer localhost:4304 get myOWServer devices -> this does return nothing !! the autocreate does not kick in nothing happens. I kill the owserver with systemctl Next step I start owserver like this root@raspberrypi:/etc#owserver --w1 -c /etc/owfs --debug and the suddenly everything works, autocreate finds everything I'm half happy the easiest workaround would be to fiddle in the startup scripts but this would be last resort. I tested to see if owserver reads the real conf file -> it does. I made some syntax errors in the conf file -> they are recognised and the argument parsing in owserver seem to work allright. root@raspberrypi:/etc# owserver --debug -c/etc/owfs.conf DEBUG MODE libow version: 3.1p5 DEBUG: ow_inotify.c:(37) Added /etc/owfs.conf to the watch list DEBUG: ow_opt.c:(298) Configuration file (/etc/owfs.conf:1) Program=Not server, Option=server, Value=localhost:4304 DEBUG: ow_opt.c:(298) Configuration file (/etc/owfs.conf:2) Program=server, Option=w1, Value= DEBUG: ow_opt.c:(343) Configuration file (/etc/owfs.conf:2) Option w1 recognized as w1. Value= ---------------------------------------------------------------------------------------^ .... By the way root@raspberrypi:/etc# owserver -c/etc/owfs.conf --debug DEBUG MODE libow version: 3.1p5 DEBUG: ow_daemon.c:(170) main thread id = 3063098528 CONNECT: ow_dnssd.c:(81) Zeroconf/Bonjour is disabled since dnssd library isn't found CALL: ow_parsename.c:(104) path=[] DEBUG: owlib.c:(77) Global temp limit 0C to 100C (for fake and mock adapters) DEBUG: ow_net_server.c:(76) ServerAddr: [localhost] [4304] DEBUG: ow_w1_list.c:(54) Sending w1 bus master list message DEBUG: ow_w1_send.c:(132) Netlink send ----------------- NLMSGHDR: len=48 type=3 (NLMSG_DONE) flags=5 seq=0|1 pid=3891 CN_MSG: idx/val=3/1 (CN_W1_IDX) seq=0|1 ack=1 len=12 flags=0 W1_NETLINK_MSG: type=6 (W1_LIST_MASTERS) len=0 id=0 W1_NETLINK_CMD: NULL w1c field NULL data DEBUG: ow_w1_send.c:(143) NETLINK sent seq=1 DEBUG: ow_w1_dispatch.c:(172) Dispatch loop DEBUG: ow_w1_parse.c:(112) Wait to peek at message DEBUG: ow_w1_parse.c:(120) Pre-parse header: 16 bytes len=52 type=3 seq=0|1 pid=0 The argument order for owserver seems to matter (here no debug info on conf_file parsing) So I'm puzzled. Does|did someone have similar symptoms If yes what was the solution? kind regards Cedric _______________________________________________ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
