`port.disconnected` fails to trigger properly.

[harry-xi]

What Happend

When I physically remove the device, I expect this event to be triggered, but it doesn't—nothing is sent.
Additionally, when I manually close the serial port using close(), it also fails to trigger.

Addition Infomation

Another noteworthy phenomenon is that after opening the serial port and removing the device, executing SerialPort.available_ports() yields the following result: it incorrectly retains the device that has been physically disconnected. When I manually close the serial port and execute SerialPort.available_ports() again, I get the expected result: the device is no longer listed in the serial port list.

the resute of SerialPort.available_ports() after physically removed

the resute of SerialPort.available_ports() when connected normally

[s00d]

Hi, try version 2.21.0.

I’ve added event handling to the disable logic.
As for the second error - I can’t say exactly what’s causing it. I’m using the Rust serialport library, and if you’re seeing this issue, it’s likely a problem within that library.
I’ve updated it to the latest version - hopefully, that helps.

[harry-xi]

The event triggering for the close() method now functions correctly. The remaining issues persist (including connections failing to disconnect automatically when the device is physically removed). Nevertheless, thank you very much for your assistance.