From 93dfed6c5e64f2afc6a8554a28c20969db6413df Mon Sep 17 00:00:00 2001 From: Gitea Actions Date: Thu, 26 Jun 2025 13:47:31 +0000 Subject: [PATCH] Auto-update blog content from Obsidian: 2025-06-26 13:47:31 --- .../post/6-ac-automation-home-assistant-node-red.md | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/content/post/6-ac-automation-home-assistant-node-red.md b/content/post/6-ac-automation-home-assistant-node-red.md index 0606a2a..f28d235 100644 --- a/content/post/6-ac-automation-home-assistant-node-red.md +++ b/content/post/6-ac-automation-home-assistant-node-red.md @@ -305,7 +305,16 @@ It is connected to a `change node` which will attach the configuration to the `r } ``` -#### 9. +#### 9. TBD + +Now that the message has the room configuration attached, we are entering in the computation pipeline. We have the AC unit name, the sensor names, the desired base temperature and the offset to apply. From these values, we will fetch the current state and do the maths. + +The first node is another `delay node` which regulate the rate of incoming messages, because the previous block could have created 3 messages in all rooms are targeted. + +The second is the most important node of the workflow, a `function node` that has multiple tasks: +- + + #### 10. #### 11. #### 12.