Bump pysml to 0.0.10

[StephanU]

Proposed change

Bump pysml to 0.0.10 which solves #90651
mtdcr/pysml@0.0.9...0.0.10

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New integration (thank you!)
• New feature (which adds functionality to an existing integration)
• Deprecation (breaking change to happen in the future)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue:
• Link to documentation pull request:

Checklist

• The code change is tested and works locally.
• Local tests pass. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the development checklist
• I have followed the perfect PR recommendations
• The code has been formatted using Black (black --fast homeassistant tests)
• Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated for www.home-assistant.io

If the code communicates with devices, web services, or third-party tools:

• The manifest file has all fields filled out correctly.
  Updated and included derived files by running: python3 -m script.hassfest.
• New or updated dependencies have been added to requirements_all.txt.
  Updated by running python3 -m script.gen_requirements_all.
• For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
• Untested files have been added to .coveragerc.

To help with the load of incoming pull requests:

• I have reviewed two other open pull requests in this repository.

[frenck]

Thanks, @StephanU 👍

../Frenck

[dsteinkopf]

I have a problem after upgrading ha to 2023.4.6 (containing this patch): My edl21 are only "half" working:

• The zabbix integration sends the values correctly to zabbix
• Automations based on these values are working correctly (when value changes -> publish via mqtt)
• The entities show up as "not available"
• The API (../api/states/sensor.my_edl_sensor) returns 500 error

Downgrading to 2023.4.5 solved the problem again.

Does this problem probably have to do anything with this change? If not: Where should I ask or open a new issue?

[dsteinkopf]

P.S. Some logs: https://gist.github.com/dsteinkopf/8689031010c1ee9631c6b85002f2c71b