actions do not work with topic filter != ""

[RSWilli]

actions don't do anything, when a topicfilter has been set

although you can choose the item to update, it wont actually update the item

without the topicfilter, the target thing will update all items to the value given to action, which is undesired in my opinion

[flic]

Not sure I understand what you mean. Can you show me an example of what you're trying to do?

[RSWilli]

I have a thermostat thing type and 5 thermostat things, each with a different id as attribute

I have set the topic filter for each of the items: battery, temp and target

I now want to set each of the items somehow and I figured I'd do it via the action node, where I can select an item and set a value either from payload or directly

but the action doesn't actually update the item, when a topicfilter is set

when I remove the topicfilter, all items get updated, not just the temp item

[flic]

Oh, okay, I see.

My thinking here is that a Thing represents a physical device. The input should be coming from the device, and the output should be sent out to the device. A command is supposed to be sent from the Thing to the device, hopefully result in a status change, which the device would then send out to be received by the Thing input, and thus update the Item value.

I realized fairly recently that there are scenarios where you'd want to create a virtual thing, for example a thing representing a scene, and so I added the option to loopback the command. It's pretty much a virtual wire connecting the Thing output to the Thing input, nothing more. As such, the command payload and topic must be formatted in a way that the input understands and accepts.

Try this:

I'm considering making it possible to update an item value directly, which I think is what you'd like to do, but it would break the concept of the Thing being a virtual representation of a physical device so I'm not sure. Still thinking about it.

[flic]

I made some changes in v1.8.0 that might be closer to what you want.

The value node can both get and set item values now. The item state is set directly without passing through any topic filters or ingress functions.