Hi all together,
currently I’m playing around in a test scenario regarding the iButton from Wiregate.
My goal is to use the iButton as an access control but I’m facing two strange things, so I would like to discuss this with others out there using the iButton or maybe even with the ones developing the One-Wire Binding.
First one is a bit cosmetic. Due to the fact that each of the iButton Holders has its own Device-ID, I need to poll all possible Device-ID’s of all my iButton Holders, regardless the Device-ID exists or not. If sometimes a Device-ID can be reached, I read out the unique identification key and grant access or not. This scenario causes hard exceptions in the log although this is a best practise scenario for iButtons. I mean it’s not an error if one or two or all Device-IDs of my iButtons can’t be reached. Wouldn’t it be more sensible only to log something like a Debug information in this case? This would avoid flooding the log with errors which aren’t really ones.
Second one has something to do with caching I think. The problem is that either the One-Wire Binding or the OWServer needs to much time to realize that a iButton Holder/Device-ID isn’t available anymore. It takes something about 120 seconds in the log file until the One-Wire Binding logs a missing Device-ID after I remove the iButton Holder from the iButton Probe. This is much to long because it would mean, I cannot open the door again within this 120 seconds with one and the same iButton Holder. Okay, could also be a feature But I would like to reduce this at about 30 seconds.
I’m looking forward to discuss this and possible other iButton scenarios with others out there.
Thanks in advance.