True, but perhaps a workaround would be to specify disconnect-on-timeout — then the @reconnect handler would keep retrying at the specified reply timeout interval. Once the device became available the @reconnect handler would succeed and things would progress as desired.
I think that would be possible. I will have a look. Be aware that not all ports can provide this event. For example asyn may not know when a RS232 cable has been plugged in.