wopdiddly retweeted
We published a white paper on what an operating system for physical AI should be.
The short version: a robot only knows what its own sensors can reach. A robot dog on a campus patrol can't know that a door just opened in a building across campus. Connect the door sensor and the robot to the same operating system, and the door opening sends the robot there, turns on the lights and alerts the guard on call.
The video is our patrol-robot demo: an AI agent runs the robot from plain-language orders, and a person decides what happens next.
Read the paper: kiloiot.io/whitepapers/physi…
#PhysicalAI #AIoT #Robotics #IoT #Kilo
wopdiddly retweeted
The tracker connector supports more than 2,000 vehicle tracker models through one endpoint.
Once connected, a vehicle can appear on the map with its live position and a selected metric reported by the tracker. Operators can also replay its route over a chosen period instead of working from a list of coordinates.
Tracker data uses the same platform as fixed sensors. It can be displayed on dashboards and used by rules and alarms without requiring a separate fleet-data interface inside the deployment.
This gives companies a way to monitor vehicles alongside buildings, equipment and other assets when those operations belong in the same view.
#Chirp #FleetTracking #IoT
wopdiddly retweeted
Back from Amsterdam.
The useful thing about putting a few thousand people who build this stuff in one building is that it makes the real bottleneck obvious, and it isn't the one the industry talks about.
Connectivity is solved. Getting bytes off a sensor stopped being hard years ago. Range, battery life, gateway cost — all of it has been ground down by people who did the work.
What has not been solved is everything after the radio. A payload arrives and means nothing until someone maps it. Automation gets written and then trusted rather than tested. Alerts fire into a void at 3am. And the whole thing still assumes an integrator sits between the hardware and the person who actually cares about the building.
Every one of those is a reason a deployment does not happen. Not a technical ceiling — an effort ceiling.
That's the gap we've spent this year building into, and the conference made us more confident it's the right one.
#Chirp #TheThingsConference #IoT
wopdiddly retweeted
Day one at The Things Conference in Amsterdam.
Our main demonstration starts without physical sensors. We create emulated devices, build dashboards, run rules and trigger alarms, then show how the same configuration can be connected to real hardware later.
We are also demonstrating supported device commands. The user sees the proposed action, approves it and can verify the result against the state reported by the device.
These are important capabilities for commercial deployments because teams can test the operational workflow before a hardware rollout and keep the work when the deployment goes live.
We are here today and tomorrow.
#Chirp #TheThingsConference #LoRaWAN
wopdiddly retweeted
LoRaWAN isn’t going anywhere, and mioty is a very promising protocol. We believe these technologies should work in tandem—and that’s the idea behind this workshop.
@tim_krav_ will be hosting “Build a Mixed LoRaWAN + mioty Monitoring Workflow” at The Things Conference in Amsterdam! 🐦
Tim will walk through how to bring both technologies together in our platform and build a shared monitoring workflow. A practical session to see the platform in action, ask questions, and explore what’s possible when different devices work together.
📅 Tuesday, September 22, 2026
🕐 13:00–13:50
📍 Workshop Room 1 · The Things Conference · Amsterdam
If you’re attending, come join Tim. We’d love to hear what you’re building!
#Chirp #depin #LoRaWAN #mioty #IoT @SuiNetwork
Sui can’t stand out with MEM projects; a true catalyst could be Depin, which is tied to real-world use cases. Take a look at the @ChirpDeWi project in the IoT–Larowan space; we’ve continued to develop our platform—please check it out. We’ll be attending The Things Conference on September 23 at De Kromhouthal in Amsterdam, where our key partnerships will be announced. @ChirpDeWi deserves much more attention.
growth is the only thing that matters to us right now
if your product is bringing new users to #Sui, show us. i want to know what’s working and what we can do to help you make it much bigger
YOU WILL HAVE MY FULL ATTENTION
wopdiddly retweeted
I’ve been waiting over a year to write this post. And next week, I’ll finally get to show you why. 👀
We’re getting ready to release a major Chirp update this week or early next week, and we’ll be showcasing it at the TTN conference.
Our partners have already had a heads-up. Now I can barely keep this one to myself.
For me, this is a huge step forward for Chirp. It opens up a whole new set of possibilities for our IoT platform and makes what we’ve been building much easier to show, explain, and get excited about.
A year of work. Almost time to show you.
Stay tuned. 🔥
wopdiddly retweeted
Chirp alarms can notify several people in sequence until somebody responds.
A team chooses one of five severity levels and builds an escalation chain with recipients, delays and delivery channels. Email, SMS and push notifications can be used at different stages of the same chain.
Schedules and timezone-aware quiet periods control when routine notifications are sent. Duplicate suppression prevents a changing sensor from producing a stream of identical alerts, while repeat behavior can be configured per severity.
The alarm inbox shows what is active, acknowledged and resolved, including the latest trigger time and the values that caused the alarm.
The platform also requires every escalation step to contain a recipient, so a team cannot save a chain that has nobody to notify.
#Chirp #IoT #DePIN
wopdiddly retweeted
The Digital Building Twin was built for more than a single floor plan.
It supports multiple floors, indoor and outdoor areas, and a site footprint traced from an aerial map. The finished model can be anchored to its real GPS position.
The object catalog contains more than 60 ready-made items covering buildings, equipment and outdoor infrastructure. Every object can be connected to a sensor from any supported connector, so different hardware and radio technologies can appear in the same model.
Operators can show live values on the model or hide the numbers and use the color conditions instead. A multi-building or multi-floor deployment can therefore keep its spatial context while the underlying devices continue to use the same dashboards, rules and alarms as the rest of the platform.
#Chirp #DigitalTwin #IoT
wopdiddly retweeted
Chirp can turn a site into a live 3D model and bind sensor data directly to the objects inside it.
A team can model multiple floors and outdoor areas, draw the site in 2D or 3D, or trace the footprint from an aerial map and anchor it to real coordinates. The editor includes more than 60 objects for buildings, equipment and outdoor infrastructure.
Any sensor can be bound to an object. As readings change, the object can change color according to number ranges, text values or true-and-false conditions. Live values can also be pinned in the position where the equipment or monitored area exists.
For a larger site, this gives operators one spatial view of many different systems. They can see which floor, room, parking area or piece of equipment needs attention without translating a list of device names first.
#Chirp #DigitalTwin #DePIN
wopdiddly retweeted
Chirp 3.9 is live — Flight Log. This release removes two things that have capped how big deployments on the network can get: false alarms that make people switch their automations off, and a rules engine that needed one rule per device.
Full changelog and docs: docs.chirpwireless.io/change…
#Chirp #DePIN #IoT
wopdiddly retweeted
Over 2,000 vehicle tracker models work on Chirp, through a single ingest endpoint.
OBD2, CAN, standalone GPS units. You get a URL, you point the tracker at it, and the vehicle becomes an ordinary device on the platform — same dashboards, same rules engine, same alarms as a sensor bolted to a wall.
Which means it inherits everything else without any special-casing. Put it on the map widget with live position and a metric of your choice — speed, fuel, engine state. Play the route back over history. Write a rule against it. Escalate an alert off it.
We think fleets are one of the fastest paths to scale for a network like this, and the reason is unglamorous: it's already someone's job. Fleet operators already track vehicles, already pay for it, and already feel the pain when the data lives in a system that does nothing else. Moving them onto a platform where the vehicle sits next to everything else they monitor is an easy argument to make.
Thousands of devices per customer, and they're already looking.
#Chirp #FleetTracking #IoT
wopdiddly retweeted
For two years AI could talk about the physical world. Now it operates it.
Say "turn on the lamp" and the lamp turns on. Ask it to flip a relay, or change how often a sensor reports, and it does that too.
The part we're proudest of is how careful it is, because something physical is about to happen in someone's building:
It only does what your device is already set up to do. It doesn't invent capabilities.
It shows you exactly what it's about to do and waits for a yes.
And afterwards it checks. A message to a sensor takes a moment, and a sleeping device can miss one — so instead of cheerfully saying "done," it verifies and tells you if it didn't land.
That last one sounds small and isn't. The difference between a demo and infrastructure is what happens when the command fails.
This is what an IoT network is for. Not dashboards you stare at — a physical layer that software can actually reach and move.
#Chirp #PhysicalAI #DePIN
wopdiddly retweeted
You don't need a single sensor to try Chirp anymore.
We shipped the Emulator, and it quietly removes the biggest thing standing between someone hearing about this platform and actually using it: hardware.
Here's how it works. You add an Emulator connector — nothing to fill in, no account to link, no keys to paste. Then you create a sensor and pick a real device model. Chirp fills in the readings that model actually sends: a multi-sensor gives you temperature, humidity, CO2 and air quality, with the right value types and a sensible reporting interval. And then it just starts reporting, on whatever schedule you choose.
From there everything else is real. Dashboards fill in. Automations run. Alerts fire. The rules engine executes against emulated telemetry exactly as it would against a device on a rooftop.
Why this matters more than it sounds: every platform in this space has the same funnel problem. Someone gets interested, hits "you'll need a gateway and a sensor," and disappears for two weeks. Most never come back. That gap has always been the ceiling on how fast an IoT network can actually grow.
Now the evaluation is instant. Model an entire deployment, prove it works, and only then buy hardware — and when the box arrives you point the same device at the real sensor and keep every dashboard, every rule, every alert.
Fewer people bounce. More deployments get built. More of the physical world ends up on the network.
Zero hardware, zero card: app.chirpwireless.io
#Chirp #DePIN #IoT
wopdiddly retweeted
One question decides whether an IoT network grows or stalls: how much of the physical world can it actually ingest?
We rebuilt the whole platform around that. Everything runs on one model — Connector, Connection, Device — and the protocol is just a detail underneath it.
What's plugged into it today:
LoRaWAN, with the network server built in. No external LNS to run or pay for. Gateway registration, joins, uplinks, downlinks, deduplication — all handled.
MQTT, either on our hosted broker or your own. That one line opens up thousands of device models across hundreds of manufacturers.
Zigbee, bridged through MQTT — Aqara, IKEA, Sonoff, Hue, Tuya.
DIY hardware. ESP32, ESP8266, Tasmota.
Vehicle trackers. Over 2,000 models, one ingest endpoint.
The point of the architecture is that adding the next protocol doesn't mean rewriting anything. Devices, rules, dashboards, alarms and access control all sit above the connector layer and don't care what's underneath.
Every protocol we add is more of the physical world that can move onto the network without anyone rebuilding their setup.
#Chirp #IoT #DePIN
wopdiddly retweeted
🎉 THANK YOU for 200 followers on X! 🎉
To celebrate this first amazing milestone, join the second HaLoWave giveaway where you can win 1 HaLoWave Miner FOR FREE! 🎁🚀
👇 To enter, complete these 3 simple tasks:
1️⃣ Follow @HaLoWaveNetwork
2️⃣ Like & Retweet this post 🔁❤️
3️⃣ Tag 3 friends in the comments 🗣️
🔥 BONUS (Increase your chances to win!):
👾 Join the HaLoWave Discord: discord.gg/gNn3tShRsA
📸 Share a photo below in the comments of your network setup and where you would install your HaLoWave Miner! So mention your country 🌎
For example share your outdoor LoRaWAN antenna, like the one for @helium IoT, since you can reuse your LoRaWAN antenna for HaLoWave! 📡
⏳ Deadline to enter: July 18, 2026
🏆 Winner announced: July 20, 2026
Participate and join the First Global HaLow Network built on @solana! 🌍🌊
halowave.io
#DePIN #Solana #HaLoWave #HaLow #First #Global #Network #Giveaway #Miner #Free
wopdiddly retweeted
I’m not sure ITV are massively advancing the idea of women’s equality in football by having Emma Hayes give her analysis from a set which looks like she’s stuck in a kitchen?
wopdiddly retweeted
Think bigger than an app that flips a switch.
The same command that dims a light scales to thousands of streetlights across a city. The same logic that nudges a thermostat can balance the climate of an entire building — or a hundred of them.
One platform. Any device. Any scale.
wopdiddly retweeted
We know — we've said "biggest release" more than once this year. This one's so big it earned a version jump from 3.1 straight to 3.4.
Chirp 3.4.0 is live, and it takes IoT to a whole new level.
Meet the Digital Building Twin.
Any property — a home, a warehouse, a parking lot, a retail site, an apartment block, a smart-city corner — can now be drawn as a live, sensor-aware 3D model inside Chirp. Walls, doors, multiple floors, garden, driveway, gates, boom
barriers, parking bays, dumpsters, smoke detectors, water tanks, AC units. 60+ ready-to-place objects in the library.
Then wire any sensor on the network to any object on the scene. The model recolors live as readings flow:
→ Red parking bays = occupied. Green = free.
→ Amber dumpsters = filling. Red = collection-day ready.
→ Red boom barriers = down. Green = up.
→ Red rooms = over setpoint. Flashing smoke detector = tripped.
Every sensor on the Chirp network now has a spatial layer above it. Every node operator, every household, every business running on Chirp can build a live digital twin of the physical space their devices cover — and read its state at a
glance.
This is what Real-World IoT actually looks like.
Drawn from scratch, or traced from an aerial map and anchored to its real GPS coordinates.
The team shipped what was promised. More coming — but meanwhile, give it a try and let us know in the comments below if you like the direction Chirp is moving in.
→ app.chirpwireless.io
→ docs.chirpwireless.io
#DePIN #RWA #IoT #DigitalTwin #Sui #SmartCity #ChirpDeWi @SuiNetwork
wopdiddly retweeted
Japan just turned thin air into fuel.
No oil rigs. No drilling. No pipelines stretching across oceans.
Just water, CO₂, and a process that flips combustion on its head.
ENEOS Corporation, Japan's biggest oil refiner, pulled it off at their Yokohama lab.
They built a demo plant that sucks carbon dioxide straight from the atmosphere, splits hydrogen out of water using renewable energy, then fuses them through Fischer-Tropsch synthesis into liquid hydrocarbons.
The result? Real, usable synthetic petroleum.
The kicker: this fuel is "drop-in ready." That means it works in the cars you already drive, the planes already in the sky, the pipelines already in the ground. Zero modifications.
They didn't just brew it in a beaker either. They ran actual vehicles on it. It works.
Think about what that unlocks. Countries with no oil reserves could manufacture their own fuel using nothing but sunlight, wind, and the air around them.
The geopolitical chessboard would flip overnight.
Sectors that electrification can't easily touch, like aviation and heavy shipping, suddenly have a clean fuel path.
There's a catch, though. The process is hungry. The same electricity it takes to brew one liter of synthetic fuel could push an EV about 200 km down the road. ENEOS quietly shelved the project in 2025 because the economics didn't math out yet.
But the science? Proven. The blueprint exists. Someone, somewhere, will crack the cost problem.
And the day they do, the oil map of the planet gets redrawn.
Source: ENEOS Corporation / TheTownHall(.)News
























