Start your EVOTECH request in under a minute.
App-Based Entry Setup in Cypress, TX 77433
Hardware on the door is the short half of this job. Setup is where a piece of equipment becomes a working system: an administrator account somebody will still control in three years, a list of people, the schedules that expire on their own, and a phone in every pocket that has been configured to actually talk to the reader. It is also where nearly all the complaints come from — and almost none of them are the lock’s fault. This page is the commissioning sequence we follow in Cypress 77433, and the order to work a fault in when a door will not open.
Where installation ends and setup begins
An installer can leave a door fully wired and fully working, and you can still be unable to run the thing a week later. Those are two different deliverables and it is worth knowing which one you have bought.
Setup is the software and people half: the platform account and who owns it, the controller adopted and named, every opening labelled so the names mean something on a phone screen at speed, users invited, credential types chosen per person, schedules built, notifications routed to somebody who will read them, and a written handover of the recovery path. On a small site that is an afternoon. On a site with several openings and a mixed roster it is a planned piece of work with a punch list.
We do it as part of an install, and we do it on systems somebody else put in — including ones where the original company is no longer reachable and nobody has the administrator password.
The first account you create outlives everything else
Get this wrong and every later problem is harder. Four rules, learned the tedious way:
- Own the account yourself. The top-level account should sit on an address the property or business controls, not on an installer’s address and not on the personal mail of an employee who may leave.
- Create a second administrator on day one. One admin is a single point of failure that reveals itself at the worst possible moment — a lost phone, a trip, a resignation.
- Use roles, not shared logins. A manager who can add a cleaner is not the same as an owner who can wipe the site. Most platforms distinguish them; most sites never switch it on.
- Enable two-factor, then record the recovery method. Two-factor on the one account that can open every door is not optional. Where the recovery codes live is part of the handover document, not a detail.
If you are reading this because you already have a system and no administrator access, that is a recoverable situation on most platforms, but it needs proof of ownership of the site and the hardware. Bring what you have and we will work through the vendor’s process with you.
Why the phone is the component that misbehaves
The reader is a simple device running one job. The phone is a general-purpose computer with an aggressive power manager and a permission model, and it is where the great majority of ‘it does not work’ calls actually live.
| Setting | What goes wrong without it |
|---|---|
| Bluetooth permission for the app | The credential cannot be presented at all. The app opens and looks healthy. |
| Location permission on Android | Scanning for nearby devices is gated behind it on many versions, so the reader is never seen. |
| Battery optimisation exclusion | The background service is killed to save power, so approach-to-unlock stops working while tap or in-app unlock still does. |
| Background app refresh | Same symptom on the other platform: works when the app is open, not when it is not. |
| Notification permission | Remote unlock prompts and low-battery warnings never surface. |
The diagnostic value here is high, because those settings produce specific symptoms rather than general flakiness. A door that opens when you launch the app but not when the phone is in your pocket is almost never a radio problem and almost always a background-execution problem.
Adding people without passing credentials around
Every user should arrive through an invitation sent by the platform to their own address, which they redeem on their own device. It takes a minute longer than the shortcut and it removes the shortcut’s two problems: nobody is typing someone else’s password anywhere, and the audit trail records a named person rather than a shared login.
Choose the credential type per person rather than per site. A phone credential suits anyone who carries a phone and will install an app. A card or fob suits a crew, a contractor, or the relative who will not. A keypad code suits a teenager without a phone and a visitor who needs one afternoon. Households in the newer Cypress subdivisions are frequently large and multi-generational, and the mixed approach is normal here rather than a compromise.
One rule worth writing into the setup: no credential gets issued without an owner’s name attached. ‘Spare fob’ in a roster is a hole in the roster.
Access that ends by itself is the point of the whole system
The reason to replace keys is not convenience — it is that a key you handed out is still working today. So the configuration that matters most is the one that ends access without anybody remembering to.
Every recurring service provider gets a window, not a permanent credential: the lawn crew on their day and a two-hour band around it, the pool service on theirs, pest control on a monthly recurrence. Every one-off gets a hard expiry date on the day it is created, not later. Contractors get the duration of the job plus a day, and a diary note rather than a promise.
Two configuration traps we fix constantly. The first is a schedule built in the wrong time zone, which works perfectly until the clocks change and then fails by an hour for half a year. The second is a holiday calendar that was never populated, so a site that should have been closed was open, and nobody found out because nobody was reading the log.
What should already be true before setup day
Half of a bad commissioning day is network, and all of it is preventable. Before we start configuring, the controller wants four things.
- A wired connection, preferably Power over Ethernet. One cable for power and data, and no dependence on a wireless signal crossing a brick elevation.
- A reserved address. A DHCP reservation on the router so the controller does not move and break everything pointed at it.
- Correct time. Schedules and logs are worthless if the clock is wrong, and a controller with no time source will drift.
- Unblocked outbound access. Cloud platforms reach out; a restrictive firewall or a guest network with client isolation will quietly prevent it.
The specific weak spot in this ZIP is distance. Houses here are large, the equipment closet is usually central and interior, and the entries people actually use — the garage service door to the side yard, the gate at the back of the lot — sit well out at the perimeter past masonry. Wireless coverage that is excellent at the router can be marginal at the gate, and a door that works nine times in ten is worse than one that never worked, because nobody trusts it and nobody fixes it.
The door did not open: work it in this order
Most people start by reinstalling the app, which is step five of six and fixes almost nothing. Working from the outside in narrows the fault in about two minutes.
| Step | Check | What it tells you |
|---|---|---|
| 1 | Does the reader light or sound change as you present the phone? | If nothing changes, the credential never reached the reader — go to the phone settings, not the lock. |
| 2 | Does another person’s credential open the same door? | Yes means the door is fine and the problem is one user’s account or phone. |
| 3 | Does your credential open a different door? | Yes means your account is fine and the problem is that door’s schedule, permission or hardware. |
| 4 | Does an unlock from the admin dashboard cycle the lock? | Yes proves controller, wiring and lock all work — the fault is the credential path. No moves you to power and wiring. |
| 5 | Does the log show a denied event, or no event at all? | A denial is a permissions or schedule problem. Silence means the presentation never arrived. |
| 6 | Does the door bind, drag or fail to close fully? | A strike that cannot release under pressure is a mechanical fault the software cannot see. |
Step six accounts for more repeat callouts than anything in the software. A door out of alignment puts side load on the latch, the strike will not release while it is loaded, and the system is blamed for a carpentry problem.
What you should be holding when we leave
A commissioning that ends with a working door and nothing written down has postponed a problem rather than finished a job. At the end of ours you have the administrator credentials in your own control with a second admin already created, an inventory of every controller and reader with its location and address, photographs of the wiring at each opening, the current roster with credential type and expiry per person, the platform’s own published subscription terms where one applies, and a one-page recovery note covering what to do if the internet is down, a phone is lost, or an administrator leaves.
Keep it somewhere that is not only inside the building it opens.
Related services
Frequently asked questions
The app says the door unlocked, but the door did not open.
That message usually means the command was accepted, not that the latch moved. Two causes dominate. The lock released for its programmed interval and re-secured before anyone reached the door — a timing setting, easily lengthened. Or the door is under side load: a misaligned or dragging door traps the latch against the strike so it cannot withdraw, and the electronics have no way to know. Push or pull the door slightly as you trigger the unlock; if it opens then, it is alignment, not software.
It works if I hold the phone to the reader, but not from my pocket like the demonstration.
Almost always background execution. Tap-to-unlock runs while the app is in the foreground; approach-to-unlock needs the app’s background service alive, and the phone’s power manager is trying to kill exactly that. Exclude the app from battery optimisation, allow background refresh, and confirm the Bluetooth permission is set to always rather than while-using. That sequence fixes the large majority of these.
Our housekeeper’s phone never works and everyone else’s is fine.
Look at her permissions before you look at your system. The single most common cause on Android is the location permission — nearby-device scanning is gated behind it on many versions, so the app is healthy and the reader is simply never seen. Aggressive vendor-specific battery managers on some handsets are the second cause. If both are correct and it still fails, re-issue the credential to that account; a credential that half-registered during a poor connection will behave this way.
Can you set up a system another company installed?
Yes, and it is a normal call for us. We work on what is there rather than proposing a rip-out. The first step is establishing administrator control on the platform, which is straightforward where you have the account and takes a documented ownership claim with the vendor where you do not. From there we audit the roster, correct schedules and time zones, fix the network prerequisites and hand back a documented system. If something in the hardware genuinely cannot do what you need, we will say so plainly rather than working around it forever.
Is there an ongoing cost for the app?
It depends entirely on the platform: some charge per door or per user on a recurring basis, some are included with the hardware, and the difference adds up over years. We do not mark up or bundle that cost — we put the vendor’s own published terms in writing beside our itemised quote at the estimate, so you are choosing with the running cost visible rather than meeting it at the first renewal.
Get it commissioned properly, or get the one that is misbehaving fixed
New system or somebody else’s, we will set up the accounts, the roster and the schedules, correct the network prerequisites and hand you the documentation. Free on-site estimate in Cypress 77433 — call (832) 359-2425.
Book a Free Consultation
Ready for EVOTECH to help?
Before you leave, send the quick version. We will review the page you came from and reply with the clean next step.