ronengr / hass_nuki_bt

Control Nuki Lock over bluetooth
MIT License
39 stars 8 forks source link

Stopped working with Homeassistant 2023.12.3 #33

Closed scho0ck closed 11 months ago

scho0ck commented 11 months ago

System Health details

System Information

version core-2023.12.3
installation_type Home Assistant OS
dev false
hassio true
docker true
user root
virtualenv false
python_version 3.11.6
os_name Linux
os_version 6.1.63-haos
arch x86_64
timezone Europe/Berlin
config_dir /config
Home Assistant Community Store GitHub API | ok -- | -- GitHub Content | ok GitHub Web | ok GitHub API Calls Remaining | 4767 Installed Version | 1.33.0 Stage | running Available Repositories | 1350 Downloaded Repositories | 27
Home Assistant Cloud logged_in | false -- | -- can_reach_cert_server | ok can_reach_cloud_auth | ok can_reach_cloud | ok
Home Assistant Supervisor host_os | Home Assistant OS 11.2 -- | -- update_channel | stable supervisor_version | supervisor-2023.11.6 agent_version | 1.6.0 docker_version | 24.0.7 disk_total | 39.6 GB disk_used | 15.4 GB healthy | true supported | true board | ova supervisor_api | ok version_api | ok installed_addons | Advanced SSH & Web Terminal (17.0.0), ESPHome (2023.11.6), MariaDB (2.6.1), Mosquitto broker (6.4.0), Studio Code Server (5.14.2), Zigbee2MQTT (1.34.0-1), Crowdsec (1.5.4)
Dashboards dashboards | 4 -- | -- resources | 16 views | 21 mode | storage
Recorder oldest_recorder_run | 5 December 2023 at 18:35 -- | -- current_recorder_run | 15 December 2023 at 11:37 estimated_db_size | 1027.55 MiB database_engine | mysql database_version | 10.6.12

Checklist

Describe the issue

Since updating to core-2023.12.3 the integration does not start anymore. Unfortunately the log does not contain any errors even when debug is enabled.

Reproduction steps

  1. Update to 2023.12.03
  2. Restart HA
  3. Integration does not initialise anymore

Debug logs

none

Diagnostics dump

No response

scho0ck commented 11 months ago

Solved it wasn't an issue with the integration but with the bluetooth proxy still surprised it did not show any error but it's working again.