You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
some adapter do not handle device/servce connection losses well and need to be restarted in order to get alive again.
For automated instance-supervision, there is no way to determine the state of the adapter when it is
running
connected to host
but not connected to a device or service
for the latter, there is not state available under system.*
Description
How can this status be derived from the available states? If not, please add a specific state for the device/service connectivity. Even better would an option, liek the scheduled restart, where you can specify that the specfici adapter instance should restart itself
if the instance is running and connected to host, but not connected to a device/service (some adapter do not handle connection losses well and need to be restarted)
and the instance is running for a defined grace-period (I use 300s)
Additional context
No response
The text was updated successfully, but these errors were encountered:
The "connected to device or service state" already exists and is named info.connection. It is per instance and created and set by the adapter code. Please note that it's the decision of the adapter if it implements that state and how it handles it.
some adapter do not handle device/servce connection losses well and need to be restarted in order to get alive again.
In this case please open a issue at the adapter repository.
js-controller (and admin even more) does not know whether an adapter has any connection to any "device" and has no possibility to check if a connection is working. Communication with any device is solely done by the adapter code - there's no interaction with js-controller or admin.
No existing issues.
Related problems
some adapter do not handle device/servce connection losses well and need to be restarted in order to get alive again.
For automated instance-supervision, there is no way to determine the state of the adapter when it is
for the latter, there is not state available under system.*
Description
How can this status be derived from the available states? If not, please add a specific state for the device/service connectivity. Even better would an option, liek the scheduled restart, where you can specify that the specfici adapter instance should restart itself
Additional context
No response
The text was updated successfully, but these errors were encountered: