Fidra Config App — Web App Manual

Remote management over the cloud

This manual covers the Fidra Config App — the web app for managing your Fidra devices remotely: signing in, registering a device, changing its settings, managing who may use it, and reading its activity. Anything specific to a particular device — how to install it, power it, bring it online, and its own controls — lives in that device's own manual (for example, the GATE ONE 4G manual).

What You Need

A Fidra Config App account — free to create with an email address (see Your Account below).
A Fidra device that you own — set up and connected to the cloud as described in its own manual. To register it here you'll need its serial number (on the device label) and the ability to confirm you hold it (see Registering a Device).
The device connected to the cloud. The app works entirely over the cloud, so it can only see or change a device that's currently connected. See Connecting to Your Device — this is the single most important thing to understand about the app.

Connecting to Your Device — read this first

The app talks to your device over the cloud, so it can only see or change a device that is connected to the cloud at that moment. To save power and data, the GATE ONE 4G keeps its cloud connection off by default and comes online only on demand.

To bring it online, the owner texts this command to the device's SIM number (from the owner's phone):

X.EnableCloud

The device connects for about 30 minutes, then disconnects on its own — there's nothing to remember to turn off. Send it again whenever you need the app. (The full details of this command are in the GATE ONE 4G Device Manual → Cloud Connectivity; other Fidra devices may connect a different way, so check that device's own manual.)

Every time you use the app:

Bring the device online — text X.EnableCloud to it.
In the app, open the device (or press Refresh) until it shows Online.
Do what you need, and Publish any changes before it disconnects.

⚠ "Offline" is normal, not a fault. A device shows Offline whenever it isn't currently connected to the cloud. Text X.EnableCloud and it turns Online; after ~30 minutes it returns to Offline on its own.

Your Account

The whole app sits behind a sign-in screen. On it you'll see the Fidra logo, "Fidra Config App", and two tabs: Sign In and Create Account.

Create an account

Select the Create Account tab.
Enter your Email, a Password, and Confirm Password, then press Create Account.
We email you a confirmation code. Type it on the Confirm screen and press Confirm to activate the account.

Sign in and out

On the Sign In tab, enter your Email and Password and press Sign in.
Forgot your password? Use the Forgot your password? link — you'll reset it with an emailed code.
To sign out, use the Sign out button at the top-right of every screen.

The top bar is always visible: the Fidra logo at the top-left returns you to My devices at any time, and next to Sign out there's a light/dark theme toggle.

Registering a Device

Registering links a device to your account. It proves you hold the device: the app gives you a code, and you send that code to the device.

Before you begin, bring the device online — text X.EnableCloud to it (see Connecting to Your Device). Registration only works while the device is connected.

On My devices, press Register device (the + button, top-right). If you have no devices yet, the empty screen ("No devices yet") has its own Register device button.
Step 1 — Serial. In the Serial number field, enter the device's serial number (e.g. 3ALHBYRUW5TQGA1H2J) and press Register.
Step 2 — Claim code. The app shows exactly what to send — a line like X.Claim:123456 — and a 5-minute countdown. Press Copy claim code and text it to your device's SIM number, just as the app instructs. This proves you physically hold the device. Keep the page open; it detects the confirmation automatically.
Step 3 — Done. When the device confirms, your new device appears on My devices.

Finding the serial number. It's printed on a sticker on the device, which also carries a QR code holding the same serial. So you have two ways to enter it: read the serial and type it in, or scan the QR code with your phone's camera and enter what it gives you — both are the exact same value.

To…	Do
Start registering	My devices → Register device
Enter the device	Type the Serial number → Register
Prove you hold it	Text the app's `X.Claim:…` line to your device
Get a fresh code	On the timeout screen, press Try again

Two clocks are running: the ~30-minute cloud window (from X.EnableCloud) and the 5-minute claim-code ring. Text the X.Claim:… line before the ring reaches 0:00, and while the device is still connected. Try again always makes a new code; any earlier code stops working.

If it times out ("We didn't hear from the device in time"): the device probably wasn't connected, or the code expired. Re-send X.EnableCloud, press Try again for a fresh code, and text the X.Claim:… line promptly. A device already registered to you reports "This device is already registered to your account."; a device owned by someone else simply times out (the app never reveals who owns a device).

The "My devices" Screen

This is your home screen after signing in — every device registered to your account, one card each.

Each card shows, top to bottom:

The device's name.
Type (device model) and Serial number.
A status badge — Online (green, reachable now), Offline (red), or Refreshing… (grey), with a four-bar signal indicator inside it for devices on a mobile connection.
A Refresh button.

The badge updates by itself while you have this screen open — turn a device on and it goes Online within a second or two, without touching anything. The signal bars only appear when the reading is recent; on a device you haven't heard from in a while the bars stay hidden until it reports again.

