Added the same filter for undefined actions as in the Ikea remote to the Ikea V2 remote. Behavior should be the same, just with the output handler.
I tested it, and the normal use case still works - however, I could not reproduce the issue you showed me in the logs.
@Dirnei According to your logs these messages come all at the same time - would this not result in multiple messages if lets say:
One time the action is filled.
One time the click is filled.
One time both are empty.
If all three events are published for the same click, the node would send two clicks.
Should we not just ignore everything where the action is not filled?
Added the same filter for undefined actions as in the Ikea remote to the Ikea V2 remote. Behavior should be the same, just with the output handler. I tested it, and the normal use case still works - however, I could not reproduce the issue you showed me in the logs.
@Dirnei According to your logs these messages come all at the same time - would this not result in multiple messages if lets say:
If all three events are published for the same click, the node would send two clicks. Should we not just ignore everything where the action is not filled?