More room on older hubs
Hubs that were running short on storage get room back during the update. Every paired device, action, port setting and schedule comes through unchanged.
FrightLink updates
Every FrightLink release, newest first: what changed, what got fixed and how to update your hub, Ghosts and Executioners. Updates install from the FrightMaps app, and your paired devices and settings come along.
How to update
Install FrightMaps 5.2.6 or later from the App Store or Google Play. The hub update only appears in 5.2.6.
In FrightMaps, go to More → Haunter tools → FrightLink and open your hub. On the Firmware Update Available card, tap Update Now. You can also use Update firmware in the hub's ⋮ menu.
Keep your phone near the hub. The hub downloads the update, restarts and checks itself before the app shows Update verified, usually in about a minute. Your paired devices, actions, port settings and schedules stay exactly as they were.
On the hub page, tap ⋮ next to each Executioner and choose Update Firmware. Keep it powered until it finishes.
No Ghost update this time: Ghosts stay on 1.0.13.
What changed
Hubs that were running short on storage get room back during the update. Every paired device, action, port setting and schedule comes through unchanged.
A 1-second wait between actions now takes 1 second. On the old firmware it could stretch to about a second and a half, which threw off timed scenes.
Firing a prop from the Remote over the internet now lands in about a second. On the old firmware the first fire could take up to 10 seconds.
The hub keeps far more memory free while it's connected to the internet. In our testing it ran overnight, connected to the cloud with a phone attached, without a single restart.
Executioners now report their firmware version every time they fire, so the app keeps showing which version each one runs instead of going blank.
5.2.6 is the app version that offers and installs the new hub firmware.
Your venue's time zone is set reliably after you connect to your hub, so sleep windows and schedules follow local time.
The Android app does far less background work on the map and FrightLink screens, so taps respond right away.
Known issues
After a one-time timer fires, its row can keep showing as upcoming. The timer did run. You can delete the row.
If an Executioner is unplugged or out of range, the hub page's Last Event card can still list it as fired. The Activity list shows the real result: “Prop controller didn't respond.”
Need a hand?
Tell us your hub's name and what the app shows, and we'll walk you through it.