How Do I Make My Product Connected?
Start from what the connection is for, then choose the radio, firmware, and cloud to serve it. Remote monitoring, over-the-air updates, and smart home integration each put different demands on the device. PDE defines those requirements with you, selects the wireless technology, and develops the device, firmware, and cloud integration together, as it did for the WiFi, BLE, Z-Wave, and MQTT connectivity in the second-generation iGuard stove safety device.
- What the connection is for: remote monitoring, control from a phone, over-the-air updates, or integration with a smart home or third-party platform. Each sets how much data moves, how often, and in which direction.
- Where the device lives: indoors or out, in a building with WiFi or a field with none, above ground or behind a concrete wall. Location narrows the wireless options before anything is tested.
- Which wireless technology: BLE, WiFi, cellular (including CAT-M1 and NB-IoT), LoRa, or Z-Wave, chosen for range, power, data rate, and coverage where the product will actually be installed.
- What changes on the board: a radio, an antenna with room around it, a power budget that covers transmitting, and a processor with the memory to run the protocol stack and security.
- What runs in the cloud: an endpoint the device talks to, such as an MQTT broker, a backend to store data and commands, and the app or API people use to reach it.
iGuard Home brought PDE a stove safety device whose first generation had already proven itself. The second generation of the iGuard needed full wireless connectivity: WiFi, BLE, and Z-Wave, plus MQTT-based IoT platform integration for remote monitoring, device management, and over-the-air updates. PDE developed the three custom PCBs, the firmware, and the IoT integration, and took the product through FCC and ISED certification.