build(deps): bump pytest-homeassistant-custom-component from 0.13.91 to 0.13.108

[dependabot[bot]]

Bumps pytest-homeassistant-custom-component from 0.13.91 to 0.13.108.

Release notes

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

Release 0.13.108

Automatic release homeassistant version: 2024.3.1

Release 0.13.107

Automatic release homeassistant version: 2024.3.0

Release 0.13.106

Automatic release homeassistant version: 2024.3.0b6

Release 0.13.105

Automatic release homeassistant version: 2024.3.0b5

Release 0.13.104

Automatic release homeassistant version: 2024.3.0b3

Release 0.13.103

Automatic release homeassistant version: 2024.2.4

Release 0.13.102

Automatic release homeassistant version: 2024.2.3

Release 0.13.101

Automatic release homeassistant version: 2024.2.2

Release 0.13.100

Automatic release homeassistant version: 2024.2.1

Release 0.13.99

Automatic release homeassistant version: 2024.2.0

Release 0.13.98

Automatic release homeassistant version: 2024.2.0b9

Release 0.13.97

Automatic release homeassistant version: 2024.2.0b8

Release 0.13.96

Automatic release

... (truncated)

Commits

• c9704e2 Bump version
• 2082f44 Bump version
• c5cc6fb Bump version
• 91b4ffb Bump version
• edb9749 Bump version
• 409ab5b Bump version
• 6cec5f6 Bump version
• bc5160c Bump version
• f8600d2 Bump version
• b902bd5 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)

[dependabot[bot]]

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.

[lbbrhzn]

@drc38 any idea why this is failing?

[drc38]

@drc38 any idea why this is failing?

Not sure, but looks like Payload is deprecated in ocpp and needs to be removed

[drc38]

Could try replacing https://github.com/lbbrhzn/ocpp/blob/d0e2da15a3569c6d1c8a57f3cf528df3ffddf83d/custom_components/ocpp/init.py#L93

With

await hass.config_entries.async_forward_entry_setups(entry, PLATFORMS)
entry.async_on_unload(entry.add_update_listener(async_reload_entry))

[lbbrhzn]

Not sure, but looks like Payload is deprecated in ocpp and needs to be removed

A lot of stuff has been made deprecrecated in ocpp 1.0. However, the merge of 1.0 did not result in test failures. The new homeassistant pytest does. It appears the gets stuck somewhere: No errors are reported, but there are some processes lingering in the end.

[drc38]

Another thought, in async_unload_entry the central system is closed but the charge point instance is not. Does it need to be or does the close of the central system take care of it? Perhaps include a __del__() method in the CentralSystem class instead to close websocket, remove chargepoints etc?