Installation External Integrations

Configuration
1

Hello everyone, and congratulations on all these new features.

When I try to install external integrations, they all go to « degraded » status (Zendure, Tapo, MTO, …etc). Here are the logs for Zendure as an example (I have a Solarflow battery and I did retrieve the cloud authorization key):

\[2026-08-17T08:50:08.091Z\] \[INFO\] Starting the Zendure integration...
\[2026-08-17T08:52:21.090Z\] \[ERROR\] \[gladys-sdk\] websocket error on ws://172.30.0.1:81: connect ETIMEDOUT 172.30.0.1:81
\[2026-08-17T08:52:21.092Z\] \[WARN\] \[gladys-sdk\] not connected to Gladys (ws://172.30.0.1:81), retrying in 1000 ms (attempt 1)
\[2026-08-17T08:54:36.253Z\] \[ERROR\] \[gladys-sdk\] websocket error on ws://172.30.0.1:81: connect ETIMEDOUT 172.30.0.1:81
\[2026-08-17T08:54:36.254Z\] \[WARN\] \[gladys-sdk\] not connected to Gladys (ws://172.30.0.1:81), retrying in 2000 ms (attempt 2)
\[2026-08-17T08:55:53.195Z\] \[INFO\] Received SIGTERM -> graceful shutdown
\[2026-08-17T08:55:53.197Z\] \[ERROR\] \[gladys-sdk\] websocket error on ws://172.30.0.1:81: WebSocket was closed before the connection was established
\[2026-08-17T08:55:55.509Z\] \[INFO\] Starting the Zendure integration...
\[2026-08-17T08:58:09.247Z\] \[ERROR\] \[gladys-sdk\] websocket error on ws://172.30.0.1:81: connect ETIMEDOUT 172.30.0.1:81
\[2026-08-17T08:58:09.248Z\] \[WARN\] \[gladys-sdk\] not connected to Gladys (ws://172.30.0.1:81), retrying in 1000 ms (attempt 1)
\[2026-08-17T09:00:24.412Z\] \[ERROR\] \[gladys-sdk\] websocket error on ws://172.30.0.1:81: connect ETIMEDOUT 172.30.0.1:81
\[2026-08-17T09:00:24.413Z\] \[WARN\] \[gladys-sdk\] not connected to Gladys (ws://172.30.0.1:81), retrying in 2000 ms (attempt 2)
\[2026-08-17T09:02:39.581Z\] \[ERROR\] \[gladys-sdk\] websocket error on ws://172.30.0.1:81: connect ETIMEDOUT 172.30.0.1:81
\[2026-08-17T09:02:39.581Z\] \[WARN\] \[gladys-sdk\] not connected to Gladys (ws://172.30.0.1:81), retrying in 4000 ms (attempt 3)
\[2026-08-17T09:04:58.844Z\] \[ERROR\] \[gladys-sdk\] websocket error on ws://172.30.0.1:81: connect ETIMEDOUT 172.30.0.1:81
\[2026-08-17T09:04:58.844Z\] \[WARN\] \[gladys-sdk\] not connected to Gladys (ws://172.30.0.1:81), retrying in 8000 ms (attempt 4)
\[2026-08-17T09:07:22.205Z\] \[ERROR\] \[gladys-sdk\] websocket error on ws://172.30.0.1:81: connect ETIMEDOUT 172.30.0.1:81
\[2026-08-17T09:07:22.206Z\] \[WARN\] \[gladys-sdk\] not connected to Gladys (ws://172.30.0.1:81), retrying in 16000 ms (attempt 5)
\[2026-08-17T09:09:53.757Z\] \[ERROR\] \[gladys-sdk\] websocket error on ws://172.30.0.1:81: connect ETIMEDOUT 172.30.0.1:81
\[2026-08-17T09:09:53.757Z\] \[WARN\] \[gladys-sdk\] not connected to Gladys (ws://172.30.0.1:81), retrying in 32000 ms (attempt 6)
\[2026-08-17T09:12:41.692Z\] \[ERROR\] \[gladys-sdk\] websocket error on ws://172.30.0.1:81: connect ETIMEDOUT 172.30.0.1:81
\[2026-08-17T09:12:41.692Z\] \[WARN\] \[gladys-sdk\] not connected to Gladys (ws://172.30.0.1:81), retrying in 60000 ms (attempt 7)

Thanks for your help.

2

Hi @jparbel,
I took the liberty of editing your post to make the logs more readable.
When you copy/paste your logs, you can then format them with this icon (by selecting your text):
image

3

When looking at your logs, it seems like Docker is having an issue.
Have you tried restarting your machine?
Another thing to check: the updates for your OS on your machine to update?

4

Thanks @mutmut

I’m on Ubuntu 24.04.4 LTS. Yes, I had restarted my machine by restarting the integration 3 hours ago with the same result.

My containers are active and running normally:

4e2fa4ec977f Package gladys-zendure · GitHub « dumb-init – node i… » 3 hours ago Up 3 hours gladys-ext-terdious-gladys-zendure

Just in case: just a particularity of my Gladys installation, my Gladys server is on port 81 and not 80.

5

The issue is therefore the Gladys container using port 81 instead of 80
Try giving Gladys a port other than 81 and everything should work :slight_smile:

6

Thanks @prohand, port 80 is already in use. I don’t understand why using another port, like 82 or another, would make a difference.

7

Because external integrations use port 81 to communicate with Gladys, if I’m not mistaken, and if Gladys is using it for the web interface, there’s a conflict.
Why didn’t you leave Gladys on port 80 by default?

8

I think you have a firewall blocking port 81 or the websocket on port 81.

9

@prohand Because it’s my main machine and I already had a server running on 80

Well spotted @cicoub13 I just authorized port 81 in my firewall and it works! Thanks to you for your responses.

10

Personally, I’m on 8420 historically because that’s the one indicated for installation on Synology, and after migrating my machine, I kept it and never had any issues :slight_smile:

Glad it’s working for you too!