search

fjs21 / homebridge-kumo

Control your Kumo cloud devices using Homebridge.
https://www.npmjs.com/package/homebridge-kumo
Apache License 2.0
35 stars 8 forks source link

Potential conflict with homebridge-wemo plugin #42

Closed esetnik closed 2 years ago

esetnik commented 2 years ago

I'm getting the following error after setting up the homebridge-kumo config. Initially I was able to access my ductless via the plugin but after restarting homebridge I repeatedly receive the error that it timed out connecting to kumo cloud. I don't know why this is the case. FWIW the kumo cloud app on my phone is able to login and control my ductless just fine from the same network.

 main  [10/30/2021, 7:37:44 PM] [Kumo] Kumo API: error - Time out on Kumo cloud connection.
 main  [10/30/2021, 7:37:44 PM] [Kumo] Failed to login. Restart Homebridge to try again.
fjs21 commented 2 years ago

This is usually due to a problem with your username and password. The plugin was unable to get a security token. Please check in your config that it is set correctly. Once you have updated your details you will need to restart home bridge for the plugin to try again.

esetnik commented 2 years ago

Username and password are both correct and I can use them to login on app.kumocloud.com. It looks like it could be a duplicate of https://github.com/fjs21/homebridge-kumo/issues/34. Should I attempt the solution from that issue?

fjs21 commented 2 years ago

It does seem to be the same. I'd try the solution posted.

I was never able to replicate the issue so I have not been able to diagnose why it happens to only some users. The time out is set to 5 secs which should be enough unless your connection is very slow/unreliable. I could expose the time out to the user to make it available to set but if it's fixed via placing on a client bridge then great too!

esetnik commented 2 years ago

@fjs21 what's weird is it worked the first time I added this plugin but seems to have stopped working after I also added homebridge-wemo plugin. I wonder if there is some conflict between the two when running on the same bridge.

fjs21 commented 2 years ago

Good theory. If you can test it, I can put a notice on the readme to warn other folks.

esetnik commented 2 years ago

It worked after adding the client bridge. The docs should probably be updated to reflect that this is necessary for some reason.

fjs21 commented 2 years ago

In v1.8.14, I have attempted a fix whereby if a time out occurs on the initial connection to the Kumo API then the plugin will try again after a delay. This will hopefully resolve the issue which appears to be intermittent as I have also recently observed it occur once and then had it resolve itself on a subsequent reboot.