NBX-ETH-BAT · Preliminary
Nody Bot
Not dead yet.
Battery Ethernet phone-home for datacenter construction
Hang it on the far end of a cable run. It sleeps for most of the build, wakes on a schedule, and POSTs a heartbeat so you know the drop is still alive. No PoE, and nothing left pingable.
Nody Bot at a glance
- Check-in interval
- ~15min
- Wakes on a timer; interval is configurable
- Collector timeout
- 8s
- Waits for an HTTP 2xx confirmation
- Attempts per check-in
- up to3
- Then back to deep sleep
- Provisioning
- USB
- Bench setup with
etctl
Preliminary specifications. Subject to change before commercial availability.
How it works
Sleep. Wake. Prove it. Sleep.
Built for multi-month cable plant builds, not always-on monitoring. One cycle, repeated for the life of the build.
-
Step 1 of 5
Wake
A timer fires about every 15 minutes. Between wakes the radio and MCU are off, with no listeners, so the battery lasts the build schedule.
-
Step 2 of 5
DHCP
Wired Ethernet comes up on the W5500 and the module obtains an address on the plant network.
-
Step 3 of 5
POST
A JSON heartbeat with unit id, battery, MAC and more is POSTed to
/et/phone-homeon your collector. The server is set as an IPv4 address; the device does no DNS lookup. -
Step 4 of 5
2xx
The unit waits for an HTTP 2xx from the collector, with an 8-second timeout and up to three tries.
-
Step 5 of 5
Sleep
It returns to deep sleep until the next wake. Nothing listens in between, so it is never pingable.
Why Nody Bot
Proof it’s alive when the plant isn’t finished.
During AI and HPC hall construction, cable drops sit unfinished for months. You need to know they still work, without leaving something pingable on an incomplete network and without PoE at the far end.
-
Not pingable by design
Deep sleep between wakes. No ICMP, and no open ports waiting for scans on an unfinished plant.
-
Months on battery
LiPo power, not PoE, so the far end works before power distribution is ready.
-
Your collector
Heartbeats POST to your endpoint. This site is marketing; collector and operations software ships separately.
Who it’s for
- Datacenter construction and cable verification crews
- Commissioning teams that need live confirmation across hundreds of drops
- Integrators building AI and HPC halls on multi-month plant schedules
Hardware
| Product / SKU | Nody Bot, NBX-ETH-BAT |
|---|---|
| Microcontroller | ESP32 |
| Ethernet | W5500 wired Ethernet (no Wi-Fi dependency in the plant) |
| Display | OLED: unit id, battery voltage, last confirmation |
| Power | LiPo battery (not PoE) |
Network behaviour
| Wake interval | ~15 minutes (configurable) |
|---|---|
| Reachability | Outbound HTTP POST only; not ICMP-pingable |
| Heartbeat payload | JSON status to customer collector endpoint |
| Endpoint | POST /et/phone-home |
| Confirmation | HTTP 2xx; 8 s timeout, up to 3 tries |
| Server address | IPv4 address (no DNS) |
Deployment
| Provisioning | USB + etctl (no mobile apps) |
|---|---|
| Deployment | Far end of cable runs during datacenter construction |
| Operating intent | Multi-month build schedules; deep sleep between wake windows |
Provisioning
Configured over USB with etctl.
Units are set up on the bench before they reach the plant. The product surface is this website and the hardware device.
- Bench
Set the collector address (IPv4), unit identity and wake interval
- Verify
Verify battery and Ethernet bring-up on the bench
- Ship
Ship configured modules to the far-end install crew
What ships
The Nody Bot module (ESP32, W5500, OLED, LiPo) and the USB provisioning path. The collector backend is separate.
Contact
Ready for a build or pilot?
Ask about Nody Bot availability, datasheets, or a custom design engagement from ESSIMPLEX.
The address above is a placeholder until the production inbox is set up. You can also open a note on GitHub.