Freddie Leeman

This would help resolve some issues for me too! I would love this as an option, especially to check which AP the client was connected to last (before being unavailable)....

Thank you for taking the time to answer me. I'll give your suggestion a try. I also have Deco M4 units, and a timeout is a likely cause. If this...

Unfortunately, so far, the results are not good:  I've increased to 90, but so far the results are still disappointing. ``` Logger: custom_components.tplink_deco Source: custom_components/tplink_deco/api.py:215 Integration: TP-Link Deco ([documentation](https://github.com/amosyuen/ha-tplink-deco),...

Here is my most recent log entry: ``` Logger: custom_components.tplink_deco Source: custom_components/tplink_deco/api.py:167 Integration: TP-Link Deco (documentation, issues) First occurred: March 14, 2022, 1:01:29 AM (17 occurrences) Last logged: March 14,...

Here is the debug data from the log. It looks like the calls have timeout issues. ``` 2022-03-15 12:01:46 DEBUG (MainThread) [custom_components.tplink_deco] Finished fetching tplink_deco-decos data in 10.638 seconds (success:...

Here are the results: Average: 5.18 seconds Highest: 7.61 seconds Lowest: 3.66 seconds What is the current timeout setting?

No, none.

It looks like the timeouts are gone now. I do see these now: ``` 2022-03-28 14:59:25 ERROR (MainThread) [custom_components.tplink_deco] Unexpected error fetching tplink_deco-clients data: 'result' Traceback (most recent call last):...

Same here; been trying to get coordinates for spot cleaning but `deebot_cleaning_job` is not firing, and `sensor.deebot_last_cleaning` is stuck at `unknown`. Not sure if it is related, but running `getStats`...

I am experiencing the same issue and have been unable to reproduce it.