Typically, an IoT device needs some form of connectivity in order to communicate with the network, whether it be Wi-Fi, Bluetooth, or cellular connectivity. But what should be done when none of these are available? Chirping, as it turns out, may be just the answer we’ve been looking for.
Remember the good old R2D2 from Star Wars? Modern IoT devices can use a similar means of communicating. However, this method has a substantial downside: the amount of data that can be transferred this way is rather limited.
To address the elephant in the room, noise pollution may also be a problem, but there is a way to make chirping almost inaudible to the human ear by using ultrasound. This method of exchanging data between devices is also rather secure, since the data is encoded and decoded in real time.
This type of solution, however, is not suitable for large IT installations and industrial gear. It’s intended for smaller, dynamic payloads.
IoT devices often don’t have a monitor attached to them. This makes things a bit challenging when trying to troubleshoot a problem. However, if they are configured to communicate their status by chirping an error code, a service technician could simply be notified of the device status via phone just by placing it next to the device during a call. This has the potential to make fixing things much easier, since, depending on the problem, the tech support personnel wouldn’t even have to enter the premises of your company.
In any case, this is an exciting technology, and companies like Chirp are already taking advantage of it.