Bump openwebifpy to 4.2.7

[autinerd]

Proposed change

This bumps openwebifpy to 4.2.7.

https://github.com/autinerd/openwebifpy/releases/tag/4.2.6
https://github.com/autinerd/openwebifpy/releases/tag/4.2.7

It would be good if this could be added to a minor release.

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 Enigma2 dead after 2024.08 update #123345
• 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 Ruff (ruff format 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.

To help with the load of incoming pull requests:

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

[TheJulianJES]

Did you confirm the new code fixes the issue?
if len(result["events"]) would throw the same error when the events key isn't included, right? You're still trying to access result["events"]) that caused the issue in the first place.

If result["events"] would exist, but be empty, the previous code should already have worked. It would already return an empty dictionary then, as there's nothing to loop through. I don't think the added code fixes an actual issue.

Looking at trace in issue #123345, I think you'd have to check that the "events" key exists: "events" in result OR result.get("events") to fall-back to None (and adjust the rest of your code accordingly).

[autinerd]

Thank you, you are right. I have added the checks, so that now everything should be catched.