Re: [Owfs-developers] python ow

Yes that's working. i will let you know what i've made.I've programmed a greenhouse control program in perl. Professionally wise i take this project to learn python. Python is hot these days. Nico Stefano Miccoli via Owfs-developers wrote: Some time ago I wrote pyownet https://pyo

Re: [Owfs-developers] python ow

Some time ago I wrote pyownet https://pyownet.readthedocs.io/en/latest/index.html to overcome some limitations of the official packages. The code is quite “stable” now, and does not have some of the fancy new features of trio-owfs (namely a

Re: [Owfs-developers] python ow

I think the recommended approach is to go with some of the other python libraries, such as https://pypi.org/project/pyownet/ (using myself, works very good) or https://github.com/python-trio/trio-owfs (have not tried). These communicate with pure python code & sockets towards owserver, rather

Re: [Owfs-developers] python-ow failure with new Raspbian Stretch

Stefano and the others who also responded, Thanks very much for your clarification of this problem and especially for the detailed suggestions on how to move forward! -- Check out the vibrant tech community on one of th

Re: [Owfs-developers] python-ow failure with new Raspbian Stretch

On 17.12.2017 17:45, Gregg Levine wrote: > Of course the merely obvious question is why the swig bindings are not > under active development. Because they're mosty useless, IMHO. In any sort off production environment I want a way to access the actual bus and check which data is actually out there

Re: [Owfs-developers] python-ow failure with new Raspbian Stretch

On Sun, Dec 17, 2017 at 04:58:15PM +0100, Matthias Urlichs via Owfs-developers wrote: > On 17.12.2017 00:19, Stefano Miccoli wrote: > > Unfortunately owpython (the swig bindings) is not under active > > development. > > I'd go a step further and remove them from the next release. +1 from me! T

Re: [Owfs-developers] python-ow failure with new Raspbian Stretch

Am 17.12.2017 um 17:45 schrieb Gregg Levine: > Hello! > I'd go a bigger step further and make them optional by way of how the > configure script is managed. I manage three platforms here. My desktop > a 32 bit machine running Slackware 11.0 Linux, and this laptop, that > also runs Slackware 14.2 in

Re: [Owfs-developers] python-ow failure with new Raspbian Stretch

I do exclusively. I was using my own wrapper reading directories but now use pyownet. C > On Dec 17, 2017, at 8:45 AM, Gregg Levine wrote: > > Hello! > I'd go a bigger step further and make them optional by way of how the > configure script is managed. I manage three platforms here. My deskto

Re: [Owfs-developers] python-ow failure with new Raspbian Stretch

Hello! I'd go a bigger step further and make them optional by way of how the configure script is managed. I manage three platforms here. My desktop a 32 bit machine running Slackware 11.0 Linux, and this laptop, that also runs Slackware 14.2 in 64 bit mode. And of course any number of Raspberry Pi

Re: [Owfs-developers] python-ow failure with new Raspbian Stretch

On 17.12.2017 00:19, Stefano Miccoli wrote: > Unfortunately owpython (the swig bindings) is not under active > development. I'd go a step further and remove them from the next release. -- -- Matthias Urlichs -- Check o

Re: [Owfs-developers] python-ow failure with new Raspbian Stretch

Unfortunately owpython (the swig bindings) is not under active development. The current best practice is to *always* run owserver on the host with the one-wire bus master, and have all clients access the one-wire bus via the owserver protocol. My personal suggestion is to take the time to try o

Re: [Owfs-developers] python ow library problem with theads, owserver protocol

Hi, I never faced the issue myself but I'm just wondering, can't we just check the CRC for those failed conversions ? Is the CRC correct in that case ? Rgds. -Romain On Wed, Sep 19, 2012 at 12:38 PM, Marcus Priesch wrote: > Well, 80 normally means that you dont have enough power to do the temp

Re: [Owfs-developers] python ow library problem with theads, owserver protocol

Well, 80 normally means that you dont have enough power to do the temp conversion ... are you doing parasite powering ? - then you should consider using another wire to get 5v to the temp sensor ... i will look what OW_get internally does and check the return code ... regards, marcus. On Mit, 2

Re: [Owfs-developers] python ow library problem with theads, owserver protocol

It seems that res could be 0, so None could be returned. I'll see if that happen. This is because one of my sensors is in my living room, and the 1wire signal goes though my telephone lines all over my house. It is not very reliable. Before I upgraded from an old debian to ubuntu precise, the bad

Re: [Owfs-developers] python ow library problem with theads, owserver protocol

> Made my wrapper to its capi, and it looks MUCH better. > Threads seem responsive again. Hey, glad to hear that ;) > Are there exceptions thrown when a sensor read goes wrong? according to libcapi.py's get and put: def get (self, path) : buf_p = ctypes.POINTER (ctypes.c_char) ()

Re: [Owfs-developers] python ow library problem with theads, owserver protocol

Hi Thanks a lot for your quick response. I used pip to install pyowfs with no problem (found out I had to install libow-dev for it to work) Made my wrapper to its capi, and it looks MUCH better. Threads seem responsive again. Are there exceptions thrown when a sensor read goes wrong? Thanks ag

Re: [Owfs-developers] python ow library problem with theads, owserver protocol

Hello Sophana, i dont know if it would help the gil issue, but you could try pyowfs (easy_install pyowfs) wihich basically is a ctypes wrapper around libow. starting a owserver instance and then talking via different pyowfs Connections (one in each thread) to the owserver should not block the ot

Re: [Owfs-developers] Python ow module and humidity (was Re: Release 2.8p10)

Peter Radcliffe probably said: >The problem is that some experimentation with the ow python module >(the one shipped with owfs) is I can't find a way to get at >HIH4000/humidity. > >I can read sensor.humidity ok, and HIH4000 is listed in >sensor.entryList() but trying to use it as an attribute wit