The Backbone of IoT.LoRaWAN Infrastructure.

LoRaWAN is not designed for large data volumes (images, video, audio) or real-time controls in the millisecond range. The bandwidth is very low (a few bytes per message). It's the perfect technology for status data (temperature, fill level, meter reading, position), but not for surveillance cameras or fast browsing.

Since LoRaWAN uses a license-free frequency band, there are 'fairness' rules (Duty Cycle). A device may usually only transmit 1% of the time. In practice, this means: Intervals of 5, 10, or 15 minutes are easily possible and standard. For second-by-second measurements, LoRaWAN is the wrong technology.

No. LoRaWAN sensors transmit with extremely low power (max. 25 mW) and only for a few milliseconds per hour. For comparison: A mobile phone at your ear transmits with up to 2,000 mW. The radiation exposure from a LoRaWAN network is negligible compared to WiFi or cellular.

Public (e.g., TTN, Telcos): You use a provider's network. Your data runs through external infrastructure. Coverage can be patchy (especially in basements). Private (merkaio approach): We build your own network on your premises. You have full control over the gateways, guaranteed coverage exactly where you need it (e.g., in the basement), and your data doesn't unnecessarily leave your control.

We use professional gateways (e.g., from Milesight) with integrated buffer storage. If the internet connection (uplink) fails, the gateway stores the sensor data locally. As soon as the connection is restored, the data is forwarded to the server. This way, no measurements are lost.

Yes, this is possible (Class C devices). You can send commands to actuators, e.g., 'close valve' or 'dim light'. However, since LoRaWAN is primarily optimized for receiving data and downlinks put more strain on network capacity, we recommend this only for occasional switching operations, not for permanent control loops.

Absolutely. This is one of the strongest use cases ('Retrofit'). We use LoRaWAN controllers (e.g., Milesight UC300) that capture old analog signals (4-20mA, 0-10V) or digital interfaces (RS485/Modbus) and transmit them wirelessly. This makes a 30-year-old water meter or lathe 'smart' without replacing the controller.

The manufacturer's claim of 'up to 10 years' is under laboratory conditions (25°C, infrequent sending). In reality, we plan more conservatively: With a 15-minute sending interval and normal conditions, good sensors last 3 to 5 years. In cold environments (cold storage) somewhat shorter. However, battery status is permanently monitored, so replacement is plannable.

LoRaWAN uses double encryption with AES-128. Network Session Key: Guarantees the authenticity of the device in the network. Application Session Key: Encrypts the actual payload data. Even if someone intercepts the radio traffic, they only see garbled data. Only on your server is the data decrypted.

Unlike NB-IoT or cellular, LoRaWAN sensors don't need a SIM card or mobile contract per device. You have one-time acquisition costs for the hardware. The ongoing costs at merkaio relate to operating the central infrastructure (Managed Gateway & Network Server), regardless of whether you operate 50 or 500 sensors in this network. This makes scaling extremely affordable.

Yes. LoRaWAN is an open standard of the LoRa Alliance. We can operate a temperature sensor from manufacturer A, a fill level sensor from manufacturer B, and a gateway from manufacturer C in the same network. This protects you from 'vendor lock-in' to a single hardware supplier.

LoRa waves are physically very long-wavelength (868 MHz). They penetrate solid matter like concrete or earth much better than short-wavelength WiFi (2.4 GHz). That's why we often still have reception in basements, elevator shafts, or behind steel doors, where mobile phones have long shown 'No Signal'.