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

webhook url? #14

Closed
cordvision opened this issue Apr 12, 2023 · 8 comments · Fixed by #15
Closed

webhook url? #14

cordvision opened this issue Apr 12, 2023 · 8 comments · Fixed by #15

Comments

@cordvision
Copy link

According to the documentation: "Once the integration is working, go to System > Logs and find the ttlock webhook url"

Where is this located exactly and what does it look like? If I go to "System > Logs" I can choose from a list: HOME ASSISTANT CORE, SUPERVISOR, HOST, etc.
Where do I find the webhook? I looked through all of those logs and couldn't find anything.

Thanks....
Michael

@jbergler
Copy link
Owner

Settings > System > Logs should have it? The url is /config/logs

From there you can search for ttlock and press the "Load full logs" button

@cordvision
Copy link
Author

cordvision commented Apr 12, 2023

Nothing shows up there relating to webhooks. This is the only entry I find when searching for "ttlock" in the logs:

2023-04-13 00:35:36.393 WARNING (SyncWorker_2) [homeassistant.loader] We found a custom integration ttlock which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant

@jbergler
Copy link
Owner

Interesting, have you actually added the integration after installing it?
If that's the only message in the logs I would guess that you need to go to Settings > Integrations and add TTLock there first

@cordvision
Copy link
Author

Yes, I have added it. I can actually already use it (I can unlock the lock via the Home Assistant Dashboard). However, no unlock events show up in the history at all. I thought this is because I haven't added the webhook url yet. Am I missing something?

@cordvision
Copy link
Author

Here are two screenshots... Am I looking in the wrong place?
Screenshot 2023-04-13 at 03 49 59
Screenshot 2023-04-13 at 03 50 27

@jlmpenedo
Copy link

jlmpenedo commented Apr 13, 2023

I have the same dificult. No webhook url on logs, only this:

_This error originated from a custom integration.

Logger: custom_components.ttlock.api
Source: custom_components/ttlock/api.py:165
Integration: TTLock (documentation, issues)
First occurred: 22:55:36 (3 occurrences)
Last logged: 22:55:39

Failed to lock Fechad M302_abfa15: The function is not supported for this lock."_

I found some information on DEVICE INFORMATION - DOWLOAD DIAGNOSTICS, but it is REDACTED
"webhook_url": "REDACTED"

@jbergler
Copy link
Owner

I guess the default log levels aren't what I thought they were.

I'll release a new version shortly that pops up a notification when the integration starts up if the webhook hasn't received data.

@jbergler
Copy link
Owner

jbergler commented Apr 14, 2023

Thanks for the feedback everyone, hopefully this sorts the issue out for you.

Failed to lock Fechad M302_abfa15: The function is not supported for this lock."

@jlmpenedo If this persists, and you can unlock your lock through the app, please file a new issue

I found some information on DEVICE INFORMATION - DOWLOAD DIAGNOSTICS, but it is REDACTED "webhook_url": "REDACTED"

This is intentional so that if you provide the diagnostic info in a ticket, sensitive info isn't exposed.

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

Successfully merging a pull request may close this issue.

3 participants