BLE2MQTT vs Network Tools

Bluetooth Broadcast → MQTT, Easily Build a Soft Gateway This app turns your iOS device into a powerful Bluetooth gateway and debugging tool. It automatically captures broadcast data from surrounding Bluetooth devices, parses it according to custom or known protocols, and publishes the data via MQTT to your server or cloud platform. Core Features Broadcast Capture – Scan and receive broadcast packets from all detectable Bluetooth devices (e.g., beacons, sensors, IoT devices). MQTT Forwarding – Publish raw or parsed data to any MQTT Broker (supports TLS authentication and username/password). Protocol Parsing – Built-in common Bluetooth broadcast protocols (HW80x Heart Rate Armband, ZY Series Wristbands etc.) for automatic parsing and structured output. Debugging Tool – View raw broadcast data in real time (Hex/ASCII), with filtering, packet capture, and log export – ideal for Bluetooth device development and debugging. Soft Gateway Mode – Run continuously in the background (with proper authorization) to forward captured data to the cloud – no additional hardware gateway required. Use Cases Collect and upload Bluetooth device data in smart homes or industrial IoT. Verify and debug broadcast protocols during Bluetooth device development. Quickly prototype and test the Bluetooth → MQTT data link. Privacy & Permissions Bluetooth permission is needed for device scanning. Network permission is required for connecting to an MQTT Broker. No personally identifiable information is collected. All data is controlled by the user, stored and forwarded to the user’s own destination. Requirements iOS 13+ or iPadOS 13+ Device with Bluetooth 4.0+ You must configure your own MQTT Broker address and subscription rules Whether you are an IoT developer, a hobbyist, or a system integrator, this app allows you to achieve cloud connectivity for Bluetooth data at the lowest cost.

A network engineer's toolkit that runs entirely on your iPhone. Seventeen tools, no account, no server of ours, and nothing about you collected. THE TOOLS • Ping — ICMP latency and packet loss, with a live chart • Traceroute — the hop-by-hop path, each router named • LAN scan — every device on your subnet, named and identified: routers, NAS boxes, printers, Macs, phones • Port scan — TCP connect scan with banners and service names, from a handful of ports to all 65535 • DNS — your own wire-format resolver: every record type at once, any public resolver you choose, DNS-over-HTTPS, reverse lookups, and a comparison mode that queries five resolvers and flags the one that disagrees • HTTP check — status, redirect chain, the DNS/connect/TLS/TTFB split, security headers • TLS — the full certificate chain, expiry, SANs, cipher suite, and whether the system trusts it • WHOIS — the referral chain followed to the registrar that actually holds the record • Wi-Fi — link quality graded against local thresholds, and a walking survey that compares rooms • Speed test — download, upload, latency and jitter, against Cloudflare or a URL you name • iperf3 — throughput against your own iperf3 server, up or down, multi-stream • IP calculator — CIDR maths, masks, host ranges, binary, and subnet division including VLSM • MAC lookup — 39,000 vendor prefixes, bundled and fully offline • Wake on LAN — the magic packet, sent to every address that might reach a sleeping machine • Network interfaces — addresses, subnets, flags and live throughput • Telnet — a raw TCP terminal for switches, PDUs and console servers • SSH — see below A REAL SSH CLIENT Not a wrapper. The protocol is implemented in Swift, and it does the things you actually need from a phone: • Jump hosts — reach a machine behind one bastion or several, each hop with its own account, its own credential and its own host key to confirm • Port forwarding — bind a local port to a service on the far side, then open it in a browser inside the app: a router's web interface, a database, a dashboard listening only on the server's loopback • scp — send a file up or pull one down, straight to the Files app • ssh-copy-id — put your public key in a server's authorized_keys without a second terminal • Keys — generate ed25519 on the device, or import ed25519, ECDSA and RSA in OpenSSH or PEM form, protected or not. Private keys live in the Keychain and can be exported under a passphrase when you need them elsewhere • Snippets — the commands you always type, one tap above the keyboard • A proper terminal — a real VT/xterm emulator, so vim and htop work, with esc, ctrl, alt, arrows and F-keys on a row of their own