As a more advanced troubleshooting step, you can consider trying an SSH experiment or jailbreaking to get SSH access to Homey. With SSH access, you can try to ping api.telegram.org to check if there’s a connectivity issue between Homey and the Telegram API.
As we discussed in the group, it’s most likely a problem on your side since you’re the only user who reported this issue, and it started after changing stuff on your local network. Maybe @robertklep has an idea why this happens to you.
2023-12-13T13:08:01.825Z [err] HttpError: Network request for 'sendMessage' failed!
at /app/node_modules/grammy/out/core/error.js:74:15
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async ApiClient.call (/app/node_modules/grammy/out/core/client.js:54:29) {
error: FetchError: request to https://api.telegram.org/***/sendMessage failed, reason: connect ENETUNREACH 2001:67c:4e8:f004::9:443
at ClientRequest.<anonymous> (/app/node_modules/grammy/node_modules/node-fetch/lib/index.js:1501:11)
at ClientRequest.emit (node:events:517:28)
at TLSSocket.socketErrorListener (node:_http_client:501:9)
at TLSSocket.emit (node:events:517:28)
at emitErrorNT (node:internal/streams/destroy:151:8)
at emitErrorCloseNT (node:internal/streams/destroy:116:3)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
type: 'system',
errno: 'ENETUNREACH',
code: 'ENETUNREACH'
}
}
(2001:67c:4e8:f004::9:443 is the IPv6 of api.telegram.org)
