Closed randallpjenkins closed 2 years ago
I suggest you check your username and password and try rebooting. This error means that the response from the server did not contain a security token and you were unable to connect to the Kumo API.
It was indeed a user/password issue. Seems my password was somehow reset/changed without me knowing which is odd.
Great. Glad you got it working!
It looks like Kumo might be doing something weird with their user auth. I was also experiencing this issue, and ended up trying to replicate the API call locally. Eventually I tried inspecting the login action on app.kumocloud.com, and it turns out the password that it had in the payload is completely different from what I was actually using to log in.
Harvesting the password from the payload of the login action from app.kumocloud.com and using that in Homebridge fixed the issue for me.
Weird. I wonder how would we be able to determine this new password? Also, what subset of users is experiencing this?
Did you try reseting it as @randallpjenkins suggested?
Just tried it. Looks like they're aligned, now. Kumo must be making moves on their backend, while choosing not to invalidate current logins.
Upon Homebridge restart I get: Kumo API: Unable to acquire a security token.
Plugin does not have any control or read/send to units.