zorruno/zorruno-homeassistant
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Compare commits

base: zorruno/zorruno-homeassistant:d8bcf05bf6a5873fe838dd8d4f316c42873b9f9e
Branches Tags
zorruno/zorruno-homeassistant:master
..
compare: zorruno/zorruno-homeassistant:master
Branches Tags
zorruno/zorruno-homeassistant:master

19 Commits
d8bcf05bf6 .. master

Author SHA1 Message Date
zorruno fe6feee250 various tidyups 2026-07-24 18:55:12 +12:00
ESPHome Device Builder fce8c7b0bc Edit esp-3dprinterpow.yaml 2026-07-24 18:21:35 +12:00
ESPHome Device Builder f46b29e6ab Edit esp-spare1-athomv1.yaml 2026-07-24 18:21:35 +12:00
ESPHome Device Builder 32df6ce407 Edit esp-rocktumbler.yaml 2026-07-24 18:21:35 +12:00
zorruno 8fdcb128a3 various tidyups 2026-07-22 22:15:25 +12:00
ESPHome Device Builder b9e9c98f7e Edit esp-centralstairs-bottom.yaml 2026-07-21 18:28:33 +12:00
ESPHome Device Builder 6dc9b56ff7 Edit esp-centralstairs-top.yaml 2026-07-21 18:28:33 +12:00
zorruno 4e2107f7f7 various tidyups 2026-07-21 13:40:06 +12:00
ESPHome Device Builder 66bee0ccf7 Edit esp-masterbdrmsouth.yaml 2026-07-20 21:02:12 +12:00
ESPHome Device Builder 5b675e1d62 Edit esp-masterbdrmwest.yaml 2026-07-20 21:00:48 +12:00
ESPHome Device Builder a76dbb6b16 Edit esp-downstkitchlights.yaml 2026-07-20 20:47:14 +12:00
ESPHome Device Builder e20e36cdb5 Edit esp-downstloungeentry.yaml 2026-07-20 20:40:18 +12:00
ESPHome Device Builder a2fb86aa93 Edit esp-downstloungemain.yaml 2026-07-20 20:37:50 +12:00
ESPHome Device Builder c6e8d7721c Edit esp-officeusbhubpower.yaml 2026-07-20 20:32:29 +12:00
ESPHome Device Builder 3ff67b883b Edit esp-downstairskitchleds.yaml 2026-07-20 20:17:04 +12:00
ESPHome Device Builder 2e645793f0 Edit esp-bedrm1arlecbulb.yaml 2026-07-20 20:09:41 +12:00
ESPHome Device Builder 4ff90ea60a Edit esp-breakfastbarleds.yaml 2026-07-20 19:59:40 +12:00
ESPHome Device Builder dcd43a18c1 Edit esp-loungecabinetleds.yaml 2026-07-20 19:44:53 +12:00
ESPHome Device Builder 2b6b91f829 Edit esp-loungebookshelfleds.yaml 2026-07-20 19:27:48 +12:00
92 changed files with 3062 additions and 6224 deletions
Expand all files Collapse all files
.ha_run.lock
+1 -1
View File
@@ -1 +1 @@
{"pid": 71, "version": 1, "ha_version": "2026.7.2", "start_ts": 1784512870.0398877}
{"pid": 74, "version": 1, "ha_version": "2026.7.3", "start_ts": 1784842567.418518}
AGENTS.md
-807
View File
@@ -1,807 +0,0 @@
# Home Assistant OpenCode Rules
You are working directly within a Home Assistant installation. Your working directory is `/homeassistant`, which is the live Home Assistant configuration directory.
## CRITICAL: User Consent and Scope Rules
You MUST follow these rules strictly:
1. **Never exceed the user's request** - Do exactly what the user asks, nothing more. Do not "improve" or "enhance" beyond the stated scope.
2. **Never make changes without explicit approval** - Before modifying ANY file:
- Show the user exactly what you plan to change
- Wait for their explicit confirmation ("yes", "go ahead", "do it", etc.)
- If they haven't approved, DO NOT proceed
3. **Ask, don't assume** - If the user's request is ambiguous:
- Ask clarifying questions first
- Present options and let them choose
- Never guess at their intent
4. **Read-only by default** - When investigating or troubleshooting:
- Only read files and gather information
- Present findings and recommendations
- Wait for user instruction before making any changes
5. **One change at a time** - When making approved changes:
- Make the minimum change needed
- Show what was changed
- Let the user verify before proceeding to any next step
6. **No unsolicited modifications** - Never:
- "Clean up" code the user didn't ask about
- Add features they didn't request
- Refactor working configurations
- Fix issues they haven't mentioned
7. **Respect "no"** - If a user declines a suggestion, do not:
- Repeat the suggestion
- Make the change anyway
- Try to convince them otherwise
## Environment Context
- You are running inside the OpenCode app
- The current directory (`/homeassistant`) contains the live Home Assistant configuration
- Changes to YAML files here directly affect the Home Assistant instance
- If add-on folder access is enabled, `/addons` and `/addon_configs` are available for Home Assistant add-on development. Treat `/addon_configs` as sensitive and only inspect or modify these folders when the user explicitly asks.
- You may have access to MCP tools for interacting with Home Assistant (check with the user)
## Home Assistant Interaction Model
There are three primary, safe ways to interact with Home Assistant:
### 1. Configuration Files (YAML)
The standard way to define and customize Home Assistant behavior:
- Automations, scripts, scenes, and blueprints
- Integration and sensor configurations
- Templates, packages, and customizations
- Dashboard (Lovelace) definitions
These files are designed for user editing and are the source of truth for your Home Assistant setup.
### 2. MCP Tools (Runtime API)
Real-time interaction with the running Home Assistant instance:
- Query current entity states and history
- Control devices and call services
- Validate configurations
- Diagnose issues and detect anomalies
- Report OpenCode/HA agent capability status with `get_agent_capabilities`
### Native Home Assistant LLM Platform
Home Assistant is developing a native `llm` integration where Core integrations and custom integrations can expose curated tools through `<integration>/llm.py` and registered LLM APIs. New Home Assistant builds may also expose those APIs over native MCP endpoints such as `/api/mcp/<API ID>`; the built-in Assist API uses `/api/mcp/assist`. This is complementary to OpenCode MCP, not a replacement.
- If the optional `homeassistant_native` MCP server is available, prefer it for requests that fit the configured native Home Assistant LLM API because those tools are curated by Home Assistant.
- Use OpenCode MCP for configuration editing, safe writes, validation, admin/dev workflows, screenshots, updates, ESPHome, `hab`, Zigbee tasks, add-on development, and Home Assistant documentation lookup.
- Use `get_agent_capabilities` or `ha://agent/capabilities` to check whether the running HA instance reports the native `llm` component and native MCP endpoints.
- Use `get_home_context` for compact area/domain/entity understanding before broad state dumps.
- Use `get_ha_llm_development_guide` when helping develop or review a custom integration's native `<integration>/llm.py` provider.
- Do not assume this add-on can register tools directly with HA's native `llm` platform; native tool registration is internal to HA integrations/custom integrations. The add-on can consume configured native LLM APIs through native MCP when Home Assistant exposes them.
### 3. hab CLI (Home Assistant Builder)
A CLI tool designed for AI agents to manage Home Assistant. Run `hab` commands via the terminal:
- **Entity management**: `hab entity list`, `hab entity get light.living_room`, `hab entity logbook sensor.power --start 2h`
- **Service calls**: `hab action call light.turn_on --entity light.living_room --data '{"brightness": 200}'`
- **Automation CRUD**: `hab automation list`, `hab automation create`, `hab automation delete`
- **Dashboard management**: `hab dashboard list`, `hab dashboard view create`
- **Area/floor/zone/label**: `hab area list`, `hab area create "Kitchen"`
- **Helpers**: `hab helper list`, `hab helper create`
- **Scripts**: `hab script list`, `hab script create`
- **Scenes**: `hab scene list`, `hab scene create`, `hab scene activate "Movie Time"`
- **Blueprints**: `hab blueprint list`
- **Backups**: `hab backup list`, `hab backup create`
- **System**: `hab system info`, `hab system health`, `hab overview`
- **Devices**: `hab device list`
- **People**: `hab person list`, `hab person create`, `hab person update`
- **Categories**: `hab category list`, `hab category assign --entity light.kitchen`
- **To-do lists**: `hab todo list`, `hab todo item list todo.shopping`, `hab todo item add todo.shopping "Milk"`
- **Notifications**: `hab notification list`, `hab notification create --message "Hello" --title "Alert"`
- **Integrations**: `hab integration list`, `hab integration reload hue`, `hab integration disable mqtt`
- **Repairs**: `hab repairs list`, `hab repairs ignore <issue_id>`
- **Events**: `hab event list`, `hab event fire my_custom_event --data '{"key": "value"}'`
- **Templates**: `hab template render --expression "{{ states('sensor.temperature') }}"`
- **Search**: `hab search related`
`hab` outputs human-readable text by default. Use `--json` for structured JSON output (ideal for parsing).
`hab` is pre-authenticated via the Supervisor token - no login required.
Run `hab --help` or `hab <command> --help` for full usage details.
<!-- HAB_LIVE_HELP_START -->
```
Home Assistant Builder (hab) is a CLI utility designed for LLMs
to build and manage Home Assistant configurations.
Interactive sessions default to human-readable text. Non-interactive sessions default to JSON.
Start with 'hab guide' for workflow-level guidance optimized for LLM and agent usage.
Usage:
hab [command]
Getting Started:
auth Manage authentication
capability Inspect runtime capabilities
guide Display built-in usage guides
overview Show an overview of the Home Assistant instance
schema Show machine-readable command schema
Registry:
area Manage areas
device Manage devices
entity Manage entities
floor Manage floors
label Manage labels
person Manage persons
search Search for items and relationships
zone Manage zones
Automation:
action Call actions (services)
automation Manage automations
blueprint Manage blueprints
category Manage categories
helper Manage groups, templates, and other helpers
scene Manage scenes
script Manage scripts
Dashboard:
dashboard Manage dashboards
Other:
backup Manage backups
calendar Manage calendar events
diagnostics Manage diagnostics handlers
energy Manage energy dashboard settings
esphome Manage ESPHome devices
event Manage Home Assistant events
integration Manage integrations
network Manage network settings
notification Manage persistent notifications
repairs Manage Home Assistant repairs
system Manage system
template Work with Home Assistant templates
thread Manage Thread credentials
todo Manage to-do list items
update Update hab to the latest version
version Show version information
Additional Commands:
help Help about any command
Flags:
--config string Path to config directory (default: ~/.config/home-assistant-builder)
-h, --help help for hab
--json Use JSON output instead of human-readable text
--skip-update-check Skip automatic update check on startup
--text Use human-readable text output
--verbose Show verbose output
Use "hab [command] --help" for more information about a command.
```
<!-- HAB_LIVE_HELP_END -->
**Use configuration files when:** defining behavior, creating automations, setting up integrations
**Use MCP tools when:** checking current state, safe config writing, anomaly detection, entity diagnostics
**Use hab CLI when:** managing dashboards, areas, helpers, backups, blueprints, and bulk admin operations
### 4. zigporter CLI (Zigbee Toolkit)
A CLI for Zigbee device management in Home Assistant. Handles cascade renames (updating entity IDs across automations, scripts, scenes, and all Lovelace dashboards atomically), device inspection, stale device cleanup, and Zigbee mesh visualization.
**Cascade rename** — zigporter's unique value: when you rename an entity or device, it automatically patches every reference in automations, scripts, scenes, and Lovelace dashboards. `hab` can rename a single entity/device but does NOT cascade to references.
Key commands:
- **Cascade rename**: `zigporter rename-entity light.old_id light.new_id --apply`, `zigporter rename-device "Old Name" "New Name" --apply`
- **Device inventory**: `zigporter list-devices --json`, `zigporter list-z2m --json` (requires Z2M config)
- **Device inspection**: `zigporter inspect "Device Name" --json`, `zigporter inspect sensor.entity_id --json`
- **Stale device management**: `zigporter stale "Device" --action remove`, `zigporter stale "Device" --action ignore`
- **Post-migration cleanup**: `zigporter fix-device "Device" --apply`
- **Connectivity check**: `zigporter check`
- **ZHA export**: `zigporter export --output devices.json`
- **Mesh visualization**: `zigporter network-map --format table` (terminal), `zigporter network-map --output mesh.svg` (SVG file)
**Output format**: Use `--json` on listing/inspect commands for structured output (ideal for AI parsing). Rename commands output diffs and confirmation text.
zigporter is pre-authenticated via the Supervisor token. Z2M commands (`list-z2m`, `network-map --backend z2m`) require Z2M URL configuration in the add-on settings.
**Important limitations**:
- `rename-entity` / `rename-device` do NOT patch Jinja2 template expressions (e.g. `{{ states('old.id') }}`). A warning is printed listing affected files — inform the user these need manual review after renaming.
- The `migrate` command is inherently interactive (requires physical device actions) and must NOT be used by AI agents.
- Dry-run is the default for renames — always preview before using `--apply`.
<!-- ZIGPORTER_LIVE_HELP_START -->
```
Usage: zigporter [OPTIONS] COMMAND [ARGS]...
Migrate Zigbee devices between ZHA and Zigbee2MQTT. Supports both ZHA → Z2M
(default) and Z2M → ZHA (--direction z2m-to-zha).
╭─ Options ────────────────────────────────────────────────────────────────────╮
│ --version -v Show version and exit. │
│ --install-completion Install completion for the current shell. │
│ --show-completion Show completion for the current shell, to │
│ copy it or customize the installation. │
│ --help -h Show this message and exit. │
╰──────────────────────────────────────────────────────────────────────────────╯
╭─ Commands ───────────────────────────────────────────────────────────────────╮
│ setup Create or update the configuration file in the zigporter │
│ config directory. │
│ check Verify that all requirements are in place before migrating. │
│ export Export current ZHA devices, entities, areas, and automation │
│ references to JSON. │
│ export-z2m Export current Z2M devices, entities, areas, and automation │
│ references to JSON. │
│ list-z2m List all devices currently paired with Zigbee2MQTT. │
│ list-devices List all Home Assistant devices across all integrations. │
│ migrate Interactive wizard to migrate devices between ZHA and │
│ Zigbee2MQTT. │
│ inspect Show all automations, scripts, scenes, and dashboard cards │
│ that depend on a device. │
│ rename-entity Rename an entity ID and update all references in automations, │
│ scripts, scenes, and dashboards. │
│ rename-device Rename a device and cascade the change to all its entities, │
│ automations, scripts, scenes, and dashboards. │
│ stale Identify and manage offline/stale devices across all │
│ integrations. │
│ fix-device Remove stale ZHA device entries left behind after migration │
│ to Zigbee2MQTT. │
│ network-map Show Zigbee mesh topology with signal strength (LQI) for each │
│ device. │
╰──────────────────────────────────────────────────────────────────────────────╯
```
<!-- ZIGPORTER_LIVE_HELP_END -->
**Use zigporter CLI when:** renaming entities/devices with cascade updates, inspecting Zigbee devices across integrations, cleaning up stale or post-migration devices, visualizing the Zigbee mesh
### 5. Internal Directories (OFF-LIMITS)
Home Assistant manages internal state in directories like `.storage/`. These are:
- Not designed for direct access
- Subject to change without notice
- Potentially dangerous to modify
**Never access internal directories directly - use configuration files or MCP tools instead.**
## RESTRICTED: Internal Home Assistant Directories
**NEVER read, modify, or directly interact with these internal directories:**
| Directory | Contains | Use Instead |
|-----------|----------|-------------|
| `.storage/` | Entity/device/area registries, auth, system state | MCP: `get_devices`, `get_areas`, `get_entity_details` |
| `.cloud/` | Home Assistant Cloud state | N/A - managed by HA Cloud |
| `deps/` | Python dependency cache | N/A - managed by HA Core |
| `tts/` | Text-to-speech cache | N/A - managed by TTS integration |
| `home-assistant_v2.db` | History SQLite database | MCP: `get_history`, `get_logbook` |
| `home-assistant.log` | Raw system logs | MCP: `get_error_log` |
These contain internal Home Assistant state that:
1. Is managed exclusively by Home Assistant core
2. Can corrupt your installation if modified incorrectly
3. May be overwritten by Home Assistant at any time
4. Has no stable schema or format guarantees
**For information that seems to require internal access, there is always a proper alternative:**
- Need entity details? -> Read configuration files OR use `get_entity_details`
- Need device info? -> Use `get_devices` MCP tool
- Need to check history? -> Use `get_history` MCP tool
- Need to see errors? -> Use `get_error_log` MCP tool
## File Structure Knowledge
### Configuration Files (Primary Interface - Read/Write with User Approval)
These are the user-facing configuration files - the primary way to define Home Assistant behavior:
- `configuration.yaml` - Main configuration file
- `automations.yaml` - Automation definitions (if using UI or split config)
- `scripts.yaml` - Script definitions
- `scenes.yaml` - Scene definitions
- `secrets.yaml` - Sensitive values (NEVER commit or expose)
- `customize.yaml` - Entity customizations
- `groups.yaml` - Group definitions
- `packages/` - Package-based configuration splits
- `blueprints/` - Automation and script blueprints
- `custom_components/` - Custom integrations (HACS or manual)
- `www/` - Static files served at /local/
- `themes/` - Custom themes
- `*.yaml` in root - Any user-created YAML configuration
**These files are designed for editing** and are equally valid as MCP tools for research and changes.
### Internal Directories (OFF-LIMITS - Never Access Directly)
- `.storage/` - Internal registries and state (use MCP tools)
- `.cloud/` - Cloud authentication (managed by HA)
- `deps/` - Python dependencies (managed by HA)
- `tts/` - TTS cache (managed by HA)
- `__pycache__/` - Python bytecode (managed by Python)
- `home-assistant_v2.db` - History database (use MCP `get_history`)
- `home-assistant.log` - Logs (use MCP `get_error_log`)
## Working with YAML on the Command Line (`yq`)
To read, query, or convert YAML from the shell, use **`yq`** (the mikefarah/Go tool, pre-installed on `PATH`). It is the correct tool because it tolerates Home Assistant's custom tags — `!include`, `!secret`, `!env_var`, `!input`, and the `!include_dir_*` family.
**Do NOT reach for `python3 -c "import yaml"` (PyYAML) or Ruby's YAML for HA config** — both crash with a constructor error on the very first `!include`/`!secret`, because those tags are Home Assistant extensions, not standard YAML. `yq` parses them with no setup.
### Read / query (always safe — never errors on HA tags)
```
yq '.homeassistant.latitude' configuration.yaml # Print a nested value
yq '.automation | tag' configuration.yaml # Inspect the tag itself -> !include
yq 'keys' configuration.yaml # List top-level keys
yq -o=json '.' configuration.yaml | jq '.sensor' # Convert to JSON to pipe into jq
```
Note: output and JSON conversion strip the tag — `!secret home_latitude` prints as `home_latitude`. Use `| tag` when you need to see the tag. Never round-trip a file *through* JSON and back; that permanently loses every `!include`/`!secret`.
### Writing / editing
Prefer the sanctioned write path: **`write_config_safe`** (MCP — validates, backs up, and blocks accidental content loss) or read the full file and use the editor. Reserve `yq -i` for quick, low-risk edits, and only with these two caveats in mind:
1. **A custom tag sticks to the value you overwrite.** `yq -i '.homeassistant.latitude = 52.37'` on a `!secret`-tagged node produces the corrupt `latitude: !secret 52.37`. When replacing a tagged value, reset the tag in the *same* expression:
```
yq -i '(.homeassistant.latitude tag = "") | .homeassistant.latitude = 52.37' configuration.yaml
```
To *add* a secret reference, set the tag explicitly: `yq -i '.http.api_key = "my_api_key" | .http.api_key tag = "!secret"' configuration.yaml`
2. **`yq -i` strips blank separator lines** (and collapses inline-comment spacing) across the whole file. No data is lost, but diffs are noisier. When a clean, minimal diff matters, use the editor instead.
### Validation is not a syntax check
`yq` only confirms YAML *parses*. To validate a Home Assistant *configuration* (resolving `!include`/`!secret` and checking integration schemas), use `check_config_syntax` / `write_config_safe` (MCP), not `yq`.
## YAML Style Guide (MANDATORY)
All YAML written or modified MUST follow the official Home Assistant YAML Style Guide.
Reference: https://developers.home-assistant.io/docs/documenting/yaml-style-guide/
A Prettier formatter is configured for this environment and will auto-format files on save.
However, Prettier only enforces a subset of the rules below. You are responsible for following
ALL rules, especially those Prettier cannot enforce (marked with *).
### Indentation
2 spaces. Tabs are forbidden.
```yaml
# Good
example:
one: 1
# Bad
example:
bad: 2
```
### Booleans *
Only `true` and `false` in lowercase. Never use `Yes`, `No`, `On`, `Off`, `TRUE`, etc.
```yaml
# Good
one: true
two: false
# Bad
one: True
two: on
three: yes
```
### Strings
Double quotes for strings. Single quotes are not allowed.
```yaml
# Good
example: "Hi there!"
# Bad
example: 'Hi there!'
```
**Exceptions** (no quotes needed): entity IDs, area IDs, device IDs, platform types,
trigger types, condition types, action names, device classes, event names, attribute names,
and values from a fixed set of options (e.g., `mode`).
```yaml
# Good
actions:
- action: light.turn_on
target:
entity_id: light.living_room
area_id: living_room
data:
message: "Hello!"
transition: 10
# Bad - don't quote entity IDs and action names
actions:
- action: "light.turn_on"
target:
entity_id: "light.living_room"
```
### Sequences (Lists) *
Use block style. Flow style `[1, 2, 3]` must not be used.
Block sequences must be indented under their key.
```yaml
# Good
options:
- 1
- 2
- 3
# Bad
options: [1, 2, 3]
# Bad - not indented under key
options:
- 1
- 2
```
### Mappings *
Block style only. Flow style `{ key: val }` must not be used.
```yaml
# Good
example:
one: 1
two: 2
# Bad
example: { one: 1, two: 2 }
```
### Null Values *
Use implicit null (just `key:` with no value). Never use `null` or `~`.
```yaml
# Good
initial:
# Bad
initial: null
initial: ~
```
### Comments
Capitalized, with a space after `#`, indented to match current level.
```yaml
# Good
example:
# This is a comment
one: true
# Bad
example:
# Comment at wrong indent
#Missing space
#lowercase start
one: true
```
### Multiline Strings
Use literal `|` (preserves newlines) or folded `>` (joins lines) block scalars.
Avoid `\n` in strings. Prefer no-chomp (`|`, `>`) unless you need strip (`|-`, `>-`).
```yaml
# Good
message: |
Hello!
This is a multiline
notification message.
# Good - folded
description: >
This is a long description that
will be joined into a single line.
# Bad
message: "Hello!\nThis is a multiline\nnotification message.\n"
```
### Templates
Double quotes outside, single quotes inside. Use `states()` and `state_attr()`
helpers, not direct state object access. Split long templates across multiple lines.
```yaml
# Good
value_template: "{{ states('sensor.temperature') }}"
attribute_template: "{{ state_attr('climate.living_room', 'temperature') }}"
# Good - long template split with folded style
value_template: >-
{{
is_state('sensor.bedroom_co_status', 'Ok')
and is_state('sensor.kitchen_co_status', 'Ok')
}}
# Bad - single quotes outside
value_template: '{{ "some_value" == other_value }}'
# Bad - direct state object access
value_template: "{{ states.sensor.temperature.state }}"
```
### Service Action Targets *
Always use `target:` for entity/device/area targeting. Do not put `entity_id` at
the action level or inside `data:`.
```yaml
# Good
actions:
- action: light.turn_on
target:
entity_id: light.living_room
# Bad
actions:
- action: light.turn_on
entity_id: light.living_room
# Bad
actions:
- action: light.turn_on
data:
entity_id: light.living_room
```
### Scalar vs List *
If a property accepts both, use a scalar for single values. Do not wrap a single
value in a list. Do not use comma-separated strings.
```yaml
# Good
entity_id: light.living_room
entity_id:
- light.living_room
- light.office
# Bad - single value in a list
entity_id:
- light.living_room
# Bad - comma separated
entity_id: "light.living_room, light.office"
```
### List of Mappings *
When a property accepts a mapping or list of mappings (e.g., `actions`, `conditions`),
always use a list even for a single item.
```yaml
# Good
actions:
- action: light.turn_on
target:
entity_id: light.living_room
# Bad
actions:
action: light.turn_on
target:
entity_id: light.living_room
```
## Core Competencies
### YAML Configuration
- Follow the YAML Style Guide above for ALL configuration changes
- Use anchors (`&name`) and aliases (`*name`) for DRY configurations
- Understand `!include`, `!include_dir_named`, `!include_dir_list`, `!include_dir_merge_named`, `!include_dir_merge_list`
- To read/query these files from the shell use `yq` (tag-tolerant); PyYAML/Ruby crash on HA tags — see "Working with YAML on the Command Line"
- Know when to use packages for organized configuration
### Automations
- Write automations using both YAML and understand the UI format
- Understand triggers: state, time, event, webhook, mqtt, template, zone, device, etc.
- Understand conditions: state, numeric_state, time, template, zone, and, or, not
- Understand actions: service calls, delays, wait_template, choose, repeat, if/then/else
- Use trigger variables and automation context effectively
- Implement proper error handling with `continue_on_error`
### Templates (Jinja2)
- Write efficient Jinja2 templates for Home Assistant
- Use filters: `float`, `int`, `round`, `timestamp_custom`, `regex_match`, etc.
- Use functions: `states()`, `state_attr()`, `is_state()`, `is_state_attr()`, `has_value()`
- Access trigger data: `trigger.to_state`, `trigger.from_state`, `trigger.entity_id`
- Handle unavailable/unknown states gracefully
### Integrations
- Know common integrations and their configuration patterns
- Understand MQTT, REST, and template-based integrations
- Configure input_* helpers: input_boolean, input_number, input_select, input_text, input_datetime
- Set up utility_meter, statistics, and history_stats sensors
### Lovelace Dashboards
- Write Lovelace YAML configurations
- Know standard cards and their options
- Understand conditional cards, custom cards, and card-mod
- Configure views, themes, and resources
## Best Practices
1. **Always validate** - Remind users to check configuration before restarting
2. **Use secrets** - Never hardcode sensitive data; use `!secret` references
3. **Backup first** - Suggest backups before major changes
4. **Incremental changes** - Make small, testable changes
5. **Comments** - Add YAML comments explaining complex logic
6. **Naming conventions** - Use consistent entity_id naming (e.g., `sensor.room_type_name`)
## Safety Guidelines
- NEVER expose or display contents of `secrets.yaml`
- NEVER include API keys, tokens, or passwords in responses
- NEVER make changes without explicit user approval
- NEVER access `.storage/`, `.cloud/`, or other internal directories
- NEVER attempt to modify Home Assistant's internal databases or registries
- NEVER parse internal JSON files for entity/device/area information
- ALWAYS prefer MCP tools for querying runtime state over internal file access
- ALWAYS use `call_service` through MCP rather than modifying state files
- WARN users before changes that require restart vs reload
- SUGGEST backing up files before major modifications
- CHECK configuration validity when possible
- ALWAYS confirm with user before writing, editing, or deleting any file
## MCP Tools and Configuration Files
You have two complementary interfaces for working with Home Assistant:
### Configuration Files
Read and modify YAML files to understand and change Home Assistant's defined behavior:
- Review `automations.yaml` to understand existing automations
- Edit `configuration.yaml` to add new integrations
- Create new files in `packages/` for organized configuration
- Examine `custom_components/` for custom integration code
### MCP Tools (When Available)
Query and interact with the running Home Assistant instance:
- `get_states`, `search_entities`, `get_home_context` - Current entity states and compact area/domain/entity context
- `call_service` - Control devices (with confirmation)
- `get_history`, `get_logbook` - Historical data
- `get_devices`, `get_areas` - Device and area registry info
- `write_config_safe` - **Safe config writing with automatic validation, content protection, and backup**
- `validate_config` - Check configuration validity
- `get_error_log` - System errors and warnings
- `diagnose_entity` - Comprehensive entity troubleshooting
- `get_agent_capabilities` - OpenCode MCP capabilities and native HA `llm` / MCP readiness
- `get_ha_llm_development_guide` - Upstream references and starter template for native `<integration>/llm.py` providers
- `watch_firmware_update` - **Real-time firmware update monitoring** (ESPHome, WLED, Zigbee, etc.)
- `get_available_updates`, `update_component` - System update management
- `screenshot_url` - **Visual verification** of dashboards and UI pages (requires `screenshot_enabled` option)
### Choosing the Right Approach
| Task | Configuration Files | MCP Tools | hab CLI | zigporter CLI |
|------|---------------------|-----------|---------|---------------|
| Create/edit automations | Primary | **Write with `write_config_safe`** | `hab automation create` | N/A |
| Understand automation logic | Read YAML | Check state with `get_states` | `hab automation get` | N/A |
| Check current device state | Reference only | Primary (`get_home_context` for focused context) | `hab entity get` | N/A |
| Control devices | N/A | `call_service` | `hab action call` | N/A |
| Add new integrations | Primary | N/A | N/A | N/A |
| Troubleshoot issues | Review configs | `diagnose_entity`, `get_error_log` | `hab system health` | N/A |
| Check agent/LLM readiness | N/A | `get_agent_capabilities` | N/A | N/A |
| Develop native HA LLM tools | `custom_components/*/llm.py` | `get_ha_llm_development_guide` | N/A | N/A |
| Find entities | Grep YAML files | `search_entities` | `hab entity list --domain` | N/A |
| View history | N/A | `get_history` | N/A | N/A |
| **Manage dashboards** | Edit YAML | N/A | **`hab dashboard` (primary)** | N/A |
| **Verify UI changes** | N/A | **`screenshot_url`** | N/A | N/A |
| **Manage areas/floors** | N/A | `get_areas` (read-only) | **`hab area/floor` (CRUD)** | N/A |
| **Manage helpers** | N/A | N/A | **`hab helper` (primary)** | N/A |
| **Backups** | N/A | N/A | **`hab backup` (primary)** | N/A |
| **Blueprints** | N/A | N/A | **`hab blueprint` (primary)** | N/A |
| **Update firmware** | N/A | **`watch_firmware_update`** | N/A | N/A |
| **Check for updates** | N/A | `get_available_updates` | N/A | N/A |
| **Update HA Core/OS** | N/A | `update_component` | N/A | N/A |
| **Rename entity with cascade** | N/A | N/A | `hab entity update` (no cascade) | **`zigporter rename-entity` (primary)** |
| **Rename device with cascade** | N/A | N/A | `hab device update` (no cascade) | **`zigporter rename-device` (primary)** |
| **Inspect Zigbee device** | N/A | `get_entity_details` | `hab device list` | **`zigporter inspect --json` (cross-ref ZHA+Z2M+HA)** |
| **List Z2M devices** | N/A | N/A | N/A | **`zigporter list-z2m --json`** |
| **Clean up stale devices** | N/A | N/A | N/A | **`zigporter stale --action`** |
| **Fix post-migration entities** | N/A | N/A | N/A | **`zigporter fix-device --apply`** |
| **Zigbee mesh topology** | N/A | N/A | N/A | **`zigporter network-map`** |
### Update Management (IMPORTANT)
**For device firmware updates (ESPHome, WLED, Zigbee, etc.):**
Always use `watch_firmware_update` - it provides real-time visual progress:
```
watch_firmware_update(entity_id="update.device_firmware", start_update=true)
```
This single tool handles: starting the update, monitoring progress, and reporting results.
**For system updates (Core, OS, Supervisor, Apps):**
```
1. get_available_updates() -> Check what needs updating
2. update_component(component="core") -> Start update (returns job_id)
3. get_update_progress(job_id="...") -> Monitor progress
```
**Both approaches are valid and complementary.** Use configuration files for defining behavior and MCP tools for runtime interaction.
## Documentation Currency
Home Assistant releases monthly updates with new features, deprecations, and breaking changes. Your training data may be outdated. **Always verify configuration syntax against current documentation.**
### Before Writing or Modifying Configuration
**ALWAYS use these MCP tools before suggesting configuration changes:**
1. **Check the installed version**: Use `get_config` to see what HA version is running
2. **Fetch current integration docs**: Use `get_integration_docs` to get current YAML syntax
3. **Check for breaking changes**: Use `get_breaking_changes` to see recent syntax changes
4. **Write config safely**: Use `write_config_safe` with `dry_run=true` to validate before presenting to user
### Documentation Tools (MCP)
| Tool | When to Use |
|------|-------------|
| `get_integration_docs` | Before writing ANY integration configuration |
| `get_breaking_changes` | When user reports config stopped working after update |
| `write_config_safe` | **ALWAYS use to write config files** — validates, blocks accidental content loss, and auto-restores on failure |
| `check_config_syntax` | Quick ad-hoc deprecation check (write_config_safe includes this automatically) |
### Workflow Example
When a user asks "Help me set up a template sensor":
```
1. get_config() -> Check HA version (e.g., 2024.12.1)
2. get_integration_docs("template") -> Get current syntax and examples
3. read_file(path) -> Read the EXISTING file content first
4. Draft configuration: include ALL existing content + new changes
5. write_config_safe(path, yaml, dry_run=true) -> Pre-validate everything
6. If errors: fix and repeat step 5
7. Present validated config to user and get approval
8. write_config_safe(path, yaml) -> Write for real (auto backup + validation)
```
### Common Deprecation Patterns
Be especially careful with these frequently-changed areas:
- **Template sensors/binary_sensors**: `platform: template` under `sensor:` is deprecated; use top-level `template:`
- **Entity configurations**: Many moved from YAML to UI-based config
- **Trigger-based templates**: Newer syntax preferred over legacy template sensors
- **Device triggers**: Syntax evolves with new device types
- **MQTT platform syntax**: `platform: mqtt` under domain keys is deprecated; use top-level `mqtt:` key
- **Direct state access**: `states.sensor.x.state` is fragile; use `states('sensor.x')` helper
- **entity_id in data**: Deprecated; use `target:` for service call targeting
**When in doubt, fetch the docs. Never rely solely on training data for configuration syntax.**
## Common Tasks
### Creating an Automation
1. **Read the existing `automations.yaml` first** — you must include ALL existing automations in the final write
2. Understand the goal and identify trigger conditions
3. Determine required entities (search if MCP available)
4. Draft the automation YAML with clear comments
5. **Show the draft to the user and wait for approval** — the draft must contain all existing automations plus the new one
6. Only write the file after explicit user confirmation
7. Suggest testing approach
> **WARNING:** Never write partial content to ANY config file. Always read the existing file first and include ALL existing content in your write. `write_config_safe` will block writes that would reduce list entries, remove top-level keys, or significantly shrink the file — but you should verify this yourself before presenting the draft to the user.
### Troubleshooting
1. Check entity states and history (via MCP if available)
2. Review relevant configuration files
3. Check Home Assistant logs for errors
4. Identify common issues (unavailable entities, template errors, timing issues)
5. **Present findings and wait for user to request specific fixes**
### Optimizing Configuration
1. Identify redundant or inefficient patterns
2. **Present recommendations to user**
3. Wait for user to approve specific changes
4. Implement only the changes the user explicitly approves
automations.yaml
-114
View File
@@ -1,114 +0,0 @@
- id: '1778927514490'
alias: NSPanel Easy Configuration (v2026.5.5)
description: ''
use_blueprint:
path: edwardtfn/nspanel_easy_blueprint.yaml
input:
nspanel_name: 369e58c3779ff3dd9a0b4c59fadeac4f
weather_entity: weather.astroweather_backyard
indoortemp: sensor.lounge_inside_temperature
- id: '1778927924212'
alias: NSPanel Easy Configuration (v2026.5.5)
description: ''
use_blueprint:
path: edwardtfn/nspanel_easy_blueprint.yaml
input:
nspanel_name: 369e58c3779ff3dd9a0b4c59fadeac4f
button_page01_label: Lounge Scenes
button_pages_icon_size: '8'
entity01: script.nspanel_lounge_scene_bright
entity01_name: Bright
entity01_icon: mdi:brightness-7
entity01_confirm: false
entity02: script.nspanel_lounge_scene_tv_general
entity02_name: TV General
entity02_icon: mdi:television
entity02_confirm: false
entity03: script.nspanel_lounge_scene_movie
entity03_name: Movie
entity03_icon: mdi:movie-open
entity03_confirm: false
entity04: script.nspanel_lounge_scene_balanced
entity04_name: Balanced
entity04_icon: mdi:scale-balance
entity04_confirm: false
entity05: script.nspanel_lounge_scene_warm_cozy
entity05_name: Warm Cozy
entity05_icon: mdi:fireplace
entity05_confirm: false
entity06: script.nspanel_lounge_scene_reading
entity06_name: Reading
entity06_icon: mdi:book-open-page-variant
entity06_confirm: false
entity07: script.nspanel_lounge_scene_dining
entity07_name: Dining
entity07_icon: mdi:silverware-fork-knife
entity07_confirm: false
entity08: script.nspanel_lounge_scene_all_off
entity08_name: All Off
entity08_icon: mdi:power
entity08_confirm: false
mode: single
- id: '1778929633433'
alias: NSPanel Easy Configuration (v2026.5.5)
description: ''
use_blueprint:
path: edwardtfn/nspanel_easy_blueprint.yaml
input:
nspanel_name: 369e58c3779ff3dd9a0b4c59fadeac4f
button_page01_label: Lounge Scenes
button_pages_icon_size: '8'
entity01: script.nspanel_lounge_scene_bright
entity01_name: Bright
entity01_icon: mdi:brightness-7
entity01_confirm: false
entity02: script.nspanel_lounge_scene_tv_general
entity02_name: TV General
entity02_icon: mdi:television
entity02_confirm: false
entity03: script.nspanel_lounge_scene_movie
entity03_name: Movie
entity03_icon: mdi:movie-open
entity03_confirm: false
entity04: script.nspanel_lounge_scene_balanced
entity04_name: Balanced
entity04_icon: mdi:scale-balance
entity04_confirm: false
entity05: script.nspanel_lounge_scene_warm_cozy
entity05_name: Warm Cozy
entity05_icon: mdi:fireplace
entity05_confirm: false
entity06: script.nspanel_lounge_scene_reading
entity06_name: Reading
entity06_icon: mdi:book-open-page-variant
entity06_confirm: false
entity07: script.nspanel_lounge_scene_dining
entity07_name: Dining
entity07_icon: mdi:silverware-fork-knife
entity07_confirm: false
entity08: script.nspanel_lounge_scene_all_off
entity08_name: All Off
entity08_icon: mdi:power
entity08_confirm: false
mode: single
- id: '1778930023427'
alias: NSPanel Lounge Controller
description: ''
use_blueprint:
path: edwardtfn/nspanel_easy_blueprint.yaml
input:
nspanel_name: 369e58c3779ff3dd9a0b4c59fadeac4f
- id: '1778930202677'
alias: NSPanel Lounge Controller
description: ''
use_blueprint:
path: edwardtfn/nspanel_easy_blueprint.yaml
input:
nspanel_name: 369e58c3779ff3dd9a0b4c59fadeac4f
- id: '1778930948144'
alias: Lounge NSPanel Controls
description: ''
use_blueprint:
path: edwardtfn/nspanel_easy_blueprint.yaml
input:
nspanel_name: 369e58c3779ff3dd9a0b4c59fadeac4f
automations/random_actions_security.yaml
-26
View File
@@ -1,26 +0,0 @@
- id: do_random_actions_when_away
alias: Activate Random Actions for Security
mode: parallel # Enable parallel executions
trigger:
- platform: time_pattern
minutes: /5
condition:
alias: "Away routine active, nearly sunset, and all family not home"
condition: and
conditions:
- condition: sun
after: sunset
after_offset: -00:30:00 #30 mins before
- condition: state
entity_id: input_boolean.away_occupied_routine
state: "on"
- condition: state
entity_id: group.family_away
state: "not_home"
action:
service: script.light_duration
data:
# Pass randomly selected light from "group.simulation_lights" as script variable "light"
light: "{{states.group.simulation_lights.attributes.entity_id | random}}"
# random value between 5 & 29
duration: "00:{{ '{:02}'.format(range(5,29) | random | int) }}:00"
automations/weekly_battery_notifications_check.yaml
-15
View File
@@ -1,15 +0,0 @@
- id: "1635929281159"
alias: Weekly Low battery level detection
description: ""
use_blueprint:
path: sbyx/low-battery-level-detection-notification-for-all-battery-sensors.yaml
input:
day: 1
time: "21:00:00"
actions:
- service: notify.pushover_zorruno
data:
message: >
Weekly Battery Check. Low Devices:
{{sensors}}
title: View Road Sensors
automations/zigbee_low_battery_notifications_2.yaml
-32
View File
@@ -1,32 +0,0 @@
- id: notify_if_batteries_are_low
alias: Daily alert that zigbee batteries Are Low
initial_state: true
trigger:
- platform: time
at: "19:00:00"
condition:
- condition: or
conditions:
- condition: template
value_template: >
{% set min_battery_level = 20 -%}
{% set ns = namespace(found=false) -%}
{% for entity_id in states.group.battery_levels.attributes.entity_id -%}
{% set parts = entity_id.split('.') -%}
{% if (states(entity_id) | replace("%","") | int) < min_battery_level -%}
{% set ns.found = true -%}
{% endif -%}
{% endfor -%}
{{ ns.found }}
action:
- service: notify.pushover_zorruno
data:
title: View Road Sensors
message: >
{%- set min_battery_level = 20 -%}
{%- for entity_id in states.group.battery_levels.attributes.entity_id -%}
{%- set parts = entity_id.split('.') -%}
{%- if (states(entity_id) | replace("%","") | int) < min_battery_level -%}
{{ states[parts[0]][parts[1]].name }} level is {{ states(entity_id) }}%.{{ '\n' }}
{%- endif -%}
{%- endfor -%}
configuration.yaml
-3
View File
@@ -39,6 +39,3 @@ zha:
salus_provider: true
inovelli_provider: true
thirdreality_provider: true
device_tracker:
- platform: bluetooth_le_tracker
custom_zha_quirks/ts0207_rain.py.old
-137
View File
@@ -1,137 +0,0 @@
"""Quirk for TS0207 rain sensors."""
import zigpy.types as t
from typing import Any, Type
from zigpy.profiles import zha
from zigpy.quirks import CustomDevice, CustomCluster
from zigpy.zcl.clusters.general import (
Basic,
Groups,
Identify,
OnOff,
Ota,
PowerConfiguration,
Scenes,
Time,
)
from zigpy.zcl.clusters.lightlink import LightLink
from zigpy.zcl.clusters.security import IasZone
from zhaquirks.const import (
DEVICE_TYPE,
ENDPOINTS,
INPUT_CLUSTERS,
MODELS_INFO,
OUTPUT_CLUSTERS,
PROFILE_ID,
)
from zhaquirks.tuya.mcu import TuyaMCUCluster
from zhaquirks.tuya import (
TuyaManufCluster,
DPToAttributeMapping,
EnchantedDevice,
TuyaNoBindPowerConfigurationCluster,
)
ZONE_TYPE = 0x0001
class TuyaSolarRainSensorCluster(TuyaMCUCluster):
"""Tuya manufacturer cluster."""
attributes = TuyaMCUCluster.attributes.copy()
attributes.update(
{
0xEF65: ("light_intensity", t.uint32_t, True),
0xEF66: ("average_light_intensity_20mins", t.uint32_t, True),
0xEF67: ("todays_max_light_intensity", t.uint32_t, True),
0xEF68: ("cleaning_reminder", t.Bool, True),
0xEF69: ("rain_sensor_voltage", t.uint32_t, True),
}
)
dp_to_attribute: dict[int, DPToAttributeMapping] = {
101: DPToAttributeMapping(
TuyaMCUCluster.ep_attribute,
"light_intensity",
),
102: DPToAttributeMapping(
TuyaMCUCluster.ep_attribute,
"average_light_intensity_20mins",
),
103: DPToAttributeMapping(
TuyaMCUCluster.ep_attribute,
"todays_max_light_intensity",
),
104: DPToAttributeMapping(
TuyaMCUCluster.ep_attribute,
"cleaning_reminder",
),
105: DPToAttributeMapping(
TuyaMCUCluster.ep_attribute,
"rain_sensor_voltage",
),
}
data_point_handlers = {
101: "_dp_2_attr_update",
102: "_dp_2_attr_update",
103: "_dp_2_attr_update",
104: "_dp_2_attr_update",
105: "_dp_2_attr_update",
}
class TuyaIasZone(CustomCluster, IasZone):
"""IAS Zone for rain sensors."""
_CONSTANT_ATTRIBUTES = {ZONE_TYPE: IasZone.ZoneType.Water_Sensor}
class TuyaSolarRainSensor(EnchantedDevice):
"""TS0207 Rain sensor quirk."""
signature = {
MODELS_INFO: [("_TZ3210_tgvtvdoc", "TS0207")],
ENDPOINTS: {
1: {
PROFILE_ID: zha.PROFILE_ID,
DEVICE_TYPE: zha.DeviceType.IAS_ZONE,
INPUT_CLUSTERS: [
Basic.cluster_id,
PowerConfiguration.cluster_id,
Groups.cluster_id,
Scenes.cluster_id,
IasZone.cluster_id,
TuyaMCUCluster.cluster_id,
],
OUTPUT_CLUSTERS: [
Identify.cluster_id,
Groups.cluster_id,
OnOff.cluster_id,
Time.cluster_id,
Ota.cluster_id,
LightLink.cluster_id,
],
},
},
}
replacement = {
ENDPOINTS: {
1: {
PROFILE_ID: zha.PROFILE_ID,
DEVICE_TYPE: zha.DeviceType.IAS_ZONE,
INPUT_CLUSTERS: [
Basic.cluster_id,
Groups.cluster_id,
Scenes.cluster_id,
TuyaNoBindPowerConfigurationCluster,
TuyaIasZone,
TuyaSolarRainSensorCluster,
],
OUTPUT_CLUSTERS: [
Time.cluster_id,
Ota.cluster_id,
],
},
},
}
custom_zha_quirks/ts0601_motion copy.py.old
-358
View File
@@ -1,358 +0,0 @@
# rivsc https://blog.rivsc.ovh
import logging
from typing import Final
from zigpy.quirks.v2 import QuirkBuilder, BinarySensorDeviceClass
import zigpy.types as t
from zigpy.zcl.foundation import ZCLAttributeDef
from zigpy.zcl.clusters.measurement import (
IlluminanceMeasurement,
OccupancySensing,
)
from zigpy.zcl.clusters.security import IasZone
from zigpy.quirks.v2.homeassistant import EntityPlatform, EntityType
from zhaquirks.tuya import (
TuyaLocalCluster,
TuyaPowerConfigurationCluster2AAA,
)
from zhaquirks.tuya.mcu import TuyaMCUCluster, DPToAttributeMapping
class PresenceState(t.enum8):
"""Presence State values"""
none = 0x00
presence = 0x01
peaceful = 0x02
small_movement = 0x03
large_movement = 0x04
class TuyaOccupancySensing(OccupancySensing, TuyaLocalCluster):
"""Tuya local OccupancySensing cluster."""
class TuyaIlluminanceMeasurement(IlluminanceMeasurement, TuyaLocalCluster):
"""Tuya local IlluminanceMeasurement cluster."""
class HumanPresenceSensorManufCluster(TuyaMCUCluster):
"""Human Presence Sensor ZG-205Z (5.8GHz)"""
class AttributeDefs(TuyaMCUCluster.AttributeDefs):
"""Tuya DataPoints attributes"""
# Presence state
presence_state: Final = ZCLAttributeDef(
id=0x0001, # DP 1
type=t.uint16_t,
access="rp",
is_manufacturer_specific=True,
)
# Target distance
target_distance: Final = ZCLAttributeDef(
id=0x0101, # DP 101
type=t.uint16_t,
access="rp",
is_manufacturer_specific=True,
)
# Illuminance value
illuminance_lux: Final = ZCLAttributeDef(
id=0x0102, # DP 102
type=t.uint16_t,
access="rp",
is_manufacturer_specific=True,
)
# None delay time (presence keep time)
none_delay_time: Final = ZCLAttributeDef(
id=0x0103, # DP 103
type=t.uint16_t,
is_manufacturer_specific=True,
)
# Indicator
indicator: Final = ZCLAttributeDef(
id=0x0104, # DP 104
type=t.Bool,
is_manufacturer_specific=True,
)
# Move detection max distance
move_detection_max: Final = ZCLAttributeDef(
id=0x0107, # DP 107
type=t.uint16_t,
is_manufacturer_specific=True,
)
# Move detection min distance
move_detection_min: Final = ZCLAttributeDef(
id=0x0108, # DP 108
type=t.uint16_t,
is_manufacturer_specific=True,
)
# Breath detection max distance
breath_detection_max: Final = ZCLAttributeDef(
id=0x0109, # DP 109
type=t.uint16_t,
is_manufacturer_specific=True,
)
# Breath detection min distance
breath_detection_min: Final = ZCLAttributeDef(
id=0x0110, # DP 110
type=t.uint16_t,
is_manufacturer_specific=True,
)
# Small move detection max distance
small_move_detection_max: Final = ZCLAttributeDef(
id=0x0114, # DP 114
type=t.uint16_t,
is_manufacturer_specific=True,
)
# Small move detection min distance
small_move_detection_min: Final = ZCLAttributeDef(
id=0x0115, # DP 115
type=t.uint16_t,
is_manufacturer_specific=True,
)
# Move sensitivity
move_sensitivity: Final = ZCLAttributeDef(
id=0x0116, # DP 116
type=t.uint8_t,
is_manufacturer_specific=True,
)
# Small move sensitivity
small_move_sensitivity: Final = ZCLAttributeDef(
id=0x0117, # DP 117
type=t.uint8_t,
is_manufacturer_specific=True,
)
# Breath sensitivity
breath_sensitivity: Final = ZCLAttributeDef(
id=0x0118, # DP 118
type=t.uint8_t,
is_manufacturer_specific=True,
)
dp_to_attribute: dict[int, DPToAttributeMapping] = {
1: DPToAttributeMapping(
TuyaMCUCluster.ep_attribute,
"presence_state",
converter=PresenceState
),
101: DPToAttributeMapping(
TuyaMCUCluster.ep_attribute,
"target_distance",
converter=lambda x: x / 100 if x is not None else 0
),
102: DPToAttributeMapping(
TuyaMCUCluster.ep_attribute,
"illuminance_lux",
),
103: DPToAttributeMapping(
TuyaMCUCluster.ep_attribute,
"none_delay_time",
converter=lambda x: x if x is not None else 30
),
104: DPToAttributeMapping(
TuyaMCUCluster.ep_attribute,
"indicator",
),
107: DPToAttributeMapping(
TuyaMCUCluster.ep_attribute,
"move_detection_max",
converter=lambda x: x / 100 if x is not None else 10
),
108: DPToAttributeMapping(
TuyaMCUCluster.ep_attribute,
"move_detection_min",
converter=lambda x: x / 100 if x is not None else 0
),
109: DPToAttributeMapping(
TuyaMCUCluster.ep_attribute,
"breath_detection_max",
converter=lambda x: x / 100 if x is not None else 6
),
110: DPToAttributeMapping(
TuyaMCUCluster.ep_attribute,
"breath_detection_min",
converter=lambda x: x / 100 if x is not None else 0
),
114: DPToAttributeMapping(
TuyaMCUCluster.ep_attribute,
"small_move_detection_max",
converter=lambda x: x / 100 if x is not None else 6
),
115: DPToAttributeMapping(
TuyaMCUCluster.ep_attribute,
"small_move_detection_min",
converter=lambda x: x / 100 if x is not None else 0
),
116: DPToAttributeMapping(
TuyaMCUCluster.ep_attribute,
"move_sensitivity",
converter=lambda x: x if x is not None else 5
),
117: DPToAttributeMapping(
TuyaMCUCluster.ep_attribute,
"small_move_sensitivity",
converter=lambda x: x if x is not None else 5
),
118: DPToAttributeMapping(
TuyaMCUCluster.ep_attribute,
"breath_sensitivity",
converter=lambda x: x if x is not None else 5
),
}
data_point_handlers = {
1: "_dp_2_attr_update",
101: "_dp_2_attr_update",
102: "_dp_2_attr_update",
103: "_dp_2_attr_update",
104: "_dp_2_attr_update",
107: "_dp_2_attr_update",
108: "_dp_2_attr_update",
109: "_dp_2_attr_update",
110: "_dp_2_attr_update",
114: "_dp_2_attr_update",
115: "_dp_2_attr_update",
116: "_dp_2_attr_update",
117: "_dp_2_attr_update",
118: "_dp_2_attr_update",
}
(
QuirkBuilder("_TZE204_dapwryy7", "TS0601")
.skip_configuration()
.removes(IasZone.cluster_id)
.adds(HumanPresenceSensorManufCluster)
#.adds(TuyaOccupancySensing)
.replaces(TuyaPowerConfigurationCluster2AAA)
.replaces(TuyaIlluminanceMeasurement)
.binary_sensor(
"presence_state",
HumanPresenceSensorManufCluster.cluster_id,
endpoint_id=1,
#entity_type=EntityType.STANDARD, # very soon (zigpy channel #dev on github
device_class=BinarySensorDeviceClass.OCCUPANCY,
fallback_name="Presence"
)
.enum(
HumanPresenceSensorManufCluster.AttributeDefs.presence_state.name,
PresenceState,
HumanPresenceSensorManufCluster.cluster_id,
entity_platform=EntityPlatform.SENSOR,
entity_type=EntityType.STANDARD,
fallback_name="Presence State",
translation_key="presence_state"
)
.number(
HumanPresenceSensorManufCluster.AttributeDefs.target_distance.name,
HumanPresenceSensorManufCluster.cluster_id,
step=0.01,
min_value=0,
max_value=10,
#unit="m", # fail :/
fallback_name="Target Distance (m)",
translation_key="target_distance",
#entity_type=EntityType.STANDARD # not yet :/
)
.number(
HumanPresenceSensorManufCluster.AttributeDefs.none_delay_time.name,
HumanPresenceSensorManufCluster.cluster_id,
step=1,
min_value=0,
max_value=28800,
unit="s",
fallback_name="Hold Delay Time",
translation_key="none_delay_time"
)
.switch(
HumanPresenceSensorManufCluster.AttributeDefs.indicator.name,
HumanPresenceSensorManufCluster.cluster_id,
fallback_name="LED Indicator",
translation_key="indicator"
)
.number(
HumanPresenceSensorManufCluster.AttributeDefs.move_detection_max.name,
HumanPresenceSensorManufCluster.cluster_id,
step=0.01,
min_value=0,
max_value=10,
#unit="m",
fallback_name="Move Detection Max Distance (m)",
translation_key="move_detection_max"
)
.number(
HumanPresenceSensorManufCluster.AttributeDefs.move_detection_min.name,
HumanPresenceSensorManufCluster.cluster_id,
step=0.01,
min_value=0,
max_value=10,
#unit="m",
fallback_name="Move Detection Min Distance (m)",
translation_key="move_detection_min"
)
.number(
HumanPresenceSensorManufCluster.AttributeDefs.small_move_detection_max.name,
HumanPresenceSensorManufCluster.cluster_id,
step=0.01,
min_value=0,
max_value=6,
#unit="m",
fallback_name="Small Move Detection Max Distance (m)",
translation_key="small_move_detection_max"
)
.number(
HumanPresenceSensorManufCluster.AttributeDefs.small_move_detection_min.name,
HumanPresenceSensorManufCluster.cluster_id,
step=0.01,
min_value=0,
max_value=6,
#unit="m",
fallback_name="Small Move Detection Min Distance (m)",
translation_key="small_move_detection_min"
)
.number(
HumanPresenceSensorManufCluster.AttributeDefs.breath_detection_max.name,
HumanPresenceSensorManufCluster.cluster_id,
step=0.01,
min_value=0,
max_value=6,
#unit="m",
fallback_name="Breath Detection Max Distance (m)",
translation_key="breath_detection_max"
)
.number(
HumanPresenceSensorManufCluster.AttributeDefs.breath_detection_min.name,
HumanPresenceSensorManufCluster.cluster_id,
step=0.01,
min_value=0,
max_value=6,
#unit="m",
fallback_name="Breath Detection Min Distance (m)",
translation_key="breath_detection_min"
)
.number(
HumanPresenceSensorManufCluster.AttributeDefs.move_sensitivity.name,
HumanPresenceSensorManufCluster.cluster_id,
step=1,
min_value=0,
max_value=10,
fallback_name="Move Sensitivity",
translation_key="move_sensitivity"
)
.number(
HumanPresenceSensorManufCluster.AttributeDefs.small_move_sensitivity.name,
HumanPresenceSensorManufCluster.cluster_id,
step=1,
min_value=0,
max_value=10,
fallback_name="Small Move Sensitivity",
translation_key="small_move_sensitivity"
)
.number(
HumanPresenceSensorManufCluster.AttributeDefs.breath_sensitivity.name,
HumanPresenceSensorManufCluster.cluster_id,
step=1,
min_value=0,
max_value=10,
fallback_name="Breath Sensitivity",
translation_key="breath_sensitivity"
)
.add_to_registry()
)
custom_zha_quirks/ts0601_power_din_tuya.py.old
-293
View File
@@ -1,293 +0,0 @@
"""Tuya Din Power Meter."""
from zigpy.profiles import zha
import zigpy.types as t
from zigpy.zcl.clusters.general import Basic, Groups, Ota, Scenes, Time
from zigpy.zcl.clusters.homeautomation import ElectricalMeasurement
from zigpy.zcl.clusters.smartenergy import Metering
from zhaquirks import Bus, LocalDataCluster
from zhaquirks.const import (
DEVICE_TYPE,
ENDPOINTS,
INPUT_CLUSTERS,
MODELS_INFO,
OUTPUT_CLUSTERS,
PROFILE_ID,
)
from zhaquirks.tuya import TuyaManufClusterAttributes, TuyaOnOff, TuyaSwitch
TUYA_TOTAL_ENERGY_ATTR = 0x0211
TUYA_CURRENT_ATTR = 0x0212
TUYA_POWER_ATTR = 0x0213
TUYA_VOLTAGE_ATTR = 0x0214
TUYA_DIN_SWITCH_ATTR = 0x0101
SWITCH_EVENT = "switch_event"
"""Hiking Power Meter Attributes"""
HIKING_DIN_SWITCH_ATTR = 0x0110
HIKING_TOTAL_ENERGY_DELIVERED_ATTR = 0x0201
HIKING_TOTAL_ENERGY_RECEIVED_ATTR = 0x0266
HIKING_VOLTAGE_CURRENT_ATTR = 0x0006
HIKING_POWER_ATTR = 0x0267
HIKING_FREQUENCY_ATTR = 0x0269
HIKING_POWER_FACTOR_ATTR = 0x026F
HIKING_TOTAL_REACTIVE_ATTR = 0x026D
HIKING_REACTIVE_POWER_ATTR = 0x026E
class TuyaManufClusterDinPower(TuyaManufClusterAttributes):
"""Manufacturer Specific Cluster of the Tuya Power Meter device."""
attributes = {
TUYA_TOTAL_ENERGY_ATTR: ("energy", t.uint32_t, True),
TUYA_CURRENT_ATTR: ("current", t.int16s, True),
TUYA_POWER_ATTR: ("power", t.uint16_t, True),
TUYA_VOLTAGE_ATTR: ("voltage", t.uint16_t, True),
TUYA_DIN_SWITCH_ATTR: ("switch", t.uint8_t, True),
}
def _update_attribute(self, attrid, value):
super()._update_attribute(attrid, value)
if attrid == TUYA_TOTAL_ENERGY_ATTR:
self.endpoint.smartenergy_metering.energy_deliver_reported(value / 100)
elif attrid == TUYA_CURRENT_ATTR:
self.endpoint.electrical_measurement.current_reported(value)
elif attrid == TUYA_POWER_ATTR:
self.endpoint.electrical_measurement.power_reported(value / 10)
elif attrid == TUYA_VOLTAGE_ATTR:
self.endpoint.electrical_measurement.voltage_reported(value / 10)
elif attrid == TUYA_DIN_SWITCH_ATTR:
self.endpoint.device.switch_bus.listener_event(
SWITCH_EVENT, self.endpoint.endpoint_id, value
)
class TuyaPowerMeasurement(LocalDataCluster, ElectricalMeasurement):
"""Custom class for power, voltage and current measurement."""
POWER_ID = 0x050B
VOLTAGE_ID = 0x0505
CURRENT_ID = 0x0508
REACTIVE_POWER_ID = 0x050E
AC_FREQUENCY_ID = 0x0300
TOTAL_REACTIVE_POWER_ID = 0x0305
POWER_FACTOR_ID = 0x0510
AC_CURRENT_MULTIPLIER = 0x0602
AC_CURRENT_DIVISOR = 0x0603
AC_FREQUENCY_MULTIPLIER = 0x0400
AC_FREQUENCY_DIVISOR = 0x0401
_CONSTANT_ATTRIBUTES = {
AC_CURRENT_MULTIPLIER: 1,
AC_CURRENT_DIVISOR: 1000,
AC_FREQUENCY_MULTIPLIER: 1,
AC_FREQUENCY_DIVISOR: 100,
}
def voltage_reported(self, value):
"""Voltage reported."""
self._update_attribute(self.VOLTAGE_ID, value)
def power_reported(self, value):
"""Power reported."""
self._update_attribute(self.POWER_ID, value)
def power_factor_reported(self, value):
"""Power Factor reported."""
self._update_attribute(self.POWER_FACTOR_ID, value)
def reactive_power_reported(self, value):
"""Reactive Power reported."""
self._update_attribute(self.REACTIVE_POWER_ID, value)
def current_reported(self, value):
"""Ampers reported."""
self._update_attribute(self.CURRENT_ID, value)
def frequency_reported(self, value):
"""AC Frequency reported."""
self._update_attribute(self.AC_FREQUENCY_ID, value)
def reactive_energy_reported(self, value):
"""Summation Reactive Energy reported."""
self._update_attribute(self.TOTAL_REACTIVE_POWER_ID, value)
class TuyaElectricalMeasurement(LocalDataCluster, Metering):
"""Custom class for total energy measurement."""
CURRENT_DELIVERED_ID = 0x0000
CURRENT_RECEIVED_ID = 0x0001
POWER_WATT = 0x0000
"""Setting unit of measurement."""
_CONSTANT_ATTRIBUTES = {0x0300: POWER_WATT}
def energy_deliver_reported(self, value):
"""Summation Energy Deliver reported."""
self._update_attribute(self.CURRENT_DELIVERED_ID, value)
def energy_receive_reported(self, value):
"""Summation Energy Receive reported."""
self._update_attribute(self.CURRENT_RECEIVED_ID, value)
class HikingManufClusterDinPower(TuyaManufClusterAttributes):
"""Manufacturer Specific Cluster of the Hiking Power Meter device."""
attributes = {
HIKING_DIN_SWITCH_ATTR: ("switch", t.uint8_t, True),
HIKING_TOTAL_ENERGY_DELIVERED_ATTR: ("energy_delivered", t.uint32_t, True),
HIKING_TOTAL_ENERGY_RECEIVED_ATTR: ("energy_received", t.uint16_t, True),
HIKING_VOLTAGE_CURRENT_ATTR: ("voltage_current", t.uint32_t, True),
HIKING_POWER_ATTR: ("power", t.uint16_t, True),
HIKING_FREQUENCY_ATTR: ("frequency", t.uint16_t, True),
HIKING_TOTAL_REACTIVE_ATTR: ("total_reactive_energy", t.int32s, True),
HIKING_REACTIVE_POWER_ATTR: ("reactive_power", t.int16s, True),
HIKING_POWER_FACTOR_ATTR: ("power_factor", t.uint16_t, True),
}
def _update_attribute(self, attrid, value):
super()._update_attribute(attrid, value)
if attrid == HIKING_DIN_SWITCH_ATTR:
self.endpoint.device.switch_bus.listener_event(SWITCH_EVENT, 16, value)
elif attrid == HIKING_TOTAL_ENERGY_DELIVERED_ATTR:
self.endpoint.smartenergy_metering.energy_deliver_reported(value / 100)
elif attrid == HIKING_TOTAL_ENERGY_RECEIVED_ATTR:
self.endpoint.smartenergy_metering.energy_receive_reported(value / 100)
elif attrid == HIKING_VOLTAGE_CURRENT_ATTR:
self.endpoint.electrical_measurement.current_reported(value >> 16)
self.endpoint.electrical_measurement.voltage_reported(
(value & 0x0000FFFF) / 10
)
elif attrid == HIKING_POWER_ATTR:
self.endpoint.electrical_measurement.power_reported(value)
elif attrid == HIKING_FREQUENCY_ATTR:
self.endpoint.electrical_measurement.frequency_reported(value)
elif attrid == HIKING_TOTAL_REACTIVE_ATTR:
self.endpoint.electrical_measurement.reactive_energy_reported(value)
elif attrid == HIKING_REACTIVE_POWER_ATTR:
self.endpoint.electrical_measurement.reactive_power_reported(value)
elif attrid == HIKING_POWER_FACTOR_ATTR:
self.endpoint.electrical_measurement.power_factor_reported(value / 10)
class TuyaPowerMeter(TuyaSwitch):
"""Tuya power meter device."""
def __init__(self, *args, **kwargs):
"""Init device."""
self.switch_bus = Bus()
super().__init__(*args, **kwargs)
signature = {
# "node_descriptor": "<NodeDescriptor byte1=1 byte2=64 mac_capability_flags=142 manufacturer_code=4098
# maximum_buffer_size=82 maximum_incoming_transfer_size=82 server_mask=11264
# maximum_outgoing_transfer_size=82 descriptor_capability_field=0>",
# device_version=1
# input_clusters=[0x0000, 0x0004, 0x0005, 0xef00]
# output_clusters=[0x000a, 0x0019]
MODELS_INFO: [
("_TZE200_byzdayie", "TS0601"),
("_TZE200_ewxhg6o9", "TS0601"),
],
ENDPOINTS: {
# <SimpleDescriptor endpoint=1 profile=260 device_type=51
# device_version=1
# input_clusters=[0, 4, 5, 61184]
# output_clusters=[10, 25]>
1: {
PROFILE_ID: zha.PROFILE_ID,
DEVICE_TYPE: zha.DeviceType.SMART_PLUG,
INPUT_CLUSTERS: [
Basic.cluster_id,
Groups.cluster_id,
Scenes.cluster_id,
TuyaManufClusterAttributes.cluster_id,
],
OUTPUT_CLUSTERS: [Time.cluster_id, Ota.cluster_id],
}
},
}
replacement = {
ENDPOINTS: {
1: {
PROFILE_ID: zha.PROFILE_ID,
DEVICE_TYPE: zha.DeviceType.SMART_PLUG,
INPUT_CLUSTERS: [
Basic.cluster_id,
Groups.cluster_id,
Scenes.cluster_id,
TuyaManufClusterDinPower,
TuyaPowerMeasurement,
TuyaElectricalMeasurement,
TuyaOnOff,
],
OUTPUT_CLUSTERS: [Time.cluster_id, Ota.cluster_id],
}
}
}
class HikingPowerMeter(TuyaSwitch):
"""Hiking Power Meter Device - DDS238-2."""
signature = {
# "node_descriptor": "<NodeDescriptor byte1=1 byte2=64 mac_capability_flags=142 manufacturer_code=4098
# maximum_buffer_size=82 maximum_incoming_transfer_size=82 server_mask=11264
# maximum_outgoing_transfer_size=82 descriptor_capability_field=0>",
# device_version=1
# input_clusters=[0x0000, 0x0004, 0x0005, 0xef00]
# output_clusters=[0x000a, 0x0019]
MODELS_INFO: [
("_TZE200_bkkmqmyo", "TS0601"),
("_TZE204_81yrt3lo", "TS0601"),
],
ENDPOINTS: {
# <SimpleDescriptor endpoint=1 profile=260 device_type=51
# device_version=1
# input_clusters=[0, 4, 5, 61184]
# output_clusters=[10, 25]>
1: {
PROFILE_ID: zha.PROFILE_ID,
DEVICE_TYPE: zha.DeviceType.SMART_PLUG,
INPUT_CLUSTERS: [
Basic.cluster_id,
Groups.cluster_id,
Scenes.cluster_id,
TuyaManufClusterAttributes.cluster_id,
],
OUTPUT_CLUSTERS: [Time.cluster_id, Ota.cluster_id],
}
},
}
replacement = {
ENDPOINTS: {
1: {
PROFILE_ID: zha.PROFILE_ID,
DEVICE_TYPE: zha.DeviceType.SMART_PLUG,
INPUT_CLUSTERS: [
Basic.cluster_id,
Groups.cluster_id,
Scenes.cluster_id,
HikingManufClusterDinPower,
TuyaElectricalMeasurement,
TuyaPowerMeasurement,
],
OUTPUT_CLUSTERS: [Time.cluster_id, Ota.cluster_id],
},
16: {
PROFILE_ID: zha.PROFILE_ID,
DEVICE_TYPE: zha.DeviceType.SMART_PLUG,
INPUT_CLUSTERS: [
TuyaOnOff,
],
OUTPUT_CLUSTERS: [],
},
}
}
custom_zha_quirks/ts0601_smoke.py.old
-175
View File
@@ -1,175 +0,0 @@
"""
DY-YG400A Smoke Sensor, TS0601 from _TZE204_ntcy3xu1
https://www.aliexpress.com/item/1005005863519099.html
https://www.aliexpress.com/item/1005005854203557.html
"""
import logging
import zigpy.profiles.zha
from zigpy.quirks import CustomDevice
import zigpy.types as t
from zigpy.zcl.clusters.general import (
Basic,
Groups,
Ota,
Scenes,
Time,
BinaryInput,
BatterySize,
)
from zigpy.zcl.clusters.security import IasZone
from zhaquirks import Bus
from zhaquirks.const import (
DEVICE_TYPE,
ENDPOINTS,
INPUT_CLUSTERS,
MODELS_INFO,
OUTPUT_CLUSTERS,
PROFILE_ID,
ZONE_TYPE,
)
from zhaquirks.tuya import (
TuyaLocalCluster,
TuyaManufCluster,
TuyaManufClusterAttributes,
TuyaPowerConfigurationCluster,
)
_LOGGER = logging.getLogger(__name__)
TUYA_SMOKE_DETECTED_ATTR = 0x0401 # [0]/[1] [Detected]/[Clear]!
TUYA_SMOKE_TAMPERED_ATTR = 0x0104 # [0]/[1] [Clear]/[Tampered]!
TUYA_SMOKE_BATTERY_ATTR = 0x040e # [0]/[1]/[2] [Low]/[Med]]/[Full]!
class TuyaSmokeDetectorCluster(TuyaManufClusterAttributes):
"""Manufacturer Specific Cluster of the TS0601 smoke detector."""
attributes = {
TUYA_SMOKE_DETECTED_ATTR: ("smoke_detected", t.uint8_t, True),
TUYA_SMOKE_TAMPERED_ATTR: ("tampered_device", t.uint8_t, True),
TUYA_SMOKE_BATTERY_ATTR: ("battery_status", t.uint8_t, True),
}
def _update_attribute(self, attrid, value):
super()._update_attribute(attrid, value)
if attrid == TUYA_SMOKE_DETECTED_ATTR:
status = IasZone.ZoneStatus.Alarm_1 if value == 0 else 0
self.endpoint.device.ias_bus.listener_event("update_attribute", "zone_status", status)
elif attrid == TUYA_SMOKE_TAMPERED_ATTR:
self.endpoint.device.tamper_detection_bus.listener_event(
"update_attribute", "present_value", bool(value)
)
elif attrid == TUYA_SMOKE_BATTERY_ATTR:
batt = 5 if value == 0 else 40 if value == 1 else 100
self.endpoint.device.battery_bus.listener_event("battery_change", batt)
else:
_LOGGER.warning(
"[0x%04x:%s:0x%04x] unhandled attribute: 0x%04x",
self.endpoint.device.nwk,
self.endpoint.endpoint_id,
self.cluster_id,
attrid,
)
class TuyaIasZone(TuyaLocalCluster, IasZone):
"""
IAS Zone: this generates the "Smoke" entity for HA.
Receives updates from TuyaSmokeDetectorCluster.
"""
_CONSTANT_ATTRIBUTES = {ZONE_TYPE: IasZone.ZoneType.Fire_Sensor}
def __init__(self, *args, **kwargs):
"""Init."""
super().__init__(*args, **kwargs)
self.endpoint.device.ias_bus.add_listener(self)
class TuyaPowerConfigCluster(TuyaPowerConfigurationCluster):
"""
Power Config Cluster: this generates the "Battery" entity for HA.
Receives updates from TuyaSmokeDetectorCluster.
"""
_CONSTANT_ATTRIBUTES = {
TuyaPowerConfigurationCluster.attributes_by_name["battery_size"].id: BatterySize.AAA,
TuyaPowerConfigurationCluster.attributes_by_name["battery_quantity"].id: 2,
TuyaPowerConfigurationCluster.attributes_by_name["battery_rated_voltage"].id: 15,
}
class TuyaTamperDetection(TuyaLocalCluster, BinaryInput):
"""
Tamper Detection Cluster: this generates the "Binary input" entity for HA, which is updated
with the Tampered state. Receives updates from TuyaSmokeDetectorCluster.
"""
_CONSTANT_ATTRIBUTES = {
BinaryInput.attributes_by_name["description"].id: "Tamper Detected",
BinaryInput.attributes_by_name["active_text"].id: "Tampered",
BinaryInput.attributes_by_name["inactive_text"].id: "Clear",
}
def __init__(self, *args, **kwargs):
"""Init."""
super().__init__(*args, **kwargs)
self.endpoint.device.tamper_detection_bus.add_listener(self)
class TuyaSmokeDetector0601(CustomDevice):
"""TS0601 Smoke detector quirk."""
def __init__(self, *args, **kwargs):
"""Init."""
self.ias_bus = Bus()
self.battery_bus = Bus()
self.tamper_detection_bus = Bus()
super().__init__(*args, **kwargs)
signature = {
MODELS_INFO: [
"""("_TZE200_uebojraa", "TS0601"),"""
("_TZE200_uebojraa"),
],
ENDPOINTS: {
1: {
PROFILE_ID: zigpy.profiles.zha.PROFILE_ID,
DEVICE_TYPE: zigpy.profiles.zha.DeviceType.SMART_PLUG,
INPUT_CLUSTERS: [
Basic.cluster_id,
Groups.cluster_id,
Scenes.cluster_id,
TuyaManufCluster.cluster_id,
],
OUTPUT_CLUSTERS: [
Time.cluster_id,
Ota.cluster_id,
],
},
},
}
replacement = {
ENDPOINTS: {
1: {
PROFILE_ID: zigpy.profiles.zha.PROFILE_ID,
DEVICE_TYPE: zigpy.profiles.zha.DeviceType.IAS_ZONE,
INPUT_CLUSTERS: [
Basic.cluster_id,
Groups.cluster_id,
Scenes.cluster_id,
TuyaIasZone,
TuyaSmokeDetectorCluster,
TuyaPowerConfigCluster,
TuyaTamperDetection,
],
OUTPUT_CLUSTERS: [
Time.cluster_id,
Ota.cluster_id,
],
},
},
}
custom_zha_quirks/ts0601_valve_garden.py.old
-151
View File
@@ -1,151 +0,0 @@
"""Tuya valve devices."""
import logging
from typing import Dict
from zigpy.profiles import zha
from zigpy.quirks import CustomDevice
import zigpy.types as t
from zigpy.zcl import foundation
from zigpy.zcl.clusters.general import (
Basic,
Groups,
Ota,
PowerConfiguration,
Scenes,
Time,
)
from zhaquirks.const import (
DEVICE_TYPE,
ENDPOINTS,
INPUT_CLUSTERS,
MODELS_INFO,
OUTPUT_CLUSTERS,
PROFILE_ID,
)
from zhaquirks.tuya import NoManufacturerCluster
from zhaquirks.tuya.mcu import (
DPToAttributeMapping,
TuyaAttributesCluster,
TuyaDPType,
TuyaLevelControl,
TuyaMCUCluster,
TuyaOnOff,
TuyaOnOffNM,
TuyaPowerConfigurationCluster,
)
_LOGGER = logging.getLogger(__name__)
class TuyaLevelControlNM(NoManufacturerCluster, TuyaLevelControl):
"""Tuya LevelControl cluster with NoManufacturerID."""
class TuyaValveManufCluster(TuyaMCUCluster):
"""Tuya valve manufacturer cluster."""
attributes = TuyaMCUCluster.attributes.copy()
attributes.update(
{
0xEF03: ("dp_3", t.uint32_t, True),
0xEF65: ("dp_101", t.uint32_t, True),
0xEF66: ("dp_102", t.uint32_t, True), # <-- new cluster attribute with fake IDs (102=0x66).Format= ID: ("name", type, True)
}
)
dp_to_attribute: Dict[int, DPToAttributeMapping] = {
2: DPToAttributeMapping(
TuyaOnOffNM.ep_attribute,
"on_off",
dp_type=TuyaDPType.BOOL,
),
1: DPToAttributeMapping(
TuyaLevelControlNM.ep_attribute,
"current_level",
dp_type=TuyaDPType.VALUE,
converter=lambda x: (x * 255) // 100,
dp_converter=lambda x: (x * 100) // 255,
),
3: DPToAttributeMapping(
TuyaMCUCluster.ep_attribute,
"dp_3",
dp_type=TuyaDPType.VALUE,
),
101: DPToAttributeMapping(
TuyaMCUCluster.ep_attribute,
"dp_101",
dp_type=TuyaDPType.VALUE,
),
102: DPToAttributeMapping( # <-- device DP102
TuyaMCUCluster.ep_attribute, # <-- reference to the cluster which has the attribute
"dp_102", # <-- attribute "name"
dp_type=TuyaDPType.VALUE, # <-- DP Type it is related to the attribute type
),
108: DPToAttributeMapping(
TuyaPowerConfigurationCluster.ep_attribute,
"battery_percentage_remaining",
dp_type=TuyaDPType.VALUE,
),
}
data_point_handlers = {
2: "_dp_2_attr_update",
1: "_dp_2_attr_update",
3: "_dp_2_attr_update",
101: "_dp_2_attr_update",
102: "_dp_2_attr_update",
108: "_dp_2_attr_update",
}
async def write_attributes(self, attributes, manufacturer=None):
"""Overwrite to force manufacturer code."""
return await super().write_attributes(
attributes, manufacturer=foundation.ZCLHeader.NO_MANUFACTURER_ID
)
class TuyaValve(CustomDevice):
"""Tuya valve device."""
signature = {
"""MODELS_INFO: [("_TZE200_sh1btabb", "TS0601")],"""
MODELS_INFO: [("_TZE200_sh1btabb")],
ENDPOINTS: {
# <SimpleDescriptor endpoint=1 profile=260 device_type=0x0051
# input_clusters=[0x0000, 0x0004, 0x0005, 0xef00]
# output_clusters=[0x000a, 0x0019]>
1: {
PROFILE_ID: zha.PROFILE_ID,
DEVICE_TYPE: zha.DeviceType.SMART_PLUG,
INPUT_CLUSTERS: [
Basic.cluster_id,
Groups.cluster_id,
Scenes.cluster_id,
TuyaValveManufCluster.cluster_id,
],
OUTPUT_CLUSTERS: [Time.cluster_id, Ota.cluster_id],
}
},
}
replacement = {
ENDPOINTS: {
1: {
DEVICE_TYPE: zha.DeviceType.ON_OFF_LIGHT,
INPUT_CLUSTERS: [
Basic.cluster_id,
Groups.cluster_id,
Scenes.cluster_id,
TuyaValveManufCluster,
TuyaOnOffNM,
TuyaLevelControlNM,
TuyaPowerConfigurationCluster,
],
OUTPUT_CLUSTERS: [Time.cluster_id, Ota.cluster_id],
}
}
}
esphome/.device-builder.json
+620 -434
View File
File diff suppressed because it is too large Load Diff
esphome/esp-3dprinterpow.yaml
+3 -3
View File
@@ -244,7 +244,7 @@ globals:
- id: max_power_7d
type: float
restore_value: true
initial_value: '0.0'
initial_value: "0.0"
update_interval: 5min
# Powered hours elapsed during the current seven-day period.
@@ -252,7 +252,7 @@ globals:
- id: max_power_hours_elapsed
type: uint16_t
restore_value: true
initial_value: '0'
initial_value: "0"
update_interval: 6h
#:########################################################################################:#
@@ -411,7 +411,7 @@ switch:
id: relay
pin: GPIO12
restore_mode: RESTORE_DEFAULT_ON
restore_mode: RESTORE_DEFAULT_OFF
on_turn_on:
then:
esphome/esp-bedrm1arlecbulb.yaml
+38 -38
View File
@@ -6,6 +6,7 @@
# https://home.fox.co.nz/gitea/zorruno/zorruno-homeassistant/src/branch/master/esphome/esp-bedrm1arlecbulb.yaml
#:########################################################################################:#
# VERSIONS:
# v1.3 2026-07-20 Simplified local MQTT command and status topics to the device root
# v1.2 2026-02-25 Updated yaml to zorruno layout V1.1
# v1.1 2026-02-21 Add "Jump Fade Up/Down" switch + configurable Jump Fade (%)
# v1.0 2026-02-21 Initial version (ported from Athom bulb YAML to Arlec GLD120HA)
@@ -42,7 +43,6 @@
# - Accurate time is NOT needed (SNTP not needed).
#:########################################################################################:#
#:########################################################################################:#
# SUBSTITUTIONS: Specific device variable substitutions
# If NOT using a secrets file, just replace these with the passwords etc (in quotes)
@@ -56,7 +56,7 @@ substitutions:
# Project Naming
project_name: "Grid Connect GLD120HA RGBWW.Arlec"
project_version: "v1.2"
project_version: "v1.3"
# Passwords & Secrets (Unfortunately, you can't use substitutions inside secret names)
# Re-using your existing bulb flasher secrets (adjust if you prefer per-device secrets)
@@ -156,32 +156,32 @@ esphome:
# Mode 0: Fade up to full (obeys fade settings; forces Warm endpoint)
- if:
condition:
lambda: 'return id(restart_mode) == 0;'
lambda: "return id(restart_mode) == 0;"
then:
- lambda: 'id(ramp_switch_target_on) = true;'
- lambda: "id(ramp_switch_target_on) = true;"
- script.execute: ramp_on_script
# Mode 1: Restore Brightness (deferred; forces Warm endpoint)
- if:
condition:
lambda: 'return id(restart_mode) == 1;'
lambda: "return id(restart_mode) == 1;"
then:
- script.execute: deferred_restore_brightness
# Mode 2: Remain Off
- if:
condition:
lambda: 'return id(restart_mode) == 2;'
lambda: "return id(restart_mode) == 2;"
then:
- script.stop: ramp_on_script
- script.stop: ramp_off_script
- lambda: 'id(ramp_switch_target_on) = false;'
- lambda: "id(ramp_switch_target_on) = false;"
- light.turn_off:
id: bulb_light
transition_length: 0s
# Boot complete: allow OFF handlers again
- lambda: 'id(booting) = false;'
- lambda: "id(booting) = false;"
#:########################################################################################:#
# ESP PLATFORM AND FRAMEWORK
@@ -301,12 +301,12 @@ logger:
#:########################################################################################:#
mqtt:
on_message:
- topic: "${mqtt_local_command_topic}/light/set"
- topic: "${mqtt_local_command_topic}"
payload: "${mqtt_local_device_command_ON}"
then:
- switch.turn_on: bulb_ramp_switch
- topic: "${mqtt_local_command_topic}/light/set"
- topic: "${mqtt_local_command_topic}"
payload: "${mqtt_local_device_command_OFF}"
then:
- switch.turn_off: bulb_ramp_switch
@@ -536,7 +536,7 @@ light:
on_turn_on:
- mqtt.publish:
topic: "${mqtt_local_status_topic}/light/state"
topic: "${mqtt_local_status_topic}"
payload: "${mqtt_local_device_command_ON}"
retain: true
- lambda: |-
@@ -546,20 +546,20 @@ light:
- script.stop: max_on_watchdog
- if:
condition:
lambda: 'return id(max_on_hours) > 0;'
lambda: "return id(max_on_hours) > 0;"
then:
- script.execute: max_on_watchdog
on_turn_off:
- if:
condition:
lambda: 'return !id(booting);'
lambda: "return !id(booting);"
then:
- mqtt.publish:
topic: "${mqtt_local_status_topic}/light/state"
topic: "${mqtt_local_status_topic}"
payload: "${mqtt_local_device_command_OFF}"
retain: true
- lambda: 'id(ramp_switch_target_on) = false;'
- lambda: "id(ramp_switch_target_on) = false;"
- script.stop: max_on_watchdog
- lambda: |-
id(last_brightness_pct) = 0.0f;
@@ -667,9 +667,9 @@ number:
set_action:
- if:
condition:
lambda: 'return x <= 0.0f;'
lambda: "return x <= 0.0f;"
then:
- lambda: 'id(suppress_slider_sync) = true;'
- lambda: "id(suppress_slider_sync) = true;"
- script.stop: ramp_on_script
- script.stop: ramp_off_script
- light.turn_off:
@@ -681,7 +681,7 @@ number:
id(last_brightness_pct) = 0.0f;
id(last_set_pos) = 0;
- delay: 400ms
- lambda: 'id(suppress_slider_sync) = false;'
- lambda: "id(suppress_slider_sync) = false;"
else:
- lambda: |-
id(suppress_slider_sync) = true;
@@ -713,7 +713,7 @@ number:
if (out_pct > maxp) out_pct = maxp;
id(last_brightness_pct) = out_pct;
- delay: 400ms
- lambda: 'id(suppress_slider_sync) = false;'
- lambda: "id(suppress_slider_sync) = false;"
- platform: template
id: cfg_max_on_hours
@@ -736,12 +736,12 @@ number:
id(cfg_max_on_hours).publish_state((float) hrs);
- if:
condition:
lambda: 'return id(bulb_light).current_values.is_on();'
lambda: "return id(bulb_light).current_values.is_on();"
then:
- script.stop: max_on_watchdog
- if:
condition:
lambda: 'return id(max_on_hours) > 0;'
lambda: "return id(max_on_hours) > 0;"
then:
- script.execute: max_on_watchdog
@@ -753,7 +753,7 @@ script:
- id: ramp_on_script
mode: restart
then:
- lambda: 'id(is_ramping) = true;'
- lambda: "id(is_ramping) = true;"
- script.stop: ramp_off_script
- if:
@@ -766,13 +766,13 @@ script:
- light.turn_on:
id: bulb_light
color_temperature: "${bulb_warm_kelvin}"
brightness: !lambda 'return id(min_brightness_pct) / 100.0f;'
brightness: !lambda "return id(min_brightness_pct) / 100.0f;"
transition_length: 80ms
- light.turn_on:
id: bulb_light
color_temperature: "${bulb_warm_kelvin}"
brightness: !lambda 'return id(max_brightness_pct) / 100.0f;'
brightness: !lambda "return id(max_brightness_pct) / 100.0f;"
transition_length: !lambda |-
const auto &cv = id(bulb_light).current_values;
const float floor = id(min_brightness_pct) / 100.0f;
@@ -795,7 +795,7 @@ script:
id(last_ramp_ms) = (int) (id(ramp_up_ms) * frac);
return (uint32_t) id(last_ramp_ms);
- delay: !lambda 'return (uint32_t) id(last_ramp_ms);'
- delay: !lambda "return (uint32_t) id(last_ramp_ms);"
- lambda: |-
id(is_ramping) = false;
const auto &cv = id(bulb_light).current_values;
@@ -807,7 +807,7 @@ script:
- id: ramp_to_target_script
mode: restart
then:
- lambda: 'id(is_ramping) = true;'
- lambda: "id(is_ramping) = true;"
- script.stop: ramp_off_script
- if:
@@ -820,7 +820,7 @@ script:
- light.turn_on:
id: bulb_light
color_temperature: "${bulb_warm_kelvin}"
brightness: !lambda 'return id(min_brightness_pct) / 100.0f;'
brightness: !lambda "return id(min_brightness_pct) / 100.0f;"
transition_length: 80ms
- light.turn_on:
@@ -858,7 +858,7 @@ script:
id(last_ramp_ms) = (int) (id(ramp_up_ms) * frac);
return (uint32_t) id(last_ramp_ms);
- delay: !lambda 'return (uint32_t) id(last_ramp_ms);'
- delay: !lambda "return (uint32_t) id(last_ramp_ms);"
- lambda: |-
id(is_ramping) = false;
const auto &cv = id(bulb_light).current_values;
@@ -878,7 +878,7 @@ script:
- light.turn_on:
id: bulb_light
color_temperature: "${bulb_warm_kelvin}"
brightness: !lambda 'return id(min_brightness_pct) / 100.0f;'
brightness: !lambda "return id(min_brightness_pct) / 100.0f;"
transition_length: !lambda |-
const auto &cv = id(bulb_light).current_values;
const float floor = id(min_brightness_pct) / 100.0f;
@@ -895,7 +895,7 @@ script:
id(last_ramp_ms) = (int) (id(ramp_down_ms) * frac);
return (uint32_t) id(last_ramp_ms);
- delay: !lambda 'return (uint32_t) id(last_ramp_ms);'
- delay: !lambda "return (uint32_t) id(last_ramp_ms);"
- light.turn_off:
id: bulb_light
transition_length: 150ms
@@ -913,12 +913,12 @@ script:
then:
- if:
condition:
lambda: 'return id(max_on_hours) > 0;'
lambda: "return id(max_on_hours) > 0;"
then:
- delay: !lambda 'return (uint32_t) (id(max_on_hours) * 3600000UL);'
- delay: !lambda "return (uint32_t) (id(max_on_hours) * 3600000UL);"
- if:
condition:
lambda: 'return id(bulb_light).current_values.is_on();'
lambda: "return id(bulb_light).current_values.is_on();"
then:
- lambda: |-
id(ramp_switch_target_on) = false;
@@ -942,17 +942,17 @@ script:
- if:
condition:
lambda: 'return id(restore_target_pct) > 0.5f;'
lambda: "return id(restore_target_pct) > 0.5f;"
then:
- lambda: |-
id(ramp_switch_target_on) = true;
id(suppress_slider_sync) = true;
- script.stop: ramp_off_script
- script.execute: ramp_to_target_script
- delay: !lambda 'return (uint32_t) id(last_ramp_ms);'
- lambda: 'id(suppress_slider_sync) = false;'
- delay: !lambda "return (uint32_t) id(last_ramp_ms);"
- lambda: "id(suppress_slider_sync) = false;"
else:
- lambda: 'id(ramp_switch_target_on) = false;'
- lambda: "id(ramp_switch_target_on) = false;"
- light.turn_off:
id: bulb_light
transition_length: 0s
@@ -1013,7 +1013,7 @@ script:
- if:
condition:
lambda: 'return id(bulb_light).current_values.is_on();'
lambda: "return id(bulb_light).current_values.is_on();"
then:
- light.turn_on:
id: bulb_light
esphome/esp-breakfastbarleds.yaml
+41 -41
View File
@@ -6,6 +6,7 @@
# https://home.fox.co.nz/gitea/zorruno/zorruno-homeassistant/src/branch/master/esphome/esp-breakfastbarleds.yaml
#:########################################################################################:#
# VERSIONS:
# V2.1 2026-07-20 Simplified local MQTT command and status topics to the device root
# V2.0 2025-09-15 A bunch of fixes and made it more standard across my devices
# V1.0 2025-08-17 First setup (and replacement of Tasmota)
#:########################################################################################:#
@@ -47,10 +48,10 @@
#:########################################################################################:#
# MQTT COMMANDS:
# Local MQTT light control:
# - ${mqtt_local_command_topic}/light/set -> ON,OFF
# - ${mqtt_local_command_topic} -> ON,OFF
#
# Local MQTT light status:
# - ${mqtt_local_status_topic}/light/state -> ON,OFF
# - ${mqtt_local_status_topic} -> ON,OFF
#:########################################################################################:#
# OFFLINE NOTES:
# a) Home Assistant OFFLINE, but Network and MQTT ONLINE
@@ -80,7 +81,7 @@ substitutions:
# Project Naming
project_name: "Magichome Single Colour V1.1 LED Controller.Generic ESP8266" # Manufacturer before the dot, device after the dot.
project_version: "v2.0" # Project version denotes release of the YAML file, allowing checking of deployed vs latest version
project_version: "v2.1" # Project version denotes release of the YAML file, allowing checking of deployed vs latest version
# Passwords & Secrets (Unfortunately, you can't use substitutions inside secret names)
api_key: !secret esp-api_key
@@ -130,8 +131,7 @@ packages:
local_current_ip_address: "${current_ip_address}"
#### HOME ASSISTANT API (choose encryption or no encryption options) ####
common_api: !include
#file: common/api_common.yaml
common_api: !include #file: common/api_common.yaml
file: common/api_common_noencryption.yaml
vars:
local_api_key: "${api_key}"
@@ -178,32 +178,32 @@ esphome:
# Mode 0: Fade up to full (obeys fade settings; no on/off flicker)
- if:
condition:
lambda: 'return id(restart_mode) == 0;'
lambda: "return id(restart_mode) == 0;"
then:
- lambda: 'id(ramp_switch_target_on) = true;'
- lambda: "id(ramp_switch_target_on) = true;"
- script.execute: ramp_on_script
# Mode 1: Restore Brightness (deferred to avoid races)
- if:
condition:
lambda: 'return id(restart_mode) == 1;'
lambda: "return id(restart_mode) == 1;"
then:
- script.execute: deferred_restore_brightness
# Mode 2: Remain Off (no blip; stays off)
- if:
condition:
lambda: 'return id(restart_mode) == 2;'
lambda: "return id(restart_mode) == 2;"
then:
- script.stop: ramp_on_script
- script.stop: ramp_off_script
- lambda: 'id(ramp_switch_target_on) = false;'
- lambda: "id(ramp_switch_target_on) = false;"
- light.turn_off:
id: mosfet_leds
transition_length: 0s
# Boot complete: allow OFF handlers again
- lambda: 'id(booting) = false;'
- lambda: "id(booting) = false;"
#:########################################################################################:#
# ESP PLATFORM AND FRAMEWORK:
@@ -345,13 +345,13 @@ status_led:
mqtt:
on_message:
# Light control to ramp up
- topic: "${mqtt_local_command_topic}/light/set"
- topic: "${mqtt_local_command_topic}"
payload: "${mqtt_local_device_command_ON}"
then:
- switch.turn_on: mosfet_ramp_switch
# Light control to ramp down
- topic: "${mqtt_local_command_topic}/light/set"
- topic: "${mqtt_local_command_topic}"
payload: "${mqtt_local_device_command_OFF}"
then:
- switch.turn_off: mosfet_ramp_switch
@@ -482,7 +482,7 @@ binary_sensor:
on_press:
- if:
condition:
lambda: 'return id(ramp_switch_target_on);'
lambda: "return id(ramp_switch_target_on);"
then:
# Target is currently ON -> press should go OFF (start ramp-down)
- lambda: |-
@@ -584,7 +584,7 @@ light:
on_turn_on:
- output.turn_on: green_led_out
- mqtt.publish:
topic: "${mqtt_local_status_topic}/light/state"
topic: "${mqtt_local_status_topic}"
payload: "${mqtt_local_device_command_ON}"
retain: true
- lambda: |-
@@ -595,7 +595,7 @@ light:
- script.stop: max_on_watchdog
- if:
condition:
lambda: 'return id(max_on_hours) > 0;'
lambda: "return id(max_on_hours) > 0;"
then:
- script.execute: max_on_watchdog
@@ -605,13 +605,13 @@ light:
- output.turn_off: green_led_out
- if:
condition:
lambda: 'return !id(booting);'
lambda: "return !id(booting);"
then:
- mqtt.publish:
topic: "${mqtt_local_status_topic}/light/state"
topic: "${mqtt_local_status_topic}"
payload: "${mqtt_local_device_command_OFF}"
retain: true
- lambda: 'id(ramp_switch_target_on) = false;'
- lambda: "id(ramp_switch_target_on) = false;"
- script.stop: max_on_watchdog
- lambda: |-
id(last_brightness_pct) = 0.0f;
@@ -699,9 +699,9 @@ number:
set_action:
- if:
condition:
lambda: 'return x <= 0.0f;'
lambda: "return x <= 0.0f;"
then:
- lambda: 'id(suppress_slider_sync) = true;'
- lambda: "id(suppress_slider_sync) = true;"
- script.stop: ramp_on_script
- script.stop: ramp_off_script
- light.turn_off:
@@ -713,7 +713,7 @@ number:
id(last_brightness_pct) = 0.0f;
id(last_set_pos) = 0;
- delay: 400ms
- lambda: 'id(suppress_slider_sync) = false;'
- lambda: "id(suppress_slider_sync) = false;"
else:
- lambda: |-
id(suppress_slider_sync) = true;
@@ -744,7 +744,7 @@ number:
if (out_pct > maxp) out_pct = maxp;
id(last_brightness_pct) = out_pct;
- delay: 400ms
- lambda: 'id(suppress_slider_sync) = false;'
- lambda: "id(suppress_slider_sync) = false;"
- platform: template
id: cfg_max_on_hours
@@ -767,12 +767,12 @@ number:
id(cfg_max_on_hours).publish_state((float) hrs);
- if:
condition:
lambda: 'return id(mosfet_leds).current_values.is_on();'
lambda: "return id(mosfet_leds).current_values.is_on();"
then:
- script.stop: max_on_watchdog
- if:
condition:
lambda: 'return id(max_on_hours) > 0;'
lambda: "return id(max_on_hours) > 0;"
then:
- script.execute: max_on_watchdog
@@ -785,7 +785,7 @@ script:
- id: ramp_on_script
mode: restart
then:
- lambda: 'id(is_ramping) = true;'
- lambda: "id(is_ramping) = true;"
- script.stop: ramp_off_script
# Ensure we start at at least the floor without a visible "pop".
@@ -798,13 +798,13 @@ script:
then:
- light.turn_on:
id: mosfet_leds
brightness: !lambda 'return id(min_brightness_pct) / 100.0f;'
brightness: !lambda "return id(min_brightness_pct) / 100.0f;"
transition_length: 80ms
# Ramp from current (>= floor) to cap over a fraction of ramp_up_ms.
- light.turn_on:
id: mosfet_leds
brightness: !lambda 'return id(max_brightness_pct) / 100.0f;'
brightness: !lambda "return id(max_brightness_pct) / 100.0f;"
transition_length: !lambda |-
const auto &cv = id(mosfet_leds).current_values;
const float floor = id(min_brightness_pct) / 100.0f;
@@ -825,7 +825,7 @@ script:
id(last_ramp_ms) = (int) (id(ramp_up_ms) * frac);
return (uint32_t) id(last_ramp_ms);
- delay: !lambda 'return (uint32_t) id(last_ramp_ms);'
- delay: !lambda "return (uint32_t) id(last_ramp_ms);"
- lambda: |-
id(is_ramping) = false;
const auto &cv = id(mosfet_leds).current_values;
@@ -838,7 +838,7 @@ script:
- id: ramp_to_target_script
mode: restart
then:
- lambda: 'id(is_ramping) = true;'
- lambda: "id(is_ramping) = true;"
- script.stop: ramp_off_script
# Ensure we start at the floor cleanly.
@@ -851,7 +851,7 @@ script:
then:
- light.turn_on:
id: mosfet_leds
brightness: !lambda 'return id(min_brightness_pct) / 100.0f;'
brightness: !lambda "return id(min_brightness_pct) / 100.0f;"
transition_length: 80ms
# Ramp from current (>= floor) to restore_target_pct over a fraction of ramp_up_ms.
@@ -884,7 +884,7 @@ script:
id(last_ramp_ms) = (int) (id(ramp_up_ms) * frac);
return (uint32_t) id(last_ramp_ms);
- delay: !lambda 'return (uint32_t) id(last_ramp_ms);'
- delay: !lambda "return (uint32_t) id(last_ramp_ms);"
- lambda: |-
id(is_ramping) = false;
const auto &cv = id(mosfet_leds).current_values;
@@ -904,7 +904,7 @@ script:
- light.turn_on:
id: mosfet_leds
brightness: !lambda 'return id(min_brightness_pct) / 100.0f;'
brightness: !lambda "return id(min_brightness_pct) / 100.0f;"
transition_length: !lambda |-
const auto &cv = id(mosfet_leds).current_values;
const float floor = id(min_brightness_pct) / 100.0f;
@@ -918,7 +918,7 @@ script:
id(last_ramp_ms) = (int) (id(ramp_down_ms) * frac);
return (uint32_t) id(last_ramp_ms);
- delay: !lambda 'return (uint32_t) id(last_ramp_ms);'
- delay: !lambda "return (uint32_t) id(last_ramp_ms);"
- light.turn_off:
id: mosfet_leds
transition_length: 150ms
@@ -935,12 +935,12 @@ script:
then:
- if:
condition:
lambda: 'return id(max_on_hours) > 0;'
lambda: "return id(max_on_hours) > 0;"
then:
- delay: !lambda 'return (uint32_t) (id(max_on_hours) * 3600000UL);'
- delay: !lambda "return (uint32_t) (id(max_on_hours) * 3600000UL);"
- if:
condition:
lambda: 'return id(mosfet_leds).current_values.is_on();'
lambda: "return id(mosfet_leds).current_values.is_on();"
then:
- lambda: |-
id(ramp_switch_target_on) = false;
@@ -967,18 +967,18 @@ script:
- if:
condition:
lambda: 'return id(restore_target_pct) > 0.5f;'
lambda: "return id(restore_target_pct) > 0.5f;"
then:
- lambda: |-
id(ramp_switch_target_on) = true;
id(suppress_slider_sync) = true;
- script.stop: ramp_off_script
- script.execute: ramp_to_target_script
- delay: !lambda 'return (uint32_t) id(last_ramp_ms);'
- lambda: 'id(suppress_slider_sync) = false;'
- delay: !lambda "return (uint32_t) id(last_ramp_ms);"
- lambda: "id(suppress_slider_sync) = false;"
else:
# Exact last was 0 -> remain OFF
- lambda: 'id(ramp_switch_target_on) = false;'
- lambda: "id(ramp_switch_target_on) = false;"
- light.turn_off:
id: mosfet_leds
transition_length: 0s
esphome/esp-centralstairs-bottom.yaml
+32 -9
View File
@@ -6,6 +6,7 @@
# https://home.fox.co.nz/gitea/zorruno/zorruno-homeassistant/src/branch/master/esphome/esp-centralstairs-bottom.yaml
#:########################################################################################:#
# VERSIONS:
# V3.9 2026-07-21 Added retained MQTT status mirroring for HA-independent two-way switching
# V3.8 2026-06-09 Added Downstairs Lights Bulk Activation virtual switch toggled by Button 1 double-click
# V3.7 2025-09-24 Upload to this device
# V3.5 2025-07-24 YAML tidyups
@@ -83,7 +84,7 @@ substitutions:
# Project Naming
project_name: "Zemismart Technologies.KS-811 Double" # Project Details
project_version: "v2.1" # Project V denotes release of yaml file, allowing checking of deployed vs latest version
project_version: "v3.9" # Project V denotes release of yaml file, allowing checking of deployed vs latest version
# MQTT Controls
mqtt_command_main_topic: !secret mqtt_command_main_topic
@@ -184,19 +185,19 @@ mqtt:
then:
- if:
condition:
lambda: 'return id(Relay_1).state;'
lambda: "return id(Relay_1).state;"
then:
- mqtt.publish:
topic: "${mqtt_status_topic_1}"
payload: "${mqtt_command_ON}"
qos: 0
retain: false
qos: 1
retain: true
else:
- mqtt.publish:
topic: "${mqtt_status_topic_1}"
payload: "${mqtt_command_OFF}"
qos: 0
retain: false
qos: 1
retain: true
on_message:
# Relay 1: only turn ON if currently OFF
@@ -241,6 +242,26 @@ mqtt:
then:
- switch.turn_off: Relay_2
# Relay 2 is a mirror of the remote physical Stair Footer Lights relay.
- topic: "${mqtt_status_topic_2}"
payload: "${mqtt_command_ON}"
then:
- if:
condition:
not:
- switch.is_on: Relay_2
then:
- switch.turn_on: Relay_2
- topic: "${mqtt_status_topic_2}"
payload: "${mqtt_command_OFF}"
then:
- if:
condition:
- switch.is_on: Relay_2
then:
- switch.turn_off: Relay_2
#:########################################################################################:#
# STATUS LED:
# https://esphome.io/components/status_led.html
@@ -298,7 +319,7 @@ binary_sensor:
# Toggle the remote Footer Lights via COMMAND topic, based on our mirrored state
- if:
condition:
lambda: 'return id(Relay_2).state;'
lambda: "return id(Relay_2).state;"
then:
- mqtt.publish:
topic: "${mqtt_command_topic_2}"
@@ -332,12 +353,14 @@ switch:
- mqtt.publish:
topic: "${mqtt_status_topic_1}"
payload: "${mqtt_command_ON}"
retain: false
qos: 1
retain: true
on_turn_off:
- mqtt.publish:
topic: "${mqtt_status_topic_1}"
payload: "${mqtt_command_OFF}"
retain: false
qos: 1
retain: true
- platform: gpio
name: "Relay 2: ${switch_2_name}"
esphome/esp-centralstairs-top.yaml
+32 -9
View File
@@ -6,6 +6,7 @@
# https://home.fox.co.nz/gitea/zorruno/zorruno-homeassistant/src/branch/master/esphome/esp-centralstairs-top.yaml
#:########################################################################################:#
# VERSIONS:
# V3.9 2026-07-21 Added retained MQTT status mirroring for HA-independent two-way switching
# V3.8 2026-04-26 Added Downstairs Lights Bulk Activation virtual switch toggled by Button 1 double-click
# V3.7 2025-09-24 Upload to this device
# V3.5 2025-07-24 YAML tidyups
@@ -83,7 +84,7 @@ substitutions:
# Project Naming
project_name: "Zemismart Technologies.KS-811 Double" # Project Details
project_version: "v2.1" # Project V denotes release of yaml file, allowing checking of deployed vs latest version
project_version: "v3.9" # Project V denotes release of yaml file, allowing checking of deployed vs latest version
# MQTT Controls
mqtt_command_main_topic: !secret mqtt_command_main_topic
@@ -184,19 +185,19 @@ mqtt:
then:
- if:
condition:
lambda: 'return id(Relay_2).state;'
lambda: "return id(Relay_2).state;"
then:
- mqtt.publish:
topic: "${mqtt_status_topic_2}"
payload: "${mqtt_command_ON}"
qos: 0
retain: false
qos: 1
retain: true
else:
- mqtt.publish:
topic: "${mqtt_status_topic_2}"
payload: "${mqtt_command_OFF}"
qos: 0
retain: false
qos: 1
retain: true
on_message:
# Relay 1: only turn ON if currently OFF
@@ -241,6 +242,26 @@ mqtt:
then:
- switch.turn_off: Relay_2
# Relay 1 is a mirror of the remote physical Main Stair Lights relay.
- topic: "${mqtt_status_topic_1}"
payload: "${mqtt_command_ON}"
then:
- if:
condition:
not:
- switch.is_on: Relay_1
then:
- switch.turn_on: Relay_1
- topic: "${mqtt_status_topic_1}"
payload: "${mqtt_command_OFF}"
then:
- if:
condition:
- switch.is_on: Relay_1
then:
- switch.turn_off: Relay_1
#:########################################################################################:#
# STATUS LED:
# https://esphome.io/components/status_led.html
@@ -286,7 +307,7 @@ binary_sensor:
then:
- if:
condition:
lambda: 'return id(Relay_1).state;'
lambda: "return id(Relay_1).state;"
then:
- mqtt.publish:
topic: "${mqtt_command_topic_1}"
@@ -338,9 +359,11 @@ switch:
- mqtt.publish:
topic: "${mqtt_status_topic_2}"
payload: "${mqtt_command_ON}"
retain: false
qos: 1
retain: true
on_turn_off:
- mqtt.publish:
topic: "${mqtt_status_topic_2}"
payload: "${mqtt_command_OFF}"
retain: false
qos: 1
retain: true
esphome/esp-downstairskitchleds.yaml
+41 -42
View File
@@ -6,6 +6,7 @@
# https://home.fox.co.nz/gitea/zorruno/zorruno-homeassistant/src/branch/master/esphome/esp-downstairskitchleds.yaml
#:########################################################################################:#
# VERSIONS:
# v2.2 2026-07-20 Simplified local MQTT command and status topics to the device root
# v2.1 2026-02-25 Updated yaml to zorruno layout V1.1
# v2.0 2025-09-15 A bunch of fixes.
# v1.5 2025-09-04 Adopt ramped "Restore Brightness" (0->last non-zero), avoid boot blip (ALWAYS_OFF + high-priority on_boot),
@@ -60,12 +61,12 @@
#:########################################################################################:#
# MQTT COMMANDS:
# - Command topic:
# ${mqtt_local_command_topic}/light/set
# ${mqtt_local_command_topic}
# Payload "${mqtt_local_device_command_ON}" -> fade up (switch ON)
# Payload "${mqtt_local_device_command_OFF}" -> fade down (switch OFF)
#
# - Status topic:
# ${mqtt_local_status_topic}/light/state
# ${mqtt_local_status_topic}
# Payload "${mqtt_local_device_command_ON}" / "${mqtt_local_device_command_OFF}"
#:########################################################################################:#
# OFFLINE NOTES:
@@ -81,7 +82,6 @@
# - Accurate time is NOT needed (SNTP not needed)
#:########################################################################################:#
#:########################################################################################:#
# SUBSTITUTIONS: Specific device variable substitutions
# If NOT using a secrets file, just replace these with the passwords etc (in quotes)
@@ -95,7 +95,7 @@ substitutions:
# Project Naming
project_name: "Sinilink.XY-WFMS" # Project details. Manufacturer before the dot, device after the dot.
project_version: "v2.1" # Project version denotes release of the YAML file, allowing checking of deployed vs latest version
project_version: "v2.2" # Project version denotes release of the YAML file, allowing checking of deployed vs latest version
# Passwords & Secrets (Unfortunately, you can't use substitutions inside secret names)
api_key: !secret esp-api_key
@@ -145,8 +145,7 @@ packages:
local_current_ip_address: "${current_ip_address}"
#### HOME ASSISTANT API (choose encryption or no encryption options) ####
common_api: !include
#file: common/api_common.yaml
common_api: !include #file: common/api_common.yaml
file: common/api_common_noencryption.yaml
vars:
local_api_key: "${api_key}"
@@ -193,32 +192,32 @@ esphome:
# Mode 0: Fade up to full (obeys fade settings; no on/off flicker)
- if:
condition:
lambda: 'return id(restart_mode) == 0;'
lambda: "return id(restart_mode) == 0;"
then:
- lambda: 'id(ramp_switch_target_on) = true;'
- lambda: "id(ramp_switch_target_on) = true;"
- script.execute: ramp_on_script
# Mode 1: Restore Brightness (deferred to avoid races)
- if:
condition:
lambda: 'return id(restart_mode) == 1;'
lambda: "return id(restart_mode) == 1;"
then:
- script.execute: deferred_restore_brightness
# Mode 2: Remain Off (no blip; stays off)
- if:
condition:
lambda: 'return id(restart_mode) == 2;'
lambda: "return id(restart_mode) == 2;"
then:
- script.stop: ramp_on_script
- script.stop: ramp_off_script
- lambda: 'id(ramp_switch_target_on) = false;'
- lambda: "id(ramp_switch_target_on) = false;"
- light.turn_off:
id: mosfet_leds
transition_length: 0s
# Boot complete: allow OFF handlers again
- lambda: 'id(booting) = false;'
- lambda: "id(booting) = false;"
#:########################################################################################:#
# ESP PLATFORM AND FRAMEWORK
@@ -358,13 +357,13 @@ status_led:
mqtt:
on_message:
# Light control to ramp up
- topic: "${mqtt_local_command_topic}/light/set"
- topic: "${mqtt_local_command_topic}"
payload: "${mqtt_local_device_command_ON}"
then:
- switch.turn_on: mosfet_ramp_switch
# Light control to ramp down
- topic: "${mqtt_local_command_topic}/light/set"
- topic: "${mqtt_local_command_topic}"
payload: "${mqtt_local_device_command_OFF}"
then:
- switch.turn_off: mosfet_ramp_switch
@@ -492,7 +491,7 @@ binary_sensor:
on_press:
- if:
condition:
lambda: 'return id(ramp_switch_target_on);'
lambda: "return id(ramp_switch_target_on);"
then:
- lambda: |-
id(ramp_switch_target_on) = false;
@@ -589,7 +588,7 @@ light:
on_turn_on:
- output.turn_on: green_led_out
- mqtt.publish:
topic: "${mqtt_local_status_topic}/light/state"
topic: "${mqtt_local_status_topic}"
payload: "${mqtt_local_device_command_ON}"
retain: true
- lambda: |-
@@ -599,7 +598,7 @@ light:
- script.stop: max_on_watchdog
- if:
condition:
lambda: 'return id(max_on_hours) > 0;'
lambda: "return id(max_on_hours) > 0;"
then:
- script.execute: max_on_watchdog
@@ -607,13 +606,13 @@ light:
- output.turn_off: green_led_out
- if:
condition:
lambda: 'return !id(booting);'
lambda: "return !id(booting);"
then:
- mqtt.publish:
topic: "${mqtt_local_status_topic}/light/state"
topic: "${mqtt_local_status_topic}"
payload: "${mqtt_local_device_command_OFF}"
retain: true
- lambda: 'id(ramp_switch_target_on) = false;'
- lambda: "id(ramp_switch_target_on) = false;"
- script.stop: max_on_watchdog
- lambda: |-
id(last_brightness_pct) = 0.0f;
@@ -700,9 +699,9 @@ number:
set_action:
- if:
condition:
lambda: 'return x <= 0.0f;'
lambda: "return x <= 0.0f;"
then:
- lambda: 'id(suppress_slider_sync) = true;'
- lambda: "id(suppress_slider_sync) = true;"
- script.stop: ramp_on_script
- script.stop: ramp_off_script
- light.turn_off:
@@ -714,7 +713,7 @@ number:
id(last_brightness_pct) = 0.0f;
id(last_set_pos) = 0;
- delay: 400ms
- lambda: 'id(suppress_slider_sync) = false;'
- lambda: "id(suppress_slider_sync) = false;"
else:
- lambda: |-
id(suppress_slider_sync) = true;
@@ -745,7 +744,7 @@ number:
if (out_pct > maxp) out_pct = maxp;
id(last_brightness_pct) = out_pct;
- delay: 400ms
- lambda: 'id(suppress_slider_sync) = false;'
- lambda: "id(suppress_slider_sync) = false;"
- platform: template
id: cfg_max_on_hours
@@ -768,12 +767,12 @@ number:
id(cfg_max_on_hours).publish_state((float) hrs);
- if:
condition:
lambda: 'return id(mosfet_leds).current_values.is_on();'
lambda: "return id(mosfet_leds).current_values.is_on();"
then:
- script.stop: max_on_watchdog
- if:
condition:
lambda: 'return id(max_on_hours) > 0;'
lambda: "return id(max_on_hours) > 0;"
then:
- script.execute: max_on_watchdog
@@ -785,7 +784,7 @@ script:
- id: ramp_on_script
mode: restart
then:
- lambda: 'id(is_ramping) = true;'
- lambda: "id(is_ramping) = true;"
- script.stop: ramp_off_script
- if:
condition:
@@ -796,11 +795,11 @@ script:
then:
- light.turn_on:
id: mosfet_leds
brightness: !lambda 'return id(min_brightness_pct) / 100.0f;'
brightness: !lambda "return id(min_brightness_pct) / 100.0f;"
transition_length: 80ms
- light.turn_on:
id: mosfet_leds
brightness: !lambda 'return id(max_brightness_pct) / 100.0f;'
brightness: !lambda "return id(max_brightness_pct) / 100.0f;"
transition_length: !lambda |-
const auto &cv = id(mosfet_leds).current_values;
const float floor = id(min_brightness_pct) / 100.0f;
@@ -820,7 +819,7 @@ script:
if (frac > 1.0f) frac = 1.0f;
id(last_ramp_ms) = (int) (id(ramp_up_ms) * frac);
return (uint32_t) id(last_ramp_ms);
- delay: !lambda 'return (uint32_t) id(last_ramp_ms);'
- delay: !lambda "return (uint32_t) id(last_ramp_ms);"
- lambda: |-
id(is_ramping) = false;
const auto &cv = id(mosfet_leds).current_values;
@@ -832,7 +831,7 @@ script:
- id: ramp_to_target_script
mode: restart
then:
- lambda: 'id(is_ramping) = true;'
- lambda: "id(is_ramping) = true;"
- script.stop: ramp_off_script
- if:
condition:
@@ -843,7 +842,7 @@ script:
then:
- light.turn_on:
id: mosfet_leds
brightness: !lambda 'return id(min_brightness_pct) / 100.0f;'
brightness: !lambda "return id(min_brightness_pct) / 100.0f;"
transition_length: 80ms
- light.turn_on:
id: mosfet_leds
@@ -873,7 +872,7 @@ script:
if (frac > 1.0f) frac = 1.0f;
id(last_ramp_ms) = (int) (id(ramp_up_ms) * frac);
return (uint32_t) id(last_ramp_ms);
- delay: !lambda 'return (uint32_t) id(last_ramp_ms);'
- delay: !lambda "return (uint32_t) id(last_ramp_ms);"
- lambda: |-
id(is_ramping) = false;
const auto &cv = id(mosfet_leds).current_values;
@@ -891,7 +890,7 @@ script:
- script.stop: ramp_on_script
- light.turn_on:
id: mosfet_leds
brightness: !lambda 'return id(min_brightness_pct) / 100.0f;'
brightness: !lambda "return id(min_brightness_pct) / 100.0f;"
transition_length: !lambda |-
const auto &cv = id(mosfet_leds).current_values;
const float floor = id(min_brightness_pct) / 100.0f;
@@ -904,7 +903,7 @@ script:
if (frac > 1.0f) frac = 1.0f;
id(last_ramp_ms) = (int) (id(ramp_down_ms) * frac);
return (uint32_t) id(last_ramp_ms);
- delay: !lambda 'return (uint32_t) id(last_ramp_ms);'
- delay: !lambda "return (uint32_t) id(last_ramp_ms);"
- light.turn_off:
id: mosfet_leds
transition_length: 150ms
@@ -921,12 +920,12 @@ script:
then:
- if:
condition:
lambda: 'return id(max_on_hours) > 0;'
lambda: "return id(max_on_hours) > 0;"
then:
- delay: !lambda 'return (uint32_t) (id(max_on_hours) * 3600000UL);'
- delay: !lambda "return (uint32_t) (id(max_on_hours) * 3600000UL);"
- if:
condition:
lambda: 'return id(mosfet_leds).current_values.is_on();'
lambda: "return id(mosfet_leds).current_values.is_on();"
then:
- lambda: |-
id(ramp_switch_target_on) = false;
@@ -950,17 +949,17 @@ script:
- if:
condition:
lambda: 'return id(restore_target_pct) > 0.5f;'
lambda: "return id(restore_target_pct) > 0.5f;"
then:
- lambda: |-
id(ramp_switch_target_on) = true;
id(suppress_slider_sync) = true;
- script.stop: ramp_off_script
- script.execute: ramp_to_target_script
- delay: !lambda 'return (uint32_t) id(last_ramp_ms);'
- lambda: 'id(suppress_slider_sync) = false;'
- delay: !lambda "return (uint32_t) id(last_ramp_ms);"
- lambda: "id(suppress_slider_sync) = false;"
else:
- lambda: 'id(ramp_switch_target_on) = false;'
- lambda: "id(ramp_switch_target_on) = false;"
- light.turn_off:
id: mosfet_leds
transition_length: 0s
esphome/esp-downstkitchlights.yaml
+24 -2
View File
@@ -6,6 +6,7 @@
# https://home.fox.co.nz/gitea/zorruno/zorruno-homeassistant/src/branch/master/esphome/esp-downstkitchlights.yaml
#:########################################################################################:#
# VERSIONS:
# v2.2 2026-07-20 Restored direct MQTT control of pantry LEDs using the flattened topic
# v2.1 2026-02-25 Updated yaml to zorruno layout V1.1
# v2.0 2025-06-05 YAML tidyups
# v1.0 2025-03-28 Initial Version
@@ -21,6 +22,13 @@
# - Relay 1: Dining Light
# - Relay 2: Kitchen Light
# - Relay 3: Extract Fan (virtual only, no power connected to 3rd relay)
# - Relay 2 publishes ON/OFF commands directly to the downstairs kitchen pantry LEDs.
#:########################################################################################:#
# MQTT COMMANDS:
# - Remote command topic:
# ${mqtt_remote_device_command_topic}
# Payload "${mqtt_remote_device_command_on}" -> pantry LEDs ON
# Payload "${mqtt_remote_device_command_off}" -> pantry LEDs OFF
#:########################################################################################:#
# OFFLINE NOTES:
# a) Home Assistant OFFLINE, but Network and MQTT ONLINE
@@ -36,7 +44,6 @@
# - Accurate time is NOT needed (SNTP not needed)
#:########################################################################################:#
#:########################################################################################:#
# SUBSTITUTIONS: Specific device variable substitutions
# If NOT using a secrets file, just replace these with the passwords etc (in quotes)
@@ -50,7 +57,7 @@ substitutions:
# Project Naming
project_name: "Zemismart Technologies.KS-811 Triple"
project_version: "v2.1"
project_version: "v2.2"
# Passwords & Secrets
api_key: !secret esp-api_key # unfortunately you can't use substitutions inside secrets names
@@ -61,6 +68,13 @@ substitutions:
# Don't forget to switch it back when changed.
current_ip_address: ${static_ip_address}
# MQTT REMOTE Controls
mqtt_command_main_topic: !secret mqtt_command_main_topic
mqtt_remote_device_name: "downstairskitchen-pantryleds"
mqtt_remote_device_command_topic: "${mqtt_command_main_topic}/${mqtt_remote_device_name}"
mqtt_remote_device_command_on: "ON"
mqtt_remote_device_command_off: "OFF"
# Device Settings
log_level: "INFO" # NONE, ERROR, WARN, INFO, DEBUG (Default), VERBOSE, VERY_VERBOSE
update_interval: "60s" # update time for general sensors etc
@@ -195,6 +209,14 @@ switch:
name: "Relay 2: ${switch_2_name}"
pin: GPIO12
id: Relay_2
on_turn_on:
- mqtt.publish:
topic: "${mqtt_remote_device_command_topic}"
payload: "${mqtt_remote_device_command_on}"
on_turn_off:
- mqtt.publish:
topic: "${mqtt_remote_device_command_topic}"
payload: "${mqtt_remote_device_command_off}"
- platform: gpio
name: "Relay 3: ${switch_3_name}"
esphome/esp-downstloungeentry.yaml
+6 -6
View File
@@ -6,6 +6,7 @@
# https://home.fox.co.nz/gitea/zorruno/zorruno-homeassistant/src/branch/master/esphome/esp-downstloungeentry.yaml
#:########################################################################################:#
# VERSIONS:
# v3.8 2026-07-20 Updated remote MQTT topics for the flattened downstairs lounge main lights topic
# v3.7 2026-02-25 Updated yaml to zorruno layout V1.1
# v3.6 2025-07-24 YAML tidyups
#:########################################################################################:#
@@ -45,7 +46,6 @@
# - Accurate time is NOT needed (SNTP not needed)
#:########################################################################################:#
#:########################################################################################:#
# SUBSTITUTIONS: Specific device variable substitutions
# If NOT using a secrets file, just replace these with the passwords etc (in quotes)
@@ -59,7 +59,7 @@ substitutions:
# Project Naming
project_name: "Zemismart Technologies.KS-811 Single"
project_version: "v3.7"
project_version: "v3.8"
# Passwords & Secrets
api_key: !secret esp-api_key # unfortunately you can't use substitutions inside secrets names
@@ -78,8 +78,8 @@ substitutions:
# MQTT REMOTE Controls
mqtt_remote_device_name: "downst-lounge-main-lights"
mqtt_remote_device_command_topic: "${mqtt_command_main_topic}/${mqtt_remote_device_name}/light1/set"
mqtt_remote_status_topic: "${mqtt_status_main_topic}/${mqtt_remote_device_name}/light1/state"
mqtt_remote_device_command_topic: "${mqtt_command_main_topic}/${mqtt_remote_device_name}"
mqtt_remote_status_topic: "${mqtt_status_main_topic}/${mqtt_remote_device_name}"
mqtt_remote_device_command_on: "On"
mqtt_remote_device_command_off: "Off"
@@ -170,7 +170,7 @@ mqtt:
- delay: 50ms
- if:
condition:
lambda: 'return !id(Relay_1).state;'
lambda: "return !id(Relay_1).state;"
then:
- switch.turn_on: Relay_1
@@ -180,7 +180,7 @@ mqtt:
- delay: 50ms
- if:
condition:
lambda: 'return id(Relay_1).state;'
lambda: "return id(Relay_1).state;"
then:
- switch.turn_off: Relay_1
esphome/esp-downstloungemain.yaml
+8 -8
View File
@@ -6,6 +6,7 @@
# https://home.fox.co.nz/gitea/zorruno/zorruno-homeassistant/src/branch/master/esphome/esp-downstloungemain.yaml
#:########################################################################################:#
# VERSIONS:
# v3.7 2026-07-20 Simplified local MQTT command and status topics to the device root
# v3.6 2026-02-25 Updated yaml to zorruno layout V1.1
# v3.5 2025-07-28 YAML tidyups
#:########################################################################################:#
@@ -23,12 +24,12 @@
#:########################################################################################:#
# MQTT COMMANDS:
# - Local command topic (Main Lights):
# ${mqtt_local_command_topic}/light1/set
# ${mqtt_local_command_topic}
# Payload "On" -> Relay 1 ON
# Payload "Off" -> Relay 1 OFF
#
# - Local status topic (Main Lights):
# ${mqtt_local_status_topic}/light1/state
# ${mqtt_local_status_topic}
# Payload "On" / "Off" published when Relay 1 changes state
#:########################################################################################:#
# OFFLINE NOTES:
@@ -45,7 +46,6 @@
# - Accurate time is NOT needed (SNTP not needed).
#:########################################################################################:#
#:########################################################################################:#
# SUBSTITUTIONS: Specific device variable substitutions
# If NOT using a secrets file, just replace these with the passwords etc (in quotes)
@@ -59,7 +59,7 @@ substitutions:
# Project Naming
project_name: "Zemismart Technologies.KS-811 Triple"
project_version: "v3.6"
project_version: "v3.7"
# Passwords & Secrets
api_key: !secret esp-api_key
@@ -156,11 +156,11 @@ logger:
mqtt:
on_message:
# Main Lights control (Relay 1)
- topic: "${mqtt_local_command_topic}/light1/set"
- topic: "${mqtt_local_command_topic}"
payload: "On"
then:
- switch.turn_on: relay_1
- topic: "${mqtt_local_command_topic}/light1/set"
- topic: "${mqtt_local_command_topic}"
payload: "Off"
then:
- switch.turn_off: relay_1
@@ -222,11 +222,11 @@ switch:
id: relay_1
on_turn_on:
- mqtt.publish:
topic: "${mqtt_local_status_topic}/light1/state"
topic: "${mqtt_local_status_topic}"
payload: "On"
on_turn_off:
- mqtt.publish:
topic: "${mqtt_local_status_topic}/light1/state"
topic: "${mqtt_local_status_topic}"
payload: "Off"
# Relay 2 (GPIO12)
esphome/esp-gasheater copy.yaml.old
-1342
View File
File diff suppressed because it is too large Load Diff
esphome/esp-loungebookshelfleds.yaml
+10 -10
View File
@@ -6,6 +6,7 @@
# https://home.fox.co.nz/gitea/zorruno/zorruno-homeassistant/src/branch/master/esphome/esp-loungebookshelfleds.yaml
#:########################################################################################:#
# VERSIONS:
# V2.2 2026-07-20 Simplified local MQTT command and status topics to the device root
# V2.1 2026-03-11 Updated yaml to zorruno layout V1.1
# V2.0 2025-09-15 A bunch of fixes and made it more standard across my devices
# V1.0 2025-08-17 First setup (and replacement of Tasmota)
@@ -48,10 +49,10 @@
# - Maximum ON time before automatic fade-down (1-48 h, 0 = no limit)
#
# MQTT COMMANDS:
# - ${mqtt_local_command_topic}/light/set = ON
# - ${mqtt_local_command_topic}/light/set = OFF
# - ${mqtt_local_command_topic} = ON
# - ${mqtt_local_command_topic} = OFF
# - State publishes to:
# - ${mqtt_local_status_topic}/light/state
# - ${mqtt_local_status_topic}
#:########################################################################################:#
# OFFLINE NOTES:
# a) Home Assistant offline (network and MQTT online):
@@ -84,7 +85,7 @@ substitutions:
# Project Naming
project_name: "Magichome Single Colour V1.1 LED Controller.Generic ESP8266" # Project details. Manufacturer before the dot, device after the dot.
project_version: "v2.1" # Project version denotes release of the YAML file, allowing checking of deployed vs latest version
project_version: "v2.2" # Project version denotes release of the YAML file, allowing checking of deployed vs latest version
# Passwords & Secrets (Unfortunately, you can't use substitutions inside secret names)
api_key: !secret esp-api_key # If using HA API
@@ -132,8 +133,7 @@ packages:
local_ota_pass: "${ota_pass}"
#### HOME ASSISTANT API (choose encryption or no encryption options) ####
common_api: !include
#file: common/api_common.yaml
common_api: !include #file: common/api_common.yaml
file: common/api_common_noencryption.yaml
vars:
local_api_key: "${api_key}"
@@ -351,12 +351,12 @@ status_led:
mqtt:
on_message:
# Light control to ramp up
- topic: "${mqtt_local_command_topic}/light/set"
- topic: "${mqtt_local_command_topic}"
payload: "${mqtt_local_device_command_ON}"
then:
- switch.turn_on: mosfet_ramp_switch
# Light control to ramp down
- topic: "${mqtt_local_command_topic}/light/set"
- topic: "${mqtt_local_command_topic}"
payload: "${mqtt_local_device_command_OFF}"
then:
- switch.turn_off: mosfet_ramp_switch
@@ -593,7 +593,7 @@ light:
on_turn_on:
- output.turn_on: green_led_out
- mqtt.publish:
topic: "${mqtt_local_status_topic}/light/state"
topic: "${mqtt_local_status_topic}"
payload: "${mqtt_local_device_command_ON}"
retain: true
- lambda: |-
@@ -617,7 +617,7 @@ light:
lambda: "return !id(booting);"
then:
- mqtt.publish:
topic: "${mqtt_local_status_topic}/light/state"
topic: "${mqtt_local_status_topic}"
payload: "${mqtt_local_device_command_OFF}"
retain: true
- lambda: "id(ramp_switch_target_on) = false;"
esphome/esp-loungecabinetleds.yaml
+42 -42
View File
@@ -6,6 +6,7 @@
# https://home.fox.co.nz/gitea/zorruno/zorruno-homeassistant/src/branch/master/esphome/esp-loungecabinetleds.yaml
#:########################################################################################:#
# VERSIONS:
# V2.2 2026-07-20 Simplified local MQTT command and status topics to the device root
# V2.1 2026-03-11 Updated yaml to zorruno layout V1.1
# V2.0 2025-09-15 A bunch of fixes, this is now the master for other similar mosfet controllers of mine
# V1.5 2025-09-11 First setup (copied from another template)
@@ -50,10 +51,10 @@
# - Maximum ON time before automatic fade-down (1-48 h, 0 = no limit)
#
# MQTT COMMANDS:
# - ${mqtt_local_command_topic}/light/set = ON
# - ${mqtt_local_command_topic}/light/set = OFF
# - ${mqtt_local_command_topic} = ON
# - ${mqtt_local_command_topic} = OFF
# - State publishes to:
# - ${mqtt_local_status_topic}/light/state
# - ${mqtt_local_status_topic}
#:########################################################################################:#
# OFFLINE NOTES:
# a) Home Assistant offline (network and MQTT online)
@@ -80,7 +81,7 @@ substitutions:
# Project Naming
project_name: "Sinilink.XY-WFMS" # Project details. Manufacturer before the dot, device after the dot.
project_version: "v2.1" # Project version denotes release of the YAML file, allowing checking of deployed vs latest version
project_version: "v2.2" # Project version denotes release of the YAML file, allowing checking of deployed vs latest version
# Passwords & Secrets (Unfortunately, you can't use substitutions inside secret names)
api_key: !secret esp-api_key # If using HA API
@@ -130,8 +131,7 @@ packages:
local_current_ip_address: "${current_ip_address}"
#### HOME ASSISTANT API (choose encryption or no encryption options) ####
common_api: !include
#file: common/api_common.yaml
common_api: !include #file: common/api_common.yaml
file: common/api_common_noencryption.yaml
vars:
local_api_key: "${api_key}"
@@ -181,32 +181,32 @@ esphome:
# Mode 0: Fade up to full (obeys fade settings; no on/off flicker)
- if:
condition:
lambda: 'return id(restart_mode) == 0;'
lambda: "return id(restart_mode) == 0;"
then:
- lambda: 'id(ramp_switch_target_on) = true;'
- lambda: "id(ramp_switch_target_on) = true;"
- script.execute: ramp_on_script
# Mode 1: Restore Brightness (deferred to avoid races)
- if:
condition:
lambda: 'return id(restart_mode) == 1;'
lambda: "return id(restart_mode) == 1;"
then:
- script.execute: deferred_restore_brightness
# Mode 2: Remain Off (no blip; stays off)
- if:
condition:
lambda: 'return id(restart_mode) == 2;'
lambda: "return id(restart_mode) == 2;"
then:
- script.stop: ramp_on_script
- script.stop: ramp_off_script
- lambda: 'id(ramp_switch_target_on) = false;'
- lambda: "id(ramp_switch_target_on) = false;"
- light.turn_off:
id: mosfet_leds
transition_length: 0s
# Boot complete: allow OFF handlers again
- lambda: 'id(booting) = false;'
- lambda: "id(booting) = false;"
# NEW: force indicator OFF after boot logic
# (Removed: output.turn_off: green_led_out)
@@ -365,13 +365,13 @@ status_led:
mqtt:
on_message:
# Light control to ramp up
- topic: "${mqtt_local_command_topic}/light/set"
- topic: "${mqtt_local_command_topic}"
payload: "${mqtt_local_device_command_ON}"
then:
- switch.turn_on: mosfet_ramp_switch
# Light control to ramp down
- topic: "${mqtt_local_command_topic}/light/set"
- topic: "${mqtt_local_command_topic}"
payload: "${mqtt_local_device_command_OFF}"
then:
- switch.turn_off: mosfet_ramp_switch
@@ -503,7 +503,7 @@ binary_sensor:
on_press:
- if:
condition:
lambda: 'return id(ramp_switch_target_on);'
lambda: "return id(ramp_switch_target_on);"
then:
# Target is currently ON -> press should go OFF (start ramp-down)
- lambda: |-
@@ -608,7 +608,7 @@ light:
on_turn_on:
- output.turn_on: green_led_out
- mqtt.publish:
topic: "${mqtt_local_status_topic}/light/state"
topic: "${mqtt_local_status_topic}"
payload: "${mqtt_local_device_command_ON}"
retain: true
- lambda: |-
@@ -619,7 +619,7 @@ light:
- script.stop: max_on_watchdog
- if:
condition:
lambda: 'return id(max_on_hours) > 0;'
lambda: "return id(max_on_hours) > 0;"
then:
- script.execute: max_on_watchdog
@@ -629,13 +629,13 @@ light:
- output.turn_off: green_led_out
- if:
condition:
lambda: 'return !id(booting);'
lambda: "return !id(booting);"
then:
- mqtt.publish:
topic: "${mqtt_local_status_topic}/light/state"
topic: "${mqtt_local_status_topic}"
payload: "${mqtt_local_device_command_OFF}"
retain: true
- lambda: 'id(ramp_switch_target_on) = false;'
- lambda: "id(ramp_switch_target_on) = false;"
- script.stop: max_on_watchdog
- lambda: |-
id(last_brightness_pct) = 0.0f;
@@ -724,10 +724,10 @@ number:
set_action:
- if:
condition:
lambda: 'return x <= 0.0f;'
lambda: "return x <= 0.0f;"
then:
# 0 means OFF
- lambda: 'id(suppress_slider_sync) = true;'
- lambda: "id(suppress_slider_sync) = true;"
- script.stop: ramp_on_script
- script.stop: ramp_off_script
- light.turn_off:
@@ -739,7 +739,7 @@ number:
id(last_brightness_pct) = 0.0f; // persist OFF immediately
id(last_set_pos) = 0;
- delay: 400ms
- lambda: 'id(suppress_slider_sync) = false;'
- lambda: "id(suppress_slider_sync) = false;"
else:
# Map 1..100 - [min..max] and set ON
- lambda: |-
@@ -771,7 +771,7 @@ number:
if (out_pct > maxp) out_pct = maxp;
id(last_brightness_pct) = out_pct; // persist exact target now
- delay: 400ms
- lambda: 'id(suppress_slider_sync) = false;'
- lambda: "id(suppress_slider_sync) = false;"
- platform: template
id: cfg_max_on_hours
@@ -794,12 +794,12 @@ number:
id(cfg_max_on_hours).publish_state((float) hrs);
- if:
condition:
lambda: 'return id(mosfet_leds).current_values.is_on();'
lambda: "return id(mosfet_leds).current_values.is_on();"
then:
- script.stop: max_on_watchdog
- if:
condition:
lambda: 'return id(max_on_hours) > 0;'
lambda: "return id(max_on_hours) > 0;"
then:
- script.execute: max_on_watchdog
@@ -813,7 +813,7 @@ script:
- id: ramp_on_script
mode: restart
then:
- lambda: 'id(is_ramping) = true;'
- lambda: "id(is_ramping) = true;"
- script.stop: ramp_off_script
# Ensure we start at at least the floor without a visible "pop".
- if:
@@ -825,12 +825,12 @@ script:
then:
- light.turn_on:
id: mosfet_leds
brightness: !lambda 'return id(min_brightness_pct) / 100.0f;'
brightness: !lambda "return id(min_brightness_pct) / 100.0f;"
transition_length: 80ms
# Ramp from current (>= floor) to cap over a fraction of ramp_up_ms.
- light.turn_on:
id: mosfet_leds
brightness: !lambda 'return id(max_brightness_pct) / 100.0f;'
brightness: !lambda "return id(max_brightness_pct) / 100.0f;"
transition_length: !lambda |-
const auto &cv = id(mosfet_leds).current_values;
const float floor = id(min_brightness_pct) / 100.0f;
@@ -850,7 +850,7 @@ script:
if (frac > 1.0f) frac = 1.0f;
id(last_ramp_ms) = (int) (id(ramp_up_ms) * frac);
return (uint32_t) id(last_ramp_ms);
- delay: !lambda 'return (uint32_t) id(last_ramp_ms);'
- delay: !lambda "return (uint32_t) id(last_ramp_ms);"
- lambda: |-
id(is_ramping) = false;
const auto &cv = id(mosfet_leds).current_values;
@@ -863,7 +863,7 @@ script:
- id: ramp_to_target_script
mode: restart
then:
- lambda: 'id(is_ramping) = true;'
- lambda: "id(is_ramping) = true;"
- script.stop: ramp_off_script
# Ensure we start at the floor cleanly.
- if:
@@ -875,7 +875,7 @@ script:
then:
- light.turn_on:
id: mosfet_leds
brightness: !lambda 'return id(min_brightness_pct) / 100.0f;'
brightness: !lambda "return id(min_brightness_pct) / 100.0f;"
transition_length: 80ms
# Ramp from current (>= floor) to restore_target_pct over a fraction of ramp_up_ms.
- light.turn_on:
@@ -906,7 +906,7 @@ script:
if (frac > 1.0f) frac = 1.0f;
id(last_ramp_ms) = (int) (id(ramp_up_ms) * frac);
return (uint32_t) id(last_ramp_ms);
- delay: !lambda 'return (uint32_t) id(last_ramp_ms);'
- delay: !lambda "return (uint32_t) id(last_ramp_ms);"
- lambda: |-
id(is_ramping) = false;
const auto &cv = id(mosfet_leds).current_values;
@@ -925,7 +925,7 @@ script:
- script.stop: ramp_on_script
- light.turn_on:
id: mosfet_leds
brightness: !lambda 'return id(min_brightness_pct) / 100.0f;'
brightness: !lambda "return id(min_brightness_pct) / 100.0f;"
transition_length: !lambda |-
const auto &cv = id(mosfet_leds).current_values;
const float floor = id(min_brightness_pct) / 100.0f;
@@ -938,7 +938,7 @@ script:
if (frac > 1.0f) frac = 1.0f;
id(last_ramp_ms) = (int) (id(ramp_down_ms) * frac);
return (uint32_t) id(last_ramp_ms);
- delay: !lambda 'return (uint32_t) id(last_ramp_ms);'
- delay: !lambda "return (uint32_t) id(last_ramp_ms);"
- light.turn_off:
id: mosfet_leds
transition_length: 150ms
@@ -955,12 +955,12 @@ script:
then:
- if:
condition:
lambda: 'return id(max_on_hours) > 0;'
lambda: "return id(max_on_hours) > 0;"
then:
- delay: !lambda 'return (uint32_t) (id(max_on_hours) * 3600000UL);'
- delay: !lambda "return (uint32_t) (id(max_on_hours) * 3600000UL);"
- if:
condition:
lambda: 'return id(mosfet_leds).current_values.is_on();'
lambda: "return id(mosfet_leds).current_values.is_on();"
then:
- lambda: |-
id(ramp_switch_target_on) = false;
@@ -987,18 +987,18 @@ script:
- if:
condition:
lambda: 'return id(restore_target_pct) > 0.5f;'
lambda: "return id(restore_target_pct) > 0.5f;"
then:
- lambda: |-
id(ramp_switch_target_on) = true; // reflect our intent
id(suppress_slider_sync) = true;
- script.stop: ramp_off_script
- script.execute: ramp_to_target_script
- delay: !lambda 'return (uint32_t) id(last_ramp_ms);'
- lambda: 'id(suppress_slider_sync) = false;'
- delay: !lambda "return (uint32_t) id(last_ramp_ms);"
- lambda: "id(suppress_slider_sync) = false;"
else:
# Exact last was 0 -> remain OFF
- lambda: 'id(ramp_switch_target_on) = false;'
- lambda: "id(ramp_switch_target_on) = false;"
- light.turn_off:
id: mosfet_leds
transition_length: 0s
esphome/esp-loungemiddleswitch.yaml.old
-507
View File
@@ -1,507 +0,0 @@
#:########################################################################################:#
# TITLE: LOUNGE MIDDLE LIGHTSWITCH
# zorruno.com layout v1.1 2026
#:########################################################################################:#
# REPO:
# https://home.fox.co.nz/gitea/zorruno/zorruno-homeassistant/src/branch/master/esphome/esp-loungemiddleswitch.yaml
#:########################################################################################:#
# VERSIONS:
# V3.6 2026-03-11 Updated yaml to zorruno layout V1.1
# V3.5 2025-07-28 YAML tidyups
#:########################################################################################:#
# HARDWARE:
# - Zemismart KS-811 Triple push button
# - ESP8266 based
# - pinout/schematic:
# https://community.home-assistant.io/t/zemismart-ks-811-working-with-esphome/
# - Relay 1 output on GPIO13
# - Relay 2 output on GPIO12
# - Relay 3 output on GPIO14
# - Button 1 input on GPIO16
# - Button 2 input on GPIO5
# - Button 3 input on GPIO4
# - Status LED on GPIO2
#:########################################################################################:#
# OPERATION NOTES:
# - Button 1:
# - Online with HA Loss manual override ON and HA Loss Test OFF:
# - Uses Home Assistant last-scene logic
# - If last scene is not "All Off", set "All Off"
# - If last scene is "All Off", set "Bright"
# - Offline/test with HA Loss manual override ON:
# - Toggles Relay_1 locally
# - Button 2:
# - Online with HA Loss manual override ON and HA Loss Test OFF:
# - Sets Home Assistant scene "Movie"
# - Offline/test with HA Loss manual override ON:
# - Toggles Relay_2 locally
# - Button 3:
# - Online with HA Loss manual override ON and HA Loss Test OFF:
# - Sets Home Assistant scene "Reading On/Off"
# - Offline/test with HA Loss manual override ON:
# - Toggles Relay_3 locally
# - On API connect:
# - If HA Loss Test is OFF, Relay_1 and Relay_2 follow HA Loss manual override state
# - If HA Loss Test is ON, relay override is not applied
# - HA Loss manual override defaults ON and persists across restarts
# - HA Loss Test defaults OFF and can force offline/test behaviour even when HA is connected
#:########################################################################################:#
# OFFLINE NOTES:
# a) Home Assistant offline (network online):
# - Device switches to manual/offline behaviour
# - Buttons still operate local relays if HA Loss manual override is ON
# - Home Assistant scene calls are unavailable
# b) MQTT offline (or HA/MQTT offline):
# - This yaml does not depend on MQTT for its button logic
# - If Home Assistant/API is offline, device falls back to manual/offline behaviour
# - Buttons still operate local relays if HA Loss manual override is ON
# c) Entire WiFi/Network offline:
# - Device operates in local manual/offline behaviour only
# - Buttons still operate local relays if HA Loss manual override is ON
# - Accurate time is not needed; SNTP is not required for operation
#:########################################################################################:#
#:########################################################################################:#
# SUBSTITUTIONS:
# Specific device variable substitutions
# If NOT using a secrets file, just replace these with the passwords etc (in quotes)
#:########################################################################################:#
substitutions:
# Device Naming
device_name: "esp-loungemiddleswitch"
friendly_name: "Lounge Middle Lightswitch (3)"
description_comment: "Lounge Main Lightswitch using a Zemismart KS-811 Triple Push Button. Downlights South (1), Downlights Middle (2), Downlights North (3) (Layout V1.1)"
device_area: "Lounge" # Allows ESP device to be automatically linked to an 'Area' in Home Assistant.
# Project Naming
project_name: "Zemismart Technologies.KS-811 Triple" # Project Details
project_version: "v3.6" # Project V denotes release of yaml file, allowing checking of deployed vs latest version
# Passwords & Secrets
api_key: !secret esp-api_key # unfortunately you can't use substitutions inside secrets names
ota_pass: !secret esp-ota_pass # unfortunately you can't use substitutions inside secrets names
static_ip_address: !secret esp-loungemiddleswitch_ip
# If we are changing IP addresses, you must update the current IP address here, otherwise it remains
# Don't forget to switch it back when changed.
current_ip_address: ${static_ip_address}
# Device Settings
log_level: "INFO" # Define logging level: NONE, ERROR, WARN, INFO, DEBUG (Default), VERBOSE, VERY_VERBOSE
update_interval: "60s" # update time for for general sensors etc
# MQTT LOCAL Controls
#mqtt_device_name: "lounge-main-lights"
#mqtt_local_command_topic: "${mqtt_command_main_topic}/${mqtt_device_name}" # Topic we will use to command this locally without HA
#mqtt_local_status_topic: "${mqtt_status_main_topic}/${mqtt_device_name}" # Topic we will use to view status locally without HA
# MQTT REMOTE Controls
# Switch/Relay/Button Naming & Icons
#relay_icon: "mdi:lightbulb-group"
switch_1_name: "Downlights South" # Lights are connected via DMX dimmer (another esphome controller) (4 Downlights)
switch_2_name: "Downlights Middle" # Lights are connected via DMX dimmer (another esphome controller) (6 Downlights)
switch_3_name: "Downlights North" # Lights are directly connected (2 downlights)
#:########################################################################################:#
# PACKAGES:
# Included Common Packages
# https://esphome.io/components/packages.html
#:########################################################################################:#
packages:
#### WIFI, Network (Static/DHCP/IPV6 etc), Fallback AP, Safemode ####
common_wifi: !include
file: common/network_common.yaml
vars:
local_device_name: "${device_name}"
local_static_ip_address: "${static_ip_address}"
local_current_ip_address: "${current_ip_address}"
local_ota_pass: "${ota_pass}"
#### HOME ASSISTANT API (choose encryption or no encryption options) ####
common_api: !include
file: common/api_common.yaml
#file: common/api_common_noencryption.yaml
vars:
local_api_key: "${api_key}"
#### MQTT ####
common_mqtt: !include
file: common/mqtt_common.yaml
vars:
local_device_name: "${device_name}"
#### WEB PORTAL ####
#common_webportal: !include common/webportal_common.yaml
#### SNTP (Only use if you want/need accurate timeclocks) ####
#common_sntp: !include common/sntp_common.yaml
#### DIAGNOSTICS Sensors ####
diag_basic: !include common/include_basic_diag_sensors.yaml
diag_more: !include common/include_more_diag_sensors.yaml
#diag_debug: !include common/include_debug_diag_sensors.yaml
#diag_resetcount: !include common/include_resetcount_diag_sensors.yaml
#:########################################################################################:#
# ESPHOME:
# https://esphome.io/components/esphome.html
#:########################################################################################:#
esphome:
name: "${device_name}"
friendly_name: "${friendly_name}"
comment: "${description_comment}" # Appears on the esphome page in HA
area: "${device_area}"
project:
name: "${project_name}"
version: "${project_version}"
#:########################################################################################:#
# HOME ASSISTANT API:
#:########################################################################################:#
api:
on_client_connected:
then:
- logger.log:
level: INFO
format: "API connected: override=%s, ha_loss_test=%s"
args:
- 'id(ha_loss_override).state ? "true" : "false"'
- 'id(ha_loss_test).state ? "true" : "false"'
- if:
condition:
switch.is_on: ha_loss_test
then:
- logger.log:
level: WARN
format: "HA Loss Test is ON: not applying relay override on connect"
else:
- if:
condition:
switch.is_on: ha_loss_override
then:
- switch.turn_on: Relay_1
- switch.turn_on: Relay_2
else:
- switch.turn_off: Relay_1
- switch.turn_off: Relay_2
on_client_disconnected:
then:
- logger.log:
level: WARN
format: "API disconnected: switching to manual/offline behavior"
#:########################################################################################:#
# ESP PLATFORM AND FRAMEWORK:
# https://esphome.io/components/esp8266.html
#:########################################################################################:#
esp8266:
board: esp01_1m
early_pin_init: false # Initialise pins early to known values. Recommended false where switches are involved. Defaults to True.
board_flash_mode: dout # Default is dout
#:########################################################################################:#
# LOGGER:
# https://esphome.io/components/logger.html
#:########################################################################################:#
logger:
level: "${log_level}" # INFO Level suggested, or DEBUG for testing
#baud_rate: 0 # set to 0 for no logging via UART, needed if you are using it for other serial things (eg PZEM)
#esp8266_store_log_strings_in_flash: false
#tx_buffer_size: 64
#:########################################################################################:#
# STATUS LED:
# https://esphome.io/components/status_led.html
#:########################################################################################:#
status_led:
pin:
number: GPIO2
inverted: true
#:########################################################################################:#
# BINARY SENSORS:
# https://esphome.io/components/binary_sensor/
#:########################################################################################:#
binary_sensor:
# GPIO16 for KS-811 first button UNLESS
# it is a single button KS-811 in which case it is GPIO00
- platform: gpio
pin:
number: GPIO16
mode: INPUT
inverted: true
use_interrupt: false # This pin doesn't support interrupts so use polling. Only suppresses a warning.
name: "Button 1: ${switch_1_name}"
on_multi_click:
# --- Single short click ---
# Online (and override ON, and NOT test mode): use HA's last scene to decide.
# Offline (override ON): toggle physical Relay_1
# Test mode (override ON): behave like offline even if HA is connected
- timing:
- ON for at most 0.5s
- OFF for at least 0.5s
then:
- if:
condition:
and:
- switch.is_on: ha_loss_override
- api.connected:
- not:
switch.is_on: ha_loss_test
then:
- if:
condition:
lambda: |-
// Defensive: treat empty/unknown as "not All Off" so we go to a safe "All Off".
auto s = id(ha_last_scene).state;
if (s.empty() || s == "unknown" || s == "unavailable") return true;
return s != "All Off";
then:
- homeassistant.service:
service: script.lounge_set_scene
data:
scene_name: "All Off"
- logger.log:
level: INFO
format: "BTN1: Single click (online) -> Last scene was not 'All Off' -> Set 'All Off'"
else:
- homeassistant.service:
service: script.lounge_set_scene
data:
scene_name: "Bright"
- logger.log:
level: INFO
format: "BTN1: Single click (online) -> Last scene was 'All Off' -> Set 'Bright'"
else:
- if:
condition:
and:
- switch.is_on: ha_loss_override
- or:
- not:
api.connected:
- switch.is_on: ha_loss_test
then:
- if:
condition:
lambda: |-
return id(Relay_1).state;
then:
- switch.turn_off: Relay_1
- logger.log:
level: INFO
format: "BTN1: Single click (offline/test) -> Relay_1 OFF"
else:
- switch.turn_on: Relay_1
- logger.log:
level: INFO
format: "BTN1: Single click (offline/test) -> Relay_1 ON"
else:
- logger.log:
level: INFO
format: "BTN1: Single click ignored (override OFF)"
# GPIO05 for second button (only for KS-811-2 Double or -3 Triple)
- platform: gpio
pin:
number: GPIO5
mode: INPUT
inverted: true
name: "Button 2: ${switch_2_name}"
on_multi_click:
# --- Single short click ---
# Online (override ON, NOT test mode): set scene
# Offline/test (override ON): toggle Relay_2
- timing:
- ON for at most 0.5s
- OFF for at least 0.5s
then:
- if:
condition:
and:
- switch.is_on: ha_loss_override
- api.connected:
- not:
switch.is_on: ha_loss_test
then:
- homeassistant.service:
service: script.lounge_set_scene
data:
scene_name: "Movie"
- logger.log:
level: INFO
format: "BTN2: Single click (online) -> Set 'Movie' Scene"
else:
- if:
condition:
and:
- switch.is_on: ha_loss_override
- or:
- not:
api.connected:
- switch.is_on: ha_loss_test
then:
- if:
condition:
lambda: |-
return id(Relay_2).state;
then:
- switch.turn_off: Relay_2
- logger.log:
level: INFO
format: "BTN2: Single click (offline/test) -> Relay_2 OFF"
else:
- switch.turn_on: Relay_2
- logger.log:
level: INFO
format: "BTN2: Single click (offline/test) -> Relay_2 ON"
else:
- logger.log:
level: INFO
format: "BTN2: Single click ignored (override OFF)"
# GPIO04 for third button (only for KS-811-3 Triple)
- platform: gpio
pin:
number: GPIO4
mode: INPUT
inverted: true
name: "Button 3: ${switch_3_name}"
on_multi_click:
# --- Single short click ---
# Online (override ON, NOT test mode): set scene
# Offline/test (override ON): toggle Relay_3
- timing:
- ON for at most 0.5s
- OFF for at least 0.5s
then:
- if:
condition:
and:
- switch.is_on: ha_loss_override
- api.connected:
- not:
switch.is_on: ha_loss_test
then:
- homeassistant.service:
service: script.lounge_set_scene
data:
scene_name: "Reading On/Off"
- logger.log:
level: INFO
format: "BTN3: Single click (online) -> Set 'Reading On/Off' Scene"
else:
- if:
condition:
and:
- switch.is_on: ha_loss_override
- or:
- not:
api.connected:
- switch.is_on: ha_loss_test
then:
- if:
condition:
lambda: |-
return id(Relay_3).state;
then:
- switch.turn_off: Relay_3
- logger.log:
level: INFO
format: "BTN3: Single click (offline/test) -> Relay_3 OFF"
else:
- switch.turn_on: Relay_3
- logger.log:
level: INFO
format: "BTN3: Single click (offline/test) -> Relay_3 ON"
else:
- logger.log:
level: INFO
format: "BTN3: Single click ignored (override OFF)"
#:########################################################################################:#
# TEXT SENSOR COMPONENT:
# https://esphome.io/components/text_sensor/
#:########################################################################################:#
text_sensor:
- platform: homeassistant
id: ha_last_scene
entity_id: input_text.lounge_last_scene
on_value:
- logger.log:
level: DEBUG
format: "HA last scene now: %s"
args: ["x.c_str()"]
#:########################################################################################:#
# SWITCH COMPONENT:
# https://esphome.io/components/switch/
#:########################################################################################:#
switch:
# GPIO13 for KS-811 first button UNLESS it is KS-811-1 then it is GPIO12
- platform: gpio
name: "Relay 1: ${switch_1_name}"
pin: GPIO13
id: Relay_1
restore_mode: RESTORE_DEFAULT_ON
# GPIO12 for second relay (only for KS-811-2 Double or -3 Triple)
- platform: gpio
name: "Relay 2: ${switch_2_name}"
pin: GPIO12
id: Relay_2
restore_mode: RESTORE_DEFAULT_ON
# GPIO14 for third relay (only for KS-811-3 Triple)
- platform: gpio
name: "Relay 3: ${switch_3_name}"
pin: GPIO14
id: Relay_3
# HA Loss manual override (default ON; persists across restarts)
- platform: template
name: "HA Loss manual override"
id: ha_loss_override
optimistic: true
restore_mode: ALWAYS_ON
# HA Loss Test (default OFF): when ON, force "offline behavior" even if HA is connected
- platform: template
name: "HA Loss Test"
id: ha_loss_test
optimistic: true
restore_mode: ALWAYS_OFF
on_turn_on:
- logger.log:
level: WARN
format: "HA Loss Test turned ON: forcing offline/test behavior for buttons"
on_turn_off:
- logger.log:
level: INFO
format: "HA Loss Test turned OFF: forcing Relay_1 and Relay_2 ON, then restoring last scene in 30s"
- switch.turn_on: Relay_1
- switch.turn_on: Relay_2
- delay: 30s
- if:
condition:
and:
- api.connected:
- lambda: |-
auto s = id(ha_last_scene).state;
return !(s.empty() || s == "unknown" || s == "unavailable");
then:
- homeassistant.service:
service: script.lounge_set_scene
data:
scene_name: !lambda |-
return id(ha_last_scene).state;
- logger.log:
level: INFO
format: "HA Loss Test OFF: restored last scene: %s"
args: ['id(ha_last_scene).state.c_str()']
else:
- logger.log:
level: WARN
format: "HA Loss Test OFF: cannot restore scene (API not connected or last scene unknown)"
esphome/esp-masterbdrmsouth.yaml
+12 -12
View File
@@ -6,6 +6,7 @@
# https://home.fox.co.nz/gitea/zorruno/zorruno-homeassistant/src/branch/master/esphome/esp-masterbdrmsouth.yaml
#:########################################################################################:#
# VERSIONS:
# v1.4 2026-07-20 Flattened retained North and South MQTT status topics to the device roots.
# v1.3 2026-06-12 Reassigned logical controls after live wiring checks.
# Relay 1 on both switches = North Lights virtual/Tasmota control.
# Relay 2 on both switches = South Lights control; WEST Relay 2 is physical load.
@@ -55,7 +56,7 @@
# NOTE: TOGGLE is intentionally not handled here to avoid double-toggle if both switches receive it.
#
# - North Lights retained status/sync topic:
# ${mqtt_local_status_topic1}/state
# ${mqtt_local_status_topic1}
# Payload "On" / "Off" mirrors the actual North Lights state.
#
# - South Lights local command topic:
@@ -65,7 +66,7 @@
# NOTE: TOGGLE is intentionally not handled here to avoid ambiguous multi-device toggles.
#
# - South Lights retained status/sync topic:
# ${mqtt_local_status_topic2}/state
# ${mqtt_local_status_topic2}
# Payload "On" / "Off" mirrors the actual South Lights state.
#:########################################################################################:#
# OFFLINE NOTES:
@@ -87,7 +88,6 @@
# - Accurate time is NOT needed (SNTP not needed).
#:########################################################################################:#
#:########################################################################################:#
# SUBSTITUTIONS: Specific device variable substitutions
# If NOT using a secrets file, just replace these with the passwords etc (in quotes)
@@ -101,7 +101,7 @@ substitutions:
# Project Naming
project_name: "Zemismart Technologies.KS-811 Triple"
project_version: "v1.3"
project_version: "v1.4"
# Passwords & Secrets
api_key: !secret esp-api_key
@@ -218,22 +218,22 @@ globals:
- id: north_update_from_sync
type: bool
restore_value: false
initial_value: 'false'
initial_value: "false"
- id: south_update_from_sync
type: bool
restore_value: false
initial_value: 'false'
initial_value: "false"
- id: north_lights_state
type: bool
restore_value: false
initial_value: 'false'
initial_value: "false"
- id: south_lights_state
type: bool
restore_value: false
initial_value: 'false'
initial_value: "false"
#:########################################################################################:#
# MQTT: Device-specific MQTT command + retained status/sync triggers
@@ -275,7 +275,7 @@ mqtt:
}
# Retained North status is a secondary mirror/sync path.
- topic: "${mqtt_local_status_topic1}/state"
- topic: "${mqtt_local_status_topic1}"
then:
- lambda: |-
if (x == "On" || x == "ON" || x == "on") {
@@ -291,7 +291,7 @@ mqtt:
# retained status after the physical Relay 2 changes, and this switch mirrors
# that status onto its local Relay 2.
# -------------------------------------------------------------------------
- topic: "${mqtt_local_status_topic2}/state"
- topic: "${mqtt_local_status_topic2}"
then:
- lambda: |-
if (x == "On" || x == "ON" || x == "on") {
@@ -410,7 +410,7 @@ script:
id(north_update_from_sync) = true;
- switch.turn_on: relay_1
- mqtt.publish:
topic: "${mqtt_local_status_topic1}/state"
topic: "${mqtt_local_status_topic1}"
payload: "On"
retain: true
- lambda: |-
@@ -424,7 +424,7 @@ script:
id(north_update_from_sync) = true;
- switch.turn_off: relay_1
- mqtt.publish:
topic: "${mqtt_local_status_topic1}/state"
topic: "${mqtt_local_status_topic1}"
payload: "Off"
retain: true
- lambda: |-
esphome/esp-masterbdrmwest.yaml
+16 -16
View File
@@ -6,6 +6,7 @@
# https://home.fox.co.nz/gitea/zorruno/zorruno-homeassistant/src/branch/master/esphome/esp-masterbdrmwest.yaml
#:########################################################################################:#
# VERSIONS:
# v1.4 2026-07-20 Flattened retained North and South MQTT status topics to the device roots.
# v1.3 2026-06-12 Reassigned logical controls after live wiring checks.
# Relay 1 on both switches = North Lights virtual/Tasmota control.
# Relay 2 on both switches = South Lights control; WEST Relay 2 is physical load.
@@ -55,7 +56,7 @@
# NOTE: TOGGLE is intentionally not handled here to avoid double-toggle if both switches receive it.
#
# - North Lights retained status/sync topic:
# ${mqtt_local_status_topic1}/state
# ${mqtt_local_status_topic1}
# Payload "On" / "Off" mirrors the actual North Lights state.
#
# - South Lights local command topic:
@@ -65,7 +66,7 @@
# NOTE: TOGGLE is intentionally not handled here to avoid ambiguous multi-device toggles.
#
# - South Lights retained status/sync topic:
# ${mqtt_local_status_topic2}/state
# ${mqtt_local_status_topic2}
# Payload "On" / "Off" published when Relay 2 changes state.
#:########################################################################################:#
# OFFLINE NOTES:
@@ -88,7 +89,6 @@
# - Accurate time is NOT needed (SNTP not needed).
#:########################################################################################:#
#:########################################################################################:#
# SUBSTITUTIONS: Specific device variable substitutions
# If NOT using a secrets file, just replace these with the passwords etc (in quotes)
@@ -102,7 +102,7 @@ substitutions:
# Project Naming
project_name: "Zemismart Technologies.KS-811 Triple"
project_version: "v1.3"
project_version: "v1.4"
# Passwords & Secrets
api_key: !secret esp-api_key
@@ -217,22 +217,22 @@ globals:
- id: north_update_from_sync
type: bool
restore_value: false
initial_value: 'false'
initial_value: "false"
- id: south_update_from_sync
type: bool
restore_value: false
initial_value: 'false'
initial_value: "false"
- id: north_lights_state
type: bool
restore_value: false
initial_value: 'false'
initial_value: "false"
- id: south_lights_state
type: bool
restore_value: false
initial_value: 'false'
initial_value: "false"
#:########################################################################################:#
# MQTT: Device-specific MQTT command + retained status/sync triggers
@@ -274,7 +274,7 @@ mqtt:
}
# Retained North status is a secondary mirror/sync path.
- topic: "${mqtt_local_status_topic1}/state"
- topic: "${mqtt_local_status_topic1}"
then:
- lambda: |-
if (x == "On" || x == "ON" || x == "on") {
@@ -296,7 +296,7 @@ mqtt:
}
# Retained South status keeps this physical relay and the SOUTH mirror in step.
- topic: "${mqtt_local_status_topic2}/state"
- topic: "${mqtt_local_status_topic2}"
then:
- lambda: |-
if (x == "On" || x == "ON" || x == "on") {
@@ -415,7 +415,7 @@ script:
id(north_update_from_sync) = true;
- switch.turn_on: relay_1
- mqtt.publish:
topic: "${mqtt_local_status_topic1}/state"
topic: "${mqtt_local_status_topic1}"
payload: "On"
retain: true
- lambda: |-
@@ -429,7 +429,7 @@ script:
id(north_update_from_sync) = true;
- switch.turn_off: relay_1
- mqtt.publish:
topic: "${mqtt_local_status_topic1}/state"
topic: "${mqtt_local_status_topic1}"
payload: "Off"
retain: true
- lambda: |-
@@ -554,10 +554,10 @@ switch:
}
- if:
condition:
lambda: 'return !id(south_update_from_sync);'
lambda: "return !id(south_update_from_sync);"
then:
- mqtt.publish:
topic: "${mqtt_local_status_topic2}/state"
topic: "${mqtt_local_status_topic2}"
payload: "On"
retain: true
on_turn_off:
@@ -568,10 +568,10 @@ switch:
}
- if:
condition:
lambda: 'return !id(south_update_from_sync);'
lambda: "return !id(south_update_from_sync);"
then:
- mqtt.publish:
topic: "${mqtt_local_status_topic2}/state"
topic: "${mqtt_local_status_topic2}"
payload: "Off"
retain: true
esphome/esp-nfcaccess1-33ad74.yaml.sample
-477
View File
@@ -1,477 +0,0 @@
#############################################
#############################################
#
# ESP Home
# NFC Tag Reader for Home Assistant
#
#############################################
#############################################
# Project Link:
# https://github.com/adonno/tagreader
#############################################
# Remember to set the switches on the PN532
# for i2C, Switch1: On (up), Switch2: Off (down)
#############################################
#############################################
# Substitution Text
#############################################
substitutions:
name: esp-nfcaccess1-33ad74
friendly_name: TagReader
#############################################
# Inport the project from Github
#############################################
#dashboard_import:
# package_import_url: github://adonno/tagreader/tagreader.yaml
#############################################
# Use Wifi
#############################################
wifi:
ssid: !secret wifi_ssid
password: !secret wifi_password
# Details for fallback hotspot (captive portal)
# in case wifi connection fails
ap:
ssid: "${name} Hotspot"
password: !secret fallback_ap_password
#############################################
# Improv
# Use the open Improv standard for configuring Wi-Fi on the
# device by using a serial connection to the device, eg. USB.
#############################################
improv_serial:
#############################################
# Fallback captive portal
# Enable the captive portal for inital WiFi setup
#############################################
captive_portal:
#############################################
# Enable Over the Air Update Capability
# Safe mode will detect boot loops
#############################################
ota:
safe_mode: true # Avoid boot loops
password: !secret esp-nfcaccess1-33ad74_ota_pass
#############################################
# ESPHome Logging Enable
#############################################
logger:
# baud_rate: 0 # Set baud rate to 0 if using the UART for soething else
# level: VERY_VERBOSE
# level: VERBOSE
#############################################
# Web Portal for display and monitoring
#############################################
#web_server:
# port: 80
# auth:
# username: !secret web_server_username
# password: !secret web_server_password
########################################
# Specific board for ESPHome device
########################################
esp8266:
board: d1_mini
#############################################
# ESPHome
#############################################
esphome:
name: ${name}
# Automatically add the mac address to the name
# so you can use a single firmware for all devices
name_add_mac_suffix: false
# This will allow for (future) project identification,
# configuration and updates.
project:
name: adonno.tag_reader
version: "1.4"
# If buzzer is enabled, notify on api connection success
on_boot:
priority: -10
then:
- wait_until:
api.connected:
- logger.log: API is connected!
- rtttl.play: "success:d=24,o=5,b=100:c,g,b"
- light.turn_on:
id: activity_led
brightness: 100%
red: 0%
green: 0%
blue: 100%
flash_length: 500ms
- switch.turn_on: buzzer_enabled
- switch.turn_on: led_enabled
#############################################
# Global variables
#############################################
globals:
- id: source
type: std::string
- id: url
type: std::string
- id: info
type: std::string
#############################################
#############################################
# MAIN SENSORS
#############################################
#############################################
#############################################
# Switches
# Define switches to control LED and buzzer from HA
#############################################
switch:
- platform: template
name: "${friendly_name} Buzzer Enabled"
id: buzzer_enabled
icon: mdi:volume-high
optimistic: true
restore_state: true
entity_category: config
- platform: template
name: "${friendly_name} LED enabled"
id: led_enabled
icon: mdi:alarm-light-outline
optimistic: true
restore_state: true
entity_category: config
#############################################
# Buttons
# Define buttons for writing tags via HA
#############################################
button:
- platform: template
name: Write Tag Random
id: write_tag_random
# Optional variables:
icon: "mdi:pencil-box"
on_press:
then:
- light.turn_on:
id: activity_led
brightness: 100%
red: 100%
green: 0%
blue: 100%
- lambda: |-
static const char alphanum[] = "0123456789abcdef";
std::string uri = "https://www.home-assistant.io/tag/";
for (int i = 0; i < 8; i++)
uri += alphanum[random_uint32() % (sizeof(alphanum) - 1)];
uri += "-";
for (int j = 0; j < 3; j++) {
for (int i = 0; i < 4; i++)
uri += alphanum[random_uint32() % (sizeof(alphanum) - 1)];
uri += "-";
}
for (int i = 0; i < 12; i++)
uri += alphanum[random_uint32() % (sizeof(alphanum) - 1)];
auto message = new nfc::NdefMessage();
message->add_uri_record(uri);
ESP_LOGD("tagreader", "Writing payload: %s", uri.c_str());
id(pn532_board).write_mode(message);
- rtttl.play: "write:d=24,o=5,b=100:b"
- wait_until:
not:
pn532.is_writing:
- light.turn_off:
id: activity_led
- rtttl.play: "write:d=24,o=5,b=100:b,b"
- platform: template
name: Clean Tag
id: clean_tag
icon: "mdi:nfc-variant-off"
on_press:
then:
- light.turn_on:
id: activity_led
brightness: 100%
red: 100%
green: 64.7%
blue: 0%
- lambda: 'id(pn532_board).clean_mode();'
- rtttl.play: "write:d=24,o=5,b=100:b"
- wait_until:
not:
pn532.is_writing:
- light.turn_off:
id: activity_led
- rtttl.play: "write:d=24,o=5,b=100:b,b"
- platform: template
name: Cancel writing
id: cancel_writing
icon: "mdi:pencil-off"
on_press:
then:
- lambda: 'id(pn532_board).read_mode();'
- light.turn_off:
id: activity_led
- rtttl.play: "write:d=24,o=5,b=100:b,b"
- platform: restart
name: "${friendly_name} Restart"
entity_category: config
#############################################
# HA API
# Enable Home Assistant API
#############################################
api:
encryption:
key: "K2H5vBNv8NLegc3RmwTQVFV7ULtba2DWDOlABmXmGBM="
services:
- service: rfidreader_tag_ok
then:
- rtttl.play: "beep:d=16,o=5,b=100:b"
- service: rfidreader_tag_ko
then:
- rtttl.play: "beep:d=8,o=5,b=100:b"
- service: play_rtttl
variables:
song_str: string
then:
- rtttl.play: !lambda 'return song_str;'
- service: write_tag_id
variables:
tag_id: string
then:
- light.turn_on:
id: activity_led
brightness: 100%
red: 100%
green: 0%
blue: 0%
- lambda: |-
auto message = new nfc::NdefMessage();
std::string uri = "https://www.home-assistant.io/tag/";
uri += tag_id;
message->add_uri_record(uri);
id(pn532_board).write_mode(message);
- rtttl.play: "write:d=24,o=5,b=100:b"
- wait_until:
not:
pn532.is_writing:
- light.turn_off:
id: activity_led
- rtttl.play: "write:d=24,o=5,b=100:b,b"
- service: write_music_tag
variables:
music_url: string
music_info: string
then:
- light.turn_on:
id: activity_led
brightness: 100%
red: 100%
green: 0%
blue: 0%
- lambda: |-
auto message = new nfc::NdefMessage();
std::string uri = "";
std::string text = "";
uri += music_url;
text += music_info;
if ( music_url != "" ) {
message->add_uri_record(uri);
}
if ( music_info != "" ) {
message->add_text_record(text);
}
id(pn532_board).write_mode(message);
- rtttl.play: "write:d=24,o=5,b=100:b"
- wait_until:
not:
pn532.is_writing:
- light.turn_off:
id: activity_led
- rtttl.play: "write:d=24,o=5,b=100:b,b"
#############################################
# i2C bus
#############################################
i2c:
scan: False
frequency: 400kHz
#############################################
# NFC Reader
#############################################
pn532_i2c:
id: pn532_board
on_tag:
then:
- if:
condition:
switch.is_on: led_enabled
then:
- light.turn_on:
id: activity_led
brightness: 100%
red: 0%
green: 100%
blue: 0%
flash_length: 500ms
- delay: 0.15s #to fix slow component
- lambda: |-
id(source)="";
id(url)="";
id(info)="";
if (tag.has_ndef_message()) {
auto message = tag.get_ndef_message();
auto records = message->get_records();
for (auto &record : records) {
std::string payload = record->get_payload();
std::string type = record->get_type();
size_t hass = payload.find("https://www.home-assistant.io/tag/");
size_t applemusic = payload.find("https://music.apple.com");
size_t spotify = payload.find("https://open.spotify.com");
size_t sonos = payload.find("sonos-2://");
if (type == "U" and hass != std::string::npos ) {
ESP_LOGD("tagreader", "Found Home Assistant tag NDEF");
id(source)="hass";
id(url)=payload;
id(info)=payload.substr(hass + 34);
}
else if (type == "U" and applemusic != std::string::npos ) {
ESP_LOGD("tagreader", "Found Apple Music tag NDEF");
id(source)="amusic";
id(url)=payload;
}
else if (type == "U" and spotify != std::string::npos ) {
ESP_LOGD("tagreader", "Found Spotify tag NDEF");
id(source)="spotify";
id(url)=payload;
}
else if (type == "U" and sonos != std::string::npos ) {
ESP_LOGD("tagreader", "Found Sonos app tag NDEF");
id(source)="sonos";
id(url)=payload;
}
else if (type == "T" ) {
ESP_LOGD("tagreader", "Found music info tag NDEF");
id(info)=payload;
}
else if ( id(source)=="" ) {
id(source)="uid";
}
}
}
else {
id(source)="uid";
}
- if:
condition:
lambda: 'return ( id(source)=="uid" );'
then:
- homeassistant.tag_scanned: !lambda |-
ESP_LOGD("tagreader", "No HA NDEF, using UID");
return x;
else:
- if:
condition:
lambda: 'return ( id(source)=="hass" );'
then:
- homeassistant.tag_scanned: !lambda 'return id(info);'
else:
- homeassistant.event:
event: esphome.music_tag
data:
reader: !lambda |-
return App.get_name().c_str();
source: !lambda |-
return id(source);
url: !lambda |-
return id(url);
info: !lambda |-
return id(info);
- if:
condition:
switch.is_on: buzzer_enabled
then:
- rtttl.play: "success:d=24,o=5,b=100:c,g,b"
on_tag_removed:
then:
- homeassistant.event:
event: esphome.tag_removed
#############################################
# OUTPUTS
#############################################
# Define the buzzer output
output:
- platform: esp8266_pwm
pin: D7
id: buzzer
#############################################
# BINARY SENSORS
#############################################
binary_sensor:
- platform: status
name: "${friendly_name} Status"
entity_category: diagnostic
#############################################
# TEXT SENSORS
#############################################
text_sensor:
- platform: version
hide_timestamp: true
name: "${friendly_name} ESPHome Version"
entity_category: diagnostic
- platform: wifi_info
ip_address:
name: "${friendly_name} IP Address"
icon: mdi:wifi
entity_category: diagnostic
ssid:
name: "${friendly_name} Connected SSID"
icon: mdi:wifi-strength-2
entity_category: diagnostic
#############################################
# Ring Tone Text Transfer Language for melody
#############################################
# Define buzzer as output for RTTTL
rtttl:
output: buzzer
#############################################
# LED
#############################################
# Configure LED
light:
- platform: neopixelbus
variant: WS2812
pin: D8
num_leds: 1
flash_transition_length: 500ms
type: GRB
id: activity_led
name: "${friendly_name} LED"
restore_mode: ALWAYS_OFF
esphome/esp-officeusbhubpower.yaml
+8 -7
View File
@@ -6,6 +6,7 @@
# https://home.fox.co.nz/gitea/zorruno/zorruno-homeassistant/src/branch/master/esphome/esp-officeusbhubpower.yaml
#:########################################################################################:#
# VERSIONS:
# V1.2 2026-07-20 Simplified local MQTT command and status topics to the device root
# V1.1 2026-02-25 Updated yaml to zorruno layout V1.1
# V1.0 2025-06-14 Initial Version
#:########################################################################################:#
@@ -22,10 +23,10 @@
#:########################################################################################:#
# MQTT COMMANDS:
# Command (set relay):
# - ${mqtt_command_topic}/relay1/set -> ON, OFF
# - ${mqtt_command_topic} -> ON, OFF
#
# Status (published from template sensor):
# - ${mqtt_status_topic}/relay1/state -> ON, OFF
# - ${mqtt_status_topic} -> ON, OFF
#:########################################################################################:#
# OFFLINE NOTES:
# a) Home Assistant OFFLINE, but Network and MQTT ONLINE
@@ -54,7 +55,7 @@ substitutions:
# Project Naming
project_name: "Sonoff Technologies.Sonoff Basic V1"
project_version: "v1.1"
project_version: "v1.2"
# Passwords & Secrets (Unfortunately, you cannot use substitutions inside secret names)
api_key: !secret esp-api_key
@@ -201,12 +202,12 @@ binary_sensor:
return id(relay1).state;
on_press:
- mqtt.publish:
topic: "${mqtt_status_topic}/relay1/state"
topic: "${mqtt_status_topic}"
payload: "ON"
retain: false
on_release:
- mqtt.publish:
topic: "${mqtt_status_topic}/relay1/state"
topic: "${mqtt_status_topic}"
payload: "OFF"
retain: false
@@ -227,12 +228,12 @@ status_led:
#:########################################################################################:#
mqtt:
on_message:
- topic: "${mqtt_command_topic}/relay1/set"
- topic: "${mqtt_command_topic}"
payload: "ON"
then:
- switch.turn_on: relay1
- topic: "${mqtt_command_topic}/relay1/set"
- topic: "${mqtt_command_topic}"
payload: "OFF"
then:
- switch.turn_off: relay1
esphome/esp-rocktumbler.yaml
+1 -1
View File
@@ -191,7 +191,7 @@ globals:
- id: restore_mode
type: int
restore_value: yes
initial_value: "2"
initial_value: "0"
#:########################################################################################:#
# SELECT COMPONENT:
esphome/esp-spare1-athomv1.yaml
+1 -7
View File
@@ -90,11 +90,6 @@ esphome:
project:
name: "${project_name}"
version: "${project_version}"
on_boot:
priority: 200
then:
- switch.turn_on: "relay"
##########################################################################################
# ESP Platform and Framework
# https://esphome.io/components/esp32.html
@@ -166,7 +161,6 @@ switch:
name: "Power Output"
pin: GPIO14
id: relay
restore_mode: RESTORE_DEFAULT_ON # Ensures the relay is restored (or off) at boot
restore_mode: RESTORE_DEFAULT_OFF # Restore previous state, default off
#internal: true # Hides the switch from Home Assistant
icon: "${relay_icon}"
esphome/m5stack-atom-echo-80be58.yaml.temp
-136
View File
@@ -1,136 +0,0 @@
substitutions:
name: m5stack-atom-echo-80be58
friendly_name: M5Stack Atom Echo 80be58
esphome:
name: "${name}"
friendly_name: "${friendly_name}"
name_add_mac_suffix: false
project:
name: m5stack.atom-echo-voice-assistant
version: "1.0"
min_version: 2023.5.0
api:
encryption:
key: XmXtlYVEuioSNapvz8G/9caKCI0T7aRW/CFy/f83D6g=
esp32:
board: m5stack-atom
framework:
type: esp-idf
logger:
ota:
wifi:
ssid: !secret wifi_ssid
password: !secret wifi_password
dashboard_import:
package_import_url: github://esphome/firmware/voice-assistant/m5stack-atom-echo.yaml@main
improv_serial:
i2s_audio:
i2s_lrclk_pin: GPIO33
i2s_bclk_pin: GPIO19
microphone:
- platform: i2s_audio
id: echo_microphone
i2s_din_pin: GPIO23
adc_type: external
pdm: true
speaker:
- platform: i2s_audio
id: echo_speaker
i2s_dout_pin: GPIO22
dac_type: external
mode: mono
voice_assistant:
microphone: echo_microphone
speaker: echo_speaker
on_start:
- light.turn_on:
id: led
blue: 100%
red: 0%
green: 0%
effect: none
on_tts_start:
- light.turn_on:
id: led
blue: 0%
red: 0%
green: 100%
effect: none
on_tts_end:
- light.turn_on:
id: led
blue: 0%
red: 0%
green: 100%
effect: pulse
on_end:
- delay: 1s
- wait_until:
not:
speaker.is_playing:
- light.turn_off: led
on_error:
- light.turn_on:
id: led
blue: 0%
red: 100%
green: 0%
effect: none
- delay: 1s
- light.turn_off: led
binary_sensor:
- platform: gpio
pin:
number: GPIO39
inverted: true
name: Button
disabled_by_default: true
entity_category: diagnostic
id: echo_button
on_multi_click:
- timing:
- ON FOR AT LEAST 350ms
then:
- voice_assistant.start:
- timing:
- ON FOR AT LEAST 350ms
- OFF FOR AT LEAST 10ms
then:
- light.turn_on:
id: led
blue: 100%
red: 0%
green: 0%
effect: pulse
- voice_assistant.stop:
light:
- platform: esp32_rmt_led_strip
id: led
name: None
disabled_by_default: true
entity_category: config
pin: GPIO27
default_transition_length: 0s
chipset: SK6812
num_leds: 1
rgb_order: grb
rmt_channel: 0
effects:
- pulse:
transition_length: 250ms
update_interval: 250ms
esphome/m5stack-atom-echo-82d244.yaml.temp
-17
View File
@@ -1,17 +0,0 @@
substitutions:
name: m5stack-atom-echo-82d244
friendly_name: M5Stack Atom Echo 82d244
packages:
m5stack.atom-echo-voice-assistant: github://esphome/firmware/voice-assistant/m5stack-atom-echo.yaml@main
esphome:
name: ${name}
name_add_mac_suffix: false
friendly_name: ${friendly_name}
api:
encryption:
key: Oh2XL+cpsK1jjTO8lW31IZ6CQiQNdqCpUgCZpoe4eYI=
wifi:
ssid: !secret wifi_ssid
password: !secret wifi_password
group/basement_lights.yaml
-8
View File
@@ -1,8 +0,0 @@
basement_lights:
name: Basement Lights
entities:
- switch.esp_officelights_relay_1_nighttime_lights
- switch.esp_officelights_relay_2_daytime_lights
- switch.esp_underhouselights_underhouse_entrance_lights
- switch.esp_underhouselights_underhouse_storage_lights
- switch.esp_laundrylights_relay_1_laundry_lights
group/family_presence.yaml
-6
View File
@@ -1,6 +0,0 @@
family_away:
name: All Family Members Away
entities:
- !secret person_1
- !secret person_2
- !secret person_3
groups.yaml
-1
View File
@@ -1 +0,0 @@
packages/16a_ev_charging_controls.yaml
+44 -1
View File
@@ -4,17 +4,60 @@
# PACKAGE: 16A EV Charger Control
###############################################################################
#
# FILE:
# packages/16a_ev_charging_controls.yaml
#
# VERSION:
# V1.2 2026-07-20
# - Added structured mode, timing, and restart behavior documentation.
#
# V1.1 2026-05-15
# - Reworked 1hr topup logic to use a hard deadline and watchdog.
# - Removed dependency on timer.finished event for relay shutoff.
# - Offpeak until charged now continues past offpeak end until charging stops.
# - 1hr topup now now rolls into Normal Offpeak if the hour ends during
# - 1hr topup now rolls into Normal Offpeak if the hour ends during
# the offpeak window, without switching the relay off and back on.
#
# V1.0 2026-05-11
# - Initial package for 16A EV charger offpeak and charge-until-full control.
#
# PURPOSE:
# Controls the Leaf 16A charger relay using scheduled offpeak operation and
# user-selectable immediate or charge-until-full modes.
#
# DEPENDENCIES:
# - switch.garage_db_control_16a_wallcharger_operation controls charger power.
# - binary_sensor.garage_db_control_16a_wallcharger_charging reports whether
# the vehicle is actively charging.
#
# CHARGE MODES:
# - Normal (Offpeak) turns the relay on and off at the configured offpeak
# start and end times. Selecting this mode takes no immediate action.
# - Offpeak until charged starts at the offpeak time, or immediately if
# selected during offpeak, and may continue beyond offpeak end until the
# vehicle stops charging.
# - 1hr topup now turns the relay on immediately and records a hard deadline
# one hour ahead.
# - Charge now until full turns the relay on immediately and keeps it on until
# the vehicle stops charging.
# - Stop charging now turns the relay off immediately and returns the selector
# to Normal (Offpeak).
#
# TIMING AND COMPLETION:
# - Charge-until-full modes allow five minutes for charging to start. This
# also handles a vehicle that is already full.
# - Charging is considered complete after the charging sensor remains off for
# five minutes.
# - The one-hour topup deadline is stored in input_datetime and checked every
# minute and when Home Assistant starts.
# - If a topup ends during offpeak, the relay remains on and the mode returns
# to Normal (Offpeak), avoiding an off/on relay cycle.
# - Equal offpeak start and end times are interpreted as an all-day window.
#
# OPERATION NOTES:
# - Normal offpeak start and end use exact-time triggers.
# - There is no startup catch-up if Home Assistant is offline at either time.
#
# PACKAGE SETTINGS:
# Car display name:
# - Leaf
packages/Job_Chore_Tracking/jobs_tracker_jobs.yaml
+49 -20
View File
@@ -9,7 +9,7 @@
# jobs_tracker_jobs.yaml
#
# VERSION:
# V2.3 2026-07-20
# V2.4 2026-07-21
#
# PURPOSE:
# Defines the job registry, MQTT Discovery entities, completion triggers and
@@ -41,6 +41,12 @@
# Complete
#
# VERSION HISTORY:
# V2.4 2026-07-21
# - Startup now waits for every retained job timestamp before refreshing.
# - Minute refreshes skip while retained MQTT state is not ready.
# - Restored stale event timestamps are no longer accepted as completions.
# - Discovery device firmware version updated to 2.4.
#
# V2.3 2026-07-20
# - All completion methods now obey the configured completion window.
# - Physical completion entities, Home Assistant discovery buttons and direct
@@ -360,7 +366,7 @@ script:
device_name: "Jobs Tracker"
device_manufacturer: "View Road Home Assistant"
device_model: "Shared household jobs tracker"
device_sw_version: "2.3"
device_sw_version: "2.4"
value_template_state: >-
{% raw %}{{ value_json.state | default('unknown') }}{% endraw %}
@@ -697,10 +703,23 @@ automation:
actions:
- action: script.jobs_tracker_publish_discovery
# Give Home Assistant a moment to process MQTT Discovery.
- delay: "00:00:10"
- variables:
jobs_tracker_jobs: *jobs_tracker_jobs
# Force retained state payloads onto each job topic.
# Do not refresh until every retained timestamp has returned from MQTT.
# Aborting on timeout protects valid retained data from being replaced by 0.
- wait_template: >-
{% set ns = namespace(ready=true) %}
{% for job in jobs_tracker_jobs %}
{% if not is_number(state_attr(job.state_entity, 'last_completed_ts')) %}
{% set ns.ready = false %}
{% endif %}
{% endfor %}
{{ ns.ready }}
timeout: "00:01:30"
continue_on_timeout: false
# Recalculate each job only after retained state is confirmed ready.
- action: script.jobs_tracker_dispatch
data:
update_all: true
@@ -711,25 +730,26 @@ automation:
mode: single
triggers:
- trigger: homeassistant
event: start
id: ha_start
- trigger: time_pattern
minutes: "/1"
id: tick
actions:
- if:
variables:
jobs_tracker_jobs: *jobs_tracker_jobs
conditions:
# Skip the minute tick until every retained timestamp is available.
- condition: template
value_template: "{{ trigger.id == 'ha_start' }}"
then:
- action: script.jobs_tracker_publish_discovery
# Let retained MQTT Discovery and job state messages restore before
# the first refresh.
- delay: "00:01:30"
value_template: >-
{% set ns = namespace(ready=true) %}
{% for job in jobs_tracker_jobs %}
{% if not is_number(state_attr(job.state_entity, 'last_completed_ts')) %}
{% set ns.ready = false %}
{% endif %}
{% endfor %}
{{ ns.ready }}
actions:
- action: script.jobs_tracker_dispatch
data:
update_all: true
@@ -747,9 +767,18 @@ automation:
conditions:
- condition: template
value_template: >-
{% set valid_state = trigger.to_state is not none
and trigger.to_state.state not in ['unknown', 'unavailable'] %}
{% set event_entity = trigger.entity_id.startswith('event.') %}
{% set event_ts = as_timestamp(trigger.to_state.state, 0)
if valid_state and event_entity else 0 %}
{% set event_age = as_timestamp(now()) - event_ts %}
{{
trigger.to_state is not none
and trigger.to_state.state not in ['unknown', 'unavailable']
valid_state
and (
not event_entity
or (event_ts > 0 and event_age >= 0 and event_age <= 30)
)
}}
actions:
packages/Lighting_2Way_Sync/central_stairway_2way_sync.yaml
+24 -1
View File
@@ -1,3 +1,27 @@
#:########################################################################################:#
# Package: Central Stairway Two-Way Synchronization
# File: Lighting_2Way_Sync/central_stairway_2way_sync.yaml
# Version: v1.1.0
# Date: 2026-07-22
#
# Purpose:
# Keeps the upper and lower controls for the main stair lights and stair footer
# lights synchronized through Home Assistant.
#
# Behaviour:
# - Synchronizes each two-member relay pair in both directions.
# - Synchronizes state after Home Assistant starts, following a five-second delay.
# - Leaves direct device-level MQTT synchronization to the ESPHome devices.
#
# Dependency:
# - Blueprint: zorruno/two_three_way_sync.yaml
#
# Version History:
# - v1.1.0 (2026-07-22): Removed the superseded lounge-middle relay and retained
# two active relays in each synchronization pair.
# - v1.0.0 (2026-06-22): Initial central stairway synchronization package.
#:########################################################################################:#
automation:
# Stair Lights Top
- id: stair_lights_top_2way_sync
@@ -9,7 +33,6 @@ automation:
members:
- switch.esp_centralstairs_top_relay_1_main_stair_lights
- switch.esp_centralstairs_bottom_relay_1_main_stair_lights_lower
- switch.esp_loungemiddleswitch_relay_3_downlights_north
sync_on_start: true
startup_delay: 5
packages/Lighting_2Way_Sync/garage_lights_2way_sync.yaml
+21
View File
@@ -1,3 +1,24 @@
#:########################################################################################:#
# Package: Garage Lighting Two-Way Synchronization
# File: Lighting_2Way_Sync/garage_lights_2way_sync.yaml
# Version: v1.0.0
# Date: 2026-06-22
#
# Purpose:
# Keeps the paired controls for the garage-entry corridor/outside lighting and
# the internal garage lighting synchronized through Home Assistant.
#
# Behaviour:
# - Synchronizes each two-member relay pair in both directions.
# - Synchronizes state after Home Assistant starts, following a five-second delay.
#
# Dependency:
# - Blueprint: zorruno/two_three_way_sync.yaml
#
# Version History:
# - v1.0.0 (2026-06-22): Initial garage lighting synchronization package.
#:########################################################################################:#
automation:
# Two lights and two switches for these corridor lights
- id: garage_entry_outside_2way_sync
packages/Pool_Controls/pool_light_operation.yaml
+13 -6
View File
@@ -6,12 +6,16 @@
# Pool Light Operation
#
# FILE:
# packages/pool_light_boost_switch.yaml
# packages/Pool_Controls/pool_light_operation.yaml
#
# VERSION:
# V1.1 2026-06-29
# V1.2 2026-07-20
#
# VERSION HISTORY:
# V1.2 2026-07-20
# - Corrected the documented package filename.
# - Documented the relationship with the native ESPHome controls.
#
# V1.1 2026-06-29
# - Tidied layout, comments, naming and automation IDs.
# - Added structured package header and section comments.
@@ -38,8 +42,15 @@
# Operation topic:
# viewroad-commands/poollight-timer/operation
#
# DEPENDENCIES:
# - switch.esp_poollightpower2_switch provides the real output state.
# - The ESPHome pool light device subscribes to the MQTT operation topic.
# - Native ESPHome mode, boost, and pool-light-mode entities coexist with
# this one-tap control.
#
# NOTES:
# The input_boolean.timer_light_midnight_pending helper is internal to this package.
# Dashboard cards currently use input_boolean.poollights_mode_switch.
#
#:########################################################################################:#
@@ -172,7 +183,3 @@ automation:
- service: input_boolean.turn_off
target:
entity_id: input_boolean.poollights_mode_switch
- service: input_boolean.turn_on
target:
entity_id: input_boolean.timer_light_midnight_pending
packages/Pool_Controls/pool_pump_operation.yaml
+63 -4
View File
@@ -1,10 +1,68 @@
# packages/poolpump_operation.yaml
#:########################################################################################:#
# Pool Pump Operation Package #
#:########################################################################################:#
#
# TITLE:
# Pool Pump Operation
#
# FILE:
# packages/Pool_Controls/pool_pump_operation.yaml
#
# VERSION:
# V1.1 2026-07-20
#
# VERSION HISTORY:
# V1.1 2026-07-20
# - Added structured package documentation and section comments.
# - Documented the relationship with the native ESPHome controls.
#
# V1.0
# - Initial package.
# - Provides a Home Assistant UI switch for pool pump BOOST / OFF behaviour.
# - Sends TIMER mode again at midnight when required.
#
# PURPOSE:
# Provides a one-tap Home Assistant UI switch for controlling the pool pump.
#
# Behaviour:
# - Turning the UI switch ON sends BOOST if the real pump output is OFF.
# - Turning the UI switch OFF sends OFF if the real pump output is ON.
# - After OFF is requested, TIMER mode is restored at midnight.
# - The UI switch follows the real ESPHome output without publishing MQTT.
#
# MQTT:
# Operation topic:
# viewroad-commands/poolpump-timer/operation
#
# Payloads used by this package:
# BOOST
# OFF
# TIMER
#
# DEPENDENCIES:
# - switch.esp_poolpumppower_power_output provides the real output state.
# - The ESPHome pool pump device subscribes to the MQTT operation topic.
# - Native ESPHome mode and boost entities coexist with this one-tap control.
#
# NOTES:
# - input_boolean.timer_midnight_pending is internal to this package.
# - Dashboard cards currently use input_boolean.poolpump_mode_switch.
#
#:########################################################################################:#
#:########################################################################################:#
# Home Assistant Customisation #
#:########################################################################################:#
homeassistant:
customize:
input_boolean.poolpump_mode_switch:
icon: mdi:pump
#:########################################################################################:#
# Input Booleans #
#:########################################################################################:#
input_boolean:
poolpump_mode_switch:
name: "Pool Pump Operation"
@@ -14,6 +72,10 @@ input_boolean:
name: "Send TIMER at Midnight"
initial: false
#:########################################################################################:#
# Automations #
#:########################################################################################:#
automation:
- alias: "Pool Pump → send BOOST when user turns UI switch ON"
trigger:
@@ -90,6 +152,3 @@ automation:
- service: input_boolean.turn_off
data:
entity_id: input_boolean.poolpump_mode_switch
- service: input_boolean.turn_on
data:
entity_id: input_boolean.timer_midnight_pending
packages/Pool_Controls/pool_timers_selections.yaml
+16 -2
View File
@@ -6,12 +6,16 @@
# Pool Timer Selection
#
# FILE:
# pool_timer_selection.yaml
# packages/Pool_Controls/pool_timers_selections.yaml
#
# VERSION:
# V1.0 2026-06-29
# V1.1 2026-07-20
#
# VERSION HISTORY:
# V1.1 2026-07-20
# - Corrected the documented package filename.
# - Documented command selectors versus ESPHome timer feedback.
#
# V1.0 2026-06-29
# - Initial package.
# - Adds Home Assistant input_select helpers for Pool Pump and Pool Light timer times.
@@ -36,6 +40,16 @@
#
# Payload format is HH:MM.
#
# STATUS AND FEEDBACK:
# - These input_select helpers send retained MQTT commands to ESPHome.
# - They do not synchronize their displayed options from the ESPHome devices.
# - The ESPHome Timeclock sensors are authoritative for the currently applied
# timer values.
# - A selector displaying "Default" does not prove that the device currently
# uses its default time.
# - Native ESPHome mode controls coexist with this package, while timer
# schedule changes continue to use the MQTT topics above.
#
# IMPORTANT:
# The current ESPHome timer logic only handles same-day timer windows:
# current_mins >= on_time AND current_mins < off_time
packages/alexa_tplink_actions.yaml
+49
View File
@@ -1,5 +1,52 @@
#:########################################################################################:#
# Alexa TP-Link Guest Wi-Fi Package #
#:########################################################################################:#
#
# TITLE:
# Alexa TP-Link Guest Wi-Fi
#
# FILE:
# packages/alexa_tplink_actions.yaml
#
# VERSION:
# V1.1 2026-07-20
#
# VERSION HISTORY:
# V1.1 2026-07-20
# - Added structured documentation and automation descriptions.
#
# V1.0
# - Initial Alexa-mediated TP-Link guest-network controls.
#
# PURPOSE:
# Enables or disables the TP-Link guest Wi-Fi network by sending custom Alexa
# requests through the kitchen Echo Show.
#
# DEPENDENCIES:
# - input_boolean.wifi_guest_network is a UI-managed helper that represents
# the requested guest-network state.
# - media_player.view_rd_kitchen_echo_show must be available through the Alexa
# Media Player integration.
# - The Alexa account must have a working, linked TP-Link skill.
#
# ALEXA REQUESTS:
# - On: ask t.p.link to enable guest network
# - Off: ask t.p.link to disable guest network
#
# OPERATION NOTES:
# - The helper records requested state; it does not confirm router state.
# - If Alexa or the TP-Link skill fails, the helper can disagree with the
# actual guest-network state.
# - After the helper remains on for two hours, it is turned off. That state
# change then sends the Alexa disable request.
# - The two-hour state-trigger period does not persist through a Home Assistant
# restart or automation reload.
#
#:########################################################################################:#
automation:
- alias: "Turn on the Wifi Guest Network"
description: "Asks the linked TP-Link Alexa skill to enable the guest Wi-Fi network."
mode: single
triggers:
- trigger: state
@@ -14,6 +61,7 @@ automation:
media_content_id: ask t.p.link to enable guest network
- alias: "Turn off the Wifi Guest Network"
description: "Asks the linked TP-Link Alexa skill to disable the guest Wi-Fi network."
mode: single
triggers:
- trigger: state
@@ -28,6 +76,7 @@ automation:
media_content_id: ask t.p.link to disable guest network
- alias: "Switch guest network off after time"
description: "Turns off the guest-network helper after it remains on for two hours."
mode: single
triggers:
- trigger: state
packages/anniversaries.yaml
+20
View File
@@ -1,3 +1,23 @@
#:########################################################################################:#
# Package: Anniversary Events
# File: anniversaries.yaml
# Version: v1.0.0
# Date: 2024-09-04
#
# Purpose:
# Provides an anniversary sensor that reports the number of days until the
# next configured event and exposes event details as attributes.
#
# Dependency:
# - Anniversary custom integration (platform: anniversary).
#
# Output:
# - sensor.events: Days until the configured holiday event.
#
# Version History:
# - v1.0.0 (2024-09-04): Initial anniversary event sensor package.
#:########################################################################################:#
sensor:
- platform: anniversary
name: events
packages/appliance_status_mqttfeed.yaml
+26
View File
@@ -1,3 +1,29 @@
#:########################################################################################:#
# Package: Appliance Activity Feed Sensors
# File: appliance_status_mqttfeed.yaml
# Version: v1.2.0
# Date: 2026-07-20
#
# Purpose:
# Provides MQTT sensors for appliance, vehicle-charger, and tool-charger
# completion messages published to the household activity feed.
#
# Dependencies:
# - Home Assistant MQTT integration and broker connectivity.
# - External publishers or the announcement router must publish completion
# payloads to the configured activity-feed topics.
#
# Known Limitation:
# - sensor.washer_finished has device_class timestamp and therefore requires
# an ISO 8601 timestamp. P013-F018 records that the current router may publish
# a time-only payload, which is not valid for this device class.
#
# Version History:
# - v1.2.0 (2026-07-20): Added the downstairs dishwasher completion sensor.
# - v1.1.0 (2025-05-18): Set the washer completion sensor as a timestamp.
# - v1.0.0 (2023-10-20): Added the initial MQTT activity-feed sensors.
#:########################################################################################:#
mqtt:
sensor:
- unique_id: washing_machine_finished
packages/auto_lights_underhouse_entrance.yaml
+18 -17
View File
@@ -1,23 +1,24 @@
################################################################################
# PACKAGE: Underhouse Entrance Auto Lights
################################################################################
#:########################################################################################:#
# Package: Underhouse Entrance Auto Lights
# File: auto_lights_underhouse_entrance.yaml
# Version: v1.2.0
# Date: 2026-05-12
#
# Version:
# 1.2 - 2026-05-12
# - Added fast Zigbee2MQTT FP1-style event triggers:
# sensor.underhouse_mmwave_sensor_x23ms_presence_event = enter
# sensor.underhouse_mmwave_sensor_x23ms_presence_event = approach
# - Keeps binary presence as a backup trigger and as the clear/off condition.
# - This should behave closer to the previous Node-RED automation.
# Purpose:
# Replaces the Node-RED automation for the underhouse entrance lights. Uses
# Zigbee2MQTT mmWave event triggers (enter/approach/presence) to turn lights
# on instantly, then off after 400 seconds of sustained clear presence.
#
# Notes:
# - The UI may show the binary sensor as "Detected", but the YAML state is
# normally "on".
# - The presence_event sensor can react earlier than the binary presence sensor.
# - The event sensor is used to turn lights on quickly, but not to decide when
# the area is clear, because it may remain on its last event value.
# Behaviour:
# - Fast Zigbee2MQTT FP1-style event triggers (enter, approach) turn lights on.
# - Binary presence sensor serves as a backup trigger and clearance condition.
# - Lights turn off 400 seconds after presence clears.
#
################################################################################
# Version History:
# - v1.2.0 (2026-05-12): Added fast Zigbee2MQTT FP1-style event triggers and
# converted header to standard package format.
#
#:########################################################################################:#
automation:
- id: underhouse_entrance_auto_lights
packages/auto_lights_underhouse_storage.yaml
+17 -23
View File
@@ -1,28 +1,24 @@
#:########################################################################################:#
# TITLE: UNDERHOUSE STORAGE LIGHTS AUTO LIGHTS PACKAGE
#:########################################################################################:#
# DESCRIPTION:
# Package: Underhouse Storage Lights
# File: auto_lights_underhouse_storage.yaml
# Version: v1.1.0
# Date: 2026-06-14
#
# Purpose:
# Replaces the Node-RED automation for the underhouse storage lights.
# Doors, PIR sensors, a remote switch, and local relay changes can start or
# extend the storage lighting timer.
#
# VERSION:
# V1.1 2026-06-14
# - Door-open trigger now watches each real door contact individually.
# - This means any door changing from closed to open turns the lights on
# immediately, even if another door is already open.
# - All doors closed now turns the lights off immediately.
# - PIR occupancy can still start/restart the motion timer after that.
# Behaviour:
# - Individual door-open triggers turn lights on immediately.
# - All doors closed turns lights off immediately.
# - PIR occupancy can start/restart the motion timer.
# - Remote switch press starts or extends the light timer.
#
# V1.0 2026-05-12
# - Initial Home Assistant package version.
#
# EDIT NOTES:
# - Add future door contacts in all places marked FUTURE DOOR.
# - Add future PIR sensors in the PIR group marked FUTURE PIR.
# - The generated group entities used below should be:
# binary_sensor.underhouse_storage_door_contacts
# binary_sensor.underhouse_storage_pir_presence
# Version History:
# - v1.1.0 (2026-06-14): Door-open trigger now watches each real door contact
# individually; all doors closed turns lights off immediately.
# - v1.0.0 (2026-05-12): Initial Home Assistant package version.
#:########################################################################################:#
binary_sensor:
@@ -112,8 +108,7 @@ automation:
entity_id:
- binary_sensor.underhouse_stealth_door_x07rs_contact
- binary_sensor.underhouse_north_door_door
# FUTURE DOOR: replace this with the actual third underhouse storage door contact.
#- binary_sensor.underhouse_future_door_contact
- binary_sensor.under_house_underhouse_east_stealth_door_door
from: "off"
to: "on"
@@ -213,8 +208,7 @@ automation:
entity_id:
- binary_sensor.underhouse_stealth_door_x07rs_contact
- binary_sensor.underhouse_north_door_door
# FUTURE DOOR: replace this with the actual third underhouse storage door contact.
#- binary_sensor.underhouse_future_door_contact
- binary_sensor.under_house_underhouse_east_stealth_door_door
from: "on"
to: "off"
action:
packages/basement_lights.yaml
+24
View File
@@ -0,0 +1,24 @@
#:########################################################################################:#
# Package: Basement Lights
# File: basement_lights.yaml
# Version: v1.0.1
# Date: 2026-07-24
#
# Purpose:
# Consolidated basement lighting configuration for two-way switching synchronization
# between the basement hallway and front door area lights.
#
# Version History:
# - v1.0.0 (2024-12-20): Created basement lighting package with two-way sync.
# - v1.0.1 (2026-07-24): Standardized header format with additional metadata.
#:########################################################################################:#
group:
basement_lights:
name: "Basement Lights"
entities:
- switch.esp_officelights_relay_1_nighttime_lights
- switch.esp_officelights_relay_2_daytime_lights
- switch.esp_underhouselights_underhouse_entrance_lights
- switch.esp_underhouselights_underhouse_storage_lights
- switch.esp_laundrylights_relay_1_laundry_lights
packages/bedroom_1_ikea_air_filter.yaml
+11 -6
View File
@@ -1,8 +1,8 @@
###############################################################################
# Bedroom 1 Ikea Air Filter Package
# File: /config/packages/bedroom_1_ikea_air_filter.yaml
# Version: 1.1
# Date: 2026-05-08
# Version: 1.2
# Date: 2026-07-20
#
# Purpose:
# - Creates a dropdown helper called "Bedroom 1 Ikea Fan".
@@ -11,7 +11,7 @@
#
# Behaviour notes:
# - Quiet time turning on sets fan speed to 2.
# - Bedside lamp turning on sets fan speed to 2.
# - Bedside lamp or Jump Fade control turning on sets fan speed to 2.
# - Bedside lamp turning off does not change the fan speed.
# - There is no 10-minute re-check, so the fan will not ramp back up just
# because the bedside lamp was switched off.
@@ -80,12 +80,16 @@ automation:
entity_id: input_boolean.quiet_time
to: "on"
# Bedside lamp only forces low when it turns on.
# Turning the lamp off does not change the fan speed.
# The lamp state catches direct light control.
- trigger: state
entity_id: light.master_bedroom_bedside_lamp_arlec_bulb_master_bedroom_bedside_lamp_arlec_bulb
to: "on"
# The Jump Fade switch catches a bedside press while the lamp is already on.
- trigger: state
entity_id: switch.master_bedroom_bedside_lamp_arlec_bulb_master_bedroom_bedside_lamp_arlec_bulb_jump_fade_up_down
to: "on"
# Main timing boundaries.
- trigger: time
at:
@@ -104,9 +108,10 @@ automation:
- variables:
trigger_entity: "{{ trigger.entity_id | default('') }}"
bedside_lamp_entity: light.master_bedroom_bedside_lamp_arlec_bulb_master_bedroom_bedside_lamp_arlec_bulb
bedside_lamp_switch_entity: switch.master_bedroom_bedside_lamp_arlec_bulb_master_bedroom_bedside_lamp_arlec_bulb_jump_fade_up_down
bedside_lamp_on_trigger: >-
{{
trigger_entity == bedside_lamp_entity
trigger_entity in [bedside_lamp_entity, bedside_lamp_switch_entity]
and trigger.to_state is defined
and trigger.to_state.state == 'on'
}}
packages/bedroom_3_led_actions.yaml
+23
View File
@@ -1,3 +1,26 @@
#:########################################################################################:#
# Package: Bedroom 3 Window LED Actions
# File: bedroom_3_led_actions.yaml
# Version: v1.0.0
# Date: 2023-10-20
#
# Purpose:
# Provides a selectable control for publishing Bedroom 3 window LED commands
# to the household MQTT command topic.
#
# Behaviour:
# - The Off option publishes the off command.
# - The 1 Hour Fade option publishes the fade_1 command.
# - The placeholder option preserves the neutral selector state.
#
# Dependencies:
# - Home Assistant MQTT integration and broker connectivity.
# - An external MQTT consumer for the Bedroom 3 window LED action topic.
#
# Version History:
# - v1.0.0 (2023-10-20): Initial Bedroom 3 window LED action package.
#:########################################################################################:#
input_select:
bedroom_3_led_actions:
icon: mdi:led-strip
packages/byd_charging_schedule_athome.yaml
+119 -30
View File
@@ -1,8 +1,8 @@
#:########################################################################################:#
# Package: BYD Charging Schedule At Home
# File: byd_charging_schedule_athome.yaml
# Version: v1.0.1
# Date: 2026-06-19
# Version: v1.1.0
# Date: 2026-07-23
#
# Purpose:
# Enables the BYD Atto 3 charging schedule when the car arrives home.
@@ -11,11 +11,12 @@
#
# Behaviour:
# - Confirmed arrival home:
# Turns ON switch.atto_3_schedule_enabled,
# but only if the car had previously been confirmed away.
# Sets the schedule to 9:00 PM through midnight with charge-to-full disabled,
# enables it, and retries cloud reconciliation once per minute.
#
# - Confirmed away:
# After away_confirm_minutes, turns OFF switch.atto_3_schedule_enabled.
# After away_confirm_minutes, disables the schedule and retries cloud
# reconciliation once per minute.
#
# - Manual control:
# If the car is already home and the user or another HA automation turns
@@ -35,24 +36,35 @@ input_boolean:
automation:
#:######################################################################################:#
# ARRIVAL - Turn schedule ON only after a confirmed away period
# ARRIVAL - Reconcile and enable schedule after a confirmed away period
#:######################################################################################:#
- id: byd_atto3_charging_schedule_arrival_enable
alias: "BYD Atto 3 Charging Schedule - Arrival Enable"
description: >
Turns the BYD charging schedule ON when the car arrives home, but only if
it was previously confirmed away. This prevents brief away/home glitches
from undoing a manual OFF while the car is actually still at home.
Reconciles the BYD charging schedule to 9:00 PM through midnight and turns
it ON when the car arrives home after a confirmed away period. Rechecks the
cloud-confirmed state once per minute and retries failed updates.
mode: single
variables: &byd_charging_schedule_vars
tracker_entity: device_tracker.byd_atto3_ibeacon_bur4c2a_bermuda_tracker
schedule_switch_entity: switch.atto_3_schedule_enabled
schedule_start_time_entity: time.atto_3_start_time
schedule_end_time_entity: time.atto_3_end_time
schedule_charge_to_full_entity: switch.atto_3_charge_to_full
# HA normally stores "At Home" as "home".
home_state: "home"
# Required charging schedule settings.
expected_start_time: "21:00:00"
expected_end_time: "00:00:00"
# Adjustable YAML-only delay before the car is treated as truly away.
away_confirm_minutes: 15
away_confirm_minutes: 10
# Verify cloud-confirmed schedule state at one-minute intervals.
schedule_verify_attempts: 6
schedule_verify_interval: "00:01:00"
# These states will not be treated as confirmed away.
ignored_tracker_states:
@@ -69,7 +81,7 @@ automation:
{{ trigger.to_state is not none
and trigger.from_state is not none
and trigger.to_state.state == home_state
and trigger.from_state.state != home_state }}
and trigger.from_state.state == 'not_home' }}
actions:
- choose:
@@ -78,23 +90,72 @@ automation:
entity_id: input_boolean.byd_atto3_charging_schedule_confirmed_away
state: "on"
sequence:
- action: switch.turn_on
target:
entity_id: "{{ schedule_switch_entity }}"
- action: input_boolean.turn_off
target:
entity_id: input_boolean.byd_atto3_charging_schedule_confirmed_away
- repeat:
count: "{{ schedule_verify_attempts | int(6) }}"
sequence:
- if:
- condition: template
value_template: "{{ is_state(tracker_entity, home_state) }}"
then:
- if:
- condition: template
value_template: >-
{{ states(schedule_start_time_entity) != expected_start_time }}
then:
- action: time.set_value
continue_on_error: true
target:
entity_id: "{{ schedule_start_time_entity }}"
data:
time: "{{ expected_start_time }}"
- if:
- condition: template
value_template: >-
{{ states(schedule_end_time_entity) != expected_end_time }}
then:
- action: time.set_value
continue_on_error: true
target:
entity_id: "{{ schedule_end_time_entity }}"
data:
time: "{{ expected_end_time }}"
- if:
- condition: template
value_template: >-
{{ not is_state(schedule_charge_to_full_entity, 'off') }}
then:
- action: switch.turn_off
continue_on_error: true
target:
entity_id: "{{ schedule_charge_to_full_entity }}"
- if:
- condition: template
value_template: >-
{{ not is_state(schedule_switch_entity, 'on') }}
then:
- action: switch.turn_on
continue_on_error: true
target:
entity_id: "{{ schedule_switch_entity }}"
- delay: "{{ schedule_verify_interval }}"
#:######################################################################################:#
# DEPARTURE - Turn schedule OFF only after confirmed away timeout
# DEPARTURE - Disable schedule after confirmed away timeout
#:######################################################################################:#
- id: byd_atto3_charging_schedule_departure_disable_after_timeout
alias: "BYD Atto 3 Charging Schedule - Departure Disable After Timeout"
description: >
When the car leaves home, waits for the configured away timeout. If the car
is still away after that delay, turns the BYD charging schedule OFF and
marks the car as confirmed away.
is still away, marks it confirmed away, turns the BYD charging schedule OFF,
and retries failed cloud updates once per minute.
mode: restart
variables: *byd_charging_schedule_vars
@@ -111,7 +172,7 @@ automation:
actions:
- delay:
minutes: "{{ away_confirm_minutes | int(15) }}"
minutes: "{{ away_confirm_minutes | int(10) }}"
- condition: template
value_template: >-
@@ -119,14 +180,28 @@ automation:
{{ current_state != home_state
and current_state not in ignored_tracker_states }}
- action: switch.turn_off
target:
entity_id: "{{ schedule_switch_entity }}"
- action: input_boolean.turn_on
target:
entity_id: input_boolean.byd_atto3_charging_schedule_confirmed_away
- repeat:
count: "{{ schedule_verify_attempts | int(6) }}"
sequence:
- if:
- condition: template
value_template: >-
{% set current_state = states(tracker_entity) %}
{{ current_state != home_state
and current_state not in ignored_tracker_states
and not is_state(schedule_switch_entity, 'off') }}
then:
- action: switch.turn_off
continue_on_error: true
target:
entity_id: "{{ schedule_switch_entity }}"
- delay: "{{ schedule_verify_interval }}"
#:######################################################################################:#
# STARTUP SAFETY - If HA restarts while the car is away, re-arm arrival logic
#:######################################################################################:#
@@ -134,8 +209,8 @@ automation:
alias: "BYD Atto 3 Charging Schedule - Startup Away Check"
description: >
On Home Assistant startup, if the car is already away and remains away
beyond the configured timeout, turn the schedule OFF and mark the car as
confirmed away so that the next confirmed arrival can enable the schedule.
beyond the configured timeout, mark it confirmed away and reconcile the
charging schedule OFF so the next confirmed arrival can enable it.
mode: single
variables: *byd_charging_schedule_vars
@@ -153,7 +228,7 @@ automation:
and current_state not in ignored_tracker_states }}
- delay:
minutes: "{{ away_confirm_minutes | int(15) }}"
minutes: "{{ away_confirm_minutes | int(10) }}"
- condition: template
value_template: >-
@@ -161,10 +236,24 @@ automation:
{{ current_state != home_state
and current_state not in ignored_tracker_states }}
- action: switch.turn_off
target:
entity_id: "{{ schedule_switch_entity }}"
- action: input_boolean.turn_on
target:
entity_id: input_boolean.byd_atto3_charging_schedule_confirmed_away
- repeat:
count: "{{ schedule_verify_attempts | int(6) }}"
sequence:
- if:
- condition: template
value_template: >-
{% set current_state = states(tracker_entity) %}
{{ current_state != home_state
and current_state not in ignored_tracker_states
and not is_state(schedule_switch_entity, 'off') }}
then:
- action: switch.turn_off
continue_on_error: true
target:
entity_id: "{{ schedule_switch_entity }}"
- delay: "{{ schedule_verify_interval }}"
packages/cctv_controls.yaml
+22
View File
@@ -1,6 +1,28 @@
#:########################################################################################:#
# Package: CCTV Motion Feed
# File: cctv_controls.yaml
# Version: v1.1.0
# Date: 2026-07-24
#
# Purpose:
# Provides a Home Assistant binary sensor for front-door motion messages
# published by the external CCTV system over MQTT.
#
# Dependencies:
# - Home Assistant MQTT integration and broker connectivity.
# - An external CCTV publisher for the configured motion topic.
#
#
# Version History:
# - v1.1.0 (2026-07-24): Added explicit numeric ON/OFF payloads (P013-F039).
# - v1.0.0 (2022-10-11): Initial CCTV front-door motion sensor package.
#:########################################################################################:#
mqtt:
binary_sensor:
- unique_id: front_door_movement_camera_corner
name: "Front Door Movement"
state_topic: "viewroad-status/cctv/front_door_motion"
payload_on: "1"
payload_off: "0"
icon: mdi:exit-run
packages/dashboard_helpers.yaml
+20
View File
@@ -1,3 +1,23 @@
#:########################################################################################:#
# Package: Dashboard Helpers
# File: dashboard_helpers.yaml
# Version: v1.0.1
# Date: 2026-07-24
#
# Purpose:
# Provides helper entities used by stored Home Assistant dashboards for
# temporary display behavior that does not belong to a device integration.
#
# Behaviour:
# - The moon-phase overlay helper controls whether the percentage is displayed.
# - The companion script enables the overlay for ten seconds and then disables it.
# - Restart mode restarts the ten-second display period when called repeatedly.
#
# Version History:
# - v1.0.0 (2026-02-16): Added the temporary moon-phase percentage overlay helper.
# - v1.0.1 (2026-07-24): Standardized header format with additional metadata.
#:########################################################################################:#
input_boolean:
moon_phase_percent_overlay:
name: Moon phase percent overlay
packages/downstairs_bulk_lights_on_from_stairs.yaml
+6 -6
View File
@@ -1,9 +1,9 @@
################################################################################
# PACKAGE: Downstairs Lights Bulk Activation
# FILE: packages/downstairs_lights_bulk_activation.yaml
# FILE: packages/downstairs_bulk_lights_on_from_stairs.yaml
#
# Version: 1.0
# Date: 2026-04-26
# Version: 1.1
# Date: 2026-07-20
#
# Notes:
# - Uses the virtual switch:
@@ -16,16 +16,16 @@
# Turns OFF the listed downstairs lights, but only if each light is currently ON.
#
# - No action is taken unless:
# input_boolean.downstairs_flat_occupied is ON.
# input_boolean.downstairs_flat_occupied is OFF.
################################################################################
automation:
- id: downstairs_lights_bulk_activation
alias: "Downstairs Lights Bulk Activation"
description: >
V1.0 - 2026-04-26: Bulk ON/OFF control for downstairs lights from the
V1.1 - 2026-07-20: Bulk ON/OFF control for downstairs lights from the
central stair lightswitch virtual switch. Only operates when the downstairs
flat occupied input_boolean is ON.
flat is not occupied.
mode: single
packages/edgerouter_snmp.yaml
+476
View File
@@ -0,0 +1,476 @@
#:########################################################################################:#
# Package: EdgeRouter SNMP Monitoring
# File: edgerouter_snmp.yaml
# Version: v1.0.1
# Date: 2026-07-21
#
# Purpose:
# Monitors the EdgeRouter X through read-only SNMPv2c after the previous EdgeOS
# integration became incompatible with EdgeOS v3.0.x. Provides traffic rates
# for the major physical interfaces and system health sensors for the router.
#
# Interfaces:
# - eth0 / ifIndex 4: WAN and Internet traffic.
# - eth1 / ifIndex 5: Home LAN traffic.
# - eth2 / ifIndex 6: Home Wireless traffic.
# - eth3 / ifIndex 7: Home Automation traffic.
# - eth4 / ifIndex 8: Secondary Home Automation traffic.
#
# Behaviour:
# - Polls 64-bit IF-MIB counters so totals remain reliable on busy interfaces.
# - Converts cumulative received/transmitted byte counters into kB/s rates.
# - Polls firmware, uptime, CPU idle, load averages, and memory counters.
# - Calculates memory usage from total, free, buffer, and cache values.
#
# Polling:
# - Traffic counters: Every 60 seconds.
# - Uptime, CPU, load, and memory: Every 60 seconds.
# - Firmware description: Every 300 seconds.
#
# Notes:
# - The SNMP community is stored in secrets.yaml and is never hardcoded here.
# - WAN traffic intentionally uses physical eth0 because hardware-offloaded
# traffic is under-reported by the logical pppoe0 and eth0.10 interfaces.
# - Received traffic on LAN interfaces is upload toward the router; transmitted
# traffic is download from the router toward clients on that interface.
# - SNMP, derivative, and template platforms create standalone entities rather
# than a combined Home Assistant device entry.
#
# Version History:
# - v1.0.1 (2026-07-21): Moved the EdgeRouter host address to secrets.yaml.
# - v1.0.0 (2026-07-21): Initial documented SNMP traffic and health package.
#:########################################################################################:#
sensor:
#:######################################################################################:#
# WAN TRAFFIC - eth0 / ifIndex 4
#:######################################################################################:#
# ifHCInOctets counts bytes received from the Internet. The physical interface
# is used so hardware-offloaded traffic is included in the total.
- platform: snmp
name: "EdgeRouter WAN Received Bytes"
unique_id: "edgerouter_wan_received_bytes"
host: !secret edgerouter_host
community: !secret edgerouter_snmp_community
version: 2c
baseoid: 1.3.6.1.2.1.31.1.1.1.6.4
accept_errors: true
device_class: data_size
state_class: total_increasing
unit_of_measurement: "B"
scan_interval: 60
# ifHCOutOctets counts bytes transmitted from the router to the Internet.
- platform: snmp
name: "EdgeRouter WAN Transmitted Bytes"
unique_id: "edgerouter_wan_transmitted_bytes"
host: !secret edgerouter_host
community: !secret edgerouter_snmp_community
version: 2c
baseoid: 1.3.6.1.2.1.31.1.1.1.10.4
accept_errors: true
device_class: data_size
state_class: total_increasing
unit_of_measurement: "B"
scan_interval: 60
# Convert the cumulative received-byte counter into the WAN download rate.
- platform: derivative
name: "EdgeRouter WAN Download Rate"
unique_id: "edgerouter_wan_download_rate"
source: sensor.edgerouter_wan_received_bytes
unit_prefix: k
unit_time: s
round: 1
time_window: "00:00:30"
# Convert the cumulative transmitted-byte counter into the WAN upload rate.
- platform: derivative
name: "EdgeRouter WAN Upload Rate"
unique_id: "edgerouter_wan_upload_rate"
source: sensor.edgerouter_wan_transmitted_bytes
unit_prefix: k
unit_time: s
round: 1
time_window: "00:00:30"
#:######################################################################################:#
# HOME LAN TRAFFIC - eth1 / ifIndex 5
#:######################################################################################:#
# Bytes received by the router from Home LAN clients become the LAN upload rate.
- platform: snmp
name: "EdgeRouter Home LAN Received Bytes"
unique_id: "edgerouter_home_lan_received_bytes"
host: !secret edgerouter_host
community: !secret edgerouter_snmp_community
version: 2c
baseoid: 1.3.6.1.2.1.31.1.1.1.6.5
accept_errors: true
device_class: data_size
state_class: total_increasing
unit_of_measurement: "B"
scan_interval: 60
# Bytes transmitted by the router to Home LAN clients become the LAN download rate.
- platform: snmp
name: "EdgeRouter Home LAN Transmitted Bytes"
unique_id: "edgerouter_home_lan_transmitted_bytes"
host: !secret edgerouter_host
community: !secret edgerouter_snmp_community
version: 2c
baseoid: 1.3.6.1.2.1.31.1.1.1.10.5
accept_errors: true
device_class: data_size
state_class: total_increasing
unit_of_measurement: "B"
scan_interval: 60
# Derive the client-to-router upload rate from the received-byte counter.
- platform: derivative
name: "EdgeRouter Home LAN Upload Rate"
unique_id: "edgerouter_home_lan_upload_rate"
source: sensor.edgerouter_home_lan_received_bytes
unit_prefix: k
unit_time: s
round: 1
time_window: "00:00:30"
# Derive the router-to-client download rate from the transmitted-byte counter.
- platform: derivative
name: "EdgeRouter Home LAN Download Rate"
unique_id: "edgerouter_home_lan_download_rate"
source: sensor.edgerouter_home_lan_transmitted_bytes
unit_prefix: k
unit_time: s
round: 1
time_window: "00:00:30"
#:######################################################################################:#
# HOME WIRELESS TRAFFIC - eth2 / ifIndex 6
#:######################################################################################:#
# Bytes received by the router from the wireless network become its upload rate.
- platform: snmp
name: "EdgeRouter Home Wireless Received Bytes"
unique_id: "edgerouter_home_wireless_received_bytes"
host: !secret edgerouter_host
community: !secret edgerouter_snmp_community
version: 2c
baseoid: 1.3.6.1.2.1.31.1.1.1.6.6
accept_errors: true
device_class: data_size
state_class: total_increasing
unit_of_measurement: "B"
scan_interval: 60
# Bytes transmitted by the router to the wireless network become its download rate.
- platform: snmp
name: "EdgeRouter Home Wireless Transmitted Bytes"
unique_id: "edgerouter_home_wireless_transmitted_bytes"
host: !secret edgerouter_host
community: !secret edgerouter_snmp_community
version: 2c
baseoid: 1.3.6.1.2.1.31.1.1.1.10.6
accept_errors: true
device_class: data_size
state_class: total_increasing
unit_of_measurement: "B"
scan_interval: 60
# Derive the wireless-to-router upload rate from the received-byte counter.
- platform: derivative
name: "EdgeRouter Home Wireless Upload Rate"
unique_id: "edgerouter_home_wireless_upload_rate"
source: sensor.edgerouter_home_wireless_received_bytes
unit_prefix: k
unit_time: s
round: 1
time_window: "00:00:30"
# Derive the router-to-wireless download rate from the transmitted-byte counter.
- platform: derivative
name: "EdgeRouter Home Wireless Download Rate"
unique_id: "edgerouter_home_wireless_download_rate"
source: sensor.edgerouter_home_wireless_transmitted_bytes
unit_prefix: k
unit_time: s
round: 1
time_window: "00:00:30"
#:######################################################################################:#
# HOME AUTOMATION TRAFFIC - eth3 / ifIndex 7
#:######################################################################################:#
# Bytes received by the router from Home Automation become its upload rate.
- platform: snmp
name: "EdgeRouter Home Automation Received Bytes"
unique_id: "edgerouter_home_automation_received_bytes"
host: !secret edgerouter_host
community: !secret edgerouter_snmp_community
version: 2c
baseoid: 1.3.6.1.2.1.31.1.1.1.6.7
accept_errors: true
device_class: data_size
state_class: total_increasing
unit_of_measurement: "B"
scan_interval: 60
# Bytes transmitted by the router to Home Automation become its download rate.
- platform: snmp
name: "EdgeRouter Home Automation Transmitted Bytes"
unique_id: "edgerouter_home_automation_transmitted_bytes"
host: !secret edgerouter_host
community: !secret edgerouter_snmp_community
version: 2c
baseoid: 1.3.6.1.2.1.31.1.1.1.10.7
accept_errors: true
device_class: data_size
state_class: total_increasing
unit_of_measurement: "B"
scan_interval: 60
# Derive the Home Automation upload rate from the received-byte counter.
- platform: derivative
name: "EdgeRouter Home Automation Upload Rate"
unique_id: "edgerouter_home_automation_upload_rate"
source: sensor.edgerouter_home_automation_received_bytes
unit_prefix: k
unit_time: s
round: 1
time_window: "00:00:30"
# Derive the Home Automation download rate from the transmitted-byte counter.
- platform: derivative
name: "EdgeRouter Home Automation Download Rate"
unique_id: "edgerouter_home_automation_download_rate"
source: sensor.edgerouter_home_automation_transmitted_bytes
unit_prefix: k
unit_time: s
round: 1
time_window: "00:00:30"
#:######################################################################################:#
# SECONDARY HOME AUTOMATION TRAFFIC - eth4 / ifIndex 8
#:######################################################################################:#
# Bytes received by the router from this network become its upload rate.
- platform: snmp
name: "EdgeRouter Home Automation 2 Received Bytes"
unique_id: "edgerouter_home_automation_2_received_bytes"
host: !secret edgerouter_host
community: !secret edgerouter_snmp_community
version: 2c
baseoid: 1.3.6.1.2.1.31.1.1.1.6.8
accept_errors: true
device_class: data_size
state_class: total_increasing
unit_of_measurement: "B"
scan_interval: 60
# Bytes transmitted by the router to this network become its download rate.
- platform: snmp
name: "EdgeRouter Home Automation 2 Transmitted Bytes"
unique_id: "edgerouter_home_automation_2_transmitted_bytes"
host: !secret edgerouter_host
community: !secret edgerouter_snmp_community
version: 2c
baseoid: 1.3.6.1.2.1.31.1.1.1.10.8
accept_errors: true
device_class: data_size
state_class: total_increasing
unit_of_measurement: "B"
scan_interval: 60
# Derive the secondary Home Automation upload rate from received bytes.
- platform: derivative
name: "EdgeRouter Home Automation 2 Upload Rate"
unique_id: "edgerouter_home_automation_2_upload_rate"
source: sensor.edgerouter_home_automation_2_received_bytes
unit_prefix: k
unit_time: s
round: 1
time_window: "00:00:30"
# Derive the secondary Home Automation download rate from transmitted bytes.
- platform: derivative
name: "EdgeRouter Home Automation 2 Download Rate"
unique_id: "edgerouter_home_automation_2_download_rate"
source: sensor.edgerouter_home_automation_2_transmitted_bytes
unit_prefix: k
unit_time: s
round: 1
time_window: "00:00:30"
#:######################################################################################:#
# ROUTER IDENTITY AND UPTIME
#:######################################################################################:#
# sysDescr reports the installed EdgeOS firmware and build information.
- platform: snmp
name: "EdgeRouter Firmware"
unique_id: "edgerouter_firmware"
host: !secret edgerouter_host
community: !secret edgerouter_snmp_community
version: 2c
baseoid: 1.3.6.1.2.1.1.1.0
accept_errors: true
scan_interval: 300
# hrSystemUptime is reported in hundredths of a second and converted to seconds.
- platform: snmp
name: "EdgeRouter Uptime"
unique_id: "edgerouter_uptime"
host: !secret edgerouter_host
community: !secret edgerouter_snmp_community
version: 2c
baseoid: 1.3.6.1.2.1.25.1.1.0
accept_errors: true
device_class: duration
state_class: measurement
unit_of_measurement: "s"
value_template: "{{ ((value | default(0) | float(0)) / 100) | round(0) }}"
scan_interval: 60
#:######################################################################################:#
# CPU USAGE AND LOAD AVERAGES
#:######################################################################################:#
# UCD-SNMP reports CPU idle percentage, so usage is calculated as 100 - idle.
- platform: snmp
name: "EdgeRouter CPU Usage"
unique_id: "edgerouter_cpu_usage"
host: !secret edgerouter_host
community: !secret edgerouter_snmp_community
version: 2c
baseoid: 1.3.6.1.4.1.2021.11.11.0
accept_errors: true
state_class: measurement
unit_of_measurement: "%"
value_template: "{{ 100 - (value | default(100) | int(100)) }}"
scan_interval: 60
# One-minute load average from the UCD-SNMP load table.
- platform: snmp
name: "EdgeRouter Load 1 Minute"
unique_id: "edgerouter_load_1_minute"
host: !secret edgerouter_host
community: !secret edgerouter_snmp_community
version: 2c
baseoid: 1.3.6.1.4.1.2021.10.1.3.1
accept_errors: true
state_class: measurement
value_template: "{{ value | default(0) | float(0) }}"
scan_interval: 60
# Five-minute load average from the UCD-SNMP load table.
- platform: snmp
name: "EdgeRouter Load 5 Minutes"
unique_id: "edgerouter_load_5_minutes"
host: !secret edgerouter_host
community: !secret edgerouter_snmp_community
version: 2c
baseoid: 1.3.6.1.4.1.2021.10.1.3.2
accept_errors: true
state_class: measurement
value_template: "{{ value | default(0) | float(0) }}"
scan_interval: 60
# Fifteen-minute load average from the UCD-SNMP load table.
- platform: snmp
name: "EdgeRouter Load 15 Minutes"
unique_id: "edgerouter_load_15_minutes"
host: !secret edgerouter_host
community: !secret edgerouter_snmp_community
version: 2c
baseoid: 1.3.6.1.4.1.2021.10.1.3.3
accept_errors: true
state_class: measurement
value_template: "{{ value | default(0) | float(0) }}"
scan_interval: 60
#:######################################################################################:#
# MEMORY COUNTERS
#:######################################################################################:#
# Total physical memory reported by UCD-SNMP in KiB.
- platform: snmp
name: "EdgeRouter Memory Total"
unique_id: "edgerouter_memory_total"
host: !secret edgerouter_host
community: !secret edgerouter_snmp_community
version: 2c
baseoid: 1.3.6.1.4.1.2021.4.5.0
accept_errors: true
device_class: data_size
state_class: measurement
unit_of_measurement: "KiB"
scan_interval: 60
# Currently free memory reported by UCD-SNMP in KiB.
- platform: snmp
name: "EdgeRouter Memory Free"
unique_id: "edgerouter_memory_free"
host: !secret edgerouter_host
community: !secret edgerouter_snmp_community
version: 2c
baseoid: 1.3.6.1.4.1.2021.4.6.0
accept_errors: true
device_class: data_size
state_class: measurement
unit_of_measurement: "KiB"
scan_interval: 60
# Memory allocated to buffers, excluded from calculated active usage.
- platform: snmp
name: "EdgeRouter Memory Buffers"
unique_id: "edgerouter_memory_buffers"
host: !secret edgerouter_host
community: !secret edgerouter_snmp_community
version: 2c
baseoid: 1.3.6.1.4.1.2021.4.14.0
accept_errors: true
device_class: data_size
state_class: measurement
unit_of_measurement: "KiB"
scan_interval: 60
# Memory allocated to cache, excluded from calculated active usage.
- platform: snmp
name: "EdgeRouter Memory Cached"
unique_id: "edgerouter_memory_cached"
host: !secret edgerouter_host
community: !secret edgerouter_snmp_community
version: 2c
baseoid: 1.3.6.1.4.1.2021.4.15.0
accept_errors: true
device_class: data_size
state_class: measurement
unit_of_measurement: "KiB"
scan_interval: 60
#:######################################################################################:#
# DERIVED MEMORY USAGE
#:######################################################################################:#
# Calculate active memory as total minus free, buffers, and cache. The template
# remains unavailable until every source counter has a valid state.
template:
- sensor:
- name: "EdgeRouter Memory Usage"
unique_id: "edgerouter_memory_usage"
unit_of_measurement: "%"
state_class: measurement
availability: >-
{{
has_value('sensor.edgerouter_memory_total')
and has_value('sensor.edgerouter_memory_free')
and has_value('sensor.edgerouter_memory_buffers')
and has_value('sensor.edgerouter_memory_cached')
}}
state: >-
{{
(
(
(states('sensor.edgerouter_memory_total') | float(0))
- (states('sensor.edgerouter_memory_free') | float(0))
- (states('sensor.edgerouter_memory_buffers') | float(0))
- (states('sensor.edgerouter_memory_cached') | float(0))
)
/ (states('sensor.edgerouter_memory_total') | float(1))
* 100
)
| round(1)
}}
packages/firewall_control.yaml
+47
View File
@@ -1,3 +1,50 @@
#:########################################################################################:#
# Firewall Internet Control Package #
#:########################################################################################:#
#
# TITLE:
# Firewall Internet Control
#
# FILE:
# packages/firewall_control.yaml
#
# VERSION:
# V1.1 2026-07-20
#
# VERSION HISTORY:
# V1.1 2026-07-20
# - Added structured MQTT and external-firewall documentation.
#
# V1.0
# - Initial persistent and temporary internet-blocking controls.
#
# PURPOSE:
# Provides Home Assistant controls for persistent and temporary internet
# blocking of Mollie's devices through an external MQTT firewall service.
#
# PERSISTENT CONTROL:
# - Blocked enables persistent internet blocking.
# - Unblocked disables persistent internet blocking.
# - The switch state is reported by the external firewall service.
#
# TEMPORARY CONTROLS:
# - One-hour block publishes Blocked to the temporary-block topic.
# - 15-minute unblock publishes Unblocked to the temporary-unblock topic.
# - One-hour unblock publishes Unblocked to its one-hour topic.
#
# EXTERNAL DEPENDENCY:
# - Home Assistant only publishes command requests.
# - The external firewall service implements temporary durations, restores the
# appropriate state afterward, and publishes persistent switch feedback.
#
# MQTT NOTES:
# - All commands are non-retained.
# - No availability topic is configured for these entities.
# - The persistent status topic retains the legacy device label
# block-unblock-mollie-iphone8.
#
#:########################################################################################:#
mqtt:
switch:
- unique_id: mollies.internet
packages/fridge_temperatures.yaml
+23
View File
@@ -1,3 +1,26 @@
#:########################################################################################:#
# Package: Refrigerator Temperature MQTT Publishing
# File: fridge_temperatures.yaml
# Version: v1.0.0
# Date: 2024-09-04
#
# Purpose:
# Publishes refrigerator and freezer temperature changes to household MQTT
# status topics for use by external displays and consumers.
#
# Behaviour:
# - Publishes the source sensor state whenever a valid temperature changes.
# - Suppresses unknown and unavailable source states.
# - Covers the drinks fridge, drinks freezer, and main kitchen fridge.
#
# Dependencies:
# - The three configured Home Assistant temperature sensors.
# - Home Assistant MQTT integration and broker connectivity.
#
# Version History:
# - v1.0.0 (2024-09-04): Initial refrigerator temperature publishing package.
#:########################################################################################:#
automation:
- id: publish_fridge_temps_drinks_fridge
alias: publish_fridge_temps_drinks_fridge
packages/grocy_api.yaml
-42
View File
@@ -1,42 +0,0 @@
rest_command:
chores1_request:
url: !secret grocy_api_uri_chore6
method: PUT
headers:
accept: "*/*"
GROCY-API-KEY: !secret grocy_api_key
content_type: "application/json"
payload: '{
"name" : "{{ name }}" ,
"next_execution_assigned_to_user_id" : "{{ assigned_to }}"
}'
# payload: '{"name" : "{{ name }}" , "next_estimated_execution_time" : "{{ next_time }}", "next_execution_assigned_to_user_id" : "{{ assigned_to }}" }'
verify_ssl: false
sensor:
- platform: rest
name: Dog Motel Cleaning
resource: !secret grocy_api_uri_chore3
method: GET
value_template: "{{ (((as_timestamp(value_json.next_estimated_execution_time))-as_timestamp(now())) | int /60/1440) | round(0) }}"
json_attributes:
- last_tracked
- estimated_execution_time
headers:
Accept: application/json
Content-Type: application/json
GROCY-API-KEY: !secret grocy_api_key
unit_of_measurement: "Days"
- platform: rest
name: Red Bin Out
resource: !secret grocy_api_uri_chore2
method: GET
value_template: "{{ (((as_timestamp(value_json.next_estimated_execution_time))-as_timestamp(now())) | int /60/1440) | round(0) }}"
json_attributes:
- last_tracked
- estimated_execution_time
headers:
Accept: application/json
Content-Type: application/json
GROCY-API-KEY: !secret grocy_api_key
unit_of_measurement: "Days"
packages/ha_summary.yaml
+44 -1
View File
@@ -2,11 +2,54 @@
# Home Assistant Summary Package - V2 #
#:########################################################################################:#
#
# Uses V2 entity IDs to avoid stale/ghost entities from earlier versions.
# TITLE:
# Home Assistant Summary V2
#
# FILE:
# packages/ha_summary.yaml
#
# VERSION:
# V2.1 2026-07-20
#
# VERSION HISTORY:
# V2.1 2026-07-20
# - Added structured documentation for refresh behavior and counting rules.
# - Documented heuristic classifications and their limitations.
#
# V2.0
# - Introduced V2 entity IDs to avoid stale entities from earlier versions.
#
# PURPOSE:
# Provides dashboard summary sensors for Home Assistant entities, devices,
# areas, cameras, scenes, scripts, automations, add-ons, and updates.
#
# It also provides device and entity counts for ESPHome, Tasmota, ZHA,
# Zigbee2MQTT, Matter, and selected cloud integrations.
#
# OUTPUTS:
# Dashboard entity prefix:
# sensor.ha_summary_v2_...
#
# REFRESH:
# Sensors refresh when Home Assistant starts, when the entity, device, or area
# registries change, when core configuration changes, and every five minutes.
#
# COUNTING NOTES:
# - Total devices counts distinct device IDs associated with current entities.
# Devices without entities are not included.
# - Broken entities are entities whose state is unknown or unavailable.
# - Add-ons are inferred from Supervisor update entities, excluding the Core,
# Supervisor, and Operating System update entities.
# - Zigbee2MQTT devices and entities are identified by searching MQTT device
# metadata for "zigbee2mqtt".
# - Matter Wi-Fi and Thread classifications search device metadata for known
# transport terms. These are heuristics rather than authoritative transport
# data, and a device can match both categories.
# - Matter unclassified counts subtract Wi-Fi and Thread counts from totals, so
# overlapping classifications can affect the result.
# - Cloud counts use the explicit integration list in the final two sensors.
# Add or remove integration domains there when maintaining cloud coverage.
#
template:
- trigger:
packages/health_checks.yaml
+27
View File
@@ -1,3 +1,30 @@
#:########################################################################################:#
# Package: Node-RED Health Checks
# File: health_checks.yaml
# Version: v1.2.0
# Date: 2025-08-25
#
# Purpose:
# Monitors the Node-RED Panda instance through independent HTTP and MQTT health
# signals and combines them into one connectivity status.
#
# Behaviour:
# - Polls the HTTP health endpoint every 30 seconds with a three-second timeout.
# - Tracks the MQTT birth/will topic with QoS 1 and a 180-second expiry.
# - Reports the combined check as available when either source is available.
# - Reports the combined check as connected when either source is connected.
#
# Dependencies:
# - Reachability of the configured Node-RED HTTP health endpoint.
# - Home Assistant MQTT integration and the Node-RED birth/will publisher.
#
# Version History:
# - v1.2.0 (2025-08-25): Reduced MQTT expiry to 180 seconds and clarified the
# combined HTTP/MQTT sensor name.
# - v1.1.0 (2025-08-22): Split HTTP and MQTT probes and added a combined sensor.
# - v1.0.0 (2025-08-21): Initial Node-RED health-check package.
#:########################################################################################:#
# ---- HTTP health probe ----
binary_sensor:
- platform: rest
packages/heat_pump_master_bedroom_schedules.yaml
+53 -1
View File
@@ -1,5 +1,57 @@
##########################################################################################
# heat_pump_master_bedroom_schedules.yaml
# Master Bedroom Heat Pump Schedules
##########################################################################################
#
# TITLE:
# Master Bedroom Heat Pump Schedules
#
# FILE:
# packages/heat_pump_master_bedroom_schedules.yaml
#
# VERSION:
# V1.1 2026-07-20
#
# VERSION HISTORY:
# V1.1 2026-07-20
# - Added structured documentation for schedules, boost, and helper behavior.
#
# V1.0
# - Initial master bedroom heat pump schedules and boost controls.
#
# PURPOSE:
# Provides optional 21:00 start and midnight stop schedules, a combined Night
# Power mode, and a manual one-hour boost for the master bedroom heat pump.
#
# DEPENDENCIES:
# - climate.master_bedroom provides the Panasonic Comfort Cloud heat pump.
# - The climate entity must support the "boost" and "none" preset modes.
# - packages/heat_pump_master_bedroom_helpers.yaml provides companion
# dashboard, setpoint, HVAC mode, profile, and sleep-timer controls.
#
# SCHEDULE MODES:
# - Night Power Mode turns the heat pump on at 21:00, applies boost for 30
# minutes, returns it to the normal preset, and turns it off at midnight.
# - 9pm On turns the heat pump on at 21:00 without changing its preset.
# - Midnight Off turns the heat pump off at midnight.
# - Enabling Night Power disables the separate 9pm On and Midnight Off modes.
# - Enabling either separate mode disables Night Power. The separate 9pm On
# and Midnight Off modes may be enabled together.
#
# MANUAL BOOST:
# - script.master_bedroom_boost_1hr applies boost for one hour.
# - If the heat pump was off when boost started, it is turned off afterward.
# - If it was already running, boost ends by restoring the normal preset and
# leaving the heat pump running.
#
# INTERNAL STATE:
# - input_boolean.master_bedroom_boost_restore_off records whether manual
# boost should restore the heat pump to off.
# - timer.master_bedroom_boost_timer controls manual and scheduled boost time.
#
# OPERATION NOTES:
# - The 21:00 and midnight schedules use exact-time triggers.
# - There is no startup catch-up if Home Assistant is offline at either time.
#
##########################################################################################
##########################################################################################
packages/internet_traffic.yaml
+37 -7
View File
@@ -1,25 +1,55 @@
#:########################################################################################:#
# Package: Internet Traffic Summary
# File: internet_traffic.yaml
# Version: v1.2.0
# Date: 2026-07-22
#
# Purpose:
# Preserves the household Internet download, upload, and total traffic sensors
# while sourcing current WAN rates from the EdgeRouter SNMP package.
#
# Behaviour:
# - Mirrors the EdgeRouter WAN download and upload rates in kB/s.
# - Calculates total traffic as the sum of download and upload rates.
# - Marks each sensor unavailable when its required source is unavailable.
#
# Dependency:
# - packages/edgerouter_snmp.yaml
#
# Version History:
# - v1.2.0 (2026-07-22): Migrated source data from EdgeOS attributes to the
# EdgeRouter SNMP WAN rate sensors and added availability handling.
# - v1.1.0 (2025-12-21): Migrated the three sensors to modern template syntax.
# - v1.0.0 (2022-10-12): Added the initial EdgeOS-based traffic sensors.
#:########################################################################################:#
template:
- sensor:
- name: "Internet Download Traffic"
unique_id: internet_downtraffic
unit_of_measurement: "kB/s"
state_class: measurement
state: >
{{ state_attr('binary_sensor.edgeos_interface_pppoe0', 'KBytes/ps (Received)') | float(0) }}
availability: "{{ has_value('sensor.edgerouter_wan_download_rate') }}"
state: "{{ states('sensor.edgerouter_wan_download_rate') | float(0) }}"
- name: "Internet Upload Traffic"
unique_id: internet_uptraffic
unit_of_measurement: "kB/s"
state_class: measurement
state: >
{{ state_attr('binary_sensor.edgeos_interface_pppoe0', 'KBytes/ps (Sent)') | float(0) }}
availability: "{{ has_value('sensor.edgerouter_wan_upload_rate') }}"
state: "{{ states('sensor.edgerouter_wan_upload_rate') | float(0) }}"
- name: "Internet Total Traffic"
unique_id: internet_totaltraffic
unit_of_measurement: "kB/s"
state_class: measurement
state: >
availability: >-
{{
(state_attr('binary_sensor.edgeos_interface_pppoe0', 'KBytes/ps (Received)') | float(0))
+ (state_attr('binary_sensor.edgeos_interface_pppoe0', 'KBytes/ps (Sent)') | float(0))
has_value('sensor.edgerouter_wan_download_rate')
and has_value('sensor.edgerouter_wan_upload_rate')
}}
state: >-
{{
(states('sensor.edgerouter_wan_download_rate') | float(0))
+ (states('sensor.edgerouter_wan_upload_rate') | float(0))
}}
packages/kogan_kettle.yaml
+27
View File
@@ -1,3 +1,30 @@
#:########################################################################################:#
# Package: Kogan Kettle MQTT Control
# File: kogan_kettle.yaml
# Version: v1.0.0
# Date: 2022-10-11
#
# Purpose:
# Provides kettle temperature monitoring, power control, and selectable
# keep-warm temperatures through a Tasmota/TuyaMCU MQTT interface.
#
# Behaviour:
# - Reads temperature data from the kettle's TuyaReceived MQTT payload.
# - Controls kettle power through its MQTT power command topic.
# - Maps the keep-warm selector to the kettle's TuyaSend4 commands.
#
# Dependencies:
# - Home Assistant MQTT integration and broker connectivity.
# - The configured Tasmota/TuyaMCU kettle MQTT topics and payload structure.
#
# Known Limitation:
# - P013-F026 records that temperature parsing assumes a fixed nested JSON
# payload. Malformed or unrelated messages may cause template errors.
#
# Version History:
# - v1.0.0 (2022-10-11): Initial kettle monitoring and control package.
#:########################################################################################:#
mqtt:
sensor:
- unique_id: kettle.temp
packages/lounge_lighting_scenes.yaml
+7 -7
View File
@@ -126,7 +126,7 @@ script:
#switch.esp_loungemiddleswitch_relay_3_downlights_north: "on"
switch.lounge_nspanel_touchscreen_lounge_stair_downlights: "on" # non dimmable pair
light.esp_breakfastbarleds_breakfast_bar_leds: 90
light.esp_loungecabinetleds2_lounge_cabinet_leds: 90
light.esp_loungecabinetleds_lounge_cabinet_leds: 90
light.esp_loungebookshelfleds_lounge_bookshelf_leds: 90
switch.lounge_cupboard_dual_usb_xus09_l2: "on"
switch.esp_loungesouthleftswitch_relay_1_wall_washer_left: "on"
@@ -146,7 +146,7 @@ script:
light.esp_lounge6chdimmer_lounge_downlights_south: 60
light.esp_lounge6chdimmer_lounge_rafter_buttons: 40
light.esp_breakfastbarleds_breakfast_bar_leds: 60
light.esp_loungecabinetleds2_lounge_cabinet_leds: 60
light.esp_loungecabinetleds_lounge_cabinet_leds: 60
light.esp_loungebookshelfleds_lounge_bookshelf_leds: 60
#switch.esp_loungemiddleswitch_relay_3_downlights_north: "off" # non-dimmable pair
switch.lounge_nspanel_touchscreen_lounge_stair_downlights: "off" # non dimmable pair
@@ -167,7 +167,7 @@ script:
light.esp_lounge6chdimmer_lounge_downlights_south: 40
light.esp_lounge6chdimmer_lounge_rafter_buttons: 30
light.esp_breakfastbarleds_breakfast_bar_leds: 50
light.esp_loungecabinetleds2_lounge_cabinet_leds: 50
light.esp_loungecabinetleds_lounge_cabinet_leds: 50
light.esp_loungebookshelfleds_lounge_bookshelf_leds: 50
#switch.esp_loungemiddleswitch_relay_3_downlights_north: "off" # non-dimmable pair
switch.lounge_nspanel_touchscreen_lounge_stair_downlights: "off" # non dimmable pair
@@ -188,7 +188,7 @@ script:
light.esp_lounge6chdimmer_lounge_downlights_south: 30
light.esp_lounge6chdimmer_lounge_rafter_buttons: 0
light.esp_breakfastbarleds_breakfast_bar_leds: 40
light.esp_loungecabinetleds2_lounge_cabinet_leds: 40
light.esp_loungecabinetleds_lounge_cabinet_leds: 40
light.esp_loungebookshelfleds_lounge_bookshelf_leds: 40
#switch.esp_loungemiddleswitch_relay_3_downlights_north: "off"
switch.lounge_nspanel_touchscreen_lounge_stair_downlights: "off" # non dimmable pair
@@ -228,7 +228,7 @@ script:
light.esp_lounge6chdimmer_lounge_downlights_south: 0
light.esp_lounge6chdimmer_lounge_rafter_buttons: 0
light.esp_breakfastbarleds_breakfast_bar_leds: 5
light.esp_loungecabinetleds2_lounge_cabinet_leds: 5
light.esp_loungecabinetleds_lounge_cabinet_leds: 5
light.esp_loungebookshelfleds_lounge_bookshelf_leds: 5
#switch.esp_loungemiddleswitch_relay_3_downlights_north: "off"
switch.lounge_nspanel_touchscreen_lounge_stair_downlights: "off" # non dimmable pair
@@ -246,7 +246,7 @@ script:
light.esp_lounge6chdimmer_couch_spots_right: 20
light.esp_lounge6chdimmer_lounge_rafter_buttons: 15
light.esp_breakfastbarleds_breakfast_bar_leds: 25
light.esp_loungecabinetleds2_lounge_cabinet_leds: 30
light.esp_loungecabinetleds_lounge_cabinet_leds: 30
light.esp_loungebookshelfleds_lounge_bookshelf_leds: 30
#light.tasmo_h801_loungeled1_6180_a: 25
#light.tasmo_h801_loungeled1_6180_b: 25
@@ -270,7 +270,7 @@ script:
#switch.esp_loungemiddleswitch_relay_3_downlights_north: "off"
switch.lounge_nspanel_touchscreen_lounge_stair_downlights: "off" # non dimmable pair
light.esp_breakfastbarleds_breakfast_bar_leds: 0
light.esp_loungecabinetleds2_lounge_cabinet_leds: 0
light.esp_loungecabinetleds_lounge_cabinet_leds: 0
light.esp_loungebookshelfleds_lounge_bookshelf_leds: 0
switch.lounge_cupboard_dual_usb_xus09_l2: "off"
switch.esp_loungesouthleftswitch_relay_1_wall_washer_left: "off"
packages/low_battery_device_quantity.yaml
+71 -16
View File
@@ -1,3 +1,49 @@
#:########################################################################################:#
# Low Battery Monitoring Package #
#:########################################################################################:#
#
# TITLE:
# Low Battery Monitoring
#
# FILE:
# packages/low_battery_device_quantity.yaml
#
# VERSION:
# V1.2 2026-07-23
#
# VERSION HISTORY:
# V1.3 2026-07-24
# - Truncated list sensor state to count-only summary; full list stays in attributes.
#
# V1.2 2026-07-23
# - Moved the weekly low-battery blueprint automation into this package.
# - Preserved the Monday 21:00 schedule and Zorruno Pushover notification.
#
# V1.1 2026-07-20
# - Changed the low-battery threshold from 97% to 20%.
# - Added structured documentation for scope, exclusions, and outputs.
#
# V1.0
# - Initial low-battery count and list sensors.
#
# PURPOSE:
# Finds numeric sensor entities with device_class battery whose value is 20%
# or lower, exposes count and list sensors, and runs a weekly notification.
#
# SCOPE AND EXCLUSIONS:
# - Only entities in the sensor domain with device_class battery are checked.
# - Unknown, unavailable, non-numeric, and "Ok" states are excluded.
# - Battery entities in other domains are not included in the summaries.
# - The notification blueprint also checks battery binary sensors.
#
# OUTPUTS:
# - sensor.devices_with_low_battery reports the number of matching sensors.
# - sensor.devices_with_low_battery_list reports names and percentages.
# - The list sensor also exposes count, entities, and names attributes.
# - A Pushover notification runs each Monday at 21:00 when batteries are low.
#
#:########################################################################################:#
template:
- sensor:
- name: "Devices with low battery"
@@ -9,7 +55,7 @@ template:
{% if s.attributes.device_class == 'battery' %}
{% set st = s.state %}
{% if st not in ['unknown', 'unavailable', 'Ok'] %}
{% if st | int(-1) != -1 and (st | int(0)) <= 97 %}
{% if st | int(-1) != -1 and (st | int(0)) <= 20 %}
{% set ns.c = ns.c + 1 %}
{% endif %}
{% endif %}
@@ -32,21 +78,11 @@ template:
mdi:battery-alert
{% endif %}
state: >
{% set ns = namespace(names=[]) %}
{% for s in states.sensor %}
{% if s.attributes.device_class == 'battery' %}
{% set st = s.state %}
{% if st not in ['unknown', 'unavailable', 'Ok'] %}
{% if st | int(-1) != -1 and (st | int(0)) <= 97 %}
{% set ns.names = ns.names + [s.name ~ ' (' ~ (st | int(0)) ~ '%)'] %}
{% endif %}
{% endif %}
{% endif %}
{% endfor %}
{% if ns.names | length == 0 %}
{% set count = states('sensor.devices_with_low_battery') | int(0) %}
{% if count == 0 %}
None
{% else %}
{{ ns.names | join(', ') }}
{{ count }} devices
{% endif %}
attributes:
count: "{{ states('sensor.devices_with_low_battery') | int(0) }}"
@@ -56,7 +92,7 @@ template:
{% if s.attributes.device_class == 'battery' %}
{% set st = s.state %}
{% if st not in ['unknown', 'unavailable', 'Ok'] %}
{% if st | int(-1) != -1 and (st | int(0)) <= 97 %}
{% if st | int(-1) != -1 and (st | int(0)) <= 20 %}
{% set ns.e = ns.e + [s.entity_id] %}
{% endif %}
{% endif %}
@@ -69,10 +105,29 @@ template:
{% if s.attributes.device_class == 'battery' %}
{% set st = s.state %}
{% if st not in ['unknown', 'unavailable', 'Ok'] %}
{% if st | int(-1) != -1 and (st | int(0)) <= 97 %}
{% if st | int(-1) != -1 and (st | int(0)) <= 20 %}
{% set ns.n = ns.n + [s.name] %}
{% endif %}
{% endif %}
{% endif %}
{% endfor %}
{{ ns.n }}
automation:
- id: "1635929281159"
alias: "Weekly Low battery level detection"
description: >
Checks battery-class entities each Monday and notifies Zorruno when any
are below the blueprint threshold.
use_blueprint:
path: sbyx/low-battery-level-detection-notification-for-all-battery-sensors.yaml
input:
day: 1
time: "21:00:00"
actions:
- action: notify.pushover_zorruno
data:
title: "View Road Sensors"
message: >
Weekly Battery Check. Low Devices:
{{ sensors }}
packages/main_sony_tv_automations.yaml
+47 -1
View File
@@ -1,7 +1,52 @@
#:########################################################################################:#
# Main Sony TV Automations Package #
#:########################################################################################:#
#
# TITLE:
# Main Sony TV Automations
#
# FILE:
# packages/main_sony_tv_automations.yaml
#
# VERSION:
# V1.1 2026-07-20
#
# VERSION HISTORY:
# V1.1 2026-07-20
# - Added structured documentation and automation descriptions.
#
# V1.0
# - Initial MQTT TV-off and surround-amplifier following automations.
#
# PURPOSE:
# Accepts an MQTT command to turn off the lounge TV and keeps the loft
# surround-amplifier power synchronized with the TV remote state.
#
# MQTT COMMAND:
# Topic:
# viewroad-commands/maintv/action
#
# Payload:
# OFF
#
# The payload is uppercase and this package does not provide an MQTT ON action.
#
# AMPLIFIER FOLLOWING:
# - remote.lounge_tv is the source-of-truth state for the amplifier.
# - The remote state must remain on or off for five seconds before action.
# - Restart mode cancels the previous wait when another state change occurs,
# preventing brief transitions from toggling amplifier power.
#
# DEPENDENCIES:
# - remote.lounge_tv controls and reports the Sony lounge TV state.
# - switch.tv_surround_amp_power_in_loft_x27pp controls amplifier power.
#
#:########################################################################################:#
automation:
- id: "1669966515993"
alias: Turn off Lounge TV
description: ""
description: "Turns off the lounge TV when the MQTT OFF command is received."
trigger:
- platform: mqtt
topic: viewroad-commands/maintv/action
@@ -16,6 +61,7 @@ automation:
- id: tv_amp_follow_remote_state
alias: Lounge surround amp follows TV remote (5s debounce)
description: "Follows the stable lounge TV remote state after a five-second debounce."
mode: restart
trigger:
- platform: state
packages/media_players.yaml.old
-5
View File
@@ -1,5 +0,0 @@
#media_player:
# MPD Media Player on Lounge Touchscreen
# - platform: mpd
# host: !secret lounge_mpd_player
# scan_interval: 1
packages/moonraker_3dprinter.yaml
-197
View File
@@ -1,197 +0,0 @@
# === Add friendly names, icons, and area for printer controls ===
homeassistant:
customize:
rest_command.3d_printer_emergency_stop:
friendly_name: "Emergency Stop (K1C)"
area_id: Laundry
icon: mdi:alert-octagon
rest_command.3d_printer_firmware_restart:
friendly_name: "Firmware Restart (K1C)"
area_id: Laundry
icon: mdi:restart
rest_command.3d_printer_cancel:
friendly_name: "Cancel Print (K1C)"
area_id: Laundry
icon: mdi:cancel
rest_command.3d_printer_pause:
friendly_name: "Pause Print (K1C)"
area_id: Laundry
icon: mdi:pause-circle
rest_command.3d_printer_resume:
friendly_name: "Resume Print (K1C)"
area_id: Laundry
icon: mdi:play-circle
sensor.printer_3d_file_metadata:
area_id: Laundry
friendly_name: "3D Printer (K1C) Print file data"
sensor.printer_3d_sensor:
area_id: Laundry
friendly_name: "3D Printer (K1C) Sensors"
sensor.printer_3d_info:
area_id: Laundry
friendly_name: "3D Printer (K1C) State"
sensor.printer_3d_server:
area_id: Laundry
friendly_name: "3D Printer (K1C) Print Server"
sensor.3d_printer_chamber_temp:
area_id: Laundry
sensor.3d_printer_hotend_target:
area_id: Laundry
sensor.3d_printer_hotend_actual:
area_id: Laundry
sensor.3d_printer_hotend_power:
area_id: Laundry
sensor.3d_printer_bed_target:
area_id: Laundry
sensor.3d_printer_bed_actual:
area_id: Laundry
sensor.3d_printer_bed_power:
area_id: Laundry
sensor.3d_printer_state:
area_id: Laundry
sensor.3d_printer_current_print:
area_id: Laundry
sensor.3d_printer_current_progress:
area_id: Laundry
sensor.3d_printer_print_time:
area_id: Laundry
sensor.3d_printer_time_remaining:
area_id: Laundry
sensor.3d_printer_eta:
area_id: Laundry
sensor.3d_printer_message:
area_id: Laundry
sensor.3d_printer_layer_height:
area_id: Laundry
sensor.3d_printer_object_height:
area_id: Laundry
sensor.3d_printer_current_height:
area_id: Laundry
sensor.3d_printer_current_layer:
area_id: Laundry
sensor.3d_printer_total_layers:
area_id: Laundry
sensor.3d_printer_actual_layer:
area_id: Laundry
sensor.3d_printer_object_thumbnails:
area_id: Laundry
sensor.3d_printer_state_message:
area_id: Laundry
sensor.3d_printer_heaters_power:
area_id: Laundry
sensor.3d_printer_printername:
area_id: Laundry
binary_sensor.3d_printer_filament:
area_id: Laundry
# === REST sensor: File metadata for current 3D print ===
rest:
scan_interval: 5
resource_template: "http://192.168.2.31:7125/server/files/metadata?filename={{ states('sensor.3d_printer_current_print') | urlencode }}"
sensor:
- name: printer_3d_file_metadata
unique_id: "192.168.2.315ec44d90-419c-419c-802d-d34071639c08"
icon: mdi:file-document-outline
json_attributes_path: "$.result"
json_attributes:
- layer_height
- object_height
- thumbnails
value_template: "OK"
rest_command:
3d_printer_emergency_stop:
url: "http://192.168.2.31:7125/printer/emergency_stop"
method: post
3d_printer_firmware_restart:
url: "http://192.168.2.31:7125/printer/firmware_restart"
method: post
3d_printer_cancel:
url: "http://192.168.2.31:7125/printer/print/cancel"
method: post
3d_printer_pause:
url: "http://192.168.2.31:7125/printer/print/pause"
method: post
3d_printer_resume:
url: "http://192.168.2.31:7125/printer/print/resume"
method: post
sensor:
# === REST sensor: Full 3D printer status (Klipper printer/objects/query) ===
- platform: rest
name: printer_3d_sensor
unique_id: "192.168.2.313a0c25fa-297d-4c19-b03c-ddf04840682b"
icon: mdi:printer-3d-nozzle
resource: "http://192.168.2.31:7125/printer/objects/query?heater_bed&extruder&print_stats&toolhead&display_status&virtual_sdcard&gcode_move&filament_motion_sensor%20btt_smart_filament&temperature_sensor%20Chamber_Temp"
json_attributes_path: "$.result.status"
json_attributes:
- heater_bed
- extruder
- print_stats
- toolhead
- display_status
- virtual_sdcard
- gcode_move
- "filament_motion_sensor btt_smart_filament_sensor"
- "temperature_sensor Chamber_Temp"
value_template: "OK"
force_update: true
scan_interval: 1
# === REST sensor: Basic printer state and message ===
- platform: rest
name: printer_3d_info
unique_id: "192.168.2.311cba6677-02bd-4273-9083-b8301bf6943b"
icon: mdi:information-outline
scan_interval: 1
resource_template: "http://192.168.2.31:7125/printer/info"
json_attributes_path: "$.result"
json_attributes:
- state_message
- state
value_template: "OK"
# === REST sensor: Server configuration details (e.g., printer name) ===
- platform: rest
name: printer_3d_server
unique_id: "192.168.2.311cba6677-02bd-4273-9083-b8301bf6949"
icon: mdi:server
scan_interval: 1
resource_template: "http://192.168.2.31:7125/server/database/item?namespace=mainsail&key=general"
json_attributes_path: "$.result.value"
json_attributes:
- printername
value_template: "OK"
packages/niwa_tides.yaml
+22
View File
@@ -1,3 +1,25 @@
#:########################################################################################:#
# Package: NIWA Local Tides
# File: niwa_tides.yaml
# Version: v1.0.0
# Date: 2022-10-12
#
# Purpose:
# Provides local tide level and forecast information from NIWA for use in Home
# Assistant dashboards, automations, and templates.
#
# Output:
# - sensor.local_tides reports the current tide level and exposes upcoming high
# and low tide times, levels, phase, and percentage as attributes.
#
# Dependencies:
# - NIWA Tides custom integration (platform: niwa_tides).
# - NIWA API key and location coordinates stored in secrets.yaml.
#
# Version History:
# - v1.0.0 (2022-10-12): Initial local NIWA tide sensor package.
#:########################################################################################:#
sensor:
- platform: niwa_tides
api_key: !secret niwa_tides_api_key
packages/nspanel_masterbdrm_controller.yaml.old
-52
View File
@@ -1,52 +0,0 @@
automation:
- id: nspanel_lounge_controller
alias: "NSPanel Master Bedroom Controller"
description: ""
use_blueprint:
path: edwardtfn/nspanel_easy_blueprint.yaml
input:
nspanel_name: 084fb5b4a94e636d01244b1838156446
button_page01_label: Lounge Lighting Scenes
button_pages_icon_size: "10"
entity01: script.nspanel_lounge_scene_bright
entity01_name: "Bright"
entity01_icon: mdi:brightness-7
entity01_confirm: false
entity02: script.nspanel_lounge_scene_tv_general
entity02_name: "TV General"
entity02_icon: mdi:television
entity02_confirm: false
entity03: script.nspanel_lounge_scene_movie
entity03_name: "Movie"
entity03_icon: mdi:movie-open
entity03_confirm: false
entity04: script.nspanel_lounge_scene_balanced
entity04_name: "Balance"
entity04_icon: mdi:scale-balance
entity04_confirm: false
entity05: script.nspanel_lounge_scene_warm_cozy
entity05_name: "Warm Cozy"
entity05_icon: mdi:fireplace
entity05_confirm: false
entity06: script.nspanel_lounge_scene_reading
entity06_name: "Reading On/Off"
entity06_icon: mdi:book-open-page-variant
entity06_confirm: false
entity07: script.nspanel_lounge_scene_dining
entity07_name: "Dining On/Off"
entity07_icon: mdi:silverware-fork-knife
entity07_confirm: false
entity08: script.nspanel_lounge_scene_all_off
entity08_name: "All Off"
entity08_icon: mdi:power
entity08_confirm: false
mode: single
packages/office_media_buttons.yaml
+56 -3
View File
@@ -1,3 +1,49 @@
#:########################################################################################:#
# Office Media Buttons Package #
#:########################################################################################:#
#
# TITLE:
# Office Media Buttons
#
# FILE:
# packages/office_media_buttons.yaml
#
# VERSION:
# V1.1 2026-07-20
#
# VERSION HISTORY:
# V1.1 2026-07-20
# - Added structured documentation and automation descriptions.
# - Identified the active ZHA implementation and disabled alternatives.
#
# V1.0
# - Initial office media-button automations.
#
# PURPOSE:
# Controls office TV playback from a Zigbee media button using direct ZHA
# click events.
#
# ACTIVE BUTTON MAPPING:
# - Single press pauses playback.
# - Double press starts or resumes playback.
# - Triple press seeks backward by 30 seconds.
#
# DEPENDENCIES:
# - ZHA event source: device IEEE 00:15:8d:00:06:79:46:c8.
# - media_player.office_tv provides the current playback position.
# - The media actions target the office TV device registered in Home Assistant.
#
# NOTES:
# - seek_amount is not normally provided by the event and defaults to -30.
# - Commented MQTT and entity-state implementations below are disabled
# historical alternatives retained for reference.
#
#:########################################################################################:#
#:########################################################################################:#
# Historical Disabled MQTT Sensor #
#:########################################################################################:#
#mqtt:
# sensor:
# - unique_id: office_media_button_1
@@ -6,10 +52,14 @@
# unit_of_measurement: "Press"
# value_template: "{{ value_json.ZbReceived.Office_Media_Button.Power }}"
#:########################################################################################:#
# Active ZHA Automations #
#:########################################################################################:#
automation:
- id: pause_office_tv_on_media_button
alias: Pause Office TV on Media Button
description: ""
description: "Pauses the office TV when the media button is pressed once."
trigger:
- platform: event
event_type: zha_event
@@ -26,7 +76,7 @@ automation:
mode: single
- id: play_office_tv_on_media_button
alias: Play Office TV on Media Button
description: ""
description: "Starts or resumes office TV playback when the media button is pressed twice."
trigger:
- platform: event
event_type: zha_event
@@ -43,7 +93,7 @@ automation:
mode: single
- id: seek_office_tv_on_media_button
alias: Seek Office TV on Media Button
description: ""
description: "Seeks office TV playback backward 30 seconds when the media button is pressed three times."
trigger:
- platform: event
event_type: zha_event
@@ -62,6 +112,8 @@ automation:
target:
device_id: abb6b5a6b4e4925dcb3a77ea2c293eaa
mode: single
# Historical disabled MQTT and entity-state alternatives.
# - id: "1629271273958"
# alias: Pause office TV on MQTT
# description: ""
@@ -90,6 +142,7 @@ automation:
# seek_position: 30
# mode: single
# Historical disabled entity-state automation block.
#automation:
# - id: "1629271273952"
# unique_id: pause_office_tv_on_media_button
packages/outdoor_lighting_control.yaml
+5 -2
View File
@@ -3,6 +3,9 @@
###############################################################################
#
# Version:
# 2026-07-20 v0.3
# - Synchronized the documented Number 16 schedule with the implementation.
#
# 2026-05-09 v0.2
# - Refactored scheduled control to use editable schedule lists.
# - Switched lights now use explicit ON/OFF schedule entries instead of
@@ -527,8 +530,8 @@ script:
# EDIT SCHEDULE HERE
# Format: trigger, offset_minutes/at, target_brightness, ramp_minutes
# Current schedule:
# - sunset -30, 80, 30
# - 20:00, 50, 30
# - sunset -30, 60, 30
# - 20:00, 50, 120
# - 01:00, 20, 120
# - 06:00, 0, 120
###########################################################################
packages/pet_feeding_and_jobs.yaml
+66
View File
@@ -1,3 +1,28 @@
#:########################################################################################:#
# Package: Pet Feeding and Jobs Timing
# File: pet_feeding_and_jobs.yaml
# Version: v1.1.0
# Date: 2026-07-21
#
# Purpose:
# Provides legacy MQTT pet activity sensors and Jobs-derived timing sensors for
# the Lounge dog-feeding and depooping gauges.
#
# Behaviour:
# - Dog feeding reports the newest valid morning or evening completion time.
# - Dog depooping reports the weekly Jobs completion time.
# - Invalid or unrestored Jobs attributes make a timing sensor unavailable
# instead of exposing a numeric sentinel value.
#
# Version History:
# - v1.1.0 (2026-07-21): Reject invalid Jobs timing attributes and remove the
# 999999-hour fallback from the dog-feeding gauge source.
# - v1.0.0 (2026-07-21): Added Jobs-derived dog timing sensors for P010.
#:########################################################################################:#
#:######################################################################################:#
# LEGACY MQTT PET ACTIVITY AND TIMING SENSORS
#:######################################################################################:#
mqtt:
sensor:
- unique_id: dog_fed_activity
@@ -24,3 +49,44 @@ mqtt:
name: "Hours Since DePooped"
state_topic: "viewroad-tele/petfeeding/hoursSinceDePooped"
unit_of_measurement: "Hours"
#:######################################################################################:#
# JOBS-DERIVED LOUNGE GAUGE SENSORS
#:######################################################################################:#
template:
- sensor:
- name: "Jobs Tracker Hours Since Dog Fed"
unique_id: "jobs_tracker_hours_since_dog_fed"
device_class: duration
state_class: measurement
unit_of_measurement: "h"
icon: "mdi:dog-side"
availability: >-
{% set morning = state_attr('sensor.jobs_tracker_dog_feeding_morning', 'hours_since_completed') %}
{% set evening = state_attr('sensor.jobs_tracker_dog_feeding_evening', 'hours_since_completed') %}
{{ is_number(morning) or is_number(evening) }}
state: >-
{% set morning = state_attr('sensor.jobs_tracker_dog_feeding_morning', 'hours_since_completed') %}
{% set evening = state_attr('sensor.jobs_tracker_dog_feeding_evening', 'hours_since_completed') %}
{% if is_number(morning) and is_number(evening) %}
{{ [morning | float(0), evening | float(0)] | min | round(0) }}
{% elif is_number(morning) %}
{{ morning | float(0) | round(0) }}
{% elif is_number(evening) %}
{{ evening | float(0) | round(0) }}
{% else %}
{{ none }}
{% endif %}
- name: "Jobs Tracker Hours Since Dog Depooped"
unique_id: "jobs_tracker_hours_since_dog_depooped"
device_class: duration
state_class: measurement
unit_of_measurement: "h"
icon: "mdi:emoticon-poop"
availability: >-
{% set hours = state_attr('sensor.jobs_tracker_dog_depooping', 'hours_since_completed') %}
{{ is_number(hours) }}
state: >-
{% set hours = state_attr('sensor.jobs_tracker_dog_depooping', 'hours_since_completed') %}
{{ hours | float(0) if is_number(hours) else none }}
packages/piano_practice.yaml.old
-45
View File
@@ -1,45 +0,0 @@
mqtt:
sensor:
- unique_id: piano.lastfinish
name: "Last Piano Practice Complete"
state_topic: "viewroad-status/activityfeed/pianopractice"
- unique_id: piano.lastpracticeduration
state_topic: "viewroad-status/piano/lastPracticeDuration"
name: "Last Piano Practice Time"
unit_of_measurement: "mins"
- unique_id: piano.todayspracticeduration
state_topic: "viewroad-status/piano/todayPracticeDuration"
name: "Today's Piano Practice Time"
unit_of_measurement: "mins"
- unique_id: piano.thisweekspracticeduration
state_topic: "viewroad-status/piano/thisWeekPracticeDuration"
name: "This Week's Piano Practice Time"
unit_of_measurement: "mins"
automation:
- id: "1648705777863"
alias: Tag Started Piano Practice is Scanned
description: ""
trigger:
- platform: tag
tag_id: af3f595c-5d41-4bb6-8985-27c70b0e6217
condition: []
action:
- service: mqtt.publish
data:
topic: viewroad-commands/chores/piano_practice
payload: start
mode: single
- id: "Tag Finished Piano Practice is Scanned"
alias: Tag Finished Piano Practice is Scanned
description: ""
trigger:
- platform: tag
tag_id: 6e7a6ab5-c7e4-47f3-be8f-830241175d69
condition: []
action:
- service: mqtt.publish
data:
topic: viewroad-commands/chores/piano_practice
payload: end
mode: single
packages/quiet_time.yaml
+19 -15
View File
@@ -5,7 +5,17 @@
# TITLE:
# Quiet Time
#
# VERSIONS:
# FILE:
# quiet_time.yaml
#
# VERSION:
# V1.4 2026-07-20
#
# VERSION HISTORY:
# V1.4 2026-07-20
# - Updated documentation for the standalone Quiet Time actions package.
# - Documented the current flattened MQTT status topic.
#
# V1.3 2026-06-07
# - Added quiet time start and stop entity action lists.
# - Turns the LED matrix display OFF when quiet time starts.
@@ -13,7 +23,8 @@
#
# V1.2 2026-05-21
# - Added MQTT publishing when input_boolean.quiet_time changes.
# - Publishes quiet_time state to viewroad-status/homeassistant/quiet-time.
# - Published quiet_time state to viewroad-status/homeassistant/quiet-time.
# This was the historical topic; the current topic is documented below.
#
# V1.1 2026-05-21
# - Reduced daily reset check frequency from every minute to every 30 minutes.
@@ -33,20 +44,13 @@
# will automatically be turned OFF.
# - Default reset time is 07:00.
# - The quiet_time state is published to MQTT whenever it changes.
# - When quiet_time changes, editable entity lists can turn things on or off.
# - The companion package handles local actions when quiet_time changes.
#
# QUIET TIME ACTION LISTS:
# - quiet_time_start_turn_off_entities:
# Entities to turn OFF when quiet time starts.
#
# - quiet_time_start_turn_on_entities:
# Entities to turn ON when quiet time starts.
#
# - quiet_time_stop_turn_off_entities:
# Entities to turn OFF when quiet time ends.
#
# - quiet_time_stop_turn_on_entities:
# Entities to turn ON when quiet time ends.
# COMPANION PACKAGE:
# - quiet_time_on_off_actions.yaml owns the editable entity action lists and
# other local actions that run when Quiet Time starts or ends.
# - This package owns input_boolean.quiet_time, the daily reset behaviour,
# and MQTT status publishing.
#
# MQTT STATUS:
# - Topic:
packages/raspberry_pi_monitor.yaml
+64
View File
@@ -1,3 +1,67 @@
#:########################################################################################:#
# Raspberry Pi CCTV Monitor Package #
#:########################################################################################:#
#
# TITLE:
# Raspberry Pi CCTV Monitor
#
# FILE:
# packages/raspberry_pi_monitor.yaml
#
# VERSION:
# V1.1 2026-07-20
#
# VERSION HISTORY:
# V1.1 2026-07-20
# - Added structured documentation for MQTT, availability, and controls.
#
# V1.0
# - Initial monitoring and remote-control configuration.
#
# PURPOSE:
# Monitors the cctvquad1 and cctvquad2 Raspberry Pi hosts and provides remote
# reboot and shutdown controls through MQTT.
#
# EXTERNAL DEPENDENCY:
# - Each Raspberry Pi requires an external process that publishes telemetry
# and state, consumes command topics, and performs the requested actions.
# - This package does not install or manage that external process.
#
# MQTT STATUS:
# Topic pattern:
# viewroad-status/rpis/<host>/<field>
#
# Fields:
# cpu-temp, cpu-use, ram-use, disk-use, uptime, last-seen, ipv4-address,
# reboot, and shutdown.
#
# The last-seen payload must be a timestamp that Home Assistant can parse with
# as_timestamp().
#
# MQTT COMMANDS:
# Topic pattern:
# viewroad-commands/rpis/<host>/reboot/set
# viewroad-commands/rpis/<host>/shutdown/set
#
# Commands use the default MQTT switch ON/OFF payloads, QoS 1, and are not
# retained. The external process must publish matching switch state feedback.
#
# AVAILABILITY:
# - A host is considered available when its last-seen timestamp is valid and
# no more than 180 seconds old.
# - The template uses now(), so Home Assistant periodically re-evaluates age.
#
# GROUPS:
# - group.pi_cctvquad1_on collects Quad1 telemetry and controls.
# - group.pi_cctvquad2_on collects Quad2 telemetry and controls.
#
# SAFETY:
# - Reboot and shutdown interrupt CCTV services and host availability.
# - Shutdown may require physical access to power the host back on.
# - Dashboard controls should require confirmation before sending commands.
#
#:########################################################################################:#
mqtt:
sensor:
- unique_id: cctvquad1_cpu_temp
packages/recorder.yaml
+31 -1
View File
@@ -1,2 +1,32 @@
# enable the recorder integration (optional)
#:########################################################################################:#
# Package: Recorder Configuration
# File: recorder.yaml
# Version: v1.1.0
# Date: 2026-07-23
#
# Purpose:
# Enables Home Assistant Recorder with targeted exclusions for high-frequency
# diagnostic and summary entities that do not require historical storage.
#
# Exclusions:
# - ESPHome uptime sensors.
# - Home Assistant summary v2 sensors.
# - Jobs Tracker summary sensor.
#
# Notes:
# - Excluded entities remain available for current-state use.
# - Recorder retention and database settings continue to use Home Assistant
# defaults unless configured elsewhere.
#
# Version History:
# - v1.1.0 (2026-07-23): Added targeted exclusions during P013-F010 cleanup.
# - v1.0.0 (2022-10-11): Initial Recorder package.
#:########################################################################################:#
recorder:
exclude:
entity_globs:
- sensor.esp_*_uptime*
- sensor.ha_summary_v2_*
entities:
- sensor.jobs_tracker_summary
packages/robotdyn_dimmers.yaml
+30
View File
@@ -1,3 +1,33 @@
#:########################################################################################:#
# Package: RobotDyn MQTT Dimmer
# File: robotdyn_dimmers.yaml
# Version: v1.1.0
# Date: 2026-02-05
#
# Purpose:
# Provides a brightness-only Home Assistant light entity for the lounge
# RobotDyn dimmer through its JSON MQTT interface.
#
# Behaviour:
# - Reads JSON state updates from the dimmer state topic.
# - Publishes power and brightness commands to the dimmer command topic.
# - Uses a separate MQTT availability topic for online/offline status.
#
# Dependency:
# - Home Assistant MQTT integration and the external RobotDyn MQTT publisher.
#
# Known Limitations:
# - P013-F027 records that command messages are retained and may replay after
# reconnecting.
# - The configured availability topic contains "availablity"; confirm whether
# that spelling matches the publisher before correcting it.
#
# Version History:
# - v1.1.0 (2026-02-05): Added the current name, default entity ID, explicit
# availability payloads, and block-style color modes.
# - v1.0.0 (2025-09-10): Initial lounge MQTT dimmer package.
#:########################################################################################:#
mqtt:
- light:
schema: json
packages/room_fan_control.yaml
+58 -7
View File
@@ -1,9 +1,55 @@
##########################################################################################
# MASTER BEDROOM FAN (Tasmota / Sonoff iFan02)
# Improvements:
# - Numeric speed entity (0-3) reflecting actual device state via MQTT
# - Button to cycle speed 1,2,3,0
# - Keep input_select in sync with actual FanSpeed (incl after reboots)
# Room Fan Control
##########################################################################################
#
# TITLE:
# Room Fan Control
#
# FILE:
# packages/room_fan_control.yaml
#
# VERSION:
# V1.1 2026-07-20
#
# VERSION HISTORY:
# V1.1 2026-07-20
# - Added structured documentation for all three bedroom fans.
# - Documented the master-bedroom feedback loop and command-only controls.
#
# V1.0
# - Initial Tasmota and Sonoff iFan02 fan controls.
#
# PURPOSE:
# Controls the master-bedroom, Bedroom 2, and Bedroom 3 ceiling-fan speeds
# through Tasmota MQTT commands and Home Assistant dropdown helpers.
#
# SPEED MAPPING:
# - 0 = Off
# - 1 = Low
# - 2 = Medium
# - 3 = High
#
# MASTER BEDROOM:
# - Queries FanSpeed when Home Assistant starts.
# - Listens to Tasmota RESULT and STATE topics for device feedback.
# - Synchronizes the numeric and dropdown helpers with actual device state.
# - Uses optimistic local updates until MQTT feedback corrects the helpers.
# - Provides a button that cycles through speeds 1, 2, 3, and 0.
#
# BEDROOMS 2 AND 3:
# - Dropdown changes publish FanSpeed commands to each Tasmota device.
# - These controls are command-only and do not synchronize from feedback.
# - Their displayed dropdown state may not reflect physical or external changes.
#
# MQTT COMMAND TOPICS:
# - Master bedroom: cmnd/tasmo-ifan02-3793-bedrm1-1/FanSpeed
# - Bedroom 2: cmnd/tasmo-ifan02-7042-bedrm2/FanSpeed
# - Bedroom 3: cmnd/tasmo-ifan02-3497-bedrm3/FanSpeed
#
# DEPENDENCIES:
# - The three Tasmota devices must accept FanSpeed values from 0 through 3.
# - Master-bedroom feedback uses its RESULT and STATE MQTT topics.
#
##########################################################################################
input_select:
@@ -75,6 +121,7 @@ automation:
- id: master_bedroom_fan_query_on_ha_start
initial_state: true
alias: Master Bedroom Fan - Query FanSpeed on HA Start
description: "Requests the current master-bedroom FanSpeed when Home Assistant starts."
trigger:
- platform: homeassistant
event: start
@@ -90,6 +137,7 @@ automation:
- id: master_bedroom_fan_sync_from_mqtt
initial_state: true
alias: Master Bedroom Fan - Sync Helpers From MQTT FanSpeed
description: "Synchronizes the master-bedroom fan helpers from Tasmota MQTT feedback."
trigger:
- platform: mqtt
topic: stat/tasmo-ifan02-3793-bedrm1-1/RESULT
@@ -122,6 +170,7 @@ automation:
- id: set_the_master_bedroom_fan
initial_state: true
alias: Set the Master Bedroom Fan
description: "Publishes master-bedroom fan speed changes and updates the numeric helper optimistically."
trigger:
- platform: state
entity_id: input_select.master_bedroom_fan_set
@@ -145,11 +194,12 @@ automation:
value: "{{ desired }}"
########################################################################################
# BEDROOM 2 FAN - Unchanged
# BEDROOM 2 FAN - Command Only
########################################################################################
- id: set_bedroom_2_fan
initial_state: true
alias: Set Bedroom 2 Fan Speed
description: "Publishes Bedroom 2 fan speed dropdown changes to Tasmota."
trigger:
entity_id: input_select.bedroom_2_fan_set
platform: state
@@ -163,11 +213,12 @@ automation:
'
########################################################################################
# BEDROOM 3 FAN - Unchanged
# BEDROOM 3 FAN - Command Only
########################################################################################
- id: set_bedroom_3_fan
initial_state: true
alias: Set Bedroom 3 Fan Speed
description: "Publishes Bedroom 3 fan speed dropdown changes to Tasmota."
trigger:
entity_id: input_select.bedroom_3_fan_set
platform: state
packages/security_and_notifications.yaml
+28 -3
View File
@@ -1,7 +1,32 @@
#:########################################################################################:#
# Package: Security and Notification Helpers
# File: security_and_notifications.yaml
# Version: v1.1.0
# Date: 2026-07-21
#
# Purpose:
# Provides the user-controlled helper that enables away-occupancy security
# behavior such as the household lighting simulation.
#
# Behaviour:
# - input_boolean.away_occupied_routine enables eligible away-mode automations.
# - The current consumer is the away-light simulation package.
#
# Dependencies:
# - packages/simulation_lights.yaml
# - packages/quiet_time.yaml owns the canonical quiet-time helper.
#
# Version History:
# - v1.1.0 (2026-07-21): Disabled the duplicate quiet-time helper after moving
# canonical ownership to the dedicated quiet-time package.
# - v1.0.0 (2024-05-27): Added quiet-time and away-security helpers.
#:########################################################################################:#
input_boolean:
quiet_time:
name: Quiet time for no notifications
icon: mdi:shield-moon
# Legacy duplicate retained temporarily for verification.
# quiet_time:
# name: Quiet time for no notifications
# icon: mdi:shield-moon
away_occupied_routine:
name: Automation for Lights etc when away
icon: mdi:shield-lock
packages/shower_controls.yaml
+51
View File
@@ -1,3 +1,52 @@
#:########################################################################################:#
# Main Bathroom Shower Detection Package #
#:########################################################################################:#
#
# TITLE:
# Main Bathroom Shower Detection
#
# FILE:
# packages/shower_controls.yaml
#
# VERSION:
# V1.1 2026-07-20
#
# VERSION HISTORY:
# V1.1 2026-07-20
# - Added structured documentation and automation descriptions.
# - Documented current indicator-only usage.
#
# V1.0
# - Initial humidity-rate shower detection.
#
# PURPOSE:
# Detects shower use from the main-bathroom humidity level and its rate of
# change, then maintains input_boolean.main_bathroom_shower as an indicator.
#
# DEPENDENCY:
# sensor.main_bathroom_environment_zth10_humidity_2 provides humidity in %.
#
# DERIVATIVE SENSOR:
# - Calculates humidity change in % per minute over a 15-minute time window.
# - Rounds the result to 0.1.
#
# DETECTION:
# - Humidity change must remain above 0.6 %/min for five minutes.
# - Current humidity must also be above 63%.
#
# CLEARING:
# - Humidity change must remain below 0.2 %/min for 15 minutes.
# - No absolute-humidity condition is required to clear the indicator.
# - The gap between activation and clearing thresholds provides hysteresis
# and prevents rapid toggling near one threshold.
#
# CURRENT USE:
# - The package only maintains input_boolean.main_bathroom_shower.
# - No other user-YAML automation, script, or package currently consumes it.
# - This package does not directly control a bathroom fan or other device.
#
#:########################################################################################:#
input_boolean:
main_bathroom_shower:
name: Main Bathroom Shower
@@ -14,6 +63,7 @@ sensor:
automation:
- id: main_bathroom_shower_detected
alias: Main Bathroom - Shower detected (humidity rate + min humidity)
description: "Turns on the shower indicator after a sustained humidity rise above the minimum humidity."
mode: single
trigger:
- platform: numeric_state
@@ -31,6 +81,7 @@ automation:
- id: main_bathroom_shower_cleared
alias: Main Bathroom - Shower cleared (humidity rate)
description: "Turns off the shower indicator after the humidity change rate remains low for 15 minutes."
mode: single
trigger:
- platform: numeric_state
packages/simulation_lights.yaml
+93 -3
View File
@@ -1,8 +1,39 @@
#:########################################################################################:#
# Package: Away-Light Security Simulation
# File: simulation_lights.yaml
# Version: v1.0.0
# Date: 2026-07-24
#
# Purpose:
# Simulates household activity while the away routine is active and all
# configured family members are away. Every five minutes after sunset, the
# automation selects a configured entity and operates it for a random period.
#
# Version History:
# - v1.0.0 (2026-07-24): Consolidated the simulation groups, away automation, and timed helper
# script into one feature package.
# - Preserved the existing automation ID, group keys, and script key.
# - Aligned the automation with the existing simulation_lights_all group.
#:########################################################################################:#
group:
simulation_lights_all:
name: Simulation Lights (All)
#:######################################################################################:#
# FAMILY PRESENCE
#:######################################################################################:#
family_away:
name: "All Family Members Away"
entities:
- group.downstairs_flat_lights # ← now valid here
- !secret person_1
- !secret person_2
- !secret person_3
#:######################################################################################:#
# SIMULATION ENTITIES
#:######################################################################################:#
simulation_lights_all:
name: "Simulation Lights (All)"
entities:
- group.downstairs_flat_lights
- switch.esp_centralstairs_top_relay_2_stair_footer_lights
- switch.esp_centralstairs_bottom_relay_1_main_stair_lights_lower
- switch.esp_entrancebathrmlights_relay_1_main_lights
@@ -16,3 +47,62 @@ group:
- light.esp_loungepelmetleds2_lounge_pelmet_leds_a
- light.esp_lounge6chdimmer_couch_spots_left
- light.esp_lounge6chdimmer_couch_spots_right
script:
#:######################################################################################:#
# RANDOM-DURATION ENTITY CONTROL
#:######################################################################################:#
light_duration:
description: "Turns an entity on for a supplied duration and then turns it off."
mode: parallel
fields:
light:
description: "Entity to operate."
example: light.bedroom
duration:
description: "How long the entity should remain on."
example: "00:25:00"
sequence:
- action: logbook.log
data:
name: "Script Notice"
message: "Light {{ light }} will be turned on for {{ duration }}"
- action: homeassistant.turn_on
target:
entity_id: "{{ light }}"
- delay: "{{ duration }}"
- action: homeassistant.turn_off
target:
entity_id: "{{ light }}"
automation:
#:######################################################################################:#
# AWAY-LIGHT SIMULATION
#:######################################################################################:#
- id: do_random_actions_when_away
alias: "Activate Random Actions for Security"
description: >
Periodically runs the timed simulation script after sunset when the away
routine is active and all configured family members are away.
mode: parallel
triggers:
- trigger: time_pattern
minutes: "/5"
conditions:
- condition: sun
after: sunset
after_offset: "-00:30:00"
- condition: state
entity_id: input_boolean.away_occupied_routine
state: "on"
- condition: state
entity_id: group.family_away
state: "not_home"
actions:
- action: script.light_duration
data:
light: "{{ state_attr('group.simulation_lights_all', 'entity_id') | random }}"
duration: "00:{{ '{:02}'.format(range(5, 29) | random | int) }}:00"
packages/vehicle_announcements.yaml
+28
View File
@@ -0,0 +1,28 @@
#:########################################################################################:#
# Package: Vehicle Announcements
# File: vehicle_announcements.yaml
# Version: v1.0.0
# Date: 2026-07-23
#
# Purpose:
# Sends vehicle arrival announcements through the View Road announcement router.
#:########################################################################################:#
automation:
- id: byd_atto3_arrival_announcement
alias: "BYD Atto 3 - Arrival Announcement"
description: >
Sends a Pushover notification to the Zorruno phone when the BYD Atto 3
Bermuda tracker arrives home.
mode: single
triggers:
- trigger: state
entity_id: device_tracker.byd_atto3_ibeacon_bur4c2a_bermuda_tracker
from: "not_home"
to: "home"
actions:
- action: script.view_road_announcement
data:
channels: "pushover_zorruno"
title: "Vehicle Notification"
long_announcement: "The BYD Atto 3 has arrived home."
packages/waste_collection.yaml
+76 -10
View File
@@ -1,13 +1,79 @@
#:########################################################################################:#
# Council Waste Collection Package #
#:########################################################################################:#
#
# TITLE:
# Council Waste Collection
#
# FILE:
# packages/waste_collection.yaml
#
# VERSION:
# V1.4 2026-07-22
#
# VERSION HISTORY:
# V1.4 2026-07-22
# - Fixed waste type names to match Auckland Council source output (recycling, food scraps)
# - Resolved P013-F019: Recycling and food-waste sensors were unknown due to type mismatch
#
# V1.3 2026-07-22
# - Moved the source identifier to !secret council_name.
# - Changed source documentation and MQTT unique IDs to generic wording.
#
# V1.2 2026-07-22
# - Moved the source area number to !secret council_area.
# - Changed package and schedule display names to generic council wording.
#
# V1.1 2026-07-20
# - Added source setup, schedule, MQTT, and maintenance documentation.
#
# V1.0
# - Initial council schedules and MQTT bin-status sensors.
#
# PURPOSE:
# Provides council rubbish, recycling, and food-waste collection schedules,
# plus independent MQTT sensors indicating whether bins are out.
#
# DEPENDENCY:
# Requires the Waste Collection Schedule custom integration and its configured
# council source.
#
# AREA NUMBER SETUP:
# - Open the council rubbish and recycling collection-day finder.
# - Select the property address.
# - Store the displayed assessment number as council_area in secrets.yaml.
# - Source documentation:
# https://github.com/mampfes/hacs_waste_collection_schedule
#
# SCHEDULE SENSORS:
# - Types are rubbish, recycling, and food scraps (matching Auckland source output).
# - Each sensor returns one upcoming collection with a one-day lead time.
# - details_format is upcoming and add_days_to adds relative-day text.
#
# MQTT BIN-OUT SENSORS:
# - These sensors are independent of the council collection schedules.
# - An external publisher must send status to the configured MQTT topics.
# - Payloads remain raw sensor strings such as "true"; these are not binary
# sensor entities and no boolean conversion is performed here.
#
# CURRENT STATUS:
# - As of 2026-07-20, the rubbish schedule resolves correctly.
# - Recycling and food-waste report unknown; review the source type names when
# investigating those schedules.
# - As of 2026-07-22, fixed type names to match Auckland Council source output.
#
#:########################################################################################:#
waste_collection_schedule:
sources:
- name: aucklandcouncil_govt_nz
- name: !secret council_name
args:
area_number: 12344403722 # see 'How to get the source argument below'
area_number: !secret council_area
sensor:
- platform: waste_collection_schedule
#source_index: 0
name: Auckland Council Waste
name: "Council Waste"
details_format: upcoming
count: 1
leadtime: 1
@@ -19,7 +85,7 @@ sensor:
- rubbish
- platform: waste_collection_schedule
#source_index: 0
name: Auckland Council Recycling
name: "Council Recycling"
details_format: upcoming
count: 1
leadtime: 1
@@ -28,10 +94,10 @@ sensor:
add_days_to: true
#event_index: EVENT_INDEX
types:
- recycle
- recycling
- platform: waste_collection_schedule
#source_index: 0
name: Auckland Council Food-Waste
name: "Council Food-Waste"
details_format: upcoming
count: 1
leadtime: 1
@@ -40,16 +106,16 @@ sensor:
add_days_to: true
#event_index: EVENT_INDEX
types:
- food-waste
- food scraps
mqtt:
sensor:
- unique_id: auckland_council_red_waste_bin_out
- unique_id: council_red_waste_bin_out
name: "Red Waste Bin Out"
state_topic: "viewroad-status/rubbishbinstatus/redbin-out"
- unique_id: auckland_council_green_recycling_bin_out
- unique_id: council_green_recycling_bin_out
name: "Green Recycling Bin Out"
state_topic: "viewroad-status/rubbishbinstatus/greenbin-out"
- unique_id: auckland_council_food_waste_bin_out
- unique_id: council_food_waste_bin_out
name: "Food Waste Bin Out"
state_topic: "viewroad-status/rubbishbinstatus/foodbin-out"
scripts.yaml
View File
scripts/office_mediaplayer.yaml
-6
View File
@@ -1,6 +0,0 @@
skip:
alias: skip
sequence:
- service: media_player.media_seek
data_template:
seek_position: "{{ state_attr(media_player.office_tv, 'media_position') | float + 10 }}"
scripts/reload_lounge_browser.yaml.old
-5
View File
@@ -1,5 +0,0 @@
action: browser_mod.javascript
data:
code: lovelace_reload()
browser_id:
- lounge
scripts/turn_light_on_for_random_time.yaml
-23
View File
@@ -1,23 +0,0 @@
light_duration:
mode: parallel # Enable parallel executions
description: "Turns on a light for a while, and then turns it off"
fields:
light:
description: "A specific light"
example: "light.bedroom"
duration:
description: "How long the light should be on in minutes"
example: "25"
sequence:
- service: logbook.log
data:
name: "Script Notice.."
message: >
"Light {{ light }} will be turned on for {{ duration }}"
- service: homeassistant.turn_on
data:
entity_id: "{{ light }}"
- delay: "{{ duration }}"
- service: homeassistant.turn_off
data:
entity_id: "{{ light }}"
templates/moonraker_3dprinter.yaml
-308
View File
@@ -1,308 +0,0 @@
- binary_sensor:
- name: 3D Printer (K1C) Filament
unique_id: "192.168.2.315ce32fc9-5e95-49e7-80e7-bfdd2cf1d1fd"
device_class: motion
state: >
{% set attr = states.sensor.printer_3d_sensor.attributes.get("filament_switch_sensor Filament") %}
{{ attr.filament_detected if attr is defined else false }}
icon: mdi:printer-3d-nozzle-alert
availability: >
{% set items = ['sensor.printer_3d_sensor'] %}
{{ expand(items) | rejectattr('state','in',['unknown','unavailable']) | list | count == items | count }}
attributes:
friendly_name: "Filament Detected"
- sensor:
- name: 3D Printer (K1C) Printer Name
unique_id: "192.168.2.313a0f3144-a801-422f-adb6-e2ed35796074"
state: '{{ states.sensor.printer_3d_server.attributes["printername"] }}'
availability: >
{% set items = ['sensor.printer_3d_server'] %}
{{ expand(items) | rejectattr('state','in',['unknown','unavailable']) | list | count == items | count }}
icon: mdi:printer-3d
attributes:
friendly_name: "Printer Name"
# === Sensor: Chamber temperature (actual) ===
- name: 3D Printer (K1C) Chamber Temp
unique_id: "192.168.2.31167e5dec-719c-42d3-9560-4f177573f741"
state: '{{ states.sensor.printer_3d_sensor.attributes["temperature_sensor Chamber_Temp"]["temperature"] | float(0) | round(1) }}'
unit_of_measurement: "°C"
icon: mdi:thermometer
availability: >
{% set items = ['sensor.printer_3d_sensor'] %}
{{ expand(items)|rejectattr('state','in',['unknown','unavailable'])|list|count == items|count }}
attributes:
friendly_name: "Chamber Actual"
# === Sensor: Hotend target temperature ===
- name: 3D Printer (K1C) Hotend Target
unique_id: "192.168.2.31167e5dec-719c-42d3-9560-4f177573f740"
state: '{{ states.sensor.printer_3d_sensor.attributes["extruder"]["target"] | float(0) | round(1) }}'
unit_of_measurement: "°C"
icon: mdi:thermometer
availability: >
{% set items = ['sensor.printer_3d_sensor'] %}
{{ expand(items)|rejectattr('state','in',['unknown','unavailable'])|list|count == items|count }}
attributes:
friendly_name: "Hotend Target"
# === Sensor: Hotend actual temperature ===
- name: 3D Printer (K1C) Hotend Actual
unique_id: "192.168.2.317c2593fb-a7dd-4ed7-a865-2e4dddddbb40"
state: '{{ states.sensor.printer_3d_sensor.attributes["extruder"]["temperature"] | float(0) | round(1) }}'
unit_of_measurement: "°C"
icon: mdi:thermometer
availability: >
{% set items = ['sensor.printer_3d_sensor'] %}
{{ expand(items)|rejectattr('state','in',['unknown','unavailable'])|list|count == items|count }}
attributes:
friendly_name: "Hotend Actual"
- name: 3D Printer (K1C) Hotend Power
unique_id: "192.168.2.31c57a1e35-92fa-403e-b3cf-ec1e97ef94cf"
state: '{{ states.sensor.printer_3d_sensor.attributes["extruder"]["power"] | float(0) | round(3) * 100}}'
availability: >
{% set items = ['sensor.printer_3d_sensor'] %}
{{ expand(items)|rejectattr('state','in',['unknown','unavailable'])
|list|count == items|count }}
unit_of_measurement: "%"
icon: mdi:flash
attributes:
friendly_name: "Hotend Power"
- name: 3D Printer (K1C) Bed Target
unique_id: "192.168.2.31eadec415-c281-4814-8fba-17c6c42670ec"
state: '{{ states.sensor.printer_3d_sensor.attributes["heater_bed"]["target"] | float(0) | round(1) }}'
unit_of_measurement: "°C"
icon: mdi:thermometer
availability: >
{% set items = ['sensor.printer_3d_sensor'] %}
{{ expand(items)|rejectattr('state','in',['unknown','unavailable']) | list | count == items | count }}
attributes:
friendly_name: "Bed Target"
- name: 3D Printer (K1C) Bed Actual
unique_id: "192.168.2.31cb33503c-c5d4-4e06-b79b-c1cd64ca2d7a"
state: '{{ states.sensor.printer_3d_sensor.attributes["heater_bed"]["temperature"] | float(0) | round(1) }}'
unit_of_measurement: "°C"
icon: mdi:thermometer
availability: >
{% set items = ['sensor.printer_3d_sensor'] %}
{{ expand(items)|rejectattr('state','in',['unknown','unavailable']) | list | count == items | count }}
attributes:
friendly_name: "Bed Actual"
- name: 3D Printer (K1C) Bed Power
unique_id: "192.168.2.31abb2fc5b-8173-4131-a942-fb11e30f4efa"
state: '{{ states.sensor.printer_3d_sensor.attributes["heater_bed"]["power"] | float(0) | round(3) * 100 }}'
unit_of_measurement: "%"
icon: mdi:flash
availability: >
{% set items = ['sensor.printer_3d_sensor'] %}
{{ expand(items)|rejectattr('state','in',['unknown','unavailable']) | list | count == items | count }}
attributes:
friendly_name: "Bed Power"
- name: 3D Printer (K1C) Printer State
unique_id: "192.168.2.31758ce84c-3210-4f29-b6b3-38139180de96"
state: '{{ states.sensor.printer_3d_sensor.attributes["print_stats"]["state"] }}'
icon: >
{% set val = states.sensor.printer_3d_sensor.attributes["print_stats"]["state"] %}
{% if val == 'standby' %}
mdi:sleep
{% elif val == 'error' %}
mdi:alert-circle
{% elif val == 'printing' %}
mdi:printer-3d-nozzle
{% elif val == 'paused' %}
mdi:pause-circle
{% elif val == 'complete' %}
mdi:printer-3d
{% else %}
mdi:help-circle
{% endif %}
availability: >
{% set items = ['sensor.printer_3d_sensor'] %}
{{ expand(items) | rejectattr('state', 'in', ['unknown','unavailable']) | list | count == items | count }}
attributes:
friendly_name: "Printer State"
- name: 3D Printer (K1C) Current Print
unique_id: "192.168.2.313a0f3144-a801-422f-adb6-e2ed35796072"
state: '{{ states.sensor.printer_3d_sensor.attributes["print_stats"]["filename"] }}'
icon: mdi:file
availability: >
{% set items = ['sensor.printer_3d_sensor'] %}
{{ expand(items) | rejectattr('state', 'in', ['unknown','unavailable']) | list | count == items | count }}
attributes:
friendly_name: "Current Print"
- name: 3D Printer (K1C) Current Progress
unique_id: "192.168.2.318ec7163b-be00-4a10-8051-48cf9a260a29"
state: '{{ ((states.sensor.printer_3d_sensor.attributes["display_status"]["progress"]) * 100) | round(0, "floor") }}'
unit_of_measurement: "%"
icon: mdi:progress-clock
availability: >
{% set items = ['sensor.printer_3d_sensor'] %}
{{ expand(items) | rejectattr('state', 'in', ['unknown','unavailable']) | list | count == items | count }}
attributes:
friendly_name: "Progress"
- name: 3D Printer (K1C) Print time
unique_id: "192.168.2.31e1ac0fac-e8ba-4e05-8fa0-c8d8076f9f63"
state: '{{ states.sensor.printer_3d_sensor.attributes["print_stats"]["print_duration"] | timestamp_custom("%H:%M:%S", 0) }}'
icon: mdi:camera-timer
availability: >
{% set items = ['sensor.printer_3d_sensor'] %}
{{ expand(items) | rejectattr('state', 'in', ['unknown','unavailable']) | list | count == items | count }}
attributes:
friendly_name: "Time Elapsed"
- name: 3D Printer (K1C) Time Remaining
unique_id: "192.168.2.31e12c8def-5ebe-43a4-9f75-605a0c46fc0f"
state: >
{{
(
(
states.sensor.printer_3d_sensor.attributes["print_stats"]["print_duration"]
/ states.sensor.printer_3d_sensor.attributes["display_status"]["progress"]
- states.sensor.printer_3d_sensor.attributes["print_stats"]["print_duration"]
) if states.sensor.printer_3d_sensor.attributes["display_status"]["progress"] > 0 else 0
) | timestamp_custom("%H:%M:%S", 0)
}}
icon: mdi:timer-sand
availability: >
{% set items = ['sensor.printer_3d_sensor'] %}
{{ expand(items) | rejectattr('state','in',['unknown','unavailable']) | list | count == items | count }}
attributes:
friendly_name: "Time Remaining"
- name: 3d_printer_eta
unique_id: "192.168.2.31a2b57068-9a32-4d2c-8cc9-57d2389a9082"
state: >
{{
(
as_timestamp(now()) +
(
(
states.sensor.printer_3d_sensor.attributes["print_stats"]["print_duration"]
/ states.sensor.printer_3d_sensor.attributes["display_status"]["progress"]
- states.sensor.printer_3d_sensor.attributes["print_stats"]["print_duration"]
) if states.sensor.printer_3d_sensor.attributes["display_status"]["progress"] > 0 else 0
)
) | timestamp_custom("%H:%M:%S", 1)
}}
icon: mdi:av-timer
availability: >
{% set items = ['sensor.printer_3d_sensor'] %}
{{ expand(items) | rejectattr('state','in',['unknown','unavailable']) | list | count == items | count }}
attributes:
friendly_name: "ETA"
- name: 3D Printer (K1C) Message
unique_id: "192.168.2.310c418c0d-e59e-4d4e-aa11-8fae53df58f8"
state: '{{ states.sensor.printer_3d_sensor.attributes["display_status"]["message"] }}'
icon: mdi:message-cog
availability: >
{% set items = ['sensor.printer_3d_sensor'] %}
{{ expand(items) | rejectattr('state','in',['unknown','unavailable']) | list | count == items | count }}
attributes:
friendly_name: "Message"
- name: 3D Printer (K1C) Layer Height
unique_id: "192.168.2.316cca455d-c327-4567-b886-4d7f99714265"
state: '{{ states.sensor.printer_3d_file_metadata.attributes["layer_height"] | float(0) }}'
unit_of_measurement: "mm"
icon: mdi:arrow-collapse-down
availability: >
{% set items = ['sensor.printer_3d_file_metadata'] %}
{{ expand(items) | rejectattr('state','in',['unknown','unavailable']) | list | count == items | count }}
attributes:
friendly_name: "Layer Height"
- name: 3D Printer (K1C) Object Height
unique_id: "192.168.2.316d6d9dc0-9a02-4ce4-a797-c84b42e011a6"
state: '{{ (states.sensor.printer_3d_file_metadata.attributes["object_height"] | float(0)) - (states.sensor.printer_3d_file_metadata.attributes["layer_height"] | float(0)) }}'
unit_of_measurement: "mm"
icon: mdi:arrow-expand-vertical
availability: >
{% set items = ['sensor.printer_3d_file_metadata'] %}
{{ expand(items) | rejectattr('state','in',['unknown','unavailable']) | list | count == items | count }}
attributes:
friendly_name: "Object Height"
- name: 3D Printer (K1C) Current Height
unique_id: "192.168.2.31d440e568-d4d1-4b3f-85c4-fdacd68c0e1a"
state: '{{ states.sensor.printer_3d_sensor.attributes["gcode_move"]["gcode_position"][2] | float(0) | round(2) }}'
unit_of_measurement: "mm"
icon: mdi:arrow-collapse-down
availability: >
{% set items = ['sensor.printer_3d_sensor'] %}
{{ expand(items) | rejectattr('state','in',['unknown','unavailable']) | list | count == items | count }}
attributes:
friendly_name: "Current Height"
- name: 3D Printer (K1C) Current Layer
unique_id: "192.168.2.316a77acc1-8134-4354-b2f6-390adab81993"
state: '{{ (states("sensor.3d_printer_current_height") | float(0) / states("sensor.3d_printer_layer_height") | float(0)) | round(0) }}'
icon: mdi:counter
availability: >
{% set items = ['sensor.3d_printer_current_height','sensor.3d_printer_layer_height'] %}
{{ expand(items) | rejectattr('state','in',['unknown','unavailable']) | list | count == items | count }}
attributes:
friendly_name: "Current Layer"
- name: 3D Printer (K1C) Total Layers
unique_id: "192.168.2.3153cfe906-28ec-44cd-926a-b08ffb8766e5"
state: '{{ (states("sensor.3d_printer_object_height") | float(0) / states("sensor.3d_printer_layer_height") | float(0)) | round(0) }}'
icon: mdi:counter
availability: >
{% set items = ['sensor.3d_printer_object_height','sensor.3d_printer_layer_height'] %}
{{ expand(items) | rejectattr('state','in',['unknown','unavailable']) | list | count == items | count }}
attributes:
friendly_name: "Total Layers"
- name: 3D Printer (K1C) Actual Layer
unique_id: "192.168.2.31167e5dec-719c-42d3-9560-4f177573f742"
state: '{{ states.sensor.printer_3d_sensor.attributes.print_stats["info"]["current_layer"] }} / {{ states.sensor.printer_3d_sensor.attributes.print_stats["info"]["total_layer"] }}'
icon: mdi:layers-triple
availability: >
{% set items = ['sensor.printer_3d_sensor'] %}
{{ expand(items) | rejectattr('state','in',['unknown','unavailable']) | list | count == items | count }}
attributes:
friendly_name: "Actual Layer"
- name: 3D Printer (K1C) Object Thumbnails
unique_id: "192.168.2.3159b37837-b751-4d31-98c2-516a52edf833"
state: >
{% set dir = states('sensor.3d_printer_current_print') %}
{% set thumb = state_attr('sensor.printer_3d_file_metadata','thumbnails') %}
{% set img = (thumb | last).relative_path if thumb else 'not available' %}
{{ (dir.split('/')[:-1] + [img]) | join('/') }}
icon: mdi:image
availability: >
{% set items = ['sensor.printer_3d_file_metadata'] %}
{{ expand(items) | rejectattr('state','in',['unknown','unavailable']) | list | count == items | count }}
attributes:
friendly_name: "Object Thumbnails"
- name: 3D Printer (K1C) State Message
unique_id: "192.168.2.319a5184c9-ac5b-44a9-a691-2b67c243d197"
state: '{{ states.sensor.printer_3d_info.attributes["state_message"] }}'
icon: mdi:message-cog
availability: >
{% set items = ['sensor.printer_3d_info'] %}
{{ expand(items) | rejectattr('state','in',['unknown','unavailable']) | list | count == items | count }}
attributes:
friendly_name: "State Message"
- name: 3D Printer (K1C) Bed and Nozzle Power
unique_id: "192.168.2.313988e9be-c910-4634-8205-38d53170d5a5"
state: '{{ states("sensor.3d_printer_bed_power") | float(0) | round(1) }}% / {{ states("sensor.3d_printer_hotend_power") | float(0) | round(1) }}%'
icon: mdi:meter-electric-outline
availability: >
{% set items = ['sensor.3d_printer_bed_power','sensor.3d_printer_hotend_power'] %}
{{ expand(items) | rejectattr('state','in',['unknown','unavailable']) | list | count == items | count }}
attributes:
friendly_name: "Bed and Nozzle Power"
themes.yaml
View File