Skip to content
OpenAppPhysical access, simplified
Login

Tasmota

Not for electrically locking a means of egress.OpenApp is ingress-only software. Occupants must be able to exit without this integration, the cloud, or a phone. SeeLife safety and egress.

  • Product: Tasmota (GPL-3 firmware; OpenApp does not fork or rebrand it)
  • Manufacturer: Espressif chips (ESP8266 and the ESP32 family)
  • Maturity: Early — first-party flash UX is new; Tasmota itself is mature
  1. Create a Tasmota integration (empty config — broker comes from env) and a device: list the GPIOs OpenApp may drive (output type and pulse per pin). Set opening class on that device (not_applicable for onboard RGB; ingress_only plus attestation for a door or gate). Optional board presets only pre-fill GPIO fields (for example ESP32-C61-DevKitC-1 onboard RGB → GPIO 8 / ws2812; ESP32-S3-DevKitC-1 v1.1 N16R8 → GPIO 38 / ws2812).
  2. OpenApp issues dev:{device_id}, scoped ACLs (openapp/tasmota/{device_id}/#), and a WebPassword. It creates one switch entity per allowlisted GPIO.
  3. Stay in the OpenApp dashboard (or the public installer) and click Flash firmware. ESP Web Tools writes Tasmota’s current stock factory binary for the chip on the USB port (the browser loads the image from this site; OpenApp proxies Tasmota’s OTA file). Then Improv sets Wi-Fi. Flashing does not send OpenApp MQTT, WebPassword, or GPIO settings. Keep USB plugged in and click Send settings over USB. Pin changes are not on the board until you send settings again. If the browser can’t open the port, see Connect the board over USB.
  4. Open a door: OpenApp publishes ON to openapp/tasmota/{device_id}/cmnd/POWER (first GPIO) or …/cmnd/POWER2 and up for later slots. Device PulseTime drops the output; OpenApp may still send OFF.

Do not list a GPIO that has other hardware on it unless you intend OpenApp to drive that pin. Unlisted pins are not configured as relays.

The C61-DevKitC-1 and S3-DevKitC-1 are dev boards, not product SKUs. Their power LEDs are not GPIO-controllable. Onboard RGB is addressable (WS2812-class): GPIO 8 on C61 (also a strapping pin), GPIO 38 on S3-DevKitC-1 hardware v1.1 (GPIO 48 on v1.0). Driving RGB as relay will not blink it cleanly. WS2812 cannot be mixed with relay outputs on the same device. OpenApp sets Tasmota Sleep 0 so MQTT POWER is not delayed by Wi-Fi DTIM power save.

Where the Tasmota UI is (optional fallback)

Section titled “Where the Tasmota UI is (optional fallback)”

Tasmota’s HTTP UI is the board’s own server. OpenApp does not proxy it.

  • Happy path: it never appears (flash + Improv + send settings over USB).
  • No Wi-Fi / no Improv: join SoftAP tasmota-XXXX, then http://192.168.4.1/.
  • Board already on LAN: http://192.168.x.y/ or http://tasmota_<id>.local/.

Use that UI only if sending settings over USB failed, you flashed from tasmota.github.io/install without OpenApp, or you want to debug. Open Troubleshoot in the dashboard, copy the console command (a Tasmota Backlog), and paste it in Console, or enter the LAN IP so OpenApp GET http://<ip>/cm.

Flash and Send settings over USB use the browser Web Serial API. Use Chrome or Edge on a computer. The page must be HTTPS or localhost. Phones and tablets can’t flash.

Use a USB cable that carries data, not charge-only. In the port picker, choose the USB-serial adapter (often CH340, CP210x, or USB Serial).

If the browser reports that it failed to open the serial port, the board is often plugged in but your user can’t open the device node (/dev/ttyUSB0 or /dev/ttyACM0). On Debian and Ubuntu that node is owned by the dialout group. The OpenApp flash modal shows these steps when USB serial fails.

Terminal window
sudo usermod -aG dialout "$USER"

Then log out of the desktop session and log back in (or reboot). A new terminal in the same session is not enough. Run groups and confirm you see dialout.

If it still fails:

  • Close anything else using the port (Arduino IDE, PlatformIO, serial monitors, another browser tab). After a failed flash, unplug the board and plug it back in before retrying — the installer may still hold the port open.
  • Use a native Chrome or Edge package. Snap Chromium often can’t open serial devices.
  • On Ubuntu, brltty can claim CH340 adapters. Disable that service if you don’t use a braille display.
  • ModemManager can claim the same adapters. Add a udev rule that sets ID_MM_DEVICE_IGNORE for your adapter’s USB vendor and product IDs, then reload udev.
  • MQTTS: deployed zones use :8883 and MqttTLS 1 in the Backlog. Local compose uses authenticated :1883. The stock ESP8266 tasmota.bin pin may omit TLS; prefer an ESP32-family chip for production MQTTS.
  • WebPassword: OpenApp issues one and writes it in the same Backlog so the board HTTP UI is not left open. Download is authenticated (GET /devices/{id}/tasmota/provisioning); do not put that URL on the public internet.
  • PulseTime: each output’s pulse_ms maps to PulseTime1, PulseTime2, … (0 = latching). OpenApp also uses OpenApp-controlled per-command auto-off and may still publish OFF. A sole WS2812 output that ignores PulseTime gets a one-shot Rule1 timer in the Backlog.

Rotate MQTT + WebPassword with POST /devices/{id}/tasmota/rotate-credentials, then re-apply the Backlog.

Dry-contact modules and low-voltage LEDs are in scope for DIY. Mains wiring needs a qualified electrician.

FieldTypeRequiredDescriptionDefaultExample
OPENAPP_MQTT_API_BROKER_HOST / OPENAPP_MQTT_API_BROKER_PORT
stringrequiredRequired deployment environment: hostname and port the **OpenApp API** uses to publish `POWER` commands. Shared with Waveshare. No defaults — the process fails fast if unset.emqx
OPENAPP_MQTT_DEVICE_BROKER_HOST / OPENAPP_MQTT_DEVICE_BROKER_PORT
stringrequiredRequired deployment environment: broker address **written into the Tasmota Backlog** (reachable from the board). Local compose uses **1883**; deployed zones use **8883**. No defaults.mqtt.openapp.house:8883
outputs
arrayrequiredAllowlist of GPIOs OpenApp may toggle. Each item has `gpio`, `output_type` (`relay`, `relay_i`, or `ws2812`), and optional `pulse_ms`. Only these pins are programmed as Tasmota relays; other user GPIOs are set to None. One OpenApp switch entity per item. Max 32 (ESP8266 factory builds typically bind 8).[{"gpio":4,"output_type":"relay","pulse_ms":1000}]

Policies

Policies restrict access on top of roles — they never grant it. Browse the policy catalog for arguments and examples. Expand a category below to see the policies that apply to this integration, then expand a policy for details.

Invitations

Guest invites — duration, uses, who may create them, and which doors they can cover.

19 policies

Invitation curfew

Blocks invitation-based opens during a forbidden time window (for example nights).

Admins and residents are never curfewed; existing invitations are evaluated live, not modified.

Learn more — Invitation curfew
Enforced at
Access-time
Tiers
OrgIntegration
Default
Not configured — no hour restrictions on invitation-based access.
Enforcement
Enforce

Max invitation duration

Caps how long each invitation schedule slot may last.

Longer create or update requests are rejected, not shortened.

Learn more — Max invitation duration
Enforced at
Authoring-time
Tiers
OrgIntegration
Default
Not configured — no policy cap on invitation slot length.
Enforcement
Enforce

Max share duration

Caps how long a short-term share (TTL invitation) may last.

Combined with max invitation duration as the stricter of the two. Longer create requests are rejected, not shortened.

Learn more — Max share duration
Enforced at
Authoring-time
Tiers
OrgIntegration
Default
System default is 86400 (1 day) when unset. Org policy may raise the share cap up to 31536000 (365d).
Enforcement
Enforce

Default share uses

When the author omits a use count on a share, store this default.

The system default is 1 when this policy is not configured.

Learn more — Default share uses
Enforced at
Authoring-time
Tiers
OrgIntegration
Default
Not configured — omitted share max_uses stores 1.
Enforcement
Enforce

Max share uses

Ceiling on how many times a share may be used.

Unlimited shares require allow_unlimited on every applicable row and no invitation_max_uses.

Learn more — Max share uses
Enforced at
Authoring-time
Tiers
OrgIntegration
Default
Not configured — no extra ceiling; unlimited shares remain forbidden.
Enforcement
Enforce

Max invitation uses

Requires a finite use count and rejects unlimited invitations or counts above the cap.

Learn more — Max invitation uses
Enforced at
Authoring-time
Tiers
OrgIntegration
Default
Not configured — unlimited-use invitations are allowed.
Enforcement
Enforce

Max invitation devices

Caps the number of unique guest browsers or app installations that may register an invitation.

Learn more — Max invitation devices
Enforced at
Authoring-time
Tiers
OrgIntegration
Default
Not configured — invitations may register any number of devices.
Enforcement
Enforce

Max active invitations per user

Caps how many enabled, unexpired invitations one person may have at once.

Learn more — Max active invitations per user
Enforced at
Authoring-time
Tiers
OrgIntegration
Default
Not configured — no cap on how many invitations one person may keep active.
Enforcement
Enforce

Require invitation expiry

Forbids open-ended recurring invitations that never end.

Learn more — Require invitation expiry
Enforced at
Authoring-time
Tiers
OrgIntegration
Default
Not configured — never-ending recurring invitations are allowed.
Enforcement
Enforce

Allowed entry kinds

Limits which portal types (door, gate, boom-gate) an invitation may grant.

Combination intersects allowed sets.

Learn more — Allowed entry kinds
Enforced at
Authoring-time
Tiers
OrgIntegration
Default
Not configured — any portal entry kind may be granted.
Enforcement
Enforce

Require invitation justification

Requires a non-empty creation justification when creating or updating an invitation.

Learn more — Require invitation justification
Enforced at
Authoring-time
Tiers
OrgIntegration
Default
Not configured — justification is optional.
Enforcement
Enforce

Max doors per invitation

Caps how many unique portals a single invitation may grant.

Learn more — Max doors per invitation
Enforced at
Authoring-time
Tiers
OrgIntegration
Default
Not configured — no policy cap on portals per invitation.
Enforcement
Enforce

Own-apartment doors only

Invitations may only grant doors the author can open as a resident of an allowed apartment.

Org/integration admins are exempt unless applies_to says otherwise. PalGate-only sites with no apartments fail for residents.

Learn more — Own-apartment doors only
Enforced at
Authoring-time
Tiers
OrgIntegration
Default
Not configured — invitations may grant any portal the author can otherwise share.
Enforcement
Enforce

Prohibit master-door invitations

Rejects an invitation if any granted portal’s door is a listed OpenApp device id (union of ids; never client-forged hardware ids).

Learn more — Prohibit master-door invitations
Enforced at
Authoring-time
Tiers
OrgIntegration
Default
Not configured — master doors may be granted on invitations.
Enforcement
Enforce

Who may invite

Literal allow-list of roles that may create invitations.

Combination intersects lists; empty intersection means nobody. Not admin-exempt. Compose with user_sharing (both must pass).

Learn more — Who may invite
Enforced at
Authoring-time
Tiers
OrgIntegration
Default
Not configured — anyone who can otherwise create invitations may do so.
Enforcement
Enforce

No invitation re-share

When the row binds the actor, invite create/update is rejected.

Org/integration default bind is resident (invitees), not generic members. Device-tier without applies_to binds everyone.

Learn more — No invitation re-share
Enforced at
Authoring-time
Tiers
OrgIntegration
Default
Not configured — invitees may create further invitations if their roles allow it.
Enforcement
Enforce

Require invitation identity

Requires a host PIN, a host-attached photo, and/or a verified invitee phone before an invitation can be created or used.

Learn more — Require invitation identity
Enforced at
Authoring-time
Tiers
OrgIntegration
Default
Not configured — PIN, photo, and verified phone are optional.
Enforcement
EnforceRequire approval

Invitation allowed days

Limits invitation-based opens to listed weekdays, minus blackout dates and optional holiday-calendar dates.

Existing invitations are evaluated live, not modified.

Learn more — Invitation allowed days
Enforced at
Access-time
Tiers
OrgIntegration
Default
Not configured — invitation-based access is not limited by weekday or blackout date.
Enforcement
Enforce

Holiday calendar

Lists organization-local ISO dates that invitation allowed-days can treat as holidays.

This type does not deny access by itself.

Learn more — Holiday calendar
Enforced at
Access-time
Tiers
OrgIntegration
Default
Not configured — no shared holiday date list.
Enforcement
Enforce

Holds

Door hold-open and hold-closed — who may set a hold and for how long.

5 policies

Require hold expiry

Members and residents cannot set a permanent hold.

Temporary (and unless also forbidden, weekly) holds are still allowed.

Learn more — Require hold expiry
Enforced at
Authoring-time
Tiers
OrgIntegration
Default
Not configured — permanent holds are allowed for anyone with the set-hold role.
Enforcement
Enforce

Max hold duration

Caps how long a temporary hold can last.

Longer requests are rejected, not shortened. PalGate hardware latch max is an extra cap when present.

Learn more — Max hold duration
Enforced at
Authoring-time
Tiers
OrgIntegration
Default
Not configured — no policy cap on temporary hold duration.
Enforcement
Enforce

No repeating holds

Members and residents may only set a one-shot hold, not a repeating calendar schedule.

Learn more — No repeating holds
Enforced at
Authoring-time
Tiers
OrgIntegration
Default
Not configured — repeating holds are allowed for anyone with set-hold.
Enforcement
Enforce

Allowed hold modes

Limits members and residents to hold-open, hold-closed, or both (for example, stay-off for lights but not stay-on).

Learn more — Allowed hold modes
Enforced at
Authoring-time
Tiers
OrgIntegration
Default
Not configured — both hold-open and hold-closed are allowed.
Enforcement
Enforce

No holds

Members and residents cannot set a hold, even if an admin granted the set-hold role.

Device-tier without applies_to binds everyone, including admins.

Learn more — No holds
Enforced at
Authoring-time
Tiers
OrgIntegration
Default
Not configured — anyone with the set-hold role may set a hold.
Enforcement
Enforce

Sharing

Who may share access or manage linked users outside invitations.

3 policies

User sharing control

Restricts whether non-admins may share access or create invitations out of band — block outright or require admin approval.

Learn more — User sharing control
Enforced at
Authoring-time
Tiers
OrgIntegration
Default
Not configured — non-admins may share access freely.
Enforcement
EnforceRequire approval

No transitive delegation

Invite create: org admin or apartment admin only.

Vendor users_admin writes (except list): org admin only. Runs in addition to user_sharing.

Learn more — No transitive delegation
Enforced at
Authoring-time
Tiers
OrgIntegration
Default
Not configured — ordinary role and user_sharing rules apply.
Enforcement
Enforce

Approval threshold

Requires N distinct organization-admin approve votes before a pending policy approval proceeds.

Any deny denies. Self-approval does not count.

Learn more — Approval threshold
Enforced at
Authoring-time
Tiers
OrgIntegration
Default
Not configured — a single admin approve or deny is enough.
Enforcement
Enforce

Lifecycle

Move-out and idle membership — revoke leftover invites without deleting the user.

2 policies

Revoke invites on move-out

When a resident is removed from an apartment, enabled invitations they authored that grant that apartment’s doors are revoked.

Learn more — Revoke invites on move-out
Enforced at
Authoring-time
Tiers
OrgIntegration
Default
Not configured — leftover invitations stay enabled after move-out.
Enforcement
Enforce

Expire dormant users

After idle days, revoke that person’s invitations and remove residencies.

The user account is not deleted. Admins are exempt unless included.

Learn more — Expire dormant users
Enforced at
Authoring-time
Tiers
OrgIntegration
Default
Not configured — idle members and residents are not auto-expired.
Enforcement
Enforce

Agent safety

Time windows, throttles, and extra confirmation for agents, API keys, and guests.

4 policies

Quiet hours

Blocks access during a local hour window for listed principal kinds (agents, API keys, invitations).

Admins are not restricted unless included.

Learn more — Quiet hours
Enforced at
Access-time
Tiers
OrgIntegration
Default
Not configured — no quiet-hours window.
Enforcement
Enforce

Rate limit

Throttles entity opens per principal in a sliding window so retrying agents cannot exhaust door quota.

Learn more — Rate limit
Enforced at
Access-time
Tiers
OrgIntegration
Default
Not configured — no policy throttle on opens.
Enforcement
Enforce

Require step-up

Requires extra confirmation before a physical write for the listed principal kinds.

Learn more — Require step-up
Enforced at
Access-time
Tiers
OrgIntegration
Default
Not configured — no extra confirmation beyond ordinary authorization.
Enforcement
Enforce

Anti-tailgating cooldown

After a successful open of an entity, further opens of that entity are denied until the cooldown elapses.

Admins are exempt by default.

Learn more — Anti-tailgating cooldown
Enforced at
Access-time
Tiers
OrgIntegration
Default
Not configured — no per-door cooldown after a successful open.
Enforcement
Enforce

Operational

Site-wide lockdown and notifications when a policy denies access.

6 policies

Emergency lockdown

When active, denies non-admin inbound cloud opens.

Does not lock a means of egress or fire-door assembly, and is not a building lock-in.

Learn more — Emergency lockdown
Enforced at
Access-time
Tiers
Org
Default
Not configured — no lockdown.
Enforcement
Enforce

Emergency free egress

When active, OpenApp will not deny inbound cloud opens.

This is not fire-alarm release.

Learn more — Emergency free egress
Enforced at
Access-time
Tiers
Org
Default
Not configured — ordinary denies still apply.
Enforcement
Enforce

Notify on curfew attempt

Emits an audit event (and configured channels) when curfew blocks an open.

Learn more — Notify on curfew attempt
Enforced at
Denial hook
Tiers
OrgIntegration
Default
Not configured — curfew denials are not additionally notified.
Enforcement
Enforce

Maintenance window

During a local hour window, only listed roles may open.

Empty role intersection means nobody. Technicians match the same way as who-may-invite.

Learn more — Maintenance window
Enforced at
Access-time
Tiers
OrgIntegration
Default
Not configured — no technician-only maintenance window.
Enforcement
Enforce

Notify on first use

Emits an audit event when an invitation’s use count goes from 0 to 1, if audit is among the channels.

Learn more — Notify on first use
Enforced at
Access-time
Tiers
OrgIntegration
Default
Not configured — first invitation use is not additionally notified.
Enforcement
Enforce

Notify on new sharing

Emits an audit event after users_admin writes (except list) and after invitation create that actually shares, if audit is among the channels.

Learn more — Notify on new sharing
Enforced at
Authoring-time
Tiers
OrgIntegration
Default
Not configured — new sharing is not additionally notified.
Enforcement
Enforce