Closed SecKatie closed 2 years ago
This is super weird... have you updated to the latest release? @LordNex
version | core-2021.5.0 |
---|---|
installation_type | Home Assistant OS |
dev | false |
hassio | true |
docker | true |
virtualenv | false |
python_version | 3.8.9 |
os_name | Linux |
os_version | 5.4.109 |
arch | x86_64 |
timezone | America/Chicago |
My internet has been acting up. On a 150gig a month cap until skylink gets here in a few months. So a lot of those errors are because of crappy internet connection. But this was occurring the other day before my wife binged watched my bandwidth away
If there is anything that changes the packet it will fail signature validation and that might be what is causing it to be unavailable.
That would certainly explain the difference between the lock and the rest of the devices because they do not have a signing mechanism
@LordNex have you tested this recently? It seems to only affect you.
Not not as of yet. We're on vacation up in Wyoming at the moment and ever since the last HACS update, I get page could not be loaded when trying to access HACS. As soon as I get home and can make some tweaks I'll test again and let you know. Thanks again!
Just to add to this. I would suspect that latency could break the signing for the locks as well, since the timestamp is included in the signature... If you have latency spikes that push the timestamp on the api's end to a different value than yours was during generation... You could very likely just be failing their signature check resultng I'm an error code.
@LordNex do you have an update on this?
Just updated to the latest release (2021.9.6b2) and had this happen to me as well. On the latest version of HA (2021.9.7) and no matter what I do only the lock comes back unavailable. Tried reloading the integration, disable/reenable, restart HA. Always comes back unavailable.
Rebooted my computer and issue was still there. Downgraded to 2021.9.5 and the lock came back. If you need me to run tests to gather logs/etc. just let me know.
I also upgraded to 2021.9.6b2 and lost my connection to my lock. I rolled back and it reappeared. Haven’t had time to investigate but maybe this weekend.
On Sep 23, 2021, at 10:17 AM, kdoh82 @.***> wrote:
Rebooted my computer and issue was still there. Downgraded to 2021.9.5 and the lock came back. If you need me to run tests to gather logs/etc. just let me know.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/JoshuaMulliken/ha-wyzeapi/issues/152#issuecomment-926005616, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAGVNVD4TSJ4TWDET4CIFIDUDNOLNANCNFSM44A6TULQ. Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
Yeah, that is a beta release and it might be related to the keypad. @kdoh82 @terrycarlin do yall have keypads?
no just a lock. no keybap
On Thu, Sep 23, 2021 at 4:30 PM Joshua Mulliken @.***> wrote:
Yeah, that is a beta release and it might be related to the keypad. @kdoh82 https://github.com/kdoh82 @terrycarlin https://github.com/terrycarlin do yall have keypads?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/JoshuaMulliken/ha-wyzeapi/issues/152#issuecomment-926131082, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOPJRXOKIMF3TAZIHARODHLUDOE4RANCNFSM44A6TULQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
Also, I didn’t see any battery data for any of my battery operated Wyze devices in HA. Did a grep battery on the sources of the custom_component and the API library and only found references to battery in the lock code. But I haven’t been able to look any further.
On Sep 23, 2021, at 1:35 PM, kdoh82 @.***> wrote:
no just a lock. no keybap
On Thu, Sep 23, 2021 at 4:30 PM Joshua Mulliken @.***> wrote:
Yeah, that is a beta release and it might be related to the keypad. @kdoh82 https://github.com/kdoh82 @terrycarlin https://github.com/terrycarlin do yall have keypads?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/JoshuaMulliken/ha-wyzeapi/issues/152#issuecomment-926131082, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOPJRXOKIMF3TAZIHARODHLUDOE4RANCNFSM44A6TULQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/JoshuaMulliken/ha-wyzeapi/issues/152#issuecomment-926134269, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAGVNVDXEVNLRU2J5JVTPALUDOFRJANCNFSM44A6TULQ. Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
@kdoh82 @terrycarlin Try the latest beta. It is working for me! Thanks to @yoinx
yes working for me too now. thanks! is there any way we can get the battery level to show up as a sensor in the battery class that way the icon automatically updates depending on the level? i guess i can create my own battery class sensor and set the state to be the attribute value of the battery as well correct?
Here's what I did to get a custom battery sensor using the value from the lock attribute that way the icon automatically updates on lovelace with the right percentage of battery.
# Custom Front Door Lock Battery Percentage Sensor from Wyze Lock Attribute - 'lock battery'
- platform: template
sensors:
front_lock_battery:
device_class: battery
friendly_name: Front Lock Battery
unit_of_measurement: "%"
value_template: "{{ state_attr('lock.front_door', 'lock battery') | replace('%', '') }}"
@kdoh82 That's awesome! Would you mind sharing this in the discussion forums as a show and tell?
Just shared it over there under the Lock Battery Status post.
Not here. Still same issues. All the cams come up as valid sensors and trigger normally. But the lock still just comes up "Unavailable". I'm running inside a VMWare host if that matters. I've talked the entire instance of HA down, but i haven't rebooted the ESXi Host itself yet. Although I shouldn't need too.
Originally posted by @LordNex in https://github.com/JoshuaMulliken/ha-wyzeapi/issues/149#issuecomment-831208836