diff --git a/content/post/6-ac-automation-home-assistant-node-red.fr.md b/content/post/6-ac-automation-home-assistant-node-red.fr.md index 748abba..5062ab8 100644 --- a/content/post/6-ac-automation-home-assistant-node-red.fr.md +++ b/content/post/6-ac-automation-home-assistant-node-red.fr.md @@ -142,7 +142,7 @@ Pour pouvoir ajuster la température sans avoir à modifier tout le workflow, j Ces valeurs représentent la température de base utilisée pour le calcul des seuils, en fonction des offsets que je détaillerai plus loin. Le premier nœud est un `trigger state node` qui regroupe les 6 entités. Si je modifie l’une de ces valeurs, le nœud est déclenché : -![Node-RED trigger state node for sliders](img/node-red-trigger-state-nmode-for-sliders.png) +![Node-RED trigger state node for sliders](img/node-red-trigger-state-mode-for-sliders.png) Le deuxième nœud est un `function node`, qui permet de déterminer la pièce concernée : ```js @@ -675,7 +675,7 @@ Parfois, pour une raison ou une autre, on souhaite utiliser la climatisation man Node-RED utilise son propre utilisateur dans Home Assistant, donc si une unité change d’état sans cet utilisateur, c’est qu’une intervention manuelle a eu lieu. Le premier nœud est un `trigger state node`, qui envoie un message dès qu’une unité AC change d’état : -![Pasted_image_20250626221149.png](img/Pasted_image_20250626221149.png) +![node-red-trigger-state-unit-change.png](img/node-red-trigger-state-unit-change.png) Le deuxième est un `function node` qui associe l’unité avec son minuteur : ```js 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 8aca6cd..997f9ac 100644 --- a/content/post/6-ac-automation-home-assistant-node-red.md +++ b/content/post/6-ac-automation-home-assistant-node-red.md @@ -142,7 +142,7 @@ To have a control over the temperature without having to change the workflow, I These values are the base temperature used for the calculation of the threshold, depending off the offset which I will detail further. The first node is a `trigger state node`, with all 6 entities combined. If I change one value, the node is triggered: -![Node-RED trigger state node for sliders](img/node-red-trigger-state-nmode-for-sliders.png) +![Node-RED trigger state node for sliders](img/node-red-trigger-state-mode-for-sliders.png) The second node is a `function node`, to determine the room affected: ```js @@ -668,7 +668,7 @@ The second node is another `call service node` which will start the lock timer o Sometime, for some reason, we want to use the AC manually. When we do, we don't want the workflow to change our manual setting, at least for some time. Node-RED is using its own user in Home Assistant, so when an AC unit change state without this user, this was manually done. The first node is a `trigger state node`, which will send a message when any AC unit is changing state: -![Pasted_image_20250626221149.png](img/Pasted_image_20250626221149.png) +![node-red-trigger-state-unit-change.png](img/node-red-trigger-state-unit-change.png) The second is a `function node` which willassociate the unit with its timer: ```js diff --git a/static/img/node-red-trigger-state-nmode-for-sliders.png b/static/img/node-red-trigger-state-mode-for-sliders.png similarity index 100% rename from static/img/node-red-trigger-state-nmode-for-sliders.png rename to static/img/node-red-trigger-state-mode-for-sliders.png diff --git a/static/img/Pasted_image_20250626221149.png b/static/img/node-red-trigger-state-unit-change.png similarity index 100% rename from static/img/Pasted_image_20250626221149.png rename to static/img/node-red-trigger-state-unit-change.png