yenoiwesa / homebridge-daikin-airbase

A Homebridge plugin for the Daikin Airbase WiFi module
Apache License 2.0
21 stars 4 forks source link

Warning from HB #42

Open cemilbrowne opened 2 years ago

cemilbrowne commented 2 years ago

HB-DA now generates a warning from HB:


[3/31/2022, 12:34:49 PM] [homebridge-daikin-airbase] This plugin slows down Homebridge. The read handler for the characteristic 'On' didn't respond at all!. Please check that you properly call the callback! See https://git.io/JtMGR for more info.
[3/31/2022, 12:34:49 PM] [homebridge-daikin-airbase] This plugin slows down Homebridge. The read handler for the characteristic 'On' didn't respond at all!. Please check that you properly call the callback! See https://git.io/JtMGR for more info.```
yenoiwesa commented 2 years ago

The platform always calls the callback method when responding to characteristic read requests, so I am not seeing any problem. Do you have any extra details about when this occurs?

cemilbrowne commented 2 years ago

No more detail - these seem to be scattered through the logs at the moment on 1.4.0. No additional useful context that I can see. Want a screenshot of the logs?

Thanks!

yenoiwesa commented 2 years ago

@cemilbrowne is this still occurring?

yenoiwesa commented 2 years ago

Closing as no response. Feel free to reopen.

cemilbrowne commented 2 years ago

Hi, don’t see these in the logs at the moment. Will reopen if I do. Thanks.

cemilbrowne commented 2 years ago

Just as soon as I thought we were good...

[9/2/2022, 6:59:56 PM] [homebridge-daikin-airbase] This plugin slows down Homebridge. The read handler for the characteristic 'Current Temperature' was slow to respond! See https://homebridge.io/w/JtMGR for more info.

I wonder why...

cemilbrowne commented 2 years ago

@yenoiwesa I don't have privs to reopen issue - but definitely still recurring. Can I help troubleshoot?

yenoiwesa commented 2 years ago

@cemilbrowne I reopened it.

This problem has never occurred to me. The read handler is what interrogates the Airbase module to get the temperature/mode settings. The plugin is entirely stateless and relies on the Airbase for its state (the source of truth). The only way it could be slow to respond is if you have a slow home network, or if the airbase itself is slow to respond.

Have you tried rebooting the Airbase module see if it helps in any way?

cemilbrowne commented 2 years ago

Interesting - is there a way to log the URL called for interrogating state of the airbase? I assume this is just on/off state - if I can test the URL manually, I can see if it occasionally takes a while to respond...

Network should be fast - HB is on a hardwired server, airbase is wifi, but quick (they're sitting right next to an AP for crying out loud!).

I could imagine that maybe the airbase module goes to sleep - or even changes DHCP IP potentially - and that's causing it?

yenoiwesa commented 2 years ago

If you restart homebridge in debug mode (-D) it will log this line that shows you the URL it queries: https://github.com/yenoiwesa/homebridge-daikin-airbase/blob/master/src/airbase-controller.js#L134-L141

I could imagine that maybe the airbase module goes to sleep - or even changes DHCP IP potentially - and that's causing it?

Potentially but then it's weird that this would not happen to other users 🤔

cemilbrowne commented 2 years ago

OK; I've got the URL now - I'll set up a running curl every few seconds to test it.

For others who might want to test:


ret=OK,pow=0,mode=1,operate=1,bk_auto=2,stemp=23,dt1=23,dt2=20,f_rate=3,dfr1=3,dfr2=3,f_airside=0,airside1=0,airside2=0,f_auto=1,auto1=1,auto2=1,f_dir=0,dfd1=0,dfd2=0,filter_sign_info=1,cent=0,en_cent=0,remo=2
curl http://x.x.x.x/skyfi/aircon/get_control_info  0.00s user 0.00s system 4% cpu 0.143 total```
yenoiwesa commented 2 years ago

@cemilbrowne any update on the curl you setup to monitor the successful/failed connections to the Airbase?

manningoz commented 1 year ago

I am getting the same error now.

[homebridge-daikin-airbase] This plugin slows down Homebridge. The read handler for the characteristic 'On' was slow to respond! See https:/ /ho mebridge.io/w/JtMGR for more info.

teh-hippo commented 1 year ago

I have had this issue fairly frequently too. I've switched HomeKit to run in debug so I can try and capture anything else. It's likely to be a slow response from the unit itself.