nearxos/kkelomatic_home
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Enhance Node-RED living room flow with new functionality and documentation updates

Browse Source 
- Added a new "Living Room" tab to the Node-RED flow for better organization.
- Introduced functions for handling Home Assistant and Zigbee interactions, allowing for more dynamic control of living room lights.
- Updated the living room flow documentation to include configuration instructions for the Action node, improving usability for users integrating with Home Assistant.

This update enhances the functionality and clarity of the Node-RED integration for the living room setup.
This commit is contained in:
nearxos
2026-02-08 17:33:48 +02:00
parent f0d883b8c2
commit eab798cda4
3 changed files with 389 additions and 281 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
docs/integration/nodered-livingroom-flow.md
View File

@@ -151,6 +151,19 @@ When you change a light with the **Zigbee switch** (or any source that doesn’t
The function only sends a message when a mapped light’s state **changed**, so multiple entities can be updated in one NVL cycle. When you use the Zigbee switch (or the PLC changes state any other way), the matching HA entities are updated.
### How to configure the Action node
You can use **one** Action node for both turn_on and turn_off (the sync sends the right `action` and `target` in each message). Connect **both** outputs of the sync function to the **same** Action node.
1. Add an **Action** node (Palette → Home Assistant → Action).
2. **Server:** Select your Home Assistant server config.
3. **Block Input Overrides:** Set to **off** (unchecked). This allows `msg.payload` from the sync to override the node config, so `payload.action` and `payload.target.entity_id` are used.
4. **Action:** The node may require a non-empty value. Enter a placeholder such as **`input_boolean.turn_on`**. With **Block Input Overrides** off, the sync’s `msg.payload.action` overrides this on each message. Leave **Entity**, **Data** etc. empty.
5. **Queue:** Optional — e.g. `none` or `last` if you want to send the last message when HA reconnects.
6. Connect **Output 1** and **Output 2** of the NVL→HA sync function to this Action node.
Alternatively use **two** Action nodes: connect Output 1 to one (optional: set action to `input_boolean.turn_on`), Output 2 to the other (optional: `input_boolean.turn_off`). Still set **Block Input Overrides** to **off** so `payload.target.entity_id` is used.
---
## Connection to Flow 1 (CODESYS)