“Get Me In” Now Follows the Gate’s Hours
What changed: When a community limits keyless entry to certain hours, the “Get me in” option appears only while it’s available and is simply absent otherwise — no disabled button, no “closed” message, and no hours to read. Everything is evaluated in the gate’s own local time.
Where to find it: Directory listing for a gate (via QR code, NFC tap, or short-code link).
What you’ll see: The “Get me in” card shows up when self-entry is available right now, and doesn’t when it isn’t. In the rare case a window closes in the moment between opening the page and tapping, you’ll get a brief “isn’t available to open right now” message.
What you need to do: No action needed.
Who this affects: Guests
Let Yourself In With Your Phone Number
What changed: Gates where the community has enabled it now offer a “Get me in” option in the directory. A visitor who doesn’t already have a key can gain entry by verifying their phone number — enter your number, receive a texted one-time code (which auto-fills on many phones), and the gate opens. The first entry is frictionless; on later visits we ask for your name so entries are attributable.
Where to find it: The community directory (via QR code or direct link) — a “Get me in” button appears above the resident list on gates that allow it.
What you’ll see: A clear “Are you here now?” prompt with a “Get me in” button, and a note that you can still just browse the directory to call a resident instead. After verifying your phone you’ll see the gate open confirmation. On scan-only gates you’ll be asked to tap your phone on the gate’s tag to complete the open.
What you need to do: Tap “Get me in,” enter your phone number, and enter (or auto-fill) the texted code. Provide your name if asked. On scan-only gates, tap your phone at the gate.
Who this affects: Guests
“Get Me In” Opens the Gate Right After You Sign In
What changed: Fixed a hitch where a guest who wasn’t signed in had to tap “Get me in” twice — once to sign in, then again to actually open the gate. Now, as soon as you verify your texted code, the gate opens automatically once you’re signed in.
Where to find it: The community directory (via QR code or direct link), when you tap “Get me in” without being signed in yet.
What you’ll see: After entering the texted code, the gate open happens on its own — no need to find and tap “Get me in” a second time.
What you need to do: No action needed.
Who this affects: Guests
Gate-Open Button Restored During Video Calls
What changed: Fixed a bug where the Open button was missing from the video-call screen for the person answering, so they couldn’t open the gate for the caller. Any gate whose enabled/disabled state was stored in the newer format was mistakenly treated as disabled, hiding the button even when the answerer held a valid, active key.
Where to find it: The community directory (via QR code or direct link), on the answer screen of an incoming video call.
What you’ll see: When you answer a directory video call and hold an active key for the gate, the Open button now appears on the call screen as expected, letting you open the gate for the caller while the call is live.
What you need to do: No action needed.
Who this affects: Members, Community Managers
Clear Message When Video Calls Aren’t Supported
What changed: When someone opens the directory in a browser that can’t access the camera and microphone — most commonly inside the Nimbio app’s built-in browser or another app’s in-app browser — the directory now detects this and shows a plain-language explanation instead of a confusing technical error.
Where to find it: The community directory (via QR code or direct link), when tapping a resident to start a video call.
What you’ll see: Instead of an error like “undefined is not an object,” a friendly dialog titled “Video Calling Unavailable Here” explains that the current browser can’t make video calls and tells you to open the page in Safari or Chrome to call the resident.
What you need to do: Open the directory link in your device’s browser (Safari or Chrome) to make the video call.
Who this affects: Guests, Members
Reconnect Fix — No More Stuck “Connecting” Screen
What changed: Fixed a bug where GuestView could get stuck on the “Connecting” screen and never recover after the browser tab had been left in the background for a long time. The automatic recovery that runs when you reopen the tab was refusing to act on a fully dropped connection — the exact case it was meant to fix — so the directory would hang indefinitely.
Where to find it: The community directory (via QR code or direct link), for both signed-in and guest visitors. Most noticeable after leaving GuestView open in a background tab and returning later.
What you’ll see: Reopening a GuestView tab that has been backgrounded for a while now reliably re-establishes the connection and shows the directory (and working Open buttons), instead of hanging on “Connecting” until you manually reload.
What you need to do: No action needed.
Who this affects: Guests, Members
Directory Speaks Your Community’s Language
What changed: The public directory now reflects whatever a community calls its members and their groupings. If a community manager has set custom terms and icons — say “Tenant” and “Suite” instead of “Resident” and “Home” — the directory heading, each listing’s subheading, and the listing icons all match. Communities that haven’t customized anything are completely unchanged.
Where to find it: The community directory (via QR code or direct link), for both signed-in and guest visitors.
What you’ll see: The section heading (“Residents Directory” / “Homes Directory” or the community’s chosen equivalent), the small label under each entry, and the avatar icons use the community’s configured wording and icons instead of the fixed “Resident”/”Home.”
What you need to do: No action needed. This is set by the community manager on their Settings page; the directory simply follows it.
Who this affects: Guests, Members