build(deps): bump pytest-homeassistant-custom-component from 0.13.49 to 0.13.72

[dependabot]

Bumps pytest-homeassistant-custom-component from 0.13.49 to 0.13.72.

Release notes

Sourced from pytest-homeassistant-custom-component's releases.

Release 0.13.72

Automatic release homeassistant version: 2023.11.0b3

Release 0.13.71

Automatic release homeassistant version: 2023.11.0b2

Release 0.13.70

Automatic release homeassistant version: 2023.11.0b1

Release 0.13.69

Automatic release homeassistant version: 2023.11.0b0

Release 0.13.68

Automatic release homeassistant version: 2023.10.5

Release 0.13.67

Automatic release homeassistant version: 2023.10.4

Release 0.13.66

Automatic release homeassistant version: 2023.10.3

Release 0.13.65

Automatic release homeassistant version: 2023.10.2

Release 0.13.64

Automatic release homeassistant version: 2023.10.1

Release 0.13.63

Automatic release homeassistant version: 2023.10.0

Release 0.13.62

Automatic release homeassistant version: 2023.10.0b7

Release 0.13.61

Automatic release homeassistant version: 2023.10.0b6

Release 0.13.60

Automatic release

... (truncated)

Commits

• b876e70 Bump version
• adc92ab Bump version
• 6438062 Bump version
• d40a8cb Bump version
• 6a3631f Bump version
• ee421c0 Bump version
• 89368e7 Bump version
• b9a6260 Bump version
• 135b858 Bump version
• 8bb8a6f Bump version
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[lbbrhzn]

@drc38 I managed to do some fixes for the most recent pytest-homeassistant-custom-component version but the init test still fails. Can you take a look?

[dependabot]

A newer version of pytest-homeassistant-custom-component exists, but since this PR has been edited by someone other than Dependabot I haven't updated it. You'll get a PR for the updated version as normal once this PR is merged.

[drc38]

@lbbrhzn I assume it is something to do with not properly unloading. Not sure why Hass is not taking care of cancelling the poller though? May need to check with a dev on discord as a google search does not provide any answers.

[drc38]

@lbbrhzn tried a few things but no real progress, not sure why the test has the following errors:
ValueError: Config entry has already been setup!

and then on unload

central_sys = hass.data[DOMAIN][entry.entry_id]
                  ~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^
KeyError: 'test_cms1'

I think if they can be solved perhaps the lingering task issue will disappear?!

[lbbrhzn]

I suspect it is due to the mock entries being added to hass, but apparently not removed on unload.

[lbbrhzn]

got it working. manually adding the entry to hass. Don't understand why this is needed though....

[drc38]

got it working. manually adding the entry to hass. Don't understand why this is needed though....

Nice one! It would be handy if there was more documentation around the dev testing change requirements.