easyBLE turns a browser, a phone or a small gateway into a secure tunnel to your BLE products. Your support team, your engineers and your test lab work on the real device, as if they were standing next to it.
Try it yourself in two browser windows, no account needed →
No app install for your customers · Works in Chrome and Edge · Phone app and Linux gateways
Bluetooth only reaches across the room. Everyone who needs to look at a device, from support to engineering, has to rely on screenshots, phone calls and guesses.
Support calls take 30 minutes, end without a diagnosis and too often with a technician on site.
Field issues depend on firmware, configuration and environment. Engineering never sees the affected device.
Firmware rollouts and test runs need someone next to every device, in every country.
No installation, no network configuration, no port forwarding. The connection is opened from the customer's side and only for this session.
In Chrome or Edge on a laptop or Android phone, or in your app. They pick their device in the Bluetooth dialog of the browser.
Like an ID and a password, valid for this session only. On the phone or in the chat.
Device type, firmware, all values with names and units, known findings, chat. Every change is confirmed by the customer.
Put two Chrome or Edge windows side by side. The left one plays your customer next to the device, the right one plays your support team anywhere in the world.
Works in Chrome and Edge on Windows, macOS, Android and ChromeOS. Both windows can also be on different computers, in different countries.
Diagnose and fix while the customer is on the phone. Fewer technician visits, shorter calls, a report for every session.
Read affected devices in the field, per firmware and dictionary version. Find patterns before they become recalls.
Labs in different countries, one test run. Automated read and write tests against real hardware.
Update devices that are offline for the cloud, with the customer's consent.
First level support that reads the device, knows the findings and hands over to a human.
A small gateway dials out to the relay, clients attach to it. Your protocol lives in a plugin, so every tool on the platform speaks your device's language.
Run a gateway next to the device$ node gateway.mjs --relay wss://easyble.io --gw lab-01 Your device as a pluginexport const sensorPlugin: DevicePlugin = { id: 'sensor-pro', services: ['6e400001-…'], match: (d) => d.name?.startsWith('SP2') ? 10 : 0, async open({link}) { await link.connect(); return { read: () => readRegisters(link), checks: (values) => knownFindings(values), // identify, describe, write, close … }; }, };
Remote access to a product at someone's home needs trust. easyBLE is built around consent.
You don't need to build anything to start. We know Bluetooth devices from firmware protocol to support desk and integrate yours.
Your protocol and parameters as a plugin: named values, units, findings, safe writes.
Branded support page, console for your team, integration into your ticket system.
easyBLE on your existing gateways or on low-cost hardware for labs and installations.
Regular analysis of your device data: anomalies per firmware, counters, outages.
Every Bluetooth Low Energy device with a GATT interface. For named values and checks we add a plugin for your protocol; without one you get the raw view.
No. The support page runs in Chrome and Edge on Windows, macOS, Android and ChromeOS. iPhones and iPads don't support Bluetooth in the browser; there we integrate easyBLE into your app.
Only parameters you allow, and only after the customer confirms each change on their screen.
No. easyBLE runs as a managed service. If you need it, the relay and workers can also run in your infrastructure.
With a demo on your own device. Then a pilot: one plugin, your support page, a few weeks with real cases.
30 minutes, your device, our support page. You will know right away what your team could see.