Images: wordmark hero + four HA screenshots scattered through pages
src/assets/manual/omnipro-ii-wordmark.png
Lifted from the Owner's Manual cover (Owner_s_Manual_page_1_img_1).
1280x592, 13KB, 8-bit grayscale. Used as the eager-loaded hero on
index.mdx via Astro's Image component, with CSS filter:invert(1) so
the black-on-white wordmark renders crisp on the dark theme.
src/assets/screenshots/ (six PNGs, copied from omni-pca/dev/artifacts):
01-overview.png HA Lovelace
02-integrations-list.png HAI/Leviton tile in the integrations list
03-omni-pca-config.png '1 device, 38 entities' integration page
04-panel-device.png Omni Pro II device page with all controls
05-entities-omni.png config-entry filtered entity table
06-developer-states.png alarm_control_panel.omni_pro_ii_main raw
attributes from Developer Tools
Wired into pages:
index.mdx wordmark hero (eager load)
start/quickstart.md 04-panel-device.png at the bottom of
step 3 so the reader sees the payoff
reference/ha-entities.md new 'What it looks like in HA' section
with four screenshots (integrations
list, integration detail, device page,
developer states)
Astro Image processed all screenshots into webp at request size:
06-developer-states 188 KB -> 91 KB after VP8 encoding.
Build: 13 pages clean in 1.66s, sitemap and Pagefind index regenerated.
Container rebuilt + recreated; verified HTTP 200 with 33315-byte index
page and the /reference/ha-entities/ page references four /_astro/*.webp
URLs that all return 200 from the running container.
BIN
src/assets/manual/omnipro-ii-wordmark.png
Normal file
|
After Width: | Height: | Size: 13 KiB |
BIN
src/assets/screenshots/01-overview.png
Normal file
|
After Width: | Height: | Size: 107 KiB |
BIN
src/assets/screenshots/02-integrations-list.png
Normal file
|
After Width: | Height: | Size: 130 KiB |
BIN
src/assets/screenshots/03-omni-pca-config.png
Normal file
|
After Width: | Height: | Size: 106 KiB |
BIN
src/assets/screenshots/04-panel-device.png
Normal file
|
After Width: | Height: | Size: 220 KiB |
BIN
src/assets/screenshots/05-entities-omni.png
Normal file
|
After Width: | Height: | Size: 85 KiB |
BIN
src/assets/screenshots/06-developer-states.png
Normal file
|
After Width: | Height: | Size: 189 KiB |
@ -5,6 +5,15 @@ template: doc
|
||||
---
|
||||
|
||||
import { Card, CardGrid, LinkCard } from '@astrojs/starlight/components';
|
||||
import { Image } from 'astro:assets';
|
||||
import wordmark from '../../assets/manual/omnipro-ii-wordmark.png';
|
||||
|
||||
<Image
|
||||
src={wordmark}
|
||||
alt="OmniPro II Automation"
|
||||
loading="eager"
|
||||
style="max-width: 480px; width: 100%; height: auto; margin: 1rem 0 2rem; filter: invert(1); opacity: 0.9;"
|
||||
/>
|
||||
|
||||
## What it is
|
||||
|
||||
|
||||
@ -204,3 +204,27 @@ first, then reload the integration.
|
||||
All of them sit on top of `OmniDataUpdateCoordinator` (`coordinator.py`),
|
||||
which keeps a long-lived `OmniClient`, runs one-time discovery on first
|
||||
refresh, and patches state in-place from the typed event stream.
|
||||
|
||||
## What it looks like in HA
|
||||
|
||||
The integration appears alongside the rest of HA's built-in integrations
|
||||
in **Settings → Devices & Services**:
|
||||
|
||||

|
||||
|
||||
Clicking through, the integration page reports the discovered counts and
|
||||
the hub:
|
||||
|
||||

|
||||
|
||||
The device page is where every entity surfaces. Lights and switches with
|
||||
toggles, areas with arm states, thermostats with current temperature and
|
||||
setpoints, panel-button macros with Press buttons, plus the Diagnostics
|
||||
download:
|
||||
|
||||

|
||||
|
||||
Developer Tools → States exposes the raw entity payloads — useful for
|
||||
template authoring and for confirming an attribute is wired through:
|
||||
|
||||

|
||||
|
||||
@ -107,6 +107,8 @@ binary_sensors for zones, climate for thermostats, and so on. State
|
||||
propagates over the panel's unsolicited push channel; a 30-second poll
|
||||
backstops anything that didn't push.
|
||||
|
||||

|
||||
|
||||
See the [HA entity catalogue](/reference/ha-entities/) for what gets created
|
||||
and the [HA service reference](/reference/ha-services/) for the seven
|
||||
services you can call from automations.
|
||||
|
||||