Provision boards and see live telemetry in minutes
Sign in to return to HaLow Flasher. Having trouble? Use the Use Auth Key tab in the desktop app instead.
Already have an account?
By signing in or creating an account, you agree to our and .
Setup Guide
Watch the 5-minute guide or follow the steps. You get live radio, sensor readings, photos, and more from the EVK on HaLow Cloud.
Set up your Pace Wireless account for your boards and private dashboard.
After signing in, download the cross-platform flasher app for your computer.
Connect your EVK by USB. The app guides firmware installation, device setup, and joining your HaLow network.
See live readings, move the board, and capture a photo to validate the device-to-cloud path.
Starting Point
Bring an EVK, an internet-connected HaLow network, and a computer. Pace provides the firmware, flasher application, and cloud dashboard.
Use the onboard temperature, humidity, and motion sensors plus the installed OV5640 camera.
Available at Mouser
One option for your connection. Any compatible Wi-Fi HaLow network or access point connected to the internet will work.
Available at MouserDownload the HaLow Flasher Application on your computer to set up the EVK over USB.
Sign In to Download HaLow Flasher App
HaLow Flasher
Returning to HaLow Flasher…
Having trouble getting the app to open automatically?
Pace Wireless LLC Policies & Disclaimers
These Terms of Use ("Terms") constitute a legally binding agreement between you ("User", "you", or "your") and Pace Wireless LLC ("Pace Wireless", "we", "us", or "our"), governing your access to and use of the HaLow Portal (halow.pacewirelessllc.com), cloud telemetry APIs, MQTT endpoints, notification services, firmware builds, device management utilities, and desktop flasher applications (including HaLow Flasher) (collectively, the "Services").
BY CREATING AN ACCOUNT, ACCESSING THE PORTAL, PROVISIONING OR FLASHING HARDWARE WITH OUR PLATFORM, CONNECTING A COMPATIBLE WI-FI HALOW (IEEE 802.11ah) DEVICE, OR USING ANY PORTION OF THE SERVICES, YOU AGREE TO BE BOUND BY THESE TERMS.
Use of the Services is also subject to our Privacy Policy, including Google Analytics measurement of landing-page and dashboard usage.
To access protected platform features and register sensor or actuator hardware, you must register for an account. You agree to provide accurate information, maintain password confidentiality, keep your Auth Key secure, and be solely responsible for all activities and device commands issued under your account. Notify Pace Wireless LLC immediately upon any suspected breach.
Pace Wireless LLC provides downloadable firmware images, reference applications, and flashing utilities (including the HaLow Flasher desktop application) to configure compatible development boards.
Flashing firmware involves low-level serial (UART/USB) communications, bootloader manipulation, and memory writes. Flashing firmware carries inherent operational risks including device bricking, memory corruption, electrical failure, or hardware damage. PACE WIRELESS LLC IS NOT LIABLE FOR BRICKED OR DAMAGED HARDWARE. YOU EXECUTE ALL FLASHING ENTIRELY AT YOUR OWN RISK.
Certain hardware configurations are controllable (power outlets, relays, smart locks, gate controllers) and accept remote cloud-to-device commands. You are solely responsible for physical safety and ensuring remote actuation does not cause fire, injury, or property damage. Public network and wireless command latency may occur; do not rely on remote commands for emergency operations. Physical equipment must include manual safety stops and physical interlocks.
THE SERVICES AND FIRMWARE ARE NOT DESIGNED OR CERTIFIED FOR HIGH-RISK OR LIFE-SAFETY APPLICATIONS. You shall not use the Services in connection with medical/life-support devices, emergency 911 dispatch, nuclear or chemical facilities, aviation, or any system where service failure could lead to death, injury, or catastrophic damage.
Wi-Fi HaLow (IEEE 802.11ah) sub-GHz RF performance, range, RSSI, SNR, and data integrity are subject to physical obstacles, terrain, antenna placement, and interference. Telemetry is provided on an "as is" basis without guarantee of continuous or error-free transmission. Telemetry retention follows our rolling 30-day downsampled cloud storage policy.
You agree not to reverse engineer backend services, flood or DoS API endpoints or MQTT brokers, bypass account authorization, inject spoofed telemetry, or transmit malicious code through the platform.
All software, portals, UI designs, APIs, logos, and firmware frameworks are the exclusive property of Pace Wireless LLC and protected by applicable copyright, trademark, and trade secret laws.
THE SERVICES ARE PROVIDED "AS IS" AND "AS AVAILABLE" WITHOUT WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, AND NON-INFRINGEMENT.
TO THE MAXIMUM EXTENT PERMITTED BY LAW, PACE WIRELESS LLC SHALL NOT BE LIABLE FOR ANY INDIRECT, INCIDENTAL, CONSEQUENTIAL, SPECIAL, PUNITIVE, OR PROPERTY DAMAGES. TOTAL AGGREGATE LIABILITY SHALL NOT EXCEED THE GREATER OF FEES PAID BY YOU IN THE PRECEDING 12 MONTHS OR $100.00 USD.
You agree to indemnify and hold harmless Pace Wireless LLC, its officers, employees, and agents from any claims, damages, liabilities, and expenses arising from your use of the Services, hardware deployments, or violation of these Terms.
These Terms are governed by the laws of the United States. For inquiries, contact Pace Wireless LLC at support@pacewirelessllc.com.
Pace Wireless LLC respects your privacy and is committed to protecting the personal information and device telemetry processed through our Wi-Fi HaLow developer platform, portal, cloud APIs, and utilities.
We process collected data exclusively to operate the dashboard, route telemetry, execute remote commands, deliver requested push notifications, provide firmware updates, and maintain platform security.
Pace Wireless LLC does NOT sell, rent, monetize, or trade your personal information, email addresses, or device telemetry to third-party data brokers or advertising networks under any circumstances.
All transmissions use Transport Layer Security (TLS 1.3 / HTTPS / MQTTS). Authenticated telemetry samples are stored in PostgreSQL schemas strictly scoped by account owner and device ID. Trend history is retained for a rolling 30-day period with database downsampling.
We work with essential cloud infrastructure providers (secure database hosting, transactional email delivery, browser push gateways) and Google Analytics 4 for product measurement. We do not enable Google advertising features, Google Signals, or ad pixels.
We use browser localStorage for operational session management (halow_jwt, halow_user, halow_selected_device, halow_last_email). Google Analytics 4 sets first-party _ga cookies to measure landing-page and dashboard usage. We do not send email addresses, Auth Keys, or device identifiers to Analytics. Browsers that send Global Privacy Control (GPC) do not grant analytics storage. See the full Privacy Policy for details.
You can regenerate your Auth Key, rename/reorder/delete registered devices, adjust notification preferences, or request full account deletion by contacting support@pacewirelessllc.com.
For privacy inquiries, contact Pace Wireless LLC at support@pacewirelessllc.com.
Point or touch the plot to inspect a reading. Use the controls, drag the timeline, or press +/− and ←/→. Ctrl/⌘ + wheel zooms. Press Esc to return to the dashboard.
Attic and Alert Preferences
These values control both the Active Alerts shown on this board and its environmental notifications. Pace evaluates each new cloud sample, notifies only when a condition changes, and sends a recovery after the reading moves safely back into range. Settings are private to your account and this device, while delivery destinations remain configurable in Notification Settings.
HVAC Alert Rules
Pace evaluates each cloud sample and emits a notification only when CO₂, PM2.5, or PM10 crosses its configured high limit. A recovery is emitted after the reading clears the limit with hysteresis. These settings belong to your account and this board.
Active boards appear first. Edit order in .
Loading your boards…
Flash and provision long-range HaLow boards with the desktop companion. When your board connects to HaLow and MQTT, live telemetry and controls appear here automatically.
Showing last known sample. Board is offline or not reporting.
Device
Customize Layout
Drag modules or focus a handle and press Arrow Up / Arrow Down to reorder. Toggle visibility with the checkbox. Tab moves between controls.
RSSI follows received AP traffic. Scan SNR and noise floor refresh on the associated primary channel about every 15 seconds; their age stays visible if a scan is delayed. Recent TX MCS uses a 20-second evidence window so a single rate-control probe cannot move the headline value.
Live readings from the MM8108-EKH05 Eval Board
Browse snapshots from this board. Photos are deleted from the database after seven days.
Current environmental readings from attached sensors.
Primary HTU31D sensing, onboard SHT40 comparison, and OPT3005 ambient light.
Attic Status
A valid primary climate reading is required.
Alerts and Notification Status
Primary and onboard comparison data over the selected range.
No samples loaded.
| Received | Primary Temp | Primary RH | Onboard Temp | Onboard RH | Ambient | RSSI |
|---|---|---|---|---|---|---|
| No History Yet | ||||||
Readings are retained for 30 days. Use the page controls to browse every sample or export the complete selected range as CSV.
Live SCD41 CO₂ and SPS30 particle readings delivered through the Pace HaLow cloud.
Alerts and Notification Status
Climate, particle distribution, and optional experimental raw SGP41 signals.
Database-downsampled charts from retained owner/device history.
No samples loaded.
| Received | CO₂ | PM2.5 | PM10 | Particle AQI | Temp | RSSI |
|---|---|---|---|---|---|---|
| No History Yet | ||||||
Readings are retained for 30 days. Page through every retained sample or export the complete selected range as CSV.
Monitor gate position, movement, and percentage open over Wi-Fi HaLow.
Live door, light and mail state from the board.
--
--
Close the mailbox and keep it still, then choose Calibrate Closed. The Accel 5 Click must move with the downward-opening door.
--
Newest door, movement, mail, and sensor events for this board.
| Received | Event | Door | Light | RSSI | Evidence |
|---|---|---|---|---|---|
| No Activity Yet | |||||
Live leak state from the Water Detect sensor.
--
--
Newest leak and recovery events for this board.
| Received | Event | Water | Link | RSSI |
|---|---|---|---|---|
| No water events yet | ||||
Live presence and filtered range from the RADAR module.
60 GHz-class field · MM5D91-00
Waiting for RADAR
Live presence and filtered range from RADAR_001.
Range is filtered with a five-reading median. Presence clears only after three continuous clear seconds.
Loading recent range readings…
| Received | Event | Range | RSSI |
|---|---|---|---|
| No presence transitions yet | |||
No samples loaded.
| Received | State | Distance | Accuracy | Direction | RSSI |
|---|---|---|---|---|---|
| No History Yet | |||||
Cloud history keeps presence and fault changes plus about one sample per minute for 30 days, scoped to your account and this board. Live 1-second MQTT still updates the gauges. Charts are database-downsampled; tables and CSV keep every retained sample.
Estimated Direction is inferred from consecutive range readings; this sensor does not report target angle or identity.
Automatically detected PIR 3 / PIR 4 motion sensing with inferred presence and retained history.
— Events
No motion recorded— Events
No motion recordedPresence is inferred from recent motion; the released profile clears after two minutes without motion.
Each zone has its own count scale. Dashed lines show its current trigger threshold. These are reported samples, not a continuous 100 Hz waveform.
Signed Signal (Counts)
Time Ago (Seconds)
Signal: — counts
Waiting for signal
Signed Signal (Counts)
Time Ago (Seconds)
Signal: — counts
Waiting for signal
State changes and one-minute health samples retained for 30 days.
Loading history…
| Time | Motion | Presence | Fusion | Zone Events |
|---|---|---|---|---|
| Loading retained samples… | ||||
Acquisition health and detector decisions.
Detection Profile: —
Searching for supported sensors…
Live sensor output over HaLow. Only detected sensors appear below.
Targets up to 4 updates per second. Frame age and valid measurements show whether each sensor is delivering usable output.
Detecting thermal hardware…
Move a warm hand or object across the field of view. Watch the warm pixels move and compare their temperatures with the background.
Waiting for sensor diagnostics.
Detecting lidar hardware…
Move a flat target closer, farther, and across the field of view. Watch the nearest distance and affected zones change.
Waiting for sensor diagnostics.
Thermal color with LiDAR zone outlines. Brighter, thicker borders indicate closer returns.
Uses the thermal color range, smoothing, and each sensor's mirror setting above. Array positions are aligned for display; different fields of view mean this is a relative overlay.
Live motion energy and detection state.
24.1 GHz Doppler field · PD-V12
Waiting for RADAR
Live motion energy from RADAR_002.
Motion Energy is comparable over time after quiet-scene calibration. RADAR_002 does not report target distance, direction, angle, speed, or identity.
Loading recent energy readings…
X-axisWhen each telemetry sample reached the dashboard, shown in your local time. Read left to right from oldest to newest.
Y-axisMotion Energy in ADC counts. The dashed orange line is the configured detection threshold.
| Received | Event | Energy | RSSI |
|---|---|---|---|
| No motion transitions yet | |||
No samples loaded.
| Received | State | Energy | Raw ADC | Baseline | RSSI |
|---|---|---|---|---|---|
| No History Yet | |||||
Cloud history keeps motion and fault changes plus about one sample per minute for 30 days, scoped to your account and this board. Live 1-second MQTT still updates the gauges. Charts are database-downsampled; tables and CSV keep every retained sample.
Stationary people may disappear from a Doppler sensor. Fans, vibration, moving machinery, vegetation, rain, traffic, and motion through nonmetal walls can cause activity.
Bench relay outputs, cycle pulse and timed hold-open.
Bench Commissioning
Waiting for controller
Relay outputs must remain disconnected from the gate during bench validation.
Position, satellite quality, and movement
Awaiting first sample
Your tracker’s route and HaLow signal
Your saved trail and map view will appear here.
Live readings from this tracker
Get your tracker ready, then start recording a walk.
Take the tracker outside with a clear view of the sky.
Apply your choice and wait for the tracker to confirm.
Received measurements become your route.
Awaiting reporting settings
Start a walk once the tracker is ready.
Start with your main access point to measure how far you walk from it. Have extenders? Add their locations too.
Choose the connection belonging to this device. Its name will appear in new walks and older walks that recorded this connection. You can do this later.
Find the HaLow AP interface address in its device dashboard.
Keep your HaLow router powered and connected to the internet. Take the battery-powered tracker outside and wait for a GPS fix and fresh telemetry. Open this dashboard on your phone using cellular data.
With one access point, save its location as Main Access Point. This is the starting reference for distance measurements. If your network also has extenders or repeaters, add a named location for each, such as Extender 1. Identify each location after adding extenders so distances and saved ranges follow the connected access point. Move an existing extender location before each walk if you relocate it; saved walks keep their original locations. Adding a map location does not configure a repeater.
Choose Range Test, tap Apply Mode, and wait for the board to confirm. Reports arrive every second while connected. Optionally clear breadcrumbs for a fresh visible trail; saved history is kept. When Start Walk becomes available, tap it.
Walk away from the router with the tracker. Keep its antenna orientation consistent for a fair comparison. Watch the live status and signal readings; breadcrumbs mark locations received by the cloud.
If reports stop, note the location and walk back toward the router. Watch for fresh telemetry to resume. The marker shows the last received location, not your current position while disconnected. Missing portions of the route are not filled in later.
When you return, tap End & Save Walk above the map. Choose a walk name and tap Save Walk, or tap Use Default Name to skip naming. Once saved, the tracker returns to Adaptive Mode; the portal shows when the board confirms it. Open it to inspect recorded signal measurements, view Estimated Coverage, or export the complete archive. If saving fails, your draft stays in this browser so you can retry Save Walk. In Inspect Points, Previous Gap and Next Gap move between reporting pauses.
A gap is a pause between received reports. It may reflect HaLow range, power, or internet loss. It does not prove a radio coverage boundary. Repeat the route with the same setup to compare results.
Loading saved walks…
Record a range walk to revisit its route and signal measurements. Saved walks stay available after live history expires.
Review the name and time range, then save your route.
Name your finished walk, or use the default date and time name. Saving also returns the tracker to Adaptive Mode.
Saved walks have no expiry and are stored for your account and board until you delete the walk, board, or account. The seven-day limit applies only to live history. Up to 50 walks per board, 12 hours each. Times use this device’s local time.
Only received measurements are shown. Telemetry gaps can reflect radio, power, or Internet loss; the disconnected route is unknown.
Color By changes which recorded radio measurement colors the points or heatmap. It does not change the tracker’s radio settings. Red/orange represents lower values; green/blue represents higher values. Read the legend for the selected metric’s scale.
Why They Can Differ: RSSI follows received traffic, Scan SNR refreshes through periodic scans, and TX MCS summarizes a recent 20-second transmit window. They describe different directions and moments. Scan SNR is not calculated from the current RSSI tile.
Reading Saved Walks: Colors use the readings stored with each GPS sample. Scan SNR and TX MCS older than 45 seconds at that sample are excluded from the color estimate. Gray points indicate an unavailable metric. In Circular Range, brighter areas interpolate between nearby measurements on the same access point; faint areas extend the radius estimate into untested directions. Overlaps favor measured areas without stacking brightness. Interpolated and circular heatmaps estimate unmeasured areas; their colors do not confirm a working connection there.
Connected To Unknown Access Point
Select a map point or move through the timeline to inspect recorded measurements.
Event times are estimated from device uptime and cloud receipt. AP markers show the first received fix after an observed change, not an exact handoff position.
Awaiting map
Live telemetry history · retained for seven days
Loading history...
| Time | GPS State | Latitude | Longitude | Speed | RSSI | Mode | Movement | Connected AP | From Connected AP | AP Distances |
|---|
Receiver health and measurement freshness
HDOP and VDOP describe satellite geometry; they are not an accuracy measurement in meters. Course over ground describes travel direction.
