Hey @pb_123, thank you for your very detailed report! I’m so sorry this happened to you and can understand that this is worrying.
Your theory was right, the socket used for AbleNet was configured to automatically re-transmit dropped commands when another host re-connects, which caused the flood of messages to your B machine.
Using a static IP address for both computers should fix this issue, but I also just released AbleSet 3.1.5 which disables this re-transmission feature.
The update also changes how the UUID deduplication works. In previous versions, UUIDs were deduplicated for a maximum time span of 2 seconds which was usually more than enough for making sure each command would only be executed once but which didn’t cover the situation you experienced.
The deduplication now keeps a list of the last 512 used UUIDs independently of when they were first received.
That’s an interesting question. My guess is that mDNS which AbleSet uses to discover other hosts on the network didn’t catch the IP address change. These mDNS records have a TTL of 75 minutes which roughly aligns with the time it took to reconnect.
I hope this helps. Please let me know if you have any further questions or feedback!