ThingAlarm vs NetPulse Diagnostics

ThingAlarm is an app for monitoring IoT sensor data. Data is sent to ThingAlarm via interfaces such as HTTP(s) from a sensor or a LoRaWAN network server. In the web console, the user defines various rules to specify which events should trigger a push notification to the ThingAlarm app clients. The app can notify users, for example, when a temperature threshold is exceeded or a smoke detector is triggered.

NetPulse Diagnostics is a clean network troubleshooting toolkit for iPhone and iPad. It helps developers, system administrators, website owners, support teams and everyday users understand what is happening with their connection. Check your network without guessing: • View Wi-Fi, cellular, VPN and network path status • Inspect local interfaces visible to iOS • Run DNS lookup and DIG-style record checks • Test ICMP ping and TCP latency • Check TCP ports and UDP diagnostic responses • Probe HTTP and HTTPS endpoints • Inspect SSL/TLS certificate details • Detect your public IP address • Scan your own LAN with ping sweep or selected TCP ports • Measure download and upload speed • Save local diagnostic history and export reports NetPulse is useful when a website does not open, a DNS record looks wrong, a VPN route changes, a certificate needs verification, a local device disappears from the network, or a service port does not respond. Built for both technical and everyday use: Developers can quickly validate hosts, ports, DNS records, SSL certificates and HTTP responses. Site owners can check whether their domain, website and certificate are reachable. Home users can inspect their current network, VPN state, public IP and local devices in a simple interface. Responsible diagnostics: LAN scanning is designed for networks you own or have permission to test. iOS may ask for Local Network permission before local device checks. Some routers, VPNs and cellular networks block ICMP ping, so NetPulse also provides TCP and HTTP checks as practical alternatives. Privacy-first workflow: No account is required. Reports are stored locally on your device. Diagnostic requests are started by the user when running a selected check, scan or speed test.