More and more "smart"/BLE wireless locksets are appearing on the market and extending the possible uses cases past the residential market, where they've been best positioned for years. For commercial use, there were always limitations, such as not being able to read prox or smart cards (PIN passwords only), the build quality not being commercial Grade 1 and scarcely Grade 2, and the communications options being limited to home automation hubs (cloud) with little or no local on-premise admin functions.
Now that all that is changing and more cost effective choices are coming out beyond Schlage NDE and various Yale, Sargent wireless locks, I am still not seeing a lockset that fits a need I have with a church with challenging architectural finishes that make running traditional IP-based access control wires nearly impossible.
* ******* ****** *** *** **** out **** ** *********** **** ** wireless ***** ***** **** **** *** the ****** ***** *** ********, *** are ******* ** *** ***** ********, and **** *** *** ******* ** know ** *** **** ** ******** open ** ****** (*** ** ** confused **** ****** ** ********, ***** is ********** *********), *** *** ******* to **** **** *** ****** ***** is ****** ** ** ** ******* the *** ***** ** *** **** to ****** **** * ***** ***. To **** **** ****** ** ****, here's * *** *** ***** **** the ******* *** ********* ** *** signals **** **** *** ** ***** wireless *********** ****:
* *** *** *** *** ***** entrants ** *** ********** ******** **** market *** * ***** *********** ... there *** ******* ***** ** *****-****** and **** **** ***********, *******, *** most *** *********** **** ***** ******* from ****** ******* *** ****** ****** the ***** **** ** **** ****** both *** ***** *** ****** ******, not ** ******* *** ********** **************. However, ** ** *********** ** *** have *** *****-** **** ****** *** REX ****** ****** ** ****** * system **** ** ****-***** ********* *** used ** ****** (** *** ** door ****** *** ***-***** ** ****** open ******).
**, ***, * ** ****** **** wireless ***** *** **********, *** **** of **** ***** ***'* **** *** basic ****** ******* ***** ** *** list *****. *******: *** ***** *** wireless ***** **** *** ** ******* via *****, **** ***** **** **** or ***** **** ***, ****** ***** credential *** (***), ***'* ******* ** expensive ******* ** ******in **** **** (a reasonably priced gateway is ok), and have a cloud app that doesn't require connection to a third party ACS panel to manage? The reason real-time is in bold is because a lot of the BLE-enabled locks cannot report events in real time and require a mobile phone to be within range for events to be harvested to the cloud. If a door opens and there is no mobile phone present, I still need to know the door opened. So if using a gateway of some type accomplishes this, that's ok, but the lock still needs to have the status signals listed above.
**** **** * *** ****, *** entrants **** *** *** *****, *** still **** *** **** ****** *** REX ****** (*****-**).
****** **** *********** *** *** **** count ************ *** ******** ***** **** door ****** *** ***, ********** *****, that **** ***** *** ****-**** ***** app, *** ******* **** ***/** ***** cards ***** **** ****** *****?
*** ***** *** ******** ***** **** can ** ******* *** *****, **** allow **** **** ** ***** **** use, ****** ***** ********** *** (***), don't ******* ** ********* ******* ** managein **** ****(* ********** ****** ******* ** **), and **** * ***** *** **** doesn't ******* ********** ** * ***** party *** ***** ** ******?
*** '**** ****' *** ** ****** going ** ** * *********, *** to ***** **** ***** ******* *******. It ** * *** ******** ******** to ***********/********* ****** *******.
*** *** **** ****** **** '***** position' ** ** ** **** ** trigger *** *********?