01
End node
MCU, LoRaWAN radio, battery, sensors, and enclosure on one board family. Sleep current and wake strategy are designed and measured — so multi-year field life is a spec, not a hope.
Last updated:
At a Glance
- LoRaWAN range is site- and antenna-dependent: open rural line-of-sight can far exceed dense urban links. Confirm ParticLIO SKU datasheets and see /lorawan-vs-wifi for qualitative tradeoffs versus short-range wireless.Source: LoRa Alliance regional and deployment guidance
- ParticLIO smoke-detector SKUs carry EN 14604, CE, and FCC marks where the specific product is certified for that market — not as a company-wide product guarantee.Source: ParticLIO SKU certification documentation
- Multi-year battery life (often cited up to 10 years) is typical for LoRaWAN nodes on standard reporting intervals. ParticLIO datasheets list expected life per SKU and duty cycle.Source: LoRaWAN power profiles and ParticLIO SKU datasheets
- LoRaWAN uses AES-128 encryption for both network and application layers, ensuring end-to-end data security.Source: LoRa Alliance Specification
- LoRaWAN operates in unlicensed ISM frequency bands: 868 MHz in Europe, 915 MHz in North America, and 923 MHz in Asia Pacific.Source: LoRa Alliance Regional Parameters
- ParticLIO helps partners develop customizable IoT and LoRaWAN hardware — sensor node, fire alarm, indoor air quality, gateway, and IoT platform lines, from SMT through certification.Source: ParticLIO Corporate Information
LoRaWAN and IoT products we already ship
Sensor, fire, IAQ, and gateway tiles are workshop and product photos. The field-install tile is a public LoRaWAN example (Wikimedia Commons) — not a ParticlIO SKU.
What a ParticlIO IoT product is
Commercial IoT hardware — not a generic factory offer. LoRaWAN is the radio we practice deepest. You run the network.
02
Gateway
Indoor or outdoor edge radio: regional band, backhaul, and antenna. The gateway forwards traffic to the network server you operate. We do not host your LoRaWAN network.
03
Payload & app
Documented uplinks for a BMS, monitoring stack, or dashboard you brand. Join, Class A/C, ADR, and OTA sit next to the circuit they boot.
The product, not the production line
End nodes, life-safety, IAQ, and gateways — told as devices that join a network you run. Manufacturing is how they get built, not the story we lead with.
End node
A LoRaWAN sensor you can actually field
MCU, radio, battery, and enclosure on one base. Partners add the measurement set, payload, and brand. Sleep current and regional band (EU868 / US915 / AS923) are planned before the first schematic — not patched after a quote.
You leave with: Node architecture, radio plan, battery budget
Continue this threadLife safety
Smoke, CO, heat — battery LoRaWAN a channel can brand
Retrofit detectors that join the network you already run. Alarm and status uplinks are documented for a monitoring panel. Marks (CE, FCC, EN 14604 where applicable) are scoped per SKU, not as a company stamp.
You leave with: Reference SKU, payload notes, mark plan
Continue this thread
Buildings
IAQ that a BMS can parse without guesswork
CO₂, VOC, temperature, humidity in a published uplink. Ceiling or wall housing, configurable intervals, and CMF that looks like a commercial product — not a lab box with a sticker.
You leave with: Payload map and housing starting points
Continue this threadNetwork edge
Indoor and outdoor gateways, one RF family
Regional band, Ethernet or cellular backhaul, wall or pole mount. The gateway forwards packets to the LoRaWAN network server you operate. We document onboarding. We do not host the network.
You leave with: Gateway SKU, RF notes, LNS onboarding
Continue this thread
In the field
Outdoor nodes that keep range and battery
Agriculture, climate, and site monitoring: UV and gasket sit in the same review as the antenna. A pretty box that kills range is not a product. Field life is measured against the architecture.
You leave with: Outdoor node CAD, keep-out, current report
Continue this threadLoRaWAN and IoT product lines we already ship
Sensor node, fire, IAQ, gateway, and an IoT software layer. Start here when you do not want a blank schematic.
Hardware platform
Sensor node
A proven end-node platform — MCU, LoRaWAN radio, power path, and enclosure options — so partners add sensors, branding, and payloads instead of starting from a blank schematic.
- · Condition-monitoring end node (industrial)
- · Facility multi-sensor wall node
- · Outdoor environmental / agriculture node
Fire safety
Fire alarm
Smoke, CO, heat, and related alarm hardware as a product line partners customize — housing, marks, and panel integration — while we handle LoRaWAN and manufacturing.
- · Wireless smoke detector (LoRaWAN)
- · CO / smoke combo detector SKU
- · Heat alarm endpoint for commercial ceilings
Building sensing
Indoor air quality
Indoor air quality and environmental sensing — CO₂, VOC, temperature, humidity — with LoRaWAN payloads partners adapt for BMS and building automation.
- · Ceiling CO₂ / VOC IAQ sensor
- · Wall-mount temp / humidity node
- · Multi-parameter office IAQ endpoint
Network edge
Gateway
Gateway hardware as a customizable platform — regional band, backhaul, enclosure, and antenna — so partners ship network edge devices under their brand.
- · Indoor LoRaWAN gateway (Ethernet backhaul)
- · Outdoor pole-mount gateway
- · Cellular-backhaul edge gateway
Software platform
IoT platform
Device models, APIs, and application building blocks partners brand and run — ParticLIO does not operate customer networks or host your production stack.
- · Branded monitoring portal starter
- · Device onboarding / fleet model pack
- · Alert and dashboard UI kit
What this looks like on a real product
Anonymous project notes — problem, what we did, what the partner kept. No customer names.
Outdoor node — enclosure vs antenna
Problem. An outdoor environmental node needed IP-rated housing. The first ID concept boxed the antenna and killed range.
What we did. Electronics and industrial design sat in one review: antenna keep-out, gasket, and wall thickness. 3D print for feel, CNC for RF and fit, then mold-ready CAD.
What they kept. A housing that still meets the radio budget. The partner owns the CAD, keep-out drawing, and DFM notes.
Custom sensor board — prove it before a panel
Problem. A facility node needed extra I/O and a different battery than the reference. The team did not want to buy a steel tool on an unproven layout.
What we did. Schematic and layout with RF and battery isolation on pass one. Automated DFM, then a small SMT run and bring-up report.
What they kept. Working prototypes and a file set (Gerbers, BOM, pick-and-place) ready for pilot — without a second vendor re-learning the board.
One family, three regional bands
Problem. The same end-node family had to join EU868, US915, and AS923 networks with one payload map.
What we did. Firmware variants on a shared radio stage: join, ADR, and documented uplink fields. Current draw measured against the battery budget.
What they kept. Band SKUs the partner flashes and points at their own network server. Payload notes stay with them.
Smoke / CO hardware for a channel brand
Problem. A life-safety reseller needed their name on a battery LoRaWAN smoke/CO device, with CE and EN 14604 scoped for the market — not a generic box.
What we did. Started from the fire-alarm product line. Brand, CMF, pack-out, and alarm payload mapped to their monitoring stack. Marks planned per SKU, not as a company stamp.
What they kept. Pilot units under their brand, plus a certification plan they can take to the next market.
Ceiling IAQ that a BMS can actually parse
Problem. A building team had wireless CO₂ / VOC sensors that joined a network but arrived as undocumented bytes.
What we did. IAQ platform firmware with a published uplink map (CO₂, VOC, temperature, humidity, status) and configurable intervals. Ceiling housing and CMF for commercial interiors.
What they kept. Devices the partner points at their LNS and BMS. They own the application layer; we own getting the hardware and payload right.
Indoor and outdoor gateway, same RF base
Problem. A campus rollout needed Ethernet indoor units and a pole-mount outdoor unit on the same band plan.
What we did. Shared concentrator and backhaul options; two enclosures and antenna kits. Onboarding notes for the LNS they already run.
What they kept. One radio family, two install SKUs, documentation they keep. We do not operate the network.
The usual way
Most IoT programs stitch a radio consultancy, a firmware shop, an industrial design studio, and an EMS. The payload, the antenna, and the housing never sit in one review. When a node fails join, no one owns the fix.
The ParticlIO way
One engineering team owns the LoRaWAN node or gateway from schematic to shipping box. Radio, battery, enclosure, and payload are decided together. You run the network server. We build the hardware that joins it.
How those products get designed and built
Hardware, firmware, enclosures, and production — in service of the IoT SKU, not a generic factory offer. Engage the full journey or a single stage.
Hardware Design
Commercial IoT electronics, designed to be built. We take LoRaWAN and related wireless products from block diagram to tested prototype: radio and battery first, schematic capture, PCB layout with antenna keep-out, and design-for-manufacturing checks on every revision.
Software Development
Embedded firmware for Commercial IoT: LoRaWAN join, Class A/C, ADR, payloads, provisioning, and OTA — written next to the circuit it boots. You run the network server. We do not host it.
Industrial Design
Enclosures for wall, ceiling, DIN, pole, and outdoor IoT nodes. Antenna window, gasket, and battery holder are designed as one assembly with the radio — not a pretty box that kills range. Print and CNC before anyone cuts steel.
Manufacturing
SMT, assembly, and functional test for the same LoRaWAN and IoT products we design — fixtures written for that radio and payload, not a generic ICT recipe. When a node fails join or a gateway drifts, the person who laid out the board is in the conversation.
Why ParticlIO
Read the pillarsOne team, end to end
Fewer handoffs, fewer surprises, one schedule.
Electronics, firmware, cloud software, industrial design, and manufacturing live in one project flow with one accountable lead. When the enclosure needs one more millimeter for a battery holder, that's a conversation across the room — not a change order across a contract.
AI-accelerated engineering
Faster iterations, fewer respins.
AI-assisted schematic review, automated DFM on every board revision, and AI-assisted test coverage planning. It is how we work — not something we put on a slide.
Commercial IoT specialists
LoRaWAN products that respect radio, battery, and field life.
Sensor nodes, fire and IAQ endpoints, and gateways — not a generic board shop guessing at duty cycles. Join, ADR, payload, and enclosure keep-out are designed together. You run the network server.
Built for overseas teams
English-first communication. Your IP stays yours.
NDA-first, English-first engineering, remote acceptance, and design files that belong to you at every milestone — not just at the end.
Where this hardware lives
All industriesSmart buildings
LoRaWAN IAQ, occupancy-adjacent sensing, and life-safety endpoints for a BMS you already run.
Environmental monitoring
Battery-first outdoor nodes — see agriculture deep dive and sensor-node platform.
Agriculture
Long-range soil, weather, and leak nodes plus outdoor gateways. No new field cabling.
Industrial
Condition-monitoring LoRaWAN nodes and gateways that report into the stack you operate.
Asset tracking
Compact battery end-nodes on the sensor-node platform — see industrial monitoring deep dive.
Retail & workplace
IAQ and smoke/CO under commercial CMF — see smart-building IAQ deep dive.
Frequently Asked Questions
LoRaWAN hardware, standard products, and custom programs
ParticLIO (est. 2020) is a LoRaWAN hardware and IoT software partner. We start from standard products — sensor node, fire alarm, IAQ, gateway, and IoT platform — then help you customize them into a total solution under your brand.
Yes. Projects can include firmware tuning, integration documentation, and optional application co-development on top of our standard hardware and software products. Software is scoped per project — we do not operate your network or a subscription SaaS platform.
Evaluate a standard product (sensor node, fire alarm, IAQ, gateway, or IoT platform) → customize hardware and software for your brand → prototype → certify → produce. Applications engineering scopes the total solution with you.
You do. Clients choose and operate their network server, dashboards, and customer apps. ParticLIO provides standard products plus integration support that connects to your stack.
LoRaWAN is a low-power wide-area protocol for battery-operated sensors. Range and battery life are site- and duty-cycle-dependent — see our LoRaWAN vs WiFi comparison (/lorawan-vs-wifi) for qualitative tradeoffs versus short-range wireless, and confirm SKU datasheets for ParticLIO products.
Fire safety products support CE, FCC, and EN 14604 where that specific product is certified for the target market — not as a company-wide guarantee. Quality management is coordinated with manufacturing partners as scoped in your project.
Use Contact Us or email [email protected] with the product or platform you want to start from, certification market, deployment scope, and customization needs. Evaluation samples are available for qualified projects.
We work with partners worldwide. Regional radio bands (EU868, US915, AS923) and delivery terms are confirmed per product and quoted per project.