Architettura di rete, firewall e modalità standby

Specifiche porte di rete, regole firewall VLAN IoT, Wake-on-LAN e gestione dell'alimentazione in standby.

Controllo LAN locale al 100% senza cloud

The VIDAA Smart TV integration operates entirely over your local network. The 4-digit PIN challenge-response handshake, certificate mutual TLS validation, and subsequent 30-day standby token renewals are calculated and verified directly on the TV motherboard hardware. No external cloud servers, vendor APIs, or internet bridges are ever contacted.

🔌 Matrice di porte e protocolli

The integration communicates across 3 network ports on your local subnet:

Port / Protocol Direction Service Name Function & Architecture
36669 / tcp HA → TV Mutual TLS MQTT Broker Primary Control & Telemetry Channel: Persistent encrypted socket connection. Transmits live power status, volume, source, app launches, and remote key commands. Enforces client-certificate mutual TLS authentication.
38400 / tcp
(or 18400 on legacy models)
HA → TV UPnP MediaRenderer Device Discovery & Clock Sync: Queries /description.xml during setup to auto-detect the OEM brand profile, extract model descriptors, and synchronize hardware clock drift.
9 / udp HA → Broadcast Wake-on-LAN (WoL) Network Power-On: Dispatches magic packets (repeated Ethernet/Wi-Fi MAC sequence) to wake supported TVs from deep eco-standby.

🛡️ Regole firewall e isolamento VLAN IoT

If you isolate smart home hardware on a dedicated IoT VLAN or guest subnet, configure your router or gateway (e.g. OpenWrt, pfSense, OPNsense, UniFi) with the following firewall rules:

Source Destination Port / Proto Action Notes
Home Assistant VIDAA TV 36669/tcp ALLOW Mandatory MQTT control stream.
Home Assistant VIDAA TV 38400/tcp ALLOW UPnP brand discovery & clock sync.
Home Assistant Subnet Broadcast 9/udp ALLOW Wake-on-LAN broadcast packets. Enable WoL relay / directed broadcast across VLANs if TV is on a separate subnet.
VIDAA TV Home Assistant Established / Related ALLOW Allows the TV to return TCP ACK packets and MQTT state updates.
VIDAA TV WAN (Internet) All DROP / REJECT Safe to Block: Disables telemetry, ACR ad tracking, and firmware auto-updates. Local Home Assistant control continues operating 100% offline.

⚡ Architettura di alimentazione e standby

VIDAA OS implements a two-tier standby lifecycle to comply with international eco-power consumption standards (≤ 0.5W):

🌙 Tier 1: Light Standby (Screen Off)

When powered off with remote or HA, the display panel shuts off while the SoC maintains a low-power background kernel for ~5–15 minutes. The MQTT broker remains active, allowing instant wake via MQTT KEY_POWER.

💤 Tier 2: Deep Standby (Cold Sleep)

After the sleep grace period expires, the TV powers down its main board and Wi-Fi radios. The TCP connection drops and the entity reports unavailable until a Wake-on-LAN packet or HDMI-CEC signal revives the NIC.

Hardware Notice: 2020–2022 Models (A6, A53, A7 Series)

On several 2020–2022 models running VIDAA U4 / U5, the mainboard completely depowers the Ethernet PHY chip in deep standby, meaning hardware Wake-on-LAN cannot wake the TV over Ethernet.

To ensure reliable power control on these models:

  1. Enable Fast Power On in the TV menu: Settings → System → Advanced Settings → Fast Power On → ON.
  2. When Fast Power On is active, the TV SoC maintains its network listening state, allowing Home Assistant to wake the display instantly via local MQTT without relying on WoL packets.
  3. Alternatively, use a Pluggable Turn-On Automation in the integration options to toggle a smart plug or send an HDMI-CEC pulse.

🔑 Ciclo di vita del token di standby e stabilità

During initial PIN pairing, the TV generates an internal 128-bit authentication token (auth_token). To maintain a valid token across deep standby cycles:

  • The integration periodically sends authenticated keep-alive pings while the TV is in Light Standby to refresh the session token.
  • If the TV experiences a power outage or deep reboot, Home Assistant automatically triggers an automatic re-authentication cascade using the stored challenge salt.
  • If token loss ever occurs, Home Assistant presents a notification in Settings → Repairs allowing a 1-click re-pair prompt.