Zones sit idle and then time out
Closed this issue · 5 comments
storkpkp commented
The zones appear in Home app just fine, but they cannot be activated. They spin at idle when selected and then time out with no response.
martijndierckx commented
Can you tell me a bit more about your setup?
storkpkp commented
What details do you need from me?
I am running:
iOS 11.4
Homebridge 0.44.4
Homebridge-Hydrawise 0.3
OS X 10.12.6
I have the Hydrawise Pro-C6 Controller with 3 zones. The zones show up fine, but when I try to run one it just says updating for a long time, and then no response.
Marcus
… On Jul 4, 2018, at 6:45 AM, martijndierckx ***@***.***> wrote:
Can you tell me a bit more about your setup?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#2 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/Am2fvJ50QxZDnVc4h4Lhq31c0AeF3nG2ks5uDJzdgaJpZM4U-WwE>.
storkpkp commented
Hey there, I now have it working after generating a new API key, but I keep getting this message in my terminal.
Unhandled rejection RequestError: Error: connect ETIMEDOUT 107.22.252.238:443
at new RequestError (/usr/local/lib/node_modules/homebridge-hydrawise/node_modules/request-promise/lib/errors.js:14:15)
at Request.RP$callback [as _callback] (/usr/local/lib/node_modules/homebridge-hydrawise/node_modules/request-promise/lib/rp.js:60:25)
at self.callback (/usr/local/lib/node_modules/homebridge-hydrawise/node_modules/request/request.js:185:22)
at Request.emit (events.js:127:13)
at Request.onRequestError (/usr/local/lib/node_modules/homebridge-hydrawise/node_modules/request/request.js:877:8)
at ClientRequest.emit (events.js:127:13)
at TLSSocket.socketErrorListener (_http_client.js:394:9)
at TLSSocket.emit (events.js:127:13)
at emitErrorNT (internal/streams/destroy.js:64:8)
at process._tickCallback (internal/process/next_tick.js:152:19)
… On Jul 4, 2018, at 6:45 AM, martijndierckx ***@***.***> wrote:
Can you tell me a bit more about your setup?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#2 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/Am2fvJ50QxZDnVc4h4Lhq31c0AeF3nG2ks5uDJzdgaJpZM4U-WwE>.
martijndierckx commented
Have a look, I fixed an issue. I hope it's the same you have.
martijndierckx commented
Did it fix the problem?