Web3 public sensors map

Welcome to the decentralized opensource sensors map which operates with the sole intent of serving the free will of individuals , without any beneficiaries. It offers two distinct layers of decentralization at your choise: peer-to-peer connectivity for direct access to sensor data, and the federative concept for accumulating sensor data and displaying measurement history. Click here for further technical details.

Map data © OpenStreetMap contributors

airalab/sensors.social v4.1.0

Secured by

Your bookmarked sensors

Save any sensor from the map here for quicker access
← Back to Blog

Coming soon: the next Altruist firmware

  • firmware
  • altruist
  • encryption
  • coming-soon

We’re preparing a major Altruist firmware update: an app-like web interface, optional map value encryption, and easier backup. Here’s what’s coming.

New web interface

The device UI will feel closer to a mobile app. Four areas:

TabPurpose
altruist.localReadings and device settings
sensors.socialMap / Robonomics related settings
CustomHome Assistant, API, InfluxDB, CSV
SystemDebug, restart, backup, wipe config

Desktop gets a sidebar; phones get bottom tabs. The captive portal for first-time Wi‑Fi setup stays familiar, with clearer steps (1 → 2 → Finish setup) and inline hints.

Mobile hub, Local tab with readingsMobile hub, System tab with readingsDesktop hub with sidebar


Encrypting values on the map

The sensors.social map is open by design: anyone can see what a sensor reports. For many readings that’s exactly the point — air is shared. Sometimes, though, you’d rather keep a few values to yourself: bedroom temperature, co2, anything you don’t want on a public pin.

The new firmware will let you choose which metrics to encrypt before they leave the device. Outwardly, a number becomes a sealed string — unreadable without your key. Neighbors still see what you leave open; encrypted fields open only for you.

In practice it looks like this. In device settings you turn on encryption for the metrics you care about. The sensor seals them so only the owner can unlock them — usually the device itself, or the account you use to log in on the map. On sensors.social you sign in with your seed phrase or import a backup, and those sealed fields become ordinary numbers again.

If the owner is set manually to a different address (not the device’s own key), you’ll need that key to decrypt on the map. A regular device backup still restores settings, but it won’t unlock ciphertext meant for someone else’s owner key.

Altruist interface with encryptionMap — encrypted metrics before loginLogin for encryptionSame metrics after owner login

The format follows Robonomics CPS: device and owner agree on a shared secret without sending it over the network, derive an AES key, and ship the value as e.…. More in the format notes and how encryption works.


Backup and restore

Your Altruist keeps more than Wi‑Fi credentials: coordinates, sharing options, and its Robonomics device identity (the address that ties readings to you on the map). Lose the config, and you’re starting from scratch.

That’s why backup becomes a first-class screen in the new firmware, not a hidden export.

System → Backup & restore will export a full settings backup (including the owner key when present). Restore replaces config and reboots. The same file can be used for map login — one export for restoring the device and unlocking your data on the map.

On guest Wi‑Fi, restore will be available before joining the home network — handy after a reset, while the sensor is still in first-time setup.

System → Backup & restore


And more

  • Unique hostnames: altruist-insight-<id> / altruist-urban-<id>
  • More reliable config save after Wi‑Fi setup
  • Datalog and Map signing that handle long encrypted fields

When the build ships, we’ll post again with updates. Stay tuned on sensors.social!