Action	How
Open a device to manage it	Tap the card
Re-check one device live	Press its Refresh button
Add another device	Register device (top-right)
Reload the whole list after an error	Retry (in the red banner)

Filtering by type. Above the list, the Type filter lets you show All devices or just one device type — most useful once you have devices of more than one type.

Refresh re-checks a single device over the cloud — its name, signal and Online/Offline status. While any refresh runs, the Refresh buttons briefly grey out; that's normal. Leaving the list and returning after ~30 seconds also triggers a fresh scan (a quick there-and-back reuses the last scan so it feels instant).

A device that has never been reached shows "Name unavailable" and "Signal unknown" until it answers once. A reached device with no name set shows "Unnamed device".

Opening a Device: the Detail Page

Tapping a card opens that device's page. At the top you'll see its name (with a pencil to rename), its Serial / Type / Registered date / Firmware, and two status badges:

Portal — your browser's own connection to the cloud (Connecting / Connected / Disconnected).
Device — whether the device itself is reachable right now (Online / Offline / Unknown / Unavailable). Unavailable means the device is connected but needs a certificate update before it will accept settings — see Troubleshooting.

The device needs to be Online for a read or a change to actually reach it, but the buttons stay usable either way: press one and you'll be told plainly if the device didn't answer.

Loading the configuration

Under Configuration, press Load config to read the device's current settings. After that the button reads Refresh config, with a "Settings last read … ago" note under it telling you how old what you're looking at is. On a fresh page the config usually loads by itself and is remembered in your browser, so it's often already there.

Refresh config never touches your unpublished edits. It asks the device what it currently has; if you've changed something and not published it yet, your version stays exactly as you left it.

Refresh config, Publish config and Load logs stay usable while the device shows Offline. If you press one and the device doesn't answer, you'll see "Your device is offline." To reach it, text X.EnableCloud to the device (see Connecting to Your Device).

How Saving Works: Draft → Publish → Verified

The app never changes the device the instant you edit a field. Your edits are kept in your browser as a draft — you'll see an amber line such as "2 unpublished changes — saved in this browser, not yet on the device." They reach the device only when you press Publish config.

That line carries two buttons:

Button	What it does
Show changes	Lists exactly what you've altered, so you can check before publishing
Discard edits	Throws your edits away and puts the editor back to what the device last reported

Discard edits never contacts the device, so it works even when the device is Offline. It asks you to confirm first, and lists what you're about to lose.

Publishing shows a change review listing exactly what will change, then sends it. The status line walks through "Config accepted by device. Verifying…" → "Config published and verified on the device."

⚠ Publishing replaces the device's entire configuration with your draft — all of its settings are sent together, not one change at a time. This is why you must Load the config before editing: publishing a draft that's missing something would reset it. (The app guards against this — an incomplete imported file blocks Publish with a "re-read the device configuration" message.)

If the device's settings changed elsewhere since you loaded them, a banner "The device's configuration changed since you loaded it — Review & refresh" appears, and the confirmation warns you that publishing overwrites those newer settings. Review before overwriting.

Device Settings

Found in the Configuration panel. Which settings a device has depends on its type — the app shows the controls that device supports. For a gate-opener (like the GATE ONE 4G), the settings are:

Setting	What it does	Notes
On time (seconds)	How long the output stays active per trigger	Whole seconds, 1–30. A blank/invalid box reverts to the device's value.
Open to everyone	Opens the gate for any request, ignoring the allowed-numbers list	Use with care — this unlocks it for everybody.
Lockout	Owner-only mode — even allowed numbers are refused	The opposite extreme of "Open to everyone".
Alert on unknown numbers	Texts you the first time an unknown number is refused	On by default. Refused attempts are logged either way.
Device name	A friendly name for the device	Renamed with the pencil by the title, not in this form. Max 32 characters, English letters only.

Renaming: click the pencil next to the device's name, type a new name, press Enter (or click away) to apply, Escape to cancel. A blank name shows as "Unnamed device". The new name is part of your draft — Publish to save it to the device.

Names are English-only. Accented or non-Latin letters (č, š, ž, đ, ć…) are rejected. This matches how the device stores names — see your device's own manual for details.

Managing Who Can Use the Device (Accounts)

Also in the Configuration panel — the list of phone numbers allowed to operate the device (for a gate-opener, the numbers that may open the gate).

Owner phone number — shown read-only. The owner is set once, from the owner's own phone, as described in the device's manual. It cannot be changed or removed from the app — not even by Factory reset. To transfer ownership, contact your installer, or Fidra support at support@fidra.rs.
Allowed phone numbers — up to 500, shown with a "N / 500" counter and a filter box.

To…	Do
Add a number	Add account → enter phone (+ name / time window) → Save
Change a name or time window	Row Edit (the phone number itself is fixed)
Remove a number	Row Remove
Find someone	Type in Filter by number or name…
Apply your changes	Publish config

