Auto-update blog content from Obsidian: 2025-06-26 13:47:31
All checks were successful
Blog Deployment / Check-Rebuild (push) Successful in 6s
Blog Deployment / Build (push) Has been skipped
Blog Deployment / Deploy-Staging (push) Successful in 10s
Blog Deployment / Test-Staging (push) Successful in 3s
Blog Deployment / Merge (push) Successful in 6s
Blog Deployment / Deploy-Production (push) Successful in 9s
Blog Deployment / Test-Production (push) Successful in 3s
Blog Deployment / Clean (push) Has been skipped
Blog Deployment / Notify (push) Successful in 2s

This commit is contained in:
Gitea Actions
2025-06-26 13:47:31 +00:00
parent bebd72319b
commit 93dfed6c5e

View File

@@ -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. #### 10.
#### 11. #### 11.
#### 12. #### 12.