Update LoqedAPI to handle invalid transitions better

[mikewoudenberg]

Proposed change

Updated the LoqedAPI companion library which handles invalid transitions better

cpolhout/loqedAPI@v2.1.7...v2.1.8

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 issue: fixes Loqed: Lock keeps a wrong state when calling a service to the current state #99384

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]

I don't see any releases on GitHub. Would be nice if the upstream package did that, so we can compare changes and see diffs.

../Frenck

[mikewoudenberg]

I don't see any releases on GitHub. Would be nice if the upstream package did that, so we can compare changes and see diffs.

../Frenck

I added releases and updated the PR

[frenck]

I added releases and updated the PR

They don't show up. Something went wrong?

../Frenck

[mikewoudenberg]

I added releases and updated the PR

They don't show up. Something went wrong?

../Frenck

I fiddled around with the release thing a bit more and I see them:

[frenck]

Aah looks like a caching thing @ GitHub or something. If I enter the URLs they are indeed there.

Ok, thanks! 👍

[frenck]

Thanks, @mikewoudenberg 👍

../Frenck