Skip to content
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

Yale home with Unity Locks #125001

Open
shsurury opened this issue Sep 1, 2024 · 14 comments
Open

Yale home with Unity Locks #125001

shsurury opened this issue Sep 1, 2024 · 14 comments

Comments

@shsurury
Copy link

shsurury commented Sep 1, 2024

The problem

The new Yale integration is functioning well and is quite fast, but I’ve noticed a bug. I have both the Unity Front Door Lock and the Unity Security Screen Door Lock, and they are linked together. The issue is that when you lock or unlock one of these locks, the other one follows suit, but the status of the second lock isn’t updated in Home Assistant. To refresh the status, you have to open the Yale Home app and check the associated lock. As a result, even if both locks are actually in the same state, one may show as locked while the other shows as unlocked.

What version of Home Assistant Core has the issue?

core-2024.9.0b2

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Yale Home

Link to integration documentation on our website

No response

Diagnostics information

home-assistant_yale_2024-09-01T02-44-42.423Z.log

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

@bdraco
Copy link
Member

bdraco commented Sep 1, 2024

It looks like the websocket isn't connected for some reason

2024-08-31 18:48:03.893 ERROR (MainThread) [engineio.client] packet queue is empty, aborting

@bdraco
Copy link
Member

bdraco commented Sep 1, 2024

2024-09-01 12:42:24.755 DEBUG (MainThread) [yalexs.manager.activity] Push updates are not connected, data will be stale

@bdraco
Copy link
Member

bdraco commented Sep 1, 2024

Please add the following to configuration.yaml, restart and provide a new log so we can figure out why the websocket won't connect

logger:
  default: info
  logs:
    socketio: debug
    engineio: debug
    yalexs: debug
    homeassistant.components.yale: debug

https://www.home-assistant.io/integrations/logger/

@shsurury
Copy link
Author

shsurury commented Sep 1, 2024

home-assistant_yale_2024-09-01T03-23-03.449Z.log
Please see attached log file after adding the above to configuration.yaml and restarting

@bdraco
Copy link
Member

bdraco commented Sep 1, 2024

Everything with yale looks correct with that log now. It seems the restart fixed whatever was wrong. Please leave debug logging on and post a new log if it stop updating.

@shsurury
Copy link
Author

shsurury commented Sep 1, 2024

home-assistant_yale_2024-09-01T04-07-24.405Z.log
Hello @bdraco, I have reattached the log again. I have opened the Unity Security Screen Door lock and as it is linked to the Front door lock the front door also opened automatically howevert in homeassistant the screen door says open but the front door says locked.
image
image

Note: This is not an issue when using the August intigration

@home-assistant
Copy link

home-assistant bot commented Sep 1, 2024

@bdraco
Copy link
Member

bdraco commented Sep 1, 2024

It looks like its possible to add support for the linked_unlock and linked_lock actions.

They aren't supported by the underlying library currently
https://github.com/bdraco/yalexs/blob/main/yalexs/activity.py#L13

@bdraco
Copy link
Member

bdraco commented Sep 1, 2024

Would you please open a feature request to add support for the linked locking actions at https://github.com/bdraco/yalexs/issues/new

@bdraco
Copy link
Member

bdraco commented Sep 1, 2024

2024-09-01 14:06:40.348 DEBUG (MainThread) [yalexs.api_common] Processing activity: {'id': '0af6bd11-621b-4e32-b0ea-1d13804d31e7', 'timestamp': 1725061953081, 'icon': 'https://d3osa7xy9vsc0q.cloudfront.net/app/ActivityFeedIcons/linked_lock@3x.png', 'action': 'linked_lock', 'deviceID': 'X', 'deviceType': 'lock', 'title': '<b>Front Door</b> locked by linked operation.'}

2024-09-01 14:06:40.348 DEBUG (MainThread) [yalexs.api_common] Unknown activity: {'id': '74b5a4b6-8c89-4aac-8eb5-38b0350f4164', 'timestamp': 1725062446640, 'icon': 'https://d3osa7xy9vsc0q.cloudfront.net/app/ActivityFeedIcons/linked_unlock@3x.png', 'action': 'linked_unlock', 'deviceID': 'x', 'deviceType': 'lock', 'title': '<b>Front Door</b> unlocked by linked operation.'}

@bdraco
Copy link
Member

bdraco commented Sep 1, 2024

Note that the yale websocket api doesn't map these yet

2024-09-01 14:06:45.868 DEBUG (MainThread) [yalexs.manager.socketio] message received with {'lockAction': '', 'doorState': '', 'lockID': 'x'}
2024-09-01 14:06:45.875 DEBUG (MainThread) [yalexs.manager.socketio] message received with {'lockAction': '', 'doorState': '', 'lockID': 'x'}

So it may still require a change on the yale side as well but we would need to add support in the yalexs library first.

@shsurury
Copy link
Author

shsurury commented Sep 2, 2024

@bdraco I have oppened a feature request to add support for the linked locking actions as per your request. Thanks for your help.

@bdraco
Copy link
Member

bdraco commented Sep 2, 2024

@bdraco I have oppened a feature request to add support for the linked locking actions as per your request. Thanks for your help.

Thanks!

@bdraco
Copy link
Member

bdraco commented Sep 2, 2024

bdraco/yalexs#175

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants