From 0348fea73a2098f61fc99af82d5787600fe1752e Mon Sep 17 00:00:00 2001 From: Franck Nijhof Date: Thu, 17 Apr 2025 07:34:44 +0200 Subject: [PATCH] Add detailed TLS/SSL limitations for Ecowitt integration (#38581) --- source/_integrations/ecowitt.markdown | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/source/_integrations/ecowitt.markdown b/source/_integrations/ecowitt.markdown index 572512f9875..1515522b932 100644 --- a/source/_integrations/ecowitt.markdown +++ b/source/_integrations/ecowitt.markdown @@ -39,4 +39,8 @@ The integration will display a Server IP / Host Name, Path, and Port. You can in - Enter the Server IP / Host Name, Path, and Port from the integration. - Save -Ecowitt doesn't support TLS/SSL, you can use the NGINX TLS Proxy Add-on to support HTTPS and HTTP at the same time. +## TLS/SSL limitations + +Ecowitt devices do not support TLS/SSL connections (HTTPS). If your Home Assistant instance is configured to use HTTPS only, the Ecowitt integration will not work properly. You must ensure your Home Assistant instance is accessible via HTTP (non-secure) for the Ecowitt devices to successfully send data. + +If you're using SSL/TLS for your Home Assistant instance, you'll need to configure your setup to accept both secure (HTTPS) and non-secure (HTTP) connections. This can typically be done by adjusting your reverse proxy configuration or by using the NGINX Home Assistant add-on which can handle both HTTP and HTTPS traffic simultaneously.