Closed FTI76 closed 2 years ago
This is a little hard to diagnose. Do you get any errors when direct connect is off?
This is a little hard to diagnose. Do you get any errors when direct connect is off?
Hi. If you look there are two screenshots. The first are the when direct connect is enabled. The second is when it’s disabled. From what I can tell it’s working alright in spite of these errors. All my automations with the Mitsu devices are working.
What type of device is homebridge running on?
Not really sure what the first issue is as that's usually a username/password issue but it could mean something else too.
The second set of errors could be due to slow response from the API which might be due to slow/weak network connection which then causes a timeout in HomeKit.
If you want to delve deeper, turn on debugging in the Homebridge UI and post the results - preferably as text rather than screenshots. Thanks
HomeBridge is running on Libuntu VM with 4 CPUs and 3GB of Memory and Bridged Gigabit. 2.9xGB is generally free. All three of the Mitsu Wifi Units show Full Connection strength to my Eero network and the credentials for Kumo Cloud are working alright. Things seems to be working fine is spite of the errors so if you want to close this that's fine, or if you want me to collect any other debug logs I can do that also. Overall I am very happy with this plugin, so thanks for your efforts.
i’ve encountered errors with direct connection and via the api.
i’ve put the Kumo plug-in on its own bridge and i’m not noticing any performance issues. plug-in appears to be functional.