jbergler / hass-ttlock

Home Assistant integration for TTLock locks
53 stars 11 forks source link

Problems connecting to HA #104

Closed ManRoumanis closed 4 months ago

ManRoumanis commented 4 months ago

Describe the bug

I set up TTLock integration with HA. It works perfect for 1-2 days. After that it fails to setup or needs more time. After 2-3 more days fails continuisly. I have to delete the integration and start over . At the moment i have delete and reintall the integration 4 times.

To Reproduce

Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Expected behavior

A clear and concise description of what you expected to happen.

Diagnostic info

Please download the diagnostic info for tttlock from within Home Assistant and attach it to this ticket. There are instructions on how to do this here

Mahalov24 commented 4 months ago

https://euopen.ttlock.com/manager/ API calls this month max 5000 Home assistant -> setting -> TTlock -> three dots -> System options -> Disble polling for updates!!!

(If Home Assistant should automatically poll TTLock entities for updates.)

ManRoumanis commented 4 months ago

Thank you very much. I changed the settings and inform you later if the problem is solved.

jbergler commented 4 months ago

How many locks do you have in your account? The 5000 requests/month limit isn't documented by ttlock, so this is news to me (but I only have a single lock)

Currently we poll for updates every 15minutes, which equates to approximately 2 requests per lock per update interval. With 8 locks that would use up 5000 requests in approximately 3 days.

Mahalov24 commented 4 months ago

I was wrong Basic Monthly max API calls:300000 Max number of App:3 Price:Free

https://euopen.ttlock.com/user/information

Снимок экрана 2024-03-14 в 01 45 49
jbergler commented 4 months ago

I'm going to close this since it doesn't have the neccesary info to debug. Please enable debug logs for the integration and reproduce the issue. The debug logging will be required to understand the behavior.

I'm happy to re-open the issue if the necessary logs are attached.