ds485_client_query_link has a builtin timeout of 2s. That means, if the server does not respond within 2s, ds485p will assume the server is disconnected and disable all dsm in turn. Together with the reduction of the interval from 30s to 1s, this happens much more often now. see #16230, especially on dss11e. it happens more often. We could tune the timeouts in ds485-client, but likely they have been set that low for some reason, (git blame revealed an unrelated commit). In fact, we don't need the state. We are only interested in dsms. The ds485d already disables all dsms if the it loses the ds485 token, which is the same logic we re-implement in ds485p. On top, the ds485-client library will emit 'link changed' callback if any timeout expires. Since we query all dsms regularly(180s) we still will get the link changed callback. The ds485d has 10s to answer query devices request, which is better than the 2s timeout of query state. Hence, simply dropping that check seems that least invasive change. #16230
Signed-off-by: Andreas Fenkart andreas.fenkart@digitalstrom.com