Align
Trace one event across the available records.
Line up device logs, packet captures, RF observations, gateway records, host events, timestamps, and sequence numbers around the same event.
Coming soon · early pilot applications open
Wireless failure investigation
Understand where a wireless failure occurred.
Hermod helps teams investigate intermittent wireless failures by bringing device logs, captures, gateway records, host events, and application logs into one case. It shows what each record supports, which causes remain possible, and what to measure next.
We’re preparing an early pilot for teams working with Wi-Fi, Bluetooth/BLE, Zigbee, wireless sensors, gateways, and multi-radio products.
Use existing evidence
Trace events across layers
Choose the next measurement
One event · multiple layers
TRACE INCOMPLETE
Observed symptom
“The sensor report never reached the application.”
Hermod traces the event across the available records.
01
Device log
Report created
02
Radio / packet capture
Transmission evidence incomplete
03
Gateway
Could be lost, buffered, rejected, or delayed
04
Host / application
Timeout recorded
Hermod’s job
Show the furthest point the event can be verified, list the remaining possible causes, and recommend the next useful measurement.
The debugging problem
Wireless failures leave evidence across several layers.
A device log may show that a report was created. A packet capture may show transmission. A gateway may have only part of the record. The application may only record a timeout.
Hermod organizes these records around the same event so teams can see where the evidence ends and which causes still need to be tested.
Missing
Determine whether the packet was created, transmitted, received, or dropped later.
Delayed
Trace where latency entered the event path.
Disconnected
Reconstruct the connection sequence around the failure.
Contradictory
Compare the sniffer, gateway, host, and application records for the same event.
What we’re building
A tool for cross-layer wireless debugging.
Hermod is designed to turn scattered technical records into a structured investigation. It helps engineers trace an event, evaluate possible causes, and decide what to measure next.
Assess
Show what each record supports.
Mark verified steps, identify evidence gaps, and keep track of the causes that remain possible.
Next step
Recommend the next measurement.
Suggest the check most likely to narrow the cause or confirm where the failure occurred.
Early pilot users
We’re looking for teams debugging real wireless failures.
The pilot is for engineers and teams with an intermittent or archived failure and some combination of logs, captures, telemetry, timestamps, or test notes.
IoT product teams
Intermittent field, validation, or integration failures across connected products.
Wireless engineers
Wi-Fi, BLE, Zigbee, gateways, embedded radios, and multi-radio coexistence.
Labs & consultancies
Cases with incomplete or conflicting evidence from wireless systems.
Integration teams
Systems with device, RF, gateway, host, and application records that need to be compared.
Pilot applications
Apply for the Hermod pilot.
We’re looking for a small number of teams to bring a real intermittent wireless failure and test the first version of Hermod. We want to learn how the tool fits into real debugging work and where it needs to improve.
Pilot spots will be limited. Use the form to describe your system, the failure, the evidence you have, and how your team investigates issues today.
A strong pilot case has
- A recurring or archived wireless failure your team wants to understand.
- Some combination of logs, captures, telemetry, timestamps, or test notes.
- A team willing to use Hermod on the case and share feedback on the result.
Google Form · replace placeholder URL before launch