Going from 5 hand-built BLE tags to 500: certified module or our own nRF52 layout?
I’ve been tinkering with BLE temperature tags at home for a while (nRF52832 on my own little PCB, coin cell, advertises temperature every 30 s). A hotel group saw them and wants 500 for minibars and cold rooms. Exciting, also terrifying.
My current design is the bare chip with a PCB antenna I copied from the reference design. For 500 units and legal sale, should I keep that or switch to a pre-certified module? And the hotel wants the readings in their Hermetry, so how would 500 tags get there? Right now a Pi at home listens and I look at a terminal.
Hotel side here (not that group, but same need). Whatever you do, I can’t be typing 500 device tokens into Hermetry.
Certified module. Testing your own radio design for intentional radiator certification costs more than your whole first batch, and a copied antenna rarely passes first time.
BLE tags can’t talk to Hermetry directly anyway, you need something with internet in every building.
Module cost me about 4 USD more than the bare chip at 500 pcs. Hotels are 3 buildings with maybe 20 rooms per floor.
4 USD × 500 is cheap next to radio certification. Take an nRF52832 module that carries its own FCC ID and CE paperwork (Raytac MDBT42Q is the one our lab uses), follow its layout rules for the antenna keep-out, and you only need the cheaper unintentional emissions testing for the whole product. Keep your firmware as is, the chip is the same.
For Hermetry: the tags themselves never log in. You put a BLE gateway on each floor (a Pi or any box with BLE and network) that listens to the adverts and reports each tag as a child device over the gateway API:
v1/gw/telemetry
{"tag-C4A1F0": {"values": {"temp_c": 4.2, "batt_mv": 2950}},
"tag-C4A1F7": {"values": {"temp_c": 6.8, "batt_mv": 2910}}}
Hermetry creates each child the first time it sees the name, puts it in the gateway profile’s „Profile of new children“, and children never have credentials of their own. That answers Emily: one token per gateway, three or so per building, nothing per tag. A gateway takes up to 500 children by default, and each child counts toward the plan’s device limit.
If two gateways on neighbouring floors hear the same tag, decide in the gateways which one reports it, otherwise you get it twice under two names. Details: Devices behind a gateway.
Ordered 20 MDBT42Q modules to rework the board, and set up a Pi gateway at home with the v1/gw format. My five tags showed up as children named after their MAC addresses within a minute. The double-reporting point is real: two Pis in my house both reported the same tag, fixed it with a strongest-RSSI rule in the gateways.
No tokens per tag, perfect. Let me know when you have a quote.
- Du musst angemeldet sein, um auf dieses Thema antworten zu können.
Mitdiskutieren
Melde dich an, um Fragen zu stellen und zu beantworten, hilfreiche Beiträge mit „Gefällt mir“ zu markieren und die Antwort zu kennzeichnen, die dein Problem gelöst hat. Jeder Beitrag bringt Punkte und Stufen.

