Skip to main content

Intro

Once Always-On Display is on, the device shows up in Home Assistant/Homey like any other device. Your automations can control it and react to its state, so your always-on display becomes part of your property’s automations, not just a screen. In Homey, their cards say Zendo device, and you pick one in the card’s Kiosk Device field. In Home Assistant, the actions for them end in (Kiosk), such as Wake up device screen (Kiosk).
  • Control: wake the screen, set the brightness and colour scheme (light/dark mode), configure the screensaver, set the device volume, reload the app, lock the screen with a PIN code (or unlock it), and set or remove the admin code that protects Settings. On a wall panel, also turn Auto-Brightness and Wake on Approach on or off.
  • React to: battery level and charging state, screen and screensaver status, whether the screen is locked, and whether the device is online. On a wall panel, also whether someone is at the panel.
Every example below comes in a Home Assistant and a Homey version. Expand the one you use.
These automations need Always-On Display switched on, that’s how Zendo registers the tablet with Home Assistant/Homey. Control actions also need the device online and responding: if it’s offline, or doesn’t answer within about ten seconds, the action fails. Reading state always works from the last values the device reported.In the Home Assistant snippets, replace YOUR_ZENDO_DEVICE_ID with your tablet’s device (the device field is a list, so add more to target several at once), or pick the devices from the dropdown in the visual editor - each is named after its tablet.

Available options and commands

Every always-on display offers the same controls and state to Home Assistant/Homey, and a wall panel offers a few more. This is the full list to build automations from.
State you can read - each tablet registers these entities, named after the device (a tablet called “Kitchen” gives sensor.kitchen_battery, and so on):There’s no separate online sensor. When a tablet goes offline, all of its entities read unavailable.Home Assistant only creates the wall panel entities for a device that reports them, so a phone or tablet doesn’t get them.Actions you can call - each targets one or more tablets (the device field is a list), picked from the device selector:The two wall panel actions skip any device that can’t take the setting, such as a phone or tablet, and only send a sensitivity to a wall panel that has one. The action fails if none of the devices you list can take it.zendo.managed_device_admin_code_configure, and the actions that lock, unlock or reload a device, only work for a Home Assistant administrator, or in an automation. See Physical security.A single call can control several tablets at once - list their device IDs:
In Developer Tools > Actions or the automation editor, the Home Assistant UI shows a description and the available choices (dropdowns, sliders) for every field.
These cards target a tablet through the Kiosk Device picker. Actions and triggers can aim at All devices / Any device, a Devices for… entry (every device in a device group, or of a person), or a single tablet. Conditions target a single tablet.Triggers (each also carries a Device name tag for use in messages):
  • Zendo device battery level changed - tag: battery level
  • Zendo device battery state changed - tag: charging state
  • Zendo device screen state changed - tag: screen state
  • Zendo device was locked / Zendo device was unlocked
  • Zendo device came online / Zendo device went offline
  • Someone came near a Zendo device / Nobody is near a Zendo device anymore - wall panels only
Conditions (each can be flipped to its opposite):
  • Zendo device battery level is above… a level you set
  • Zendo device battery charging state is… charger unplugged / charging / plugged in, not charging
  • Zendo device screen state is… active / screensaver
  • Zendo device is locked
  • Zendo device is online
  • Someone is near a Zendo device - wall panels only. A device that’s offline, or has no sensor for it, counts as nobody near.
Actions:
  • Wake up Zendo device screen - wake the screen
  • Configure screen for Zendo device - brightness (1-100%) and colour scheme (dark/light)
  • Configure screensaver for Zendo device - mode (none/dim/black/clock) and timer (1-60 min)
  • Set volume for Zendo device - volume (0-100%)
  • Lock Zendo device - lock with a PIN (4/6/8 digits) and an optional message
  • Unlock Zendo device - unlock the screen
  • Reload Zendo app - re-fetch settings and return to the start screen
  • Set auto-brightness for Zendo device - Auto-Brightness on/off (wall panels)
  • Configure wake on approach for Zendo device - Wake on Approach on/off (wall panels) and sensitivity (very close/close/medium/far, some wall panels)
  • Set admin code for Zendo device - set the admin code that protects Settings (4/6/8 digits)
  • Remove admin code from Zendo device - remove the admin code
  • Get admin code of Zendo device (deprecated) - look up a device’s admin code, even while the device is offline. Tags: Admin code, Status and Reported at
