ThingsLog IoT solutions FAQ

More Questions About ThingsLog IoT Solutions

Q10: What industries does ThingsLog serve?

ThingsLog serves water utilities (municipal and regional), commercial and industrial energy management, smart agriculture, hotels and commercial buildings, FMCG and retail chains, municipalities and public-sector organisations, and telecommunications operators deploying private LoRaWAN infrastructure. If your operation involves distributed assets that need to be measured or controlled remotely, ThingsLog has a relevant deployment model.

Q11: What connectivity technologies are supported?

ThingsLog data loggers support multiple radio technologies on a single device: LoRaWAN (EU868, US915, AS923) for long-range, ultra-low-power communication over private or public LPWAN networks; NB-IoT and LTE-M for cellular-based low-power wide-area coverage; 4G/LTE for high-data-rate or near-real-time applications; and 2G/GSM as a legacy fallback in areas where newer cellular standards have limited penetration. Selected models can operate across multiple networks simultaneously and auto-select the best available link.

Q12: How long do batteries last in ThingsLog data loggers?

In LoRa or NB-IoT low-power mode with a 15-minute reading interval, ThingsLog loggers are designed for up to 10 to 15 years of operation on a single battery set — eliminating the need for routine battery replacement site visits. Loggers using 4G connectivity for high-frequency transmission have higher power consumption and typically require an external power supply or solar panel with battery backup for continuous outdoor deployments.

Q13: What is non-revenue water and how does ThingsLog address it?

Non-revenue water (NRW) is the difference between the volume of water entering a distribution system and the volume billed to customers. In ageing networks, NRW commonly represents 20 to 40% of total production — a direct financial loss to the utility and a waste of treated water resources. ThingsLog addresses NRW through continuous pressure and flow monitoring across district metered areas (DMAs), automated minimum night flow analysis, and AI-assisted anomaly detection that pinpoints the location of losses so field crews can intervene quickly and precisely.

Q14: Can ThingsLog integrate with existing meters?

Yes. ThingsLog data loggers are designed to connect to existing infrastructure without requiring meter replacement in the majority of cases. Supported interfaces include pulse output (S0), Modbus RTU and TCP, wired M-BUS, and wireless M-BUS. This means most water meters, energy meters, and gas meters already installed at customer sites can be read remotely by a ThingsLog logger added to the existing installation.

Q15: What smart meter protocols are supported?

ThingsLog supports wired M-BUS (EN 13757), wireless M-BUS (OMS), Modbus RTU over RS-485, Modbus TCP over Ethernet or 4G, pulse output (S0 / reed switch), and MBUS-over-LoRa for retrofitting older meters with long-range wireless communication. This breadth of protocol support ensures compatibility with the widest possible range of metering equipment from leading European and international manufacturers.

Q16: How is data secured?

Security is applied at every layer of the ThingsLog stack. Data in transit is protected by TLS/SSL encryption. LoRa transmissions use AES-128 encryption at the network and application layers as defined by the LoRaWAN specification. The platform enforces role-based access control (RBAC) so users see only the data and features relevant to their role. Data handling is GDPR-compliant, with EU-based data storage as the default. For utilities with stricter data sovereignty requirements, on-premises or PAAS deployment keeps all data within the customer’s own infrastructure.

Q17: What is the difference between SaaS and on-premises deployment?

In the SaaS model, ThingsLog hosts and manages the entire platform in EU cloud data centres — customers benefit from zero infrastructure investment, automatic updates, and a managed uptime SLA. In the PAAS (Platform as a Service) or on-premises model, customers deploy the ThingsLog platform on their own servers or private cloud environment, retaining full data sovereignty and the ability to integrate with internal networks not reachable from the public internet. Hybrid configurations — where data ingestion is on-premises but analytics and dashboards are cloud-hosted — are also available.

Q18: How does the ThingsLog mobile app work?

The ThingsLog mobile app is available for iOS and Android. It provides real-time sensor readings, interactive historical graphs, active alarm management, and push notifications for threshold breaches and system events. The app supports multiple sites and multiple accounts, making it suitable for field engineers managing several customer deployments. A white-label version of the app is available for operators who wish to offer the platform under their own brand.

Q19: What is the typical deployment timeline?

A pilot deployment covering 10 to 50 devices can typically be operational within 2 to 4 weeks from order placement, including device configuration, network provisioning, and platform setup. Full-scale rollouts depend on the number of sites and the complexity of integration requirements. ThingsLog devices support firmware updates over-the-air (OTA), meaning configuration changes and software upgrades can be applied remotely without site visits after initial installation.

Q20: How is the platform priced?

ThingsLog uses a subscription model priced per active device per month, covering platform access, data storage, and support. SaaS and PAAS licences are priced separately to reflect the difference in hosting and management responsibilities. Hardware is priced independently from the software subscription. Volume discounts are available for utilities and operators deploying 1,000 or more endpoints. Contact ThingsLog for a tailored quote based on your specific device count, connectivity mix, and deployment model.

Q21: What training and support is provided?

All customers receive online onboarding support, access to the ThingsLog documentation portal, and access to technical support via email and ticketing system. Optional on-site installation support and training sessions are available for larger deployments. Enterprise customers can agree a formal service level agreement (SLA) specifying response times and escalation paths for critical issues.

Q22: What certifications do ThingsLog devices have?

ThingsLog data loggers carry CE marking for the European market and are rated IP68 for permanent submersion — essential for underground meter pit deployments. Selected LoRaWAN models are certified by the LoRa Alliance, ensuring interoperability with any LoRaWAN-compliant network server. Specific models include an embedded 1NCE SIM for global cellular connectivity with no SIM logistics overhead.

Q23: Can ThingsLog integrate with SCADA, GIS, or ERP systems?

Yes. ThingsLog provides a REST API and MQTT broker interface for real-time and historical data export to any system capable of consuming standard web services. A Modbus TCP gateway option allows legacy SCADA systems to poll ThingsLog data using the same protocol they use for local PLCs. Documented integration examples include AVEVA and Ignition SCADA platforms, Esri ArcGIS and QGIS for spatial analysis, SAP and Microsoft Dynamics for ERP-level asset and billing data flows.