How to Set Up Holy Stone HS720E
By Sai Kiran Pandrala · reviewed by Sai Kiran Pandrala, Editor Last verified: 2026-05-30
| Brand | Holy Stone |
|---|---|
| Model | HS720E |
| Category | Drones |
| Guide type | Setup |
| Skill level | Beginner to intermediate |
How to set it up
- Charge the drone + remote + smartphone fully.
- Update Holy Stone app + drone firmware on a phone connected to Wi-Fi.
- Calibrate compass + IMU per the app prompts.
- Register the drone with your civil aviation authority (FAA / DGCA / EASA).
- Check the no-fly zone map for your launch site.
- Take off in an open area , first flight no higher than 30 m / 100 ft.
- Verify Return-To-Home behaves correctly before doing anything ambitious.
Pitfalls to dodge
- Always verify the model + revision before applying any procedure.
- Use OEM parts where the manual calls for OEM.
- Document everything you do , particularly on warranty-eligible devices.
- If a step requires opening a sealed unit, check warranty implications first.
Frequently asked questions
Will this exact procedure work on my unit?
The procedure reflects current Holy Stone HS720E behaviour as of 2026-05-30. Always cross-check with the official manual for your model revision.
Where do I get official support?
Visit the Holy Stone official support portal and search for your model number + serial number.
Is this DIY-safe?
Yes for the steps above; some advanced fixes require service centre tools.
Does this affect my warranty?
Anything beyond cleaning, software update, and consumables replacement typically requires the Holy Stone authorised service centre to preserve warranty.
Related guides
- All Drones guides → /devices/section/drones.html
- All device categories → /devices/
Related fixes
Related guides worth a look while you sort this one out:
- How to Fix Holy Stone HS720E
- How to Troubleshoot Holy Stone HS720E
- How to Use Holy Stone HS720E
- How to Set Up Holy Stone HS720G
- Autel Robotics vs Holy Stone: Which Drones to Buy
- DJI vs Holy Stone: Which Drones to Buy
References
- Holy Stone official support portal (search 'Holy Stone HS720E')
- Holy Stone user manual (download PDF from the support portal)
- Community forums + manufacturer repair guides (where applicable)
Reference material, not professional advice. Validate with your manufacturer manual and follow local regulations.
Identify
When this symptom shows up on the device in front of you, three patterns repeat:
1. Recent firmware update changed behavior — the symptom started within a week of an OTA push. Rollback or wait for the hotfix. 2. Environmental trigger. temperature, humidity, line voltage, network changes. Look at what changed in the environment. 3. Cumulative wear, components like batteries, gaskets, fans degrade over time. Replace the consumable rather than chasing a software fix.
Knowing which pattern applies saves time on the wrong fix.
Safety + preconditions
Before any work on the device in front of you:
- Unplug from mains for any internal-access procedure.
- Discharge stored energy (capacitors in PSUs, residual battery charge) per manufacturer guidance.
- Use ESD-safe handling for boards and modules: no carpet, no wool sleeves.
- Avoid moisture; never apply liquids near vents or connectors.
- If you smell smoke, see scorch marks, or feel uneven heat, stop and escalate.
Validate
After applying the fix on your hardware, confirm:
- The original symptom is no longer reproducible.
- Related features (status LEDs, app sync, paired accessories) still work.
- The device responds to a soft reboot without the fault returning.
- Any error codes that were on display have cleared.
- Documentation (your service log, the brand companion app) reflects the change.
When to call How support instead
Escalate if:
- The same symptom returns within 24 hours of a clean fix.
- You see physical damage (burn marks, swollen battery, cracked PCB).
- The device is in warranty and a hardware replacement is the cheaper outcome.
- Repair requires specialised tools you don't own (alignment jigs, calibration software).
- Following the official path keeps the warranty intact, which matters more than the time spent.
More frequently asked questions
Will the procedure work on the international variant?
Some features and firmware paths are region-locked. Check the model spec sheet to confirm your variant supports the menu option referenced. If you're outside the US/EU, look for the regional support portal.
Can I roll this back if something breaks?
Yes for software-level changes (firmware rollback, config rollback). Hardware changes are usually one-way. Always back up settings before starting.
Will this void my warranty?
Applying official firmware updates and following the user manual will not affect warranty. Opening sealed components, jumping safety circuits, or using third-party parts can void warranty in most jurisdictions.
Does this affect other devices on my network?
Generally no. The procedure is local to this device. Network-side changes (firmware updates that affect TLS, SMB, or routing) are flagged explicitly in the steps.
Is it safe to apply during business hours?
If the device is in production use, apply during a scheduled maintenance window. Most procedures need 2-15 minutes of downtime. Capture pre-change state so you can roll back if needed.
Field notes from real Drones incidents
When I work on Set Up Holy Stone HS720E the rhythm I lean on is the one I have built over years of these tickets. Drone misbehaviour after a firmware update is real and frequent, I never push aircraft + remote firmware on the same day a flight is planned. Single-cell voltage divergence is the earliest warning a flight pack is failing; the app's percentage display is too coarse to catch it.
Tools I actually reach for
For Set Up Holy Stone HS720E on Holy Stone the cheapest signal I can land usually comes from GPS log download (DAT / TXT), then Battery cell-voltage reader, Companion app diagnostics, RC transmitter calibration menu when GPS log download (DAT / TXT) cannot see the layer the fault sits in, and Manufacturer flight controller utility for the cases where neither of those answers cleanly. That ordering is not academic. It matches the layers the failure tends to surface through, so the cheap signal lands first and the heavier tooling only comes out when the simpler answer does not hold up under scrutiny.
Verification I run before I close the ticket
Before I mark Set Up Holy Stone HS720E resolved on a Holy Stone unit, the verification loop below is what I actually run. Each step proves a different layer is green, and the order matters - the cheap checks gate the more expensive ones.
Hover test in P-mode at 2 m for 30 seconds before any aggressive flightIf that one comes back clean, move to the next check. If it does not, stop and dig in there before layering more verification on top of a red signal.
IMU and compass calibration on a non-magnetic surfaceIf that one comes back clean, move to the next check. If it does not, stop and dig in there before layering more verification on top of a red signal.
Firmware version check on aircraft, remote, and batteryOnly when every line above runs clean do I close the ticket and update the runbook with the timestamps.
Where I check first when the docs disagree
When two sources contradict each other on a Drones detail, the disambiguation order I lean on is stable. I usually start at manufacturer firmware archive for the ground-truth view on Drones. I usually start at manufacturer support portal for the ground-truth view on Drones. I usually start at FAA / DGCA notices for the airframe class for the ground-truth view on Drones. Random blog posts and reseller wikis are signal, not ground truth, and I treat them as such until the references above either confirm or contradict the claim.
Pitfalls I have walked into on this exact path
The shortcuts that look smart on Set Up Holy Stone HS720E have a habit of biting back. The pitfalls below are the ones I have personally walked into on a Holy Stone unit, not things I read about. Single-cell voltage divergence is the earliest warning a flight pack is failing; the app's percentage display is too coarse to catch it. Drone misbehaviour after a firmware update is real and frequent. I never push aircraft + remote firmware on the same day a flight is planned. When in doubt I revert to the slower path that the manual prescribes - the time I save by skipping it is always smaller than the time I spend cleaning up afterwards.
What I tell the next on-call
When I hand Set Up Holy Stone HS720E off to the next person on rotation, the three lines I leave in the runbook are these. First, the symptom signature for Holy Stone on the Drones family - not a paraphrase, the exact string that surfaces. Second, the diagnostic that gave the highest signal in the least time. Third, the exact verification command whose green output justified closing the ticket. That trio is what turns a one-off fix into a runbook entry the next engineer can use without paging me at three in the morning.
I also add a one-line note on the cost of getting this wrong. For Set Up Holy Stone HS720E on a Holy Stone unit, the cost is rarely the replacement part. It is the downtime, the second site visit, and the trust deficit you spend with whoever owns the asset when the fix does not hold. That framing keeps the next on-call from choosing the cheap-looking shortcut that ends up costing the most in elapsed hours and goodwill.