Issue #663 filed

Hi, yes, I have noticed the same thing. This in combination with the fact that a node can be several hops away, strongly motivates a setting to make ACK timeout longer or at least configurable. I have filed a issue on the github page for this. Hopefully, it will be included in future releases ...

It could be. I'm not sure. The node does send ACK but domoticz has a too short timeout for the ACK to arrive. On the communication channel, the ACK is sent to domoticz before domoticz sends the second message but I am not sure of the order "inside" domoticz. I have a different thread where I have ...

I notice that when I enable Ack for a node, Domoticz sends commands to that node twice. Is this intentional? If I disable ACK in Domoticz for the node (the child representing my actuator) Domoticz just sends one command as intended. But with ACK "on" it sends the command two times in rapid ...

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 ...

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'?

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 ...

Hello again, any update on this? It is really important for MySensors compatibility that controllers can handle secured nodes as well. And in this case, the issue also affects relayed nodes who take longer time to respond based on the number of hops in the mesh network. I am not asking for this to ...

what is the maximum delay you expect ? as i remember, i have read somewhere normally it was arround 100ms (for normal sensors) Well, the nonce timeout default setting in the MySensors library I believe is 5s so I think it should be at least that (although any MySensors user can reduce/increase it ...

It is not as fast for secured nodes because a nonce needs to be exchanged beforehand. So no, 1.2 seconds is not enough in this case. Also, depending on the number of repeaters in the mesh network, delay could be arbitrary so I really think a timeout needs to be configurable.

gizmocuz wrote:that you should ask on the mysensors forum

@gizmocuz
Ok, I have made a post in the MySensors forum as well. Same question, in the domoticz thread there. We can continue the discussion there if you prefer.

Sent from my D5803 using Tapatalk

Domosapiens wrote:Useless information detection:

Sent from my D5803 using Tapatalk

Who cares?

Domosapiens

Automatic signature from my app. Problem?

Sent from my D5803 using Tapatalk

that you should ask on the mysensors forum Hm, ok. But my question has nothing to do with the MySensors library, it is very domoticz specific. Do you have some topic on the MySensors forum this should be posted in if you still think it should be discussed in that context? Sent from my D5803 using ...

Hi, I am trying to use a secured node (that require signed messages) and it seem the ack timeout is too short for the signing handshaking to finish in time. Is there a way of increasing/specifying the acceptable timeout for an ACK to arrive? It would also be great if that timeout was then ...