For binary onewire sensors there might be a need for updating their state in almost real time. For instance, they might be used to detect open doors and windows. In such a scenario, a maximum latency of about 2 seconds is desirable I believe.
To make this possible, I was thinking about offering two additional things to the user:
Make scan_interval adjustable for the onewire platform (via yaml config)
Add an uncached config option (boolean) for onewire sensors.
I think the main issue is that owfs uses polling not push (Classifying the Internet of Things - Home Assistant). As far as I’m aware, push is not available on owfs, regardless of the library used to communicate with it.
Regarding the scan_interval and uncached options, both might be useful but should be disabled by default. Depending on the number of devices connected to the bus, it might overload the bus…
I agree. Onewire devices don’t support push as they need to be explicitly polled by a master device.
Regarding the different ways to set config values: what would be the best way to make optional config entries so the user can decide on a per-entity basis? I’m a bit puzzled looking at config flows vs. yaml.
I’ve checked the link you provided: while there’s certainly some good stuff in there worth considering I think HA’s onewire implementation is in a pretty good shape right now.