Configurable ack timeout

[Anticimex]

Creating a new topic for this as I suspect my post in the ACK thread isn't monitored as the thread is marked "fixed".

MySensors use a mesh type network. This means that the delay for a message to pass through the network depend on the number of hops the message need to make to reach the destination. Currently, the timeout for ACK is too short for networks where the node is farther away than one hop. The timeout is also too short to support signed messages with only one hop because there is a handshaking mechanism involved for signed messages.
The best solution for this would be, in my opinion, that the dialog where ACK is configured (per node) in domoticz, also provide a field where the acceptable timeout for an ACK can be entered (in ms or s). That way, the timeout can be optimized depending on node position and capabilities.

[Anticimex]

No feedback on this?
Could I at least get a 'yes we will look into this at some point' or 'no, we are not going to change the ack timeout'?

[alexsh1]

No feedback on this?
Could I at least get a 'yes we will look into this at some point' or 'no, we are not going to change the ack timeout'?

I'd suggest you post the same or ask Moderators to move it to the "Suggestions" section of this forum.

[Anticimex]

Well, I consider this a bug in Domoticz since it is by definition not supporting MySensors if it cannot accommodate the requirements of the protocol. And having a static value for ack timeout is not within MySensors specifications. So I do not consider this a "suggestion". It is a requirement for MySensors compliance.

[gizmocuz]

It is a feature.....

So i kindly suggest to "kindly" add an issue on github/domoticz requesting this feature so we can assign it

for now, why not modify the code, it is not that hard:

Code: Select all

bool MySensorsBase::SendNodeSetCommand

[Anticimex]

Issue #663 filed