search

fjs21 / homebridge-kumo

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

Kumo API: error parsing json. undefined #62

Closed chrisbrummel closed 2 years ago

chrisbrummel commented 2 years ago

Hi! Everything looks straightforward — I put in my credentials through the Homebridge settings dialog for "Homebridge Kumo" and hit save. Here's the errors I'm getting:

Kumo API: error parsing json. undefined [08/06/2022, 09:18:16] [Kumo] Failed to login. Will retry in 10 secs. [08/06/2022, 09:18:26] [Kumo] Kumo API: error - FetchError: request to https://geo-c.kumocloud.com/login failed, reason: getaddrinfo EAI_AGAIN geo-c.kumocloud.com at ClientRequest.<anonymous> (file:///usr/local/lib/node_modules/homebridge-kumo/node_modules/node-fetch/src/index.js:108:11) at ClientRequest.emit (node:events:402:35) at TLSSocket.socketErrorListener (node:_http_client:447:9) at TLSSocket.emit (node:events:390:28) at emitErrorNT (node:internal/streams/destroy:157:8) at emitErrorCloseNT (node:internal/streams/destroy:122:3) at processTicksAndRejections (node:internal/process/task_queues:83:21) { type: 'system', errno: 'EAI_AGAIN', code: 'EAI_AGAIN', erroredSysCall: 'getaddrinfo' }

I've triple-checked my credentials and they seem good. Is there something I should change?

Thanks!

fjs21 commented 2 years ago

I'm not seeing any issues over here. I'm not sure how to trouble shoot this error message. A very quick Google suggested it might point to a DNS issue. Are you using a proxy server?

chrisbrummel commented 2 years ago

I am not, just a Raspberry Pi. Is there anything else that I could show on my end that may help you? Thanks for looking!

jasongin commented 2 years ago

I saw this just today, after restarting homebridge. The Kumo plugin was working fine before I restarted.

I added some diagnostic code to the plugin and found the request to https://geo-c.kumocloud.com/login returned:

503 Service Unavailable: Back-end server is at capacity.

So, this is obviously a problem with the Kumo cloud service.