search

iklein99 / homebridge-smartthings

This is a plugin to Homebridge to connect your Smartthings network into Apple Home Kit.
Apache License 2.0
150 stars 52 forks source link

"This plugin slows down Homebridge" Warning #82

Closed kevinjonsutton closed 1 year ago

kevinjonsutton commented 1 year ago

I just started receiving multiple warnings in my log after the 1.4.14 update. This makes sense because I noticed my homebridge has been working extremely slow since I updated. I tried restarting the plugin to see if the error goes away but it comes back. This warning only started appearing on installation of the current version.

[11/8/2022, 9:02:09 AM] [homebridge-smartthings-ik] This plugin slows down Homebridge. The read handler for the characteristic 'Current Temperature' didn't respond at all!. Please check that you properly call the callback! See https://homebridge.io/w/JtMGR for more info. [11/8/2022, 9:02:09 AM] [homebridge-smartthings-ik] 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://homebridge.io/w/JtMGR for more info. [11/8/2022, 9:02:09 AM] [homebridge-smartthings-ik] This plugin slows down Homebridge. The read handler for the characteristic 'Status Low Battery' didn't respond at all!. Please check that you properly call the callback! See https://homebridge.io/w/JtMGR for more info.

iklein99 commented 1 year ago

Purge your log files, then turn on debug. restart Homebridge and drop the logs on my google drive. You may have to request access.

https://drive.google.com/drive/folders/1xNrYdjVmo1Uvn-GxZuv5Z0rIQJQ7jwgx?usp=share_link

kevinjonsutton commented 1 year ago

Couldn't get access to the Google Drive so I just emailed you the logs.

iklein99 commented 1 year ago

There are a lot of network errors I'm seeing that may indicate a router issue or something that correspond with those messages. I may have introduced an issue that is causing the warning you see, but the underlying issue is a network problem. I think you can ignore the messages, but you may want to look at the logs to see the times where you will see failures (not jut my plugin) and see why that is.