Interesting, in the log it shows the box is not responding:
{
"time": "2023-10-20T06:46:41.631Z",
"elapsed": 4.89,
"source": "Right front: Local command failed (will try cloud)",
"data": "command: {
"name": "close",
"parameters": []
}, error = timeout of 10000ms exceeded
Error: timeout of 10000ms exceeded
at createError (/node_modules/axios/lib/core/createError.js:16:15)
at ClientRequest.handleRequestTimeout (/node_modules/axios/lib/adapters/http.js:303:16)
at Object.onceWrapper (node:events:645:28)
at ClientRequest.emit (node:events:526:28)
at TLSSocket.emitRequestTimeout (node:_http_client:758:9)
at Object.onceWrapper (node:events:645:28)
at TLSSocket.emit (node:events:538:35)
at TLSSocket.Socket._onTimeout (node:net:501:8)
at listOnTimeout (node:internal/timers:559:17)
at processTimers (node:internal/timers:502:7))"
},
The mDNS has found the box:
{
"time": "2023-10-20T06:46:25.865Z",
"elapsed": 0.447,
"source": "mDNS Found a local bridge",
"data": "{
"pin": "####-####-####",
"address": "192.168.1.68",
"port": 8443,
"api_version": "1",
"fw_version": "2023.4.4-9"
}"
},
{
"time": "2023-10-20T06:46:25.880Z",
"elapsed": 0.015,
"source": "Doing local login",
"data": ""
},
{
"time": "2023-10-20T06:46:26.352Z",
"elapsed": 0.472,
"source": "Tahoma Local Login",
"data": "Set local token for https://gateway-####-####-####local"
},
{
"time": "2023-10-20T06:46:26.358Z",
"elapsed": 0.006,
"source": "Local login: Getting local API version",
"data": ""
},
{
"time": "2023-10-20T06:46:27.021Z",
"elapsed": 0.663,
"source": "Local login Successful",
"data": "{
"protocolVersion": "2023.4.4-9"
}"
},
The login is still done through the cloud, even though it is for the local connection.
So unless the app is getting the wrong IP address via Homey’s mDNS, I can’t see why it would fail.
Would it be possible to make sure the Tahoma box is assigned a fixed IP address, just in case it is changing and Homey is not picking it up correctly?