The two wall panel actions skip the devices that can’t take the setting when they target All devices or a Devices for… entry, and only send a sensitivity to a wall panel that has one. Aimed at a single device that can’t take the setting, such as a tablet, or a wall panel without a sensitivity given one, the card fails.Get admin code of Zendo device is deprecated, and will be removed in a future version. Flows that already use it keep working, but you can’t add it to a new flow. To look up a device’s admin code, use Zendo instead: see Forgot the admin code?.

Lock a device

Locking puts a full-screen PIN pad over the app, so the tablet can’t be used to control your property until it’s unlocked. It’s useful when you arm the alarm, head out, or have guests over.

How the lock works

  • PIN: 4, 6, or 8 digits, chosen when you lock. An optional message shows above the keypad (for example “Locked while we’re out”).
  • Unlocking at the device: anyone can unlock by typing the PIN on the keypad, so pick one you’re happy to share with the people who use the device. There’s no override code or fingerprint, only the PIN.
  • Wrong PINs slow down: the first few tries are instant, then a delay builds up - a few seconds at first, up to a minute if someone keeps guessing. There’s no hard lockout, and nothing is wiped.
  • Unlocking remotely: an automation can unlock the tablet at any time, with no PIN needed.
  • It survives a restart: the lock stays on even if the app is force-quit or the device reboots, so it can’t be bypassed by closing the app. Like everything on this page, it needs Always-On Display on to show.

Lock and unlock from an automation

Lock on one trigger (leaving, arming the alarm) and unlock on another (arriving, disarming).
The PIN must be 4, 6, or 8 digits. List more device IDs under device to lock several tablets together.
Two flows, one to lock and one to unlock.Lock
  • When: for example Homey’s leaves home presence trigger, or your alarm’s armed trigger.
  • Then: Lock Zendo device. Set Kiosk Device to your tablet, PIN (required, 4/6/8 digits) to something like 1234, and Lock screen message (optional) to a note like Locked while we're out.
Unlock
  • When: for example Homey’s comes home presence trigger, or your alarm’s disarmed trigger.
  • Then: Unlock Zendo device. Set Kiosk Device to the same tablet. No PIN is needed to unlock remotely.

Group devices

A new tablet, or the same tablet after you reinstall the app, joins Home Assistant/Homey as a new device. To have it take the old device’s place, replace the old device from “Control Panels” on your phone or tablet: automations that target the old device then control the new one, with no changes. Replace a Device is available if an installer set up Zendo at your property. Otherwise, change your automations to target the new device. Targeting a device group is another way to reach several tablets, and the tablets you add to the group later.
  • Homey: target a device group instead of a single device. Add each tablet to a device group, then choose the Devices for… entry for that group in your flow. It follows whichever tablets are in the group. You can still pick a single device when you want to. (Conditions are the one exception, they always target a specific device.)
  • Home Assistant: an action’s device field is a list, so one automation can control several tablets at once. There’s no group entry like Homey’s Devices for…, so list each tablet. With Replace a Device, a new tablet keeps the old one’s device and entity IDs, so the list doesn’t change. Otherwise, change your automations to use the new tablet’s device and entity IDs. Doorbell rings are the exception: zendo.ring_doorbell targets a device group through its event entity, such as event.zendo_door_panels, so a ring reaches every tablet in the group, including the ones you add later (Ring only some panels).

Automation ideas

Some ready-made automations to get you started, each with a Home Assistant and a Homey version.

Wake the screen on motion

