Connect your own hardware to Entrixy
An open protocol with code samples and test vectors. Build a controller yourself on an ESP32 or Raspberry Pi, add Entrixy support to your own device, or order a turnkey system.
Take what is ready and build your own
Every sketch and firmware image is published openly. Wire an ESP32 to a barrier relay in an evening, or build a battery-powered BLE lock — with HMAC and end-to-end encryption out of the box.
ESP32 — BLE controller
Direct control from a phone over Bluetooth, with no internet and no server. ESP32 / S3 / C3 / C6, deep sleep, years on AA batteries, ECDH X25519 with HMAC. Building the .bin right in the browser for the pins and chip you need.
ESP32 / ESP8266 — Internet
A permanent channel to the Entrixy server over WSS. A command from the app arrives in about 0.5 s and the relay fires. ESP32, S3, C3, ESP8266 (Wemos D1 mini, NodeMCU). Off-the-shelf Shelly Plus 1 and 1PM relays can be reflashed. Building in the browser with the Wi-Fi credentials and the device_key.
Raspberry Pi (Python)
Pi Zero W / 3 / 4 / 5. A Python script plus a systemd unit: a WebSocket client that reconnects and drives the GPIO. The browser configurator fills in the device_key, the GPIO pin and the pulse length.
Documentation for users
Installing the app, choosing and flashing a controller, pairing, guest keys, automation (geo, Wi-Fi and schedule) and security. With steps and screenshots.
Build Entrixy into your product
A barrier, a lock, an intercom, a gate controller. Implement the open protocol and your customers get a mobile app, guest keys and geo-automation without you running a server or an app. The protocol is public and comes with test vectors: you can build a prototype today, with no reverse engineering.
1. Open specification
Full specifications for both channels — byte-level layout, the cryptography and known-answer test vectors. Implement it on your own board and verify the signatures without our hardware. Standard primitives (HMAC-SHA256, HKDF, X25519), no vendor lock-in.
2. A prototype today
ESP32 and ESP8266 firmware and the Raspberry Pi script (open source, MIT) — use them as a reference or build for your own board in the configurator, which returns a .bin and the source. One Device object in the app and the whole protocol can be checked at once.
3. Into production
A BLE controller ships empty: binding to an owner happens locally and no server is involved. For socket devices in production there is the manufacturer account: issue a batch with one button, the server hands out keys and binding codes, and you print a QR code on the case. The buyer scans it and binds the device to their account. A white-label app under your own brand is available by agreement.
Want your product to work independently of us rather than depend on one company? The protocol is open, the server is replaceable and BLE works offline — see the open architecture. Do you manufacture hardware? Become a manufacturer →
Build a system for your client
A residential complex, an office building, a warehouse, a private house. Connect the existing hardware through a webhook or a ready IoT stack. Guest keys are handed out by QR code, with no calls to the concierge.
Webhook with HMAC
Anything with an HTTP endpoint connects in a minute. Entrixy sends a POST to your URL signed with a shared secret. Forgery protection follows RFC 2104.
Internet devices
A controller with a permanent connection, for sites where a webhook will not do: no public IP, NAT, mobile internet. ESP32, ESP8266, Raspberry Pi, plus reflashing for Shelly Plus 1 and 1PM.
Smart home systems
Home Assistant
A webhook trigger in configuration.yaml — Entrixy can drive any HA entity: a relay, a lamp, a script.
Node.js
A ready WebSocket client for custom servers, with reconnection and command de-duplication.
Tasmota
Through the web UI: an HTTP rule for the incoming webhook, a GPIO toggle on the output.
Do not see your case?
Write to us: we will help pick an integration route and share draft docs that are not on the site yet.
hello@entrixy.com