FAQ
TL;DR: 0 native SATEL NFC bus readers; "they only give 125 kHz." This FAQ explains workable options, integrations, and phone-as-card limitations for SATEL access control. [Elektroda, 345, post #18310254]
Why it matters: SATEL owners, installers, and tinkerers want to open doors with phones; this shows what works and what doesn’t today.
Quick Facts
- SATEL bus readers support 125 kHz passive transponders; no native NFC on the bus. [Elektroda, 345, post #18310254]
- NFC runs at 13.56 MHz (HF), not 125 kHz (LF); that frequency mismatch blocks direct phone use. [“RFID i NFC — NFC24”]
- Many phones randomize the NFC UID; every tap can report a different ID to the reader. [Elektroda, slavo_s2k, post #18999780]
- Stick-on NFC/MIFARE tags are approx. 25 mm diameter; hiding one under a case gives a stable ID. [Elektroda, slavo_s2k, post #18999944]
- NFC/BLE readers exist but need an external controller/relay, adding cost and wiring. [Elektroda, gkwiatkowski, post #20528976]
Can I use my smartphone’s NFC as a SATEL access card directly?
Not with SATEL’s native bus readers. They use 125 kHz low‑frequency tags, not NFC. “They only give 125 kHz.” Phone-as-card requires hardware beyond the SATEL bus readers. [Elektroda, 345, post #18310254]
Why doesn’t my phone work on a 125 kHz SATEL reader?
Phones implement NFC at 13.56 MHz, while classic SATEL readers expect 125 kHz transponders. The radio layers and protocols differ, so a phone cannot present a compatible signal to a 125 kHz reader. [“RFID i NFC — NFC24”]
What’s the easiest way to get phone-based access on a SATEL system?
Add an NFC/BLE reader with its controller, then wire the controller’s relay to SATEL. How‑To: 1. Pick an NFC/BLE reader compatible with a controller/relay. 2. Connect reader to its controller; enroll phones/cards. 3. Wire the controller relay to SATEL input/lock and test triggering. [Elektroda, gkwiatkowski, post #20528976]
Is there a proven MIFARE card emulator app with a fixed UID?
Users report no reliable fixed‑UID emulation on phones. Many phones rotate the NFC UID, so each tap shows a different ID. That breaks one‑time enrollment workflows. Use a physical tag or an external reader/controller instead. [Elektroda, slavo_s2k, post #18999780]
My phone shows a different ID every time on a MIFARE reader. How do I fix that?
Place a thin NFC/MIFARE sticker under your phone case to provide a stable UID. Many tags are about 25 mm diameter, so a case helps hide bulk. Enroll the sticker once, then tap your phone as usual. This bypasses phone UID randomization. [Elektroda, slavo_s2k, post #18999944]
Do I need to unlock my phone for NFC access?
Some readers, such as STid Architect Blue, can read NFC without unlocking. The companion app must run in the background. “The application must run in the background.” Check the reader’s configuration to enable background NFC. [Elektroda, gkwiatkowski, post #20528997]
Will an NFC/BLE reader directly switch my lock relay?
No. NFC/BLE heads typically drive an external controller. The controller provides the relay output that connects to your lock or panel. Budget for both the reader and its controller. [Elektroda, gkwiatkowski, post #20528976]
Does the Roger MCT80M‑BLE open doors automatically when I approach?
A user notes operation requires the phone app and it does not automatically read NFC tags. Expect an explicit app action instead of hands‑free NFC. “It does not automatically read NFC tags.” [Elektroda, sosarek, post #20528984]
Can I clone my 125 kHz fob or card into my phone?
No. Phones implement NFC at 13.56 MHz and do not emulate 125 kHz transponders. That makes cloning low‑frequency tags into phones unworkable with standard hardware. [“RFID i NFC — NFC24”]
Can I drive SATEL with my phone via Home Assistant instead?
Yes. With a SATEL ETH module, users report arming and disarming through Home Assistant. If your phone can trigger an automation, HA can send commands to the panel over the network. [Elektroda, przeqpiciel, post #20526035]
Is moving to NFC worth it now for small sites?
One installer argues to stick with 125 kHz for now due to simplicity and ubiquity. “No point in introducing as standard… technology for the selected few.” NFC is growing, but adoption in public deployments takes time. [Elektroda, Serwis_LX, post #18314589]
Is there any SATEL‑native NFC reader on the bus yet?
No. The thread states SATEL provides 125 kHz readers only and lacks a bus‑integrated NFC solution. “They only give 125 kHz.” [Elektroda, 345, post #18310254]
What integration paths have users considered for NFC with SATEL?
Options mentioned: SATEL with Arduino/Raspberry plus an NFC module, SATEL + INT‑RS Plus with an RS‑232 13.56 MHz reader, or SATEL + Roger with an MCT80M‑BLE module. The note stresses integrated control panels only. [Elektroda, bercik_gsi, post #18652939]
How can I encourage a native SATEL NFC solution?
Contact the manufacturer. The advice: email and call with clear requests; documented customer demand pushes roadmaps faster than anything else. [Elektroda, Serwis_LX, post #18314589]
so I'd like to hear from you ...
