[GELÖST] FHEM OWServer Debian Jessie / SET ohne Funktion

[V3ndetta]

Hallo zusammen,

sind aktuell Probleme mit FHEM im Zusammenspiel mit owserver/owhttpd 2.9p8 (Debian-Jessie) bekannt? Ich kann über das Webinterface alles sehen und schalten was zu schalten sein soll, allerdings kann FHEM nur lesen. Jeder "set" Versuch wird ohne Fehlermeldung ausgeführt, aber nichts passiert. Weder owserver mit error_level=9 noch verbose 5 in FHEM liefern brauchbare Daten :-/ Ein tshark auf Port 4304 zeigt dass zumindest etwas gesendet wird. Meine Vermutung ist eine Änderung im owfs Protokoll, kann dazu aber in den Changelogs nichts finden. Bin für jeden Hinweis dankbar!

Gruß

V3ndetta

[eldrik]

japp,

wenn du nach 2.9 in diesem Forumsbereich suchst wirst du einige Threads finden, die genau die von dir beschriebene Problematik behandeln, einziger funktionierender Workaround scheint derzeit der Downgrade auf Version 2.8 zu sein.

Greetz
Eldrik

[V3ndetta]

Danke für die Info! Hab jetzt die armhf Pakete für wheezy runtergeladen ( http://ftp.de.debian.org/debian/pool/main/o/owfs/ ) und per "dpkg -i " installiert. Geht wieder alles wie gewohnt, Installation war problemlos.

Benötigte Pakete:
- libow-2.8-15_2.8p15-1_armhf.deb
- owfs-common_2.8p15-1_all.deb
- owfs_2.8p15-1_all.deb
- owftpd_2.8p15-1_armhf.deb
- owhttpd_2.8p15-1_armhf.deb
- owserver_2.8p15-1_armhf.deb

sollte auch ohne owftp funktionieren, aber da ich es sowieso nutze hab ich es nicht versucht. Wenn ich Zeit habe schau ich mal ob ich markante Unterschiede in den Versionen finde die das Problem verursachen könnten.

Kann das vielleicht jemand im fhemwiki ergänzen?

Gruß

Marc

[ritter_runkel]

Hallo,
klingt so als ob ich das gleiche Problem hätte.
Bei mir läuft Jessie auf dem RPi und die per "sudo apt-get install owserver ow-shell owhttpd owftpd" installierten Pakete Version 2.9p8. Offenbar verursachen die aber das Problem, dass man nicht mehr schreiben kann.

Hast Du die Pakete einfach "drüber installiert"?
Kannst DU sagen, ob die alten Pakete auch unter  Jessie laufen?

grüße
Erik

[fruit]

Sorry for English reply...

There have been many small changes between wheezy and jessie versions of owserver. To see all changes you will need to look at git history, the included changelog is a long way out of date

The fhem supplied version of OWNet.pm no longer works correctly for writing to my Louis Swart OWDevice LCD with >=v2.9p8 - and possbly write operations to other devices but I have none to test.

OWNet.pm has now been fixed but I think is only available at present from git, not the snapshot files (https://sourceforge.net/p/owfs/code/ci/master/tree/module/ownet/perl5/OWNet/lib/).
This version will work with jessie owserver.
See https://sourceforge.net/p/owfs/mailman/message/34936918/

NB. you will only need this new version for owserver >=v2.9p8 and note also if using the latest OWNet.pm you will need to exclude OWNet.pm from fhem updates

It is also possible to build the current git master on raspbian jessie and replace relevant distro files with those built.

Perhaps there should be a note about this in OWDevice commandref - but I am not sure how to contact the maintainer

[MichaelO]

Would you mind to shortly explain the steps needed to "fix" an already performed "standard" installation with the apt-get command as described here:

http://www.fhemwiki.de/wiki/OWServer_%26_OWDevice

I think that your solution might solve my problem with OWServer and Jessie, however my Linux knowledge is not sufficient enough to know what exactly needs to be done with your explanation.

Thanks
Michael

[fruit]

I will try

If you have a Hobbyboards LCD there are still problems, hopefully resolved soon. Otherwise...

The simplest way, as you have jessie and probably owserver v2.9p8-6, is to replace just OWNet.pm with the latest available from the owfs git repository.
You should be able to download just the OWNet.pm file from https://sourceforge.net/p/owfs/code/ci/master/tree/module/ownet/perl5/OWNet/lib/ without having to clone the whole lot.

fhem uses OWNet.pm installed in /opt/fhem/FHEM/lib/ so rename or copy this file just in case you need it later then copy the downloaded version to the same location, something like..

Code Auswählen Erweitern

sudo cp ./Downloads/OWNet.pm /opt/fhem/FHEM/lib/

Restart fhem and see if your problem is solved, if not then you can replace the original OWNet.pm

If it does work then fhem will replace the new OWNet.pm with the previous version next time you update - so set

Code Auswählen Erweitern

attr global exclude_from_update lib/OWNet.pm

(There may be another copy of OWNet.pm on your system, /usr/share/perl5/OWNet.pm but I do not think fhem uses this one, if in doubt try rename and copy over.)

Please let me know if this has worked - or if my explanation is not clear

[MichaelO]

Thanks for the instructions, however - it didn't work out for my configuration.

• I downloaded the whole snapshot from the sourceforge link given.
• I then navigated to the desired file (perl5 directory) and copied this to the tmp on raspberry
• I then stopped fhem, via ssh renamed the old OWNet and moved the "new" file into the lib-folder
• I then set the rights to 666 (as original) and set chown fhem:dialout OWNet.pm

After raspi reboot fhem shows as up running but no access to website and no actions working. I also couldn't stop the service... no reaction at all. I then overwrote everything with the backup from this morning, after reboot everything's fine again.

I don't know where it went wrong, but altering with the file seems to crash fhem at once on my system. It seems that I have to keep up my second wheezy-raspbian with OWServer running until a solution is found.

Thanks anyways
Michael

[fruit]

The snapshot should have contained the current version, adapted to work with jessie owserver and it seems you installed correctly.

I am puzzled that it crashes your system, I have it running on two Pis and a jessie desktop.

It is possible to run the wheezy version on jessie, I did it to get my LCD working before chasing this bug.

If you have a backup of a wheezy install you can find and save the packages from /var/cache/apt/archives or at http://archive.raspbian.org/raspbian/pool/main/o/owfs/ where you need to download the 2.8p15 versions of owfs, owserver and any other ow, libow, libownet packages you have installed in jessie

I cannot remember if I uninstalled the jessie versions before

Code Auswählen Erweitern

sudo dpkg -i owserver_2.8p15-1_armhf.debor just installed them. Same for the others

What is the issue you are having? I can see if there has been anything similar on the owfs list

[MichaelO]

I use a sheepwalk electronics RPI2 1-Wire Host Adapter as a busmaster. Some time ago I moved my fhem from my old pi B+ running wheezy to a new pi 2 model B and installed jessie. From that moment on, the busmaster was not working properly with fhem.

I can see all 1-wire data by opening the OWhttp server however on my Jessie pi with the adapter but I cannot get the data into fhem. It simply doesn't show any reading in fhem.

So at the moment I am using my old wheezy pi with the adapter to access the 1-wire bus with and access the OWserver on that pi with fhem running on my jessie pi.

I just thought that your idea of replacing the file would solve my problem so I can attach the host adapter to my pi 2 and use the other pi for some different stuff. Since I am not very familiar with 1-wire I am not sure if using OWX instead of OWServer would help here. I cannot find enough ocumentation on OWX so I could give it a try.

Greetings
Michael

[fruit]

I have Sheepwalk RPI3 (26 and 40 pin versions), both working with jessie. RPI2 and RPI3 use a similar chip, I have not seen any other non-working reports
I suspect you may have a configuration issue.

Is i2c enabled (raspi-config) and i2c-tools installed? Do you see expected results from

Code Auswählen Erweitern

sudo i2cdetect -y 1

Run

Code Auswählen Erweitern

sudo dpkg-query -l 'ow*'
sudo dpkg-query -l '*libow*'on your wheezy and jessie, compare results

My /boot/config.txt contains these at the end

Code Auswählen Erweitern

dtparam=spi=on
dtparam=i2s=on
dtparam=i2c_arm=on
dtoverlay=i2c-rtc,ds1307

/etc/modules

Code Auswählen Erweitern

i2c-dev
i2c-bcm2708
#spi-bcm2708
#bcm2708_wdog
rtc-ds1307

Edit:
I forgot that I also had to edit /etc/owfs.conf

Code Auswählen Erweitern

#server: port = localhost:4304
server: port = 4304

[MichaelO]

Well, this weekend I finally found the time to check all settings on both systems. Somehow I had a mixup in my owfs.conf and after correcting it, everything works fine now. I have no idea how that happened since I copied all settings during the initial setup of my Jessie-Pi.

One thing is still kind of strange. On my Wheezy-Pi I get

Code Auswählen Erweitern

sudo dpkg-query -l '*libow*'

||/ Name           Version      Architektur  Beschreibung
+++-==============-============-============-=================================
ii  libow-2.8-15:a 2.8p15-1     armhf        1-Wire File System full library

Code Auswählen Erweitern

sudo dpkg-query -l 'ow*'

||/ Name           Version      Architektur  Beschreibung
+++-==============-============-============-=================================
ii  ow-shell       2.8p15-1     armhf        shell utilities to talk to an 1-W
ii  owfs           2.8p15-1     all          Dallas 1-wire support
ii  owfs-common    2.8p15-1     all          common files used by any of the O
un  owfs-doc       <keine>                   (keine Beschreibung vorhanden)
ii  owfs-fuse      2.8p15-1     armhf        1-Wire filesystem
ii  owftpd         2.8p15-1     armhf        FTP daemon providing access to 1-
ii  owhttpd        2.8p15-1     armhf        HTTP daemon providing access to 1
ii  owserver       2.8p15-1     armhf        Backend server for 1-Wire control


and on the Jessie-Pi it's

Code Auswählen Erweitern

sudo dpkg-query -l '*libow*'

||/ Name               Version        Architektur    Beschreibung
+++-==================-==============-==============-==========================================
ii  libow-2.8-15:armhf 2.8p15-1       armhf          1-Wire File System full library
ii  libow-2.9-8:armhf  2.9p8-6        armhf          1-Wire File System full library


Code Auswählen Erweitern

sudo dpkg-query -l 'ow*'

||/ Name               Version        Architektur    Beschreibung
+++-==================-==============-==============-==========================================
ii  ow-shell           2.9p8-6        armhf          shell utilities to talk to an 1-Wire owser
ii  owfs               2.8p15-1       all            Dallas 1-wire support
ii  owfs-common        2.9p8-6        all            common files used by any of the OWFS progr
un  owfs-doc           <keine>        <keine>        (keine Beschreibung vorhanden)
ii  owfs-fuse          2.8p15-1       armhf          1-Wire filesystem
ii  owftpd             2.9p8-6        armhf          FTP daemon providing access to 1-Wire netw
ii  owhttpd            2.9p8-6        armhf          HTTP daemon providing access to 1-Wire net
ii  owserver           2.9p8-6        armhf          Backend server for 1-Wire control

Will the version mixup on the Jessie-Pi cause any trouble?

Thanks
Michael

[fruit]

Well, this weekend I finally found the time to check all settings on both systems. Somehow I had a mixup in my owfs.conf and after correcting it, everything works fine now.

Good news

Will the version mixup on the Jessie-Pi cause any trouble?

I think it may do especially owserver and OWNet.pm. T
o be safe replace 2.9p8-6 with 2.8p15-1 versions and that will ensure that fhem OWNet.pm works correctly.
You can find the packages at http://archive.raspbian.org/raspbian/pool/main/o/owfs/ if you don't have them and install with

Code Auswählen Erweitern

sudo dpkg -i /path/to/package

[krueuw]

Das Thema ist als gelöst markiert. Trotzdem würde ich gerne, von jemanden bei dem es läuft, in klaren Worten eine Zusammenfassung lesen, welche Schritte letzendlich erfolgreich waren, eventuell sogar in deutsch Was ist konkret zu tun? Muss die originale Version entfernt werden. Ist eine Änderung an OWNet.pm nötig?

Ich bin bei der Anleitung für die Installation von  owfs_2.8p17-1_all.zip wie im Wiki beschrieben mit einem frisch installierten Raspian Jessie auf nicht erfüllte Abhängigkeiten gestossen, die ich nicht auflösen konnte.

Code Auswählen Erweitern

Setting up libownet-php (2.8p17-1) ...
dpkg: dependency problems prevent configuration of libow-perl:
libow-perl depends on perlapi-5.14.2; however:
Package perlapi-5.14.2 is not installed.

dpkg: error processing package libow-perl (--install):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libow-php5:
libow-php5 depends on phpapi-20100525+lfs; however:
Package phpapi-20100525+lfs is not installed.

dpkg: error processing package libow-php5 (--install):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libow-tcl:
libow-tcl depends on tcl8.5 (>= 8.5.0); however:
Package tcl8.5 is not installed.

Kann mir jemand auf die Sprünge helfen?

[ak323]

Kann mir jemand auf die Sprünge helfen?

Einfach die OWNet.pm in /opt/fhem/FHEM/lib mit folgender ersetzen:
https://sourceforge.net/p/owfs/code/ci/master/tree/module/ownet/perl5/OWNet/lib/

Dann geht es auch ohne Downgrade ... 

VG ak323