Before this change, terminate! would get called with nil from reset-local-device!. So get-local-device would grab the first device it found instead of the intended one.
I found this when an MSTP device was getting reset by the creation of another (IP) device. The reset was not pretty and it threw an error down in the serial implementation.
Before this change, terminate! would get called with nil from reset-local-device!. So get-local-device would grab the first device it found instead of the intended one.
I found this when an MSTP device was getting reset by the creation of another (IP) device. The reset was not pretty and it threw an error down in the serial implementation.
That itself might also be a separate issue...