Adding a number: in the Add account box, the Phone number field keeps a fixed + and takes digits only — country code first, e.g. 447911123456. Name is optional (max 16 characters, English letters only). Optionally set an Allowed time window (below). Press Save.

Every add, edit, and remove is a draft until you Publish config — the same amber "Unpublished edits" line applies. Publishing replaces the device's whole allowed-numbers list with your draft.

A phone number needs its country code and 7–15 digits after the +. A too-short or malformed number makes the device reject the entire publish.

Allowed time windows (time-limited access)

By default an account is "Always allowed". To limit when someone can use the device, tick Restrict to a time window in the add/edit box and set a Start and End time:

A dial (on desktop) or slider (on mobile) with Start and End handles, plus time inputs in 15-minute steps.
If Start is later than End, the window crosses midnight ("Wraps past midnight into the next day") — e.g. 22:00 – 06:00. The end can run up to two hours past midnight.
Keyboard: arrow keys ±15 min, Shift+arrow ±1 hour, Home = 00:00, End = 24:00.

The window travels inside the normal config Publish — there's no separate step.

Checking Activity (Logs)

The Logs panel keeps the device's recent activity. Press Load logs (then Refresh logs to update), or Save to file to download them as JSON. Entries are newest-first, and each tab shows a "N of M entries" count.

Tab	Shows
Gate	Gate openings — who and when
System	Device events (reboots, connection outages, cloud sessions)
Command	Commands received, each marked OK or FAIL (rows tint green/red)
Info	Text messages sent to the device
Denied	Refused attempts — who tried, why, how often

Shared From / To date filters sit above the tabs (with Clear dates), and each tab has its own search. The Command tab adds an "All command types" dropdown and Show successful only / Show failed only toggles.

The Denied tab is the useful one for troubleshooting access. Each row shows the number, a reason (not registered, out of window, or lockout) and a Times count. A not registered attempt from a valid new number gets an Add as user button that jumps straight to Add account with that number pre-filled — the easiest way to catch and fix a number entered wrong.

Logs are read-only and load on demand (they're cached in the current browser tab, not live). The set of activity a device records depends on its type.

Backing Up & Restoring a Configuration

In the Configuration panel:

Save to file downloads the current configuration as a .fidra backup.
Read from file loads a saved configuration back in as a draft (a plain .json export is also accepted). Importing a file that sets an owner number shows a warning to double-check it.

As always, an imported configuration is a draft — review it and Publish to send it to the device.

A file you saved from this app opens straight away. If Read from file reports "This file isn't a valid device config" on a file you didn't save from the app, it isn't a Fidra configuration — import one you saved with Save to file.

Danger Zone

At the bottom of the device's page:

Factory reset → Reset device. Erases all accounts and settings on the device, returning every setting to its default. Cannot be undone. (The owner is not removed — that's set on the device itself, per its manual.)
Unregister device → Remove device. Removes the device from your account. You can re-register it later.

Troubleshooting

The device shows Offline / the app can't reach it

This is normal when the device isn't currently connected to the cloud. Text X.EnableCloud to it and wait a few seconds — the badge turns Online by itself while you have the app open. Pressing Refresh does the same thing immediately if you'd rather not wait.
The cloud connection lasts ~30 minutes, so if you've been away you may need to send X.EnableCloud again.
Check the Portal badge too — if it's Disconnected, your browser lost its own connection; refresh the page.

Registration timed out

The device probably wasn't connected, or the 5-minute claim code expired. Re-send X.EnableCloud, press Try again for a fresh code, and text the X.Claim:… line to the device promptly.

The device says "Unavailable"

The device is connected but can't verify the cloud yet, so it won't accept settings or logs until you press Install certificate update on the card that appears. It keeps working through its own local controls in the meantime — see the device's manual.

A setting or name won't publish

Name rejected: device names and account names are English letters only (max 32 / 16 characters). Remove accented or special characters.
On time rejected: it must be a whole number from 1 to 30.
Number rejected: allowed numbers need a country code and 7–15 digits after +.
"Couldn't confirm the update": the device went quiet mid-publish (its connection may have dropped). Your edits are still saved as a draft — reconnect it and Publish again.

The page looks wrong or rejects a valid config after an update

Your browser may be showing an old cached version of the app. Do a hard refresh — Ctrl + Shift + R (Windows) or Cmd + Shift + R (Mac) — to load the current version, then try again.

"Session expired. Please sign in again."

Your login timed out. Sign out and back in, then retry.

This manual covers the web app. Your device's own manual covers its physical setup, its local controls, and the full list of its text-message commands — this manual only uses the couple the app's flow relies on (X.EnableCloud to bring it online, X.Claim:… to register it).