-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue Unlocking/Locking After Newest HA Update #14
Comments
Note: After looking at breaking changes, it might be the upgrade to python 3.9 -> 3.10. |
I also had this problem and it seems to be async_lock and async_unlock should be accepting arguments but currently are not. I made a small change and now the locks are working. I don't know a lot about this system, but I am basing it off this change I saw in the Home Assistant Core repo. --- async def async_lock(self):
+++ async def async_lock(self, **kwargs):
--- async def async_unlock(self):
+++ async def async_unlock(self, **kwargs): |
Hi @Palmer-Pesta! Glad to hear this integration is working out for you! Guess you saw my latest release. Low key I haven't updated my HA instance yet & make sure everything works out there but i'm guessing its all good since the issue is closed! Let me know if theres any other issues in general though Also thanks for the help @tjleach98! |
|
Apologies, I might have too hastefully resolved this issue. It looks like it is now rejecting the |
Please note I made the following changes and the integration works again. |
Since upgrading not only does my lock not work, but it can't even be set up. Please help! Traceback (most recent call last): |
Same issue as above. You can edit the code by control + f to find it in vscode (under custom_components) and remove the |
Sorry ya'll! I just pushed out a new release. Should restore the functionality of the locks. I was able to update my HA instance to latest and test it there too. So the original issue should be fixed as well. Let me know if anything else is goin wrong and I can take a look at things |
Confirmed that these changes worked. Closing the issue now. Thanks for your help, Zach! |
It's no problem! Thanks for the great feedback & helping me test out stuff! |
Sorry for noob question, but I am also having this same issue. Yet I get the following error when triggering lock/unlock from the frontend:
|
@yousefmansy1 after you reinstalled the SmartRent integration have you restarted your Homeassistant instance? |
Yes I have restarted my HA instance. Is there a way to validate the version of the plug in I'm using? |
Im actually not sure if theres a way to view the info reliably with the UI 🤔 But if you have command line access you can output some information that contains the version number for the integration.
|
Yep that looks to be the issue.
So pt2 of noob question, how can I ensure I'm installing the latest version of an integration? |
@yousefmansy1 what normally works for me is when you are on the HACS page for Smartrent is clicking:
If thats not working at all you can delete your Here is some more info about that method: |
I had a major brain fart, I forgot about the HACS store showing its own updates. Thanks! |
haha no problem!! Glad you got everything working out! |
First, I want to say great job on this integration; I use it a lot.
Recently I've hit this stack trace when trying to lock/unlock. Everything else works, and I've tried to uninstall, wipe pvcs, etc.
The text was updated successfully, but these errors were encountered: