Description
If you stop an external driver via the the REST API (PUT /intg/drivers/{driverId}), wait for the remote to go into standby and then exit standby mode the driver is not in idle status anymore and tries to reconnect.
I'm not sure if this is a bug or the expected behaviour. Otherwise this can be converted into a feature request.
How to Reproduce
- Stop an external driver via the REST API (PUT /intg/drivers/{driverId})
- Wait for the remote to enter standby mode
- Exit standby mode
Expected behavior
All stopped drivers should have the same status before the remote has entered standby mode.
Your Environment
- Version used: 1.7.7
- Running on:
Additional context
I personally use the start and stop command for test versions of my integrations that are not running 24/7. When the driver is not in idle mode the remote constantly tries to reconnect to the integration and I need to delete the driver configuration to stop this.
Description
If you stop an external driver via the the REST API (PUT /intg/drivers/{driverId}), wait for the remote to go into standby and then exit standby mode the driver is not in idle status anymore and tries to reconnect.
I'm not sure if this is a bug or the expected behaviour. Otherwise this can be converted into a feature request.
How to Reproduce
Expected behavior
All stopped drivers should have the same status before the remote has entered standby mode.
Your Environment
Additional context
I personally use the start and stop command for test versions of my integrations that are not running 24/7. When the driver is not in idle mode the remote constantly tries to reconnect to the integration and I need to delete the driver configuration to stop this.