On 05.09.2018 07:45, Jan Kandziora wrote: > So my advice from pratice is basing all the automatical mechanisms on > a logical abstraction of a whole peripheral, with the Onewire stuff > being only a part of a bigger picture. My main goal with this library is that the instance representing a slave device should be able to tell the system what it want, and be able to rely on the library to do it, instead of being forced to do all the work by itself.
The "big picture" abstraction is the job of projects like HomeAssistant (since we're talking Python …), which currently has no 1wire support to speak of – which is one reason why I'm doing this. > The DS2409 is already transparently supported by owlib. Is it? Last time I checked, slaves behind a DS2409 or two do not show up in "owdir /" or "owdir /bus.0" or "owdir /alarm", they do not notice when I set /simultaneous/temperature, … So either I'm missing something, or your definition of "transparent" differs from mine. :-/ > Not sure what you want to put on top. For one, support for (bus-specific) handling of /alarm or /simultaneous. The idea is that different 1wire buses may have different requirements (timing, polling, alarm handling, how often to trigger temperature conversion, bus re-enumeration, …); it's the client system's job to coordinate the device instances' requirements to do the least-possible amount of work, and only on the bus(es) it cares about. -- -- Matthias Urlichs
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
