Stopping the docker container in Hass.io doesn't put sensors as unavailable

Describe the bug Shutting down the docker container (Hass.io) doesn’t put monitored Classic Bluetooth devices as unavailable (maybe others too). Note: I only have 1 instance.

To reproduce

1. Install the addon
2. Configure some classic BT devices
3. verify that they appear in HA’s dev-state
4. stop the container

Relevant logs N/A

Relevant configuration Paste the relevant parts of your configuration below.

global:
  instanceName: Office
  integrations:
    - homeAssistant
    - bluetoothClassic
homeAssistant:
  mqttUrl: 'mqtts://xxxxxxxx'
  mqttOptions:
    username: xxxxxxxx
    password: xxxxxxxx
bluetoothClassic:
  hciDeviceId: 0
  minRssi: -20
  interval: 6
  addresses:
    - 'xx:xx:xx:xx:xx:xx'

Expected behavior Putting sensors as unavailable when the last instance is down or when there where no updates for some time (ideally configurable).

This would help secure the solution a bit, especially if the app crashes.

Environment

• room-assistant version: [e.g. 2.0.0] 2.4.0
• installation type: [e.g. NodeJS, Docker, Hass.io]: Hass.io
• hardware: [e.g. Raspberry Pi Zero W, NUC]: NUC
• OS: [e.g. Linux, Windows, macOS]: Linux

Additional context Add any other context about the problem here.

[mKeRix]

Do you think that utilizing the expire_after attribute of MQTT sensors in Home Assistant would also be an ok solution for you? If we set that from the room-assistant side and let the leader re-post the states as a heartbeat every x seconds we could ensure that the distributed sensors also go unavailable if room-assistant is turned off, room-assistant crashes or MQTT goes down.

[github-actions[bot]]

🎉 This issue has been resolved in version 2.18.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