RFID reader for Loxone
Secure RFID reader / writer connecting to Loxone via TCP/IP.
Currently OUT OF STOCK. Contact us for availability
Free shipping in BE, NL, LU on orders >80EUR
Free shipping in the rest of Europe on orders >800EUR
This product is OUT OF STOCK and can no longer be purchased.
We are currently looking for an alternative generic product. We can however provide a number of RFID, fingerprint and keypad solutions on demand with similar functioning to our Loxone customers only.
RFID reader for Loxone
There are 5 problems with the Access Control solution in Loxone based on iButtons:
- it is less secure than a regular key:
- Anyone with a battery powered Arduino or Raspberry Pi (less than 50euro) can copy your key by just touching it with 2 wires for a splt second. The software is freely available on the internet.
- The same device can then emulate your key and open your door by touching the 2 wires to your iButton reader.
- people are used to RFID cards/keyfobs, to the speed, to their usage for access control at work and for payments like public transportation. With an iButton, you have to make uninterrupted physical contact to a reader for a variable amount of time. Depending on your configuration of your 1-wire bus, this often takes more than a second. This makes the system feel unreliable and for some difficult to use. Coming from RFID tokens, an iButton feels old fashioned.
- you can not differentiate between iButton readers on a single 1-wire bus, so you need a separate 1-wire extension for each reader, which is expensive and complicates cabling.
- you can not add or remove users or iButtons, or change groups or permissions while operational. User and iButton management can only be changed via Loxone Config, which is often too complicated for the user, or the PC might not be accessible when needed, e.g. to black list a stolen or lost badge. Moreover, it requires a reboot of the Miniserver, often causing side effects like lights or heating switching on/off.
- only 1 iButton can be linked to 1 user. You can not have 2 or more keys, e.g. 1 on you keychain and 1 in your car.with
- RFID cards/tokens supported: Ntag 203; MIFARE Ultralight®, MIFARE Ultralight C®, MIFARE® Classic 1K/4K, MIFARE® Pro/Prox, MIFARE Plus®, MIFARE® DESFire® EV1 and other ISO14443A compatible cards, Sony Felica
- TCP/IP and UDP connectivity
- Unlimited number of readers and doors
- NFC compatible. We plan to develop an app for using you phone as a key (first on Android).
- Reader/Writer: Any of the supported cards/tokens can be written to to store secured or encrypted user information or access rights. Software is provided to configure the reader with your own access keys and encryption keys.
- With or without keypad
- Power: 9 - 12 V DC or PoE via optional PoE injector (not via 48V PoE switch)
Many RFID readers are not secure
Many of the RFID readers on the market just read the serial number of the card or keyfob. This is because it is simple to implement: any reader that support the same type of token can read the serial number. There is no configuration of the reader required because there are no access keys or encryption keys used. This however makes it more easy to steal someone's 'key': anyone with a reader + some portable device (e.g. a battery powered Arduino or Rapsberry Pi) can read someones token, without touching it, even when it remains in someones pocket or wallet.
Depending on the technology, there are multiple ways to emulate the stolen key and open the door: e.g. Mifare cards can be purchased online with a blanco and writeable serial number. Rooted NFC enabled Android phones can emulate a Mifare token. Our card reader can be configured to emulate a token and carried battery powered.
Therefore, we strongly suggest not to base access rights on a token's serial number, but rather on your own information stored in a secured sector on the token, secured by your own access keys or encryption keys. Furthermore, this allows simplifcation of the access control management, as you can have multiple tokens for a single users, all storing the user information. It could also store the group the user belongs to, or even the individual access rights.
To do this your RFID reader must be configurable with access keys and encryption keys, and it must be able to encrypt and write user information to the tokens.
Special usage of the keypad
- you can type a key and then swipe your token to trigger alternate functions, e.g.
- just swiping opens the front door; first typing '1' and then swiping opens the gate, so you need only 1 reader to control 2 doors
- first typing '0' and then swiping locks down the house and arms the burglar alarm
- just typing '*' rings the door bell.
- you can have short and long codes mixed, e.g. '1#' switches on the outside lights, a 4 digit PIN opens the door.
- you can easily change/activate/de-activate codes from within the Loxone App because the authorization is done in the Miniserver
- you can have the Miniserver automate the PIN code access authorization, e.g.
- only allow access dynamically on a certain schedule and state of the house
- issue one-time PIN codes
- generate a new random PIN code and send to the user(s) via email or SMS, e.g. each week, or day, or each time the (one-time) code is used.
Usage in the Loxone app
Configuration in Loxone
- business owners or home family members: access all doors at any time
- employees or cleaning personel: access all doors only during office hours
- guests: access main door only, only when visiting
- 2 PIN codes can be changed (PIN1 grants access to a door, PIN2 triggers some other function)
- multiple cards are created beforehand for any types of users: the data on the cards consist of a User ID and a Group ID and version number. The Group ID is used for authorizing access. The User ID is used for monitoring (who arrived when) and to trigger user specific actions (e.g. swith on prefered radio station).
- Occupants are authorized at any time. Guests only when their schedule is active. Using the Loxone Schedule block, fixed times can be set on certain weekdays, or manually changed to on or off for some period, using it's Override function.
Via a simple PicoC script in Loxone, more functionality can be added to the Loxone app:
- link User Name to User ID to show in access logs
- blacklist User ID, in case of a lost or stolen badge, so access is never granted. (The user has to get a new UserID on his other badges).
- create/change/delete badges: In the app: select a Group ID, select a UserID, activate 'Write 1 badge', hold the badge in front of the reader to write the new data to the badge.