Use msg.payload as "value" for actions

[Mahai17]

Hi,
device node works fine, but to use a fixed value for actions is limiting the fun.
I would love to use i.e. msg.payload as input for actions.
Regards Martin

[harwoodr]

You can! For example, I have an accelerometer on a microcontroller that feeds that value to a display on a dial - my "data" field looks like thisL

{"value":$number($entities("sensor.stamp_train_mpu6886_accel_x").state)}

[Mahai17]

I think that does not work for my Huawei Solar Integration. "Just" set the value for an entity does not work, because it does not change the parameter in the inverter. After the next poll from the inverter the value is changed back. There is an action from within the integration to change the attribute, but this action is not exposed to the global actions. It's hard to explain.
So device node is perfect, but forces a fixed value.

[harwoodr]

Sorry - misunderstood - I'm just using the action node, not the device node - it didn't seem to do what I wanted.

[zachowj]

Sorry, the device node in trigger or action mode only accepts static values. You can use the action node for the same purpose as shown above.

[Mahai17]

Maybe I missed something, but no, action node does not work. I want to execute an action which is only available within the context of the device. This specific action is not available (exposed) in the global context.
DevTools doesn't list this action (service) and the so the action node doesn't list this action.
Only the device node list this action.