HAPass Invitations
HAPass Invitations is a self-hosted fork of HAPass that creates shareable, schedule-controlled guest links for controlling selected Home Assistant entities…
Platform availability
Available on 1 of 9 platforms
- Unraid
- TrueNAS (not listed)
- Umbrel (not listed)
- ZimaOS (not listed)
- Proxmox (not listed)
- Helm (not listed)
- Mac (not listed)
- Windows (not listed)
- Linux (not listed)
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
46/100 Fair
- Maintained
- 88last commit 2 days ago
- Popular
- 00 GitHub stars
- Easy to install
- 201 install platform, Docker image
- Light to run
- No data
Based on 3 of 4 factors.
Availability: platform listings confirmed today
- GitHub stars
- 0
- Open issues
- 0
- Last commit
- 2026-10-11
- Latest release
- v1.11.0
- Activity
- declining
Checked today - source: GitHub (Nebur692/ha-pass-invitations)
Resources & Compatibility
Requirements not published yet.
Checked today - source: Docker Hub image tags and published docs
First-install notes
- Home Assistant connection Requires an existing Home Assistant instance reachable from this container and a Long-Lived Access Token with access to the entities you want to expose. source
Fetched today - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
Can I create a guest link now but make it start later, or only work on certain weekdays and times?
Yes. The fork supports future activation with starts_at and recurring weekly windows that limit a token to chosen weekdays and a daily time range, while still respecting the absolute expiry.
Can a guest view a lock, cover, or button link remotely while triggering it only from my local network?
For access-type domains only, the link and live state remain viewable from anywhere, but the action is refused unless the request source IP is inside the configured home-network CIDR. This is source-IP based rather than GPS-based, and the setting is fixed for the whole add-on.
Can I expose a button or input_button entity, such as a gate relay helper, to a guest link?
Yes, this fork adds button and input_button domain support for guests. These single-action, stateless entities were not included in the original service allowlist.
Does the admin UI automatically add every plausible entity to an invitation?
No. The optional entity suggestions only scan for access entities matching door or gate keywords and light-domain entities, then pre-select matches for you to review and adjust.
Can I get a one-time signal when a guest first opens their link?
Yes. A distinct first_use activity event fires exactly once the first time the link is actually opened, which is useful for a guest arrival notification.
Answers sourced from github.com
Community
Collected today - public community threads