Got a motion or presence sensor nearby? Let it wake the screen as you approach, so the tablet lights up when you walk up, then settles back to its screensaver once you leave. A wall panel can do this without an automation: Wake on Approach wakes its screen when someone comes near. Use this automation for a tablet or a phone, or to wake a wall panel from a motion sensor that detects people further away.
Trigger on your motion sensor, then call the wake-up action on your tablet.
Build a two-card flow:
  • When: your motion sensor’s Motion turned on trigger (the exact wording depends on the sensor).
  • Then: add Wake up Zendo device screen. In the Kiosk Device field, pick your tablet.
No condition is needed.
There’s a Wake up action but no matching turn-off, and that’s on purpose. Once woken, the screen returns to its screensaver on its own after the timer you set in the Always-On Display settings. A raw on/off switch wired to a motion sensor would flicker the screen every time the sensor tripped; waking on motion and letting the timer take over keeps it smooth.
You can fire the same Wake up action from any trigger, not just motion. A door unlocking or an arrival geofence/location-based automation works just as well, and you can target every tablet at once (All devices on Homey, or a list of devices in a single Home Assistant action).

Keep the battery healthy

A wall tablet left plugged in sits at 100% all day, which wears the battery down over time. Keeping it in a healthier range helps: plug its charger on a smart plug, then start charging when the battery drops below 20% and switch the plug off once it climbs above 80%.
Read the tablet’s battery sensor (named after the device, e.g. sensor.kitchen_battery) and switch the plug from two numeric-state automations.
Two flows, one to start charging and one to stop.Start charging when low
  • When: Zendo device battery level changed. Set Kiosk Device to your tablet.
  • And: Zendo device battery level is above…. Set the level to 20, then invert the card (tap it so it reads as not above 20%) so it matches when the battery is at or below 20%.
  • Then: your smart plug’s Turn on.
Stop charging when full
  • When: Zendo device battery level changed. Set Kiosk Device to your tablet.
  • And: Zendo device battery level is above…. Set the level to 80 and leave it as-is.
  • Then: your smart plug’s Turn off.

Dim the tablet in the evening

In the evening, make the tablet dimmer and quieter: dark mode, lower brightness, a shorter screensaver timer so it isn’t sitting bright for long, and lower volume. The examples switch to these settings at 20:00 and back to day settings at 08:00. Lowering the volume here also quiets a doorbell ring that follows the device volume. On a wall panel with Auto-Brightness on, the brightness you set here is how bright the screen is in normal light, and Auto-Brightness still makes it brighter or dimmer from there. To set an exact brightness, turn off Auto-Brightness in the same automation.
One automation switches to night settings at 20:00, another switches back to day settings at 08:00.
Two flows, one for night and one for morning.Night mode at 20:00
  • When: Date & Time’s The time is… trigger, set to 20:00.
  • Then, add three action cards, all pointed at your tablet in the Kiosk Device field:
    • Configure screen for Zendo device: set Color scheme to Dark and Brightness % to something low like 15.
    • Configure screensaver for Zendo device: set Timer in minutes to 2.
    • Set volume for Zendo device: set Volume % to 20.
Day mode at 08:00
  • When: the same The time is… trigger, set to 08:00.
  • Then: the same three cards with daytime values, a Light colour scheme, higher brightness, a longer timer, and a higher volume.

Know when a device goes offline

Get an alert if a device drops off the network, after a crash, a reboot, or a Wi-Fi drop, so a dark screen doesn’t go unnoticed. The alert also runs when someone turns off Always-On Display on the device, because the device stops reporting to Home Assistant/Homey. If an installer set up Zendo at your property, you can tell the two apart in “Control Panels”: a device that has lost contact shows a grey dot, and a device with Always-On Display off shows no dot.
There’s no dedicated offline sensor. Instead, an offline device’s entities read unavailable, so trigger on any one of them changing to unavailable. The for delay avoids alerting on a brief blip.
  • When: Zendo device went offline. Set Kiosk Device to Any device so one flow watches them all, or pick a single tablet to watch just that one.
  • Then: a notification card, for example Send a push notification. Put the trigger’s Device name tag in the message, like [Device name] has gone offline, so it names whichever tablet dropped.
To be told when it recovers, add a matching flow with the Zendo device came online trigger.