Re: [Owfs-developers] Devices listed multiple times

2015-12-31 Thread Colin Reese
Can somebody explain to me why on earth people use so many 1wire buses? Do many use hundreds of devices and need to split them across buses? That thing has 17 1wire channels. I have never had need for more than 1, even with >100 sensors. The whole beauty of 1Wire is extendable single bus multi

Re: [Owfs-developers] Devices listed multiple times

2015-12-31 Thread Henrik Östman
:-) I bought it mainly because it made interfacing with Raspberry Pi easy (don't have to solder something up myself), and it contains a Realtime-watch which is nice to have if NTP is not available. But also I think a failing device or short circuit would not bring down the whole network if the

Re: [Owfs-developers] Devices listed multiple times

2015-12-31 Thread Jan Kandziora
Am 31.12.2015 um 09:30 schrieb Colin Reese: > Can somebody explain to me why on earth people use so many 1wire > buses? > You may want to have topographical addressing when you only have iButtons and passive Keylocks. In that case, the only chance to find out where the iButton was plugged is to

Re: [Owfs-developers] Devices listed multiple times

2015-12-31 Thread Jan Kandziora
Am 31.12.2015 um 09:17 schrieb Henrik Östman: > > I have a question, why does some of my 1-wire devices get listed several > times by OWFS? They have the same ID and inode-number, so now my > application have to filter out the duplicates. > I'm running OWSERVER: > > owserver version: >

[Owfs-developers] Devices listed multiple times

2015-12-31 Thread Henrik Östman
Hello! I have a question, why does some of my 1-wire devices get listed several times by OWFS? They have the same ID and inode-number, so now my application have to filter out the duplicates. I'm running OWSERVER: owserver version: 2.8p15 libow version: 2.8p15 On a Raspberry Pi with