I set up an IoT vlan that works in almost all cases except for trying to connect my Samsun Smart TV to Home Assistant. When I connect the TV to my regular wifi that is on the same vlan as the HA server, the TV is auto discovered and able to be added to HA. The TV will give a prompt to apprve the connection to Home Assistant.
But when I connect the TV to my IoT wifi on the IoT vlan I am unable to connect the TV to Home Assistant. The TV is not auto discovered and when I try to manually add the TV through the integration, plugging in the IP address, it appears to see the TV (the model number is listed in the window) but I do not get hte prompt on the TV to approve the connection. I’ve tried clearing out Home Assistant from the approved devices list on the TV but that didn’t help. Its like HA can see the TV on the network but can’t complete the setup.
Additionally, I am able to ping the device from a laptop on my main wifi/main vlan.
I’ve tried to diable my drop traffic rule between vlans to see if that was the issue but even that didn’t allow HA to add the TV.
I’m not quite sure what is causing this issue and I’m at a loss on what to try next.
My network set up is as follows:
HA is hosted as docker container on 192.168.1.x (upper/main subnet)
Samsung TV is either connected to the same “main” network (192.168.1.y),
or to “lower” subnet (GL.iNet router connected to main network; 192.168.8.x)
and tv gets different ip 192.168.8.y
Router has static ip assigned on main network 192.168.1.Z;
All devices from upper “main” network are available from “lower” network, so that
ping 192.168.1.123 works fine from 192.168.8.123 but not vice versa.
Original Samsung TV integration works fine with TV connected to main subnet. But once tv is moved to “lower” network,
it becomes unavailabe.
+-----------------------------------+
| network: 192.168.1.x |
| TV1 (192.168.1.y) |
| HA (192.168.1.h) |
| GL.iNET router (192.168.1.Z) |
| +----------------------+ |
| | netork: 192.168.8.x | |
| | | |
| | TV2 (192.168.8.y) | |
| +----------------------+ |
+-----------------------------------+
note: "TV1" and "TV2" is the same physical tv
I have installed “haproxy” on GL.iNet router (OpenWRT), configuration:
# --------------------------
# Frontend: WebSocket (8002)
# --------------------------
frontend ws_front
bind *:8002
mode tcp
default_backend ws_back
backend ws_back
mode tcp
balance first
option tcp-check
server tv_lan1 192.168.8.y:8002 check inter 2s fall 2 rise 1
server tv_lan2 192.168.1.y:8002 check inter 2s fall 2 rise 1 backup
# --------------------------
# Frontend: DLNA/DMR (9197)
# --------------------------
frontend dmr_front
bind *:9197
mode http
option httplog
default_backend dmr_back
backend dmr_back
mode http
balance first
option httpchk GET /
server tv_lan1 192.168.8.y:9197 check inter 2s fall 2 rise 1
server tv_lan2 192.168.1.y:9197 check inter 2s fall 2 rise 1 backup
So integration itself has to be configured to use router IP (192.168.1.Z) not tv (192.168.1.y);
Why not standard samsung tv integration? I didn’t make it work: once connected to is connected back to main network, reconfiguration promt pops up, which you cannot ignore. It basically reconfigures it back to use tv ip and overwrites previously configured proxy settings. This is not happenning with custom HACS configuration.