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 together a working solution.
Apart from a very minor patch to the onewire module, most of the time was spent on OWFS. i really didn't like the way this made the readings available (under a sub-directory). Reading the comments, I suspect that this is a OWFS design problem, rather than collectd. If ever I get the time, I might look into this a bit more. Since i am looking at a large system, hints & tips prior to this welcomed. Best regards, Phil On 13 January 2012 17:36, Phil White <[email protected]> wrote: > 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 <[email protected]> wrote: > >> 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 specifying the whole OWFS path (also >> documented in the patch). >> >> Or just use it as an inspiration :-) >> >> Best regards, >> Tomas >> >> >> On 13/01/2012 14:55, Phil White wrote: >> >> 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 >> (though for different reasons). >> >> I have DS18B20 as my temperature sensors, rather than the DS18S20 that >> the plugin appears to recognise. These report themselves as a device with >> the prefix '28', rather than 10 - therefore collectd does not record data >> from these sensors. >> >> Now, I'd rather like to have a play with the plugin, and attempt to get >> this working. Rather than just submit a request, I'd rather like to get my >> hands dirty, and fix it myself. Just because I have never done any coding >> in C really shouldn't stop me, should it?! Another reason being that I also >> have a device prefix '7E', which is somewhat different, and I'd also like >> to see this one recognised. >> >> Therefore, can someone offer some 'beginners tips' as to how I'm going to >> start on the '28' issue - advice & info? Which files, and what I need to do >> in order not to break anything? >> >> Many thanks, >> >> Phil >> >> >> _______________________________________________ >> collectd mailing >> [email protected]http://mailman.verplant.org/listinfo/collectd >> >> >
_______________________________________________ collectd mailing list [email protected] http://mailman.verplant.org/listinfo/collectd
