Retrieve Entity ID from msg. or flow. #1573
Replies: 1 comment 9 replies
|
In a subflow, you can pass any property from the incoming message ( For example, if the incoming {
"id": "xxxx",
"room": "office"
}Inside the subflow, you can reference properties like Example: msg.sensor1 = "sensor.hvac_" + msg.room + "_temperature";
return msg;In this case, the |
|
Any idea how I can rebuild my subflow then: |
|
debug 2 and debug 3 are just to verify it works with other nodes. at debug 5 i want to add my flow, that should always run if in HASS UI the input select is changed |
|
Can you describe what you would like the subflow to do? |
|
Hi, I want to create a subflow for heating that handles all aspects of heating a room and can be reused for each room. The subflow needs to work with more than 8 entities related to the room. All of these entities follow the schema like sensor.heating_temperature, input_select.heatmode, etc. My goal is to reduce the number of input parameters for the subflow so that only the room needs to be provided, without having to specify each individual entity used inside. To achieve this, at the beginning of the subflow, I have a function that constructs all the necessary entity IDs for the subflow and adds them to the message (msg). As I learned from you, I can then use these directly, for example in the current-state node, using {{temperature}}. However, for something like heatmode, the subflow needs to start "state listening" for msg.heatmode, which is executed every time the heat mode is selected. Unfortunately, as you pointed out, trigger-state or state-changed nodes don't use entity_id from the message (msg). Therefore, the only option at the moment is to use ${heatmode} from the environment, which would require an additional parameter. I've found a workaround solution, and I can share it later when I'm back at my PC. |
|
The limitations of using a subflow might add unnecessary complexity here. I suggest using a standard flow instead, starting with the events: state node to monitor all rooms. Then, in your function node, insert logic at the top to parse the entity_id from the events: state node and extract the room information. From there, you can proceed with the rest of your flow. If you prefer to manage sensor and input IDs using flow context, you could place everything after the events: state node into a subflow, leaving the events: state node as the only input.
|
Uh oh!
There was an error while loading. Please reload this page.
Would be nice if the Entity id can be Retrieved from msg or flow parts. I want to make reusable subflows which can be configured from outside by example with the room name a function node can then build all needed Entity id's for example bedroom sensors Entity ids Can be set inside the subflow like this:
At the moment I can only to hand all needed sensors as separated env variables .
All reactions