Enhance onewire binding

[GoogleCodeExporter]

Here are some feature requests that I'd like to see go into the onewire binding:

1) Per-device configurable polling interval

I'm thinking if we should enhance the onewire binding and specify an (optional) 
polling interval for each device. An easy way to do that would be to just add 
the polling interval such as
{ onewire="1F.A96005000000/main/10.5FB813020800#temperature#300" } where 300 
means poll every 5 minutes (300s). Then the onewire binding could be configured 
in openhab.cfg to execute e.g. every second, and the code enhanced to keep a 
list of the last polling time for each device. If a device does not need to be 
polled at an execution cycle it is simply skipped.

2) Retry in case Undefined is returned

I keep getting Undefined values back randomly (so e.g. a temp sensor may report 
some successful values and then one or more Undefined). I think that adding a 
retry parameter (in openhab.cfg) and in case no value was received from a 
sensor the onewire binding could retry the poll.

/Henrik

Original issue reported on code.google.com by henrik.sjostrand on 9 Aug 2012 at 9:07

[GoogleCodeExporter]

Original comment by kai.openhab on 9 Aug 2012 at 10:17

[GoogleCodeExporter]

Original comment by teichsta on 10 Aug 2012 at 7:21

• Changed state: Accepted

[GoogleCodeExporter]

Here is another feature request from someone whose water freezes at 32 degrees.

3) Configurable temperature scale via a parameter in openhab.cfg.  It looks 
like it's hard-coded to Celsius in OneWireBinding.java, though the enum also 
has values for Fahrenheit, Rankine, and Kelvin.

This seemed like a good place for this... I apologize if I should have made it 
a new issue instead.

Original comment by griffit...@gmail.com on 13 Oct 2012 at 2:56

[GoogleCodeExporter]

temperature scale is now configurable!

See: 
http://code.google.com/p/openhab/source/detail?r=0d11b4a0a72201a13c13fdcd5c03846
2571f6acb

Regards,

Thomas E.-E.

Original comment by teichsta on 21 Oct 2012 at 1:11

[GoogleCodeExporter]

Have rewritten the OneWire binding using the 1.1. Plugwise binding as a model. 
Onewire now supports flexible per-device polling intervals. Code not finalized 
as of today (Nov 29), but working on it.

Original comment by henrik.sjostrand on 29 Nov 2012 at 8:50

[GoogleCodeExporter]

thanks for the update Henrik!

Original comment by teichsta on 29 Nov 2012 at 8:52

[GoogleCodeExporter]

it is possible to enhance the onewire binding to read ibuttons? Please look at 
http://knx-user-forum.de/special/Digitales%20Schluesselbrett%20mit%201-Wire%20iB
uttons/

regards ansgar

Original comment by abode...@gmail.com on 14 Jan 2013 at 10:29

[GoogleCodeExporter]

As long as iButtons are supported over OWFS (OneWire File System) and the 
jowfsclient library we use in the Openhab onewire binding also supports it it 
should be doable. I would need to look into that and also get some iButton 
devices to test with.

We have other features of the onewire binding that currently are higher 
priority but we'll put iButton support on the wish list.

/Henrik

Original comment by henrik.sjostrand on 15 Jan 2013 at 8:15

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

@henrik.sjostrand is your code commited? I have not seen it...

If not, I have another suggestion (and I could help to implement it). Defining 
a ratio per device, a ratio means that the base polling time is multiplied by 
the ratio, that number is the polling time of the device.
The advantage of this is that the system could distribute the pollings per 
ratio evenly. 
If for example all temperature sensors have 300s, then every 300th second all 
temperatures are polled and the devices without different poll time like 
switches. That poll could take a lot of time.

Original comment by c.hoefl...@gmail.com on 25 Jun 2013 at 6:01

[GoogleCodeExporter]

Hi Henrik, any news on regarding the 1-Wire binding? Best, Thomas E.-E.

Original comment by teichsta on 1 Sep 2013 at 8:21

[GoogleCodeExporter]

Hi Thomas,

Sorry, but haven't had any bandwidth over for Openhab at all this year. 
I'm fully occupied developing a mobile app for Diabetes management for 
children. So need to finish that project before I can go back to work 
with Openhab again. And that is going to take me the remaining of 2013, 
unfortunately.

/Henrik

Original comment by henrik.sjostrand on 2 Sep 2013 at 6:30

[GoogleCodeExporter]

Original comment by teichsta on 5 Nov 2013 at 10:47

• Added labels: To-Github

[GoogleCodeExporter]

This issue has been migrated to Github. If this issue id is greater than103 its 
id has been preserved on Github. You can open your issue by calling the URL 
https://github.com/openhab/openhab/issues/<issueid>. Issues with ids less or 
equal 103 new ids were created.

Original comment by teichsta on 17 Nov 2013 at 8:08

• Added labels: Migrated-To-Github

[GoogleCodeExporter]

see above!

Issue has been migrated to Github and should be discussed there.

Original comment by teichsta on 21 Nov 2013 at 1:51

• Changed state: Invalid