masaccio / ha-kingspan-watchman-sensit

Kingspan Connect Sensor integration for Home Assistant
MIT License
9 stars 0 forks source link

Integration breaks after installing HA 2023.11 #10

Closed natkins76 closed 9 months ago

natkins76 commented 9 months ago

Since updating to HA Core 2023.11.0, the integration fails to load (I'm using version 1.6.1 of this integration and can't see any newer versions or betas). In the logs, the following errors are shown:

2023-11-01 21:10:13.933 ERROR (SyncWorker_9) [homeassistant.util.package] Unable to install package kingspan-connect-sensor==3.0.0: ERROR: Cannot install kingspan-connect-sensor==3.0.0 because these package versions have conflicting dependencies. ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts 2023-11-01 21:10:19.367 ERROR (SyncWorker_9) [homeassistant.util.package] Unable to install package kingspan-connect-sensor==3.0.0: ERROR: Cannot install kingspan-connect-sensor==3.0.0 because these package versions have conflicting dependencies. ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts 2023-11-01 21:10:24.792 ERROR (SyncWorker_9) [homeassistant.util.package] Unable to install package kingspan-connect-sensor==3.0.0: ERROR: Cannot install kingspan-connect-sensor==3.0.0 because these package versions have conflicting dependencies. ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts 2023-11-01 21:10:24.794 ERROR (MainThread) [homeassistant.setup] Setup failed for custom integration kingspan_watchman_sensit: Requirements for kingspan_watchman_sensit not found: ['kingspan-connect-sensor==3.0.0'].

vintner123 commented 9 months ago

yes, mine has stopped working too, same errors recorded in logs.

masaccio commented 9 months ago

Looks like there might be more of these as aiohttp heads towards an official 4.x release. But fixed in v1.6.2.

Chris-tpt commented 9 months ago

Thanks for the quick response - this was broken for me too but this update has now resolved it.