Changelog & Release Notes

Share a key that switches itself off at a date and time you choose, open a chosen gate from an iOS home-screen widget (one tap on iOS 17 and newer), and re-read past community announcements in the app. Also: faster startup, one-tap logout, six-digit sign-in codes that fill in automatically, and notifications that stop when you sign out.

Share a key that switches itself off at a date and time you choose, open a chosen gate from an Android home-screen widget, and re-read past community announcements in the app. Also: faster startup, one-tap logout, six-digit sign-in codes that fill in automatically, and notifications that stop when you sign out.

Nimbio’s official Model Context Protocol (MCP) server lets an AI assistant list gates, members, keys, and access logs — and, only when you allow it, act on them. Read-only by default; irreversible actions such as opening a gate ask a person first. Installs with one command.

Version 0.6.0 brings the TypeScript SDK to full API coverage, matching the Python release: webhook delivery replay and retry, writable recurring hold opens, member approval and bulk key operations, homes and move-out dates, GuestLinks and visitor access codes, community settings, per-manager notification quiet hours, NFC fobs and gate sensor lines, plus a ConflictError class and built-in capability constants. Conditional requests cut monthly quota use on polling reads. Upgrade with npm install @nimbio/community-api@latest.

Version 0.6.0 wraps every documented API operation. New in Python: replay or retry webhook deliveries your receiver missed, create and edit recurring hold-open schedules, approve members and run bulk key operations, sync homes and record move-out dates, issue and revoke GuestLinks and visitor access codes, read and change community settings, manage NFC fobs and gate sensor lines, and a dedicated ConflictError for 409s. Reads now use conditional requests, so unchanged polls no longer count against your monthly quota. Upgrade with pip install -U nimbio-community-api.

Version 0.11.0 is a major expansion of the public API. Integrations can now issue and revoke GuestLinks and visitor access codes, sync a unit roster from a property-management system, approve members, run bulk key operations for up to 100 members in one call, create recurring hold-open schedules, read and change community settings, set gate geofences, and replay any webhook delivery a receiver missed. Existing API keys gain every new capability automatically; nothing changes for existing integrations.

Re-send a failed webhook delivery — one at a time, or every failed one for a webhook — straight from the Deliveries dialog. The API Playground now covers every endpoint your key can reach, grouped by area, and can send edits and deletes. Turning Event Keys off for the community now only stops members from creating them: links you created keep working, and you can still create one while the feature is off. Also fixes long-open tabs piling up background work and an inflated member count when scheduling the community key.

Access schedules now apply to a community’s own keys only: the schedule list returns just those keys, and reading or setting a member key’s schedule is refused with 403 not_a_community_key — the community-wide schedule already covers every member. descendant_key_count now counts live member keys only, and a new inactive_window_count reports expired windows. These endpoints had never been called in production, so no live integration is affected.

Version 0.5.0 tracks the API 0.4.0 change: key_schedules() returns the community’s own keys, schedule calls on a member key raise PermissionDeniedError, and inactive_window_count is exposed. Upgrade with pip install -U nimbio-community-api.

The same change in the npm package: keySchedules() returns the community’s own keys, member-key schedule calls reject with 403 not_a_community_key, and inactiveWindowCount is exposed. Upgrade with npm install @nimbio/community-api@latest.

Integrations can now open a live event stream and receive every gate open, status change, and hold-open change the moment it happens — no server exposed to the internet. This release also adds endpoints to read and set day-and-hour key schedules, control hold opens, and register webhooks; notes sent with API opens now appear in the access log; and routine status reads no longer count against the monthly quota.

Version 0.4.0 adds key-schedule support: read when each key may open its gates, set a new schedule, or clear one — sync and async — mirroring the new public API endpoints. Upgrade with pip install -U nimbio-community-api.

The same key-schedule support as the Python SDK, now in the npm package — read, set, or clear when a key may open its gates. Upgrade with npm install @nimbio/community-api@latest.

Create an event link that works only during the hours you set, or a limited-use link that stops after a chosen number of uses — visitors just tap it to open the gate, no app or account needed. This release also adds day-and-hour access schedules on keys, and reworks the whole dashboard to run properly from a phone.

Tap a shared event or guest link and you get a clean page showing what it’s for and a button for each gate it opens, with active hours in your local time. And GuestView pages no longer get stuck on “Connecting…” after your phone’s screen locks — they reconnect on their own.

With debug logging on, the Nimbio integration now records named fields from each gate event instead of the whole raw server message — same troubleshooting detail, safer to paste into a support request. Update through HACS; no reconfiguration needed.

Restrict a gate to NFC tap only, with in-app opening switched off. The toggle won’t turn on until the gate has a tag assigned, so you can’t accidentally lock everyone out.

Choose your own words for members and their groupings — like “Tenant” and “Unit,” or “Employee” and “Office” — instead of the default “Resident” and “Home.” Your choice shows up across the dashboard and your public directory.

On gates where a community has enabled it, a visitor with no key can now verify their phone number and open the gate — tap “Get me in,” enter the texted code, and you’re in.

Community managers can generate their own API keys, test calls in a built-in Playground, and register webhooks for real-time notifications on gate opens and membership changes. Contact Nimbio to enable API access for your community.

When a visitor calls from the community directory, their camera is always on so you can see who’s there right away. You’re still in control of your own camera — off by default, with the option to turn it on.

When the app has trouble reaching Nimbio at startup, the loading screen now shows a short, clear status message instead of spinning silently.

Same loading-screen status message improvement as iOS, now on Android.

The community manager site now loads each page’s code only when you open that page, instead of downloading everything up front.

The Add Member page has been visually refreshed, with the form constrained to a more comfortable reading width.

When you’re signed into the directory and viewing a directory page, the avatar in the top-right corner now offers a quick sign-out option.

Community managers can now create and assign directory short codes directly from the community page.

Guests can now enter an access code to open the gate directly from the community directory — no video call needed.

A brand-new dedicated screen for viewing and managing all your communities in one place, organized for faster switching.

Same new My Communities screen as Android, now on iOS.

Community managers can now hide specific members from the guest-facing directory while keeping them active on the account.