I need to change the locks on the doors to my house. Are there any locks on the market that can be used with our chips? I’ve looked around, and it looks like a lot of them require you to use their RFID media. Looking for something that also has keypad access, because my wife isn’t as gung ho as I am about the implants, but would still like to not have to carry a key.
Thanks!
@toasty
FYI, that spreadsheet is a living document, but also a work in progress, and needs a little tidy up.
However, it still is a great starting point.
I did just notice, the “freeze pane” function is not working on the mobile view. So a PC will be a slightly better experience at the moment. <\s>
EDIT
Freeze pane now fixed on mobile
Thanks so much, very helpful!
You probably saw all of these during your search, but incase you missed them.
There is a community driven open source dead bolt lock project progressing slowly.
It might be worth keeping and eye on this thread
Also some others have tested a few.
So I bought an RFID door lock and it doesn't seem to be working - #45 by anon3825968
we might consider putting some links into the document to these forum posts? Could be done as a cell comment not a cell value.
3 posts were merged into an existing topic: Chip compatibility matrix - Google Sheets
Just wanted to put my hat in the ring for another rightoff.
I bought this one and installed it DOES NOT SUPPORT “NeXT”
Hope that help future people trying to buy this lock!
I wanted to thank Pilgrimsmaster
For the great spreadsheet! im wish i looked at that before I went and bought my own!
ARDWOLF A30 Keypad Door Lock, Keyless Entry Electronic Door-Locks with Lever and Automatic Locking，Compatible with Ardwolf 13.56MHz RFID Keyfobs
update: (20210209)
Looking for advice + Update on reader.
I have the NeXT:
Just bought another door lock, on the 'chip compatibility matrix google sheet"
and that one doesn’t work either! darn (frowning face emoji)
I’m beginning to suspects that its something not with the locks but my 13.xxx mhz side of my implant.
The base reader black use reader registers the EM side of the chip with a beep, but i cant read the xNT side from my phone, or a diy 13.xxx mhz reader I had laying around.
Em side works fine.
xNT is having issues.
Any debugging advice?
here’s reader model i bought
Laxre Bluetooth keyless Fingerprint Door Lock, Entry Front Door Lock , biometric Door Lock deadbolt, One-Touch Locking Touchscreen Digital gate Lock, Easy Install for Home and Office
No led lights up in any orentation with led’s powered or non powered
I do hope not for your sake.
I also hope that the the Matrix is correct and not misleading.
My concern was adding devices to the matrix that are not compatible and people ending up with a potentially expensive paper weight.
All of the devices reccomended on the matrix SHOULD have a link to a thread where somebody has tested, reccomended and hopefully documented them.
That one you mentioned above was a relatively recent addition and there was a great write-up to accompany it by @Intector
In theory, it SHOULD be working!
Apologies in advance, no insult intended. sometimes its the little things that catch us out.
Can you confirm:
All this just to get a clear starting point
really inyteresting.
Just bought an Apex Flex, and I’m wondering, since I have an Evva NFC enabled lock (evva airkey) and a NFC enabled BMW (it offers the use of NFC card to open and start):
The cells in the matrix for BMW and Evva are all empty: does that mean that it is still to be tested?
And can I be of service to test it with my Apex Flex?
(I’m a total noob with NFC, so forgive me if I’m asking something that is obviously impossible)
I couldn’t find anything definitive, but based on their manuals and some other marketing material I suspect that the AirKey locks work like most other NFC locks and only care about the UUID of the chip. Those locks typically allow enrollment and access with multiple types of NFC devices including NTAG and MiFare chips. Basically as long as the chip chirps a UUID of the expected length and in the expected format, the lock will enroll it and/or open.
Unfortunately, I have not found a single lock that works with the Apex. The P71 chip in the Apex is substantially different from the other NFC implants. It chirps a very different ATR and has a UUID that isn’t recognized by any of the locks I’ve tested.
The few locks it does work with have required specific applets, such as for Tesla. And those locks are already programmed to work with app-based NFC devices that have multiple rounds of commands (e.g. the lock sees the device, gets some basic information, sends an applet select command, then does some mutual authentication before unlocking).
I doubt that the Evva locks are doing this kind of protocol, so I don’t think an applet will ever be available for the Apex to work with them.
I think there is more to the locks / keys than a simple exchange of an UUID. The keys somethimes need an update, And when I look at the admin panel, it currently has “keyring 8.5”. The picture has some of that info.
When I read these release notes, It mentions “Only locking components with the latest firmware (with Java Card Applet 8.5+) can be added to newly created access control systems.”
I assume that this java card applet cannot simple be copied from the keycard to the apex flex, right?
in that case: what could be a way to get such an applet on my Apex? Simply email the creator of the lock?
when I follow the procedure for programming a genuine Airkey-fob (which is done with the lock itself), but I present my Apex in stead of the official keyfob, I see that the lock detect the Apex. But it ends with the error that it cannot be updated.
So my conclusion: the medium (chip) might be usable, but it would at least need an installen javacard applet of Evva Airkey.
If you begin a pointed campaign to work with AirKey, find a developer or a business development manager, convince them to work with third parties, then we can work with them to develop a applet that can be purchased by end users and deployed to Apex chips.
I’m pretty sure the idea being that they will not want to sacrifice a revenue stream in the form of fobs, so purchasing the applet should probably be a cornerstone of the proposal.
If anybody can find a representative willing to talk about this, I’m more than happy to engage.
Good to know Amal. I will do some research to find a representative. i don’t expect much of it, but hey: who knows…
How about me contacting the innovation manager? To frame the question as an opportunity to investigate an innovation? Since it’s an Austrian company, I would expect them to be very conservative towards a niche like implants. Reaching out to an innovation manager, rather than e business developer might increase the chance of success. Agree?
Possibly… depends on if they want to innovate they far as to support implants haha
mail is sent, I’ll keep you posted
