Add ability to force a hub to send the payload

[hashworks]

When msg.payload.forceSend is set the hub will not determine if the state of the node changed, forcing a send regardless of it.

This is useful when the actual state of the device changes without knowledge of the hub.

[datech]

Hello, @hashworks.

Thanks for your contribution. I want to sheet some light on state change limitation. It was intentionally created to prevent infinite loops if hub output is used as input.

I was thinking to revise the list of input options to:
No
Process
Process and output
Process and output on state change

Would it be helpful for your cases?

[hashworks]

Since I've no inputs that could fire twice (or create infinite loops), yes. If one needs both input options one could always create two hubs.

[datech]

Ok, I will add it in v0.1.10

[Barabba11]

How is useful to have 2 hubs? Does not has sense to drag 2 hubs on flow? Thanks

[hashworks]

How is useful to have 2 hubs? Does not has sense to drag 2 hubs on flow? Thanks

This is only useful if you need different input settings for specific nodes. Then you need one hub with Process and output and one hub with Process and output on state change.