, but not with collectd onewire plugin.
some testings with the onewire plugin offers
Device -s localhost 4304 -- works better than localhost:4304.
# Sensor 10028505/
# Sensor 28.10028505/temperature
# Sensor 28.10028505 fasttemp
Sensor 28.10028505
result:
onewire plugin: OW_get
Hello,
found this (verry old) discusion about the onewire plugin for collectd.
A small way to get a lot of sensors to work and automatic datacollection
will be to extend the onewire.c file for more than one type.
I have test this only with the type 28, but this was working also for me
and i
Hi All,
Thanks Tomas - all is working.
I'm afraid I didn't go with your patch in the end (mainly because I lost
the ability to automatically read a sensor without specifically including
the path location in the configuration). However, it pointed me in a
direction which enabled me to cobble
Hello all,
Long ago, I looked at collectd and 1-wire monitoring, and never progressed
because I had problems with owfs, and because of the plugin's
'experimental' status (though I do use collectd for other monitoring).
I revisited the issue the other day, and still can't get things to work
Hi Phil,
you could use my patch - see
http://mailman.verplant.org/pipermail/collectd/2011-November/004810.html
This would solve your problem with device family 28 (had the same problem).
For the other device with 7E you can use the other option which offers
the patch - to use direct accss by
Hi Tomas,
Thanks - I'll have a look over the weekend, and let you know how I get on.
Cheers
On 13 January 2012 16:52, Tomas tomasa...@googlemail.com wrote:
Hi Phil,
you could use my patch - see
http://mailman.verplant.org/pipermail/collectd/2011-November/004810.html
This would solve
