2019 LG TV with HomeKit and AirPlay 2

ASchneiderBR commented 5 years ago

Home Assistant release with the issue:

96.5

Last working Home Assistant release (if known):

Not sure.

Operating environment (Hass.io/Docker/Windows/etc.):

Hassio running on RPI3B

Component/platform:

Homekit and maybe HomeKit controller

Description of problem:

Hello everyone.

I've just installed the new LG TV SM86 2019 with WebOS and the new HomeKit/airplay 2 integration.

WebOS component is configured and working fine, the main problem is that every time I turn on the TV, it broadcasts as a HomeKit accessory (still not compatible with HA) and my system goes wild with 35% constant use of CPU, some ESPHome devices are disconnect and so on.

Here is the notification:

And this is the device:

(Discovered: Homekit accessory: LG......)

I have both zeroconf and discovery components enabled with homekit on the ignore list (discovery):

discovery:

  ignore:
    - homekit

Also tried disabling discovery and zeroconf components with no luck.

I just have the homekit component enable on my setup.

This is the CPU usage when the TV is ON and OFF:

This is ratter new (AirPlay 2) and not sure what is going on…

Is there a way to disable it? I don't want add it as a regular HomeKit accessory since the media_player entity is working just fine with the webos component.

Thanks!

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

Traceback (if applicable):

Additional information:

ASchneiderBR commented 5 years ago

Hello again.

I've also disabled the media_player webos component with no luck. The moment the TV turns on, all local area networks becomes "flooded" and slow. I have no idea what is going on.

ASchneiderBR commented 5 years ago

Even tough I have zeroconf commented on my config file, I still get this:

2019-08-01 20:54:28 DEBUG (zeroconf-ServiceBrowser__hap._tcp.local.) [homeassistant.components.zeroconf] Discovered new device LG webOS TV 7492._hap._tcp.local. {'host': '192.168.1.168', 'port': 38619, 'hostname': 'LGwebOSTV.local.', 'type': '_hap._tcp.local.', 'name': 'LG webOS TV 7492._hap._tcp.local.', 'properties': {'c#': '1', 'ff': '8', 'id': 'C7:AB:F2:2A:BB:35', 'md': 'WEBOS', 'pv': '1.1', 's#': '1', 'sf': '1', 'ci': '31', 'sh': '0WjAag=='}}

Jc2k commented 5 years ago

I don't think homekit is involved in this at all, but homekit_controller might be and so might zeroconf.

If you have default_config: in your configuration pulled in. I don't think there is a way to stop it while you have default_config.

zeroconf doesn't respect the ignore list for discovery and it doesn't have its own ignore list.

If you turn on logging to DEBUG for homekit_controller:

logger:
  logs:
    homeassistant.components.homekit_controller.config_flow: debug

do you see something like:

2019-08-02 10:11:31 DEBUG (MainThread) [homeassistant.components.homekit_controller.config_flow] Discovered device DemoAccessory (DemoAccessory - 10:30:10:00:00:00)

How often do you see that?

How often do you see the zeroconf ServiceBrowser log item you posted ^ in your logs? Just once? Or multiple times a second?

Do you see any KeyError messages about discovery?

ghost commented 5 years ago

Hey there @Jc2k, mind taking a look at this issue as its been labeled with a integration (homekit_controller) you are listed as a codeowner for? Thanks!

This is a automatic comment generated by codeowners-mention to help ensure issues and pull requests are seen by the right people.

ASchneiderBR commented 5 years ago

Hello @Jc2k! Thank you so much for your time and effort for helping me here, really appreciate it.

I don't have default_config enable on my config, here is my current config file:

homeassistant:
  name: Casa
  latitude: !secret latitude
  longitude: !secret longitude
  elevation: 30
  unit_system: metric
  time_zone: America/Sao_Paulo
  customize: !include includes/customize.yaml
  packages: !include_dir_named includes/packages/
  auth_providers: !include includes/auth_providers.yaml

zone:
  name: Home
  latitude: !secret latitude_home
  longitude: !secret longitude_home
  icon: mdi:home
  radius: 18
zone 2:
  name: Trabalho
  latitude: !secret latitude_work
  longitude: !secret longitude_work
  icon: mdi:home-modern
  radius: 18

api:
config:
conversation:
ffmpeg:
hassio:
history:
logbook:
map:
#stream:
sun:
system_health:
updater:
wake_on_lan:
zeroconf:
#ssdp:

alarm_control_panel: !include includes/alarm.yaml
asuswrt: !include includes/asuswrt.yaml
automation: !include includes/automation.yaml
binary_sensor: !include includes/binary_sensor.yaml
camera: !include includes/camera.yaml
climate: !include includes/climate.yaml
cover: !include includes/cover.yaml
device_tracker: !include includes/device_tracker.yaml
discovery: !include includes/discovery.yaml
fastdotcom: !include includes/fastdotcom.yaml
frontend: !include includes/frontend.yaml
google_assistant: !include includes/google_assistant.yaml
#googlehome: !include includes/googlehome.yaml
group: !include includes/group.yaml
homekit: !include includes/homekit.yaml
http: !include includes/http.yaml
input_boolean: !include includes/input_boolean.yaml
input_number: !include includes/input_number.yaml
input_select: !include includes/input_select.yaml
ios: !include includes/ios.yaml
light: !include includes/light.yaml
logger: !include includes/logger.yaml
media_player: !include includes/media_player.yaml
#mqtt: !include includes/mqtt.yaml
notify: !include includes/notify.yaml
octoprint: !include includes/octoprint.yaml
panel_iframe: !include includes/panel_iframe.yaml
person: !include includes/person.yaml
recorder: !include includes/recorder.yaml
rest_command: !include includes/rest_command.yaml
scene: !include includes/scene.yaml
script: !include includes/script.yaml
sensor: !include includes/sensor.yaml
shell_command: !include includes/shell_command.yaml
smartir: !include includes/smartir.yaml
#spotcast: !include includes/spotcast.yaml
switch: !include includes/switch.yaml
timer: !include includes/timer.yaml
tts: !include includes/tts.yaml
tuya: !include includes/tuya.yaml
vacuum: !include includes/vacuum.yaml
weather: !include includes/weather.yaml
xiaomi_aqara: !include includes/xiaomi_aqara.yaml

Even tough I don't have components.homekit_controller enable (config above), I've enabled debug on log, like this:

default: error
logs:
  homeassistant.components.homekit_controller: debug
  homeassistant.components.zeroconf: debug
  homeassistant.components.ssdp: debug

This is my discovery config file:

ignore:
  - apple_tv
  - axis
  - belkin_wemo
  - bluesound
  - bose_soundtouch
  - denonavr
  - directv
  - enigma2
  - frontier_silicon
  - harmony
  - homekit
  - igd
  - ikea_tradfri
  - logitech_mediaserver
  - netgear_router
  - octoprint
  - openhome
  - panasonic_viera
  - philips_hue
  - plex_mediaserver
  - roku
  - sabnzbd
  - samsung_printer
  - samsung_tv
  - sonos
  - songpal 
  - tellstick
  - wink
  - yamaha
  - yeelight
  - xiaomi_gw

I've enable it last night, turned on the TV for half an hour and had to turn it off to go to sleep... Here is the entire log file: home-assistant.log. My TV is on 192.168.1.168.

I can assure that the moment the TV is on, the CPU goes to 30%, my network gets flooded and becomes slow with latency up to 3000ms when pinging a local ESPHOME sonoff device, finally they show up as unavailable. I'm not sure why but this is related to the ESPHOME component, maybe because they seems to use zeroconfig for discovery. This TV is destroying my network hahaha

Also, I've turned off HA service entirely for testing and turned on the TV while pinging a few ESPHOME devices, their results was normal, about 8ms of response time, so I believe it is HA and the discovery protocol that is causing my network to brake down.

I cannot turn the TV on for now because my home network is the same as my work network, so I'll have to wait for a couple of hours to test it again.

Thanks a lot!

ASchneiderBR commented 5 years ago

Hello again @Jc2k! I've got a few minutes here and tested my network again for half an hour, these results baffles me :(

Here are my "normal" ping results:

I've turned on the TV on 10:24:19 and started pinging both my main router (RT-AC68U) and the TV, here are the results:

Then the network started not work properly:

My ESPHOME devices started to become unavailable after 10 mins or so. Here is the graph of my CPU:

This is when I've turned of the TV:

Here are the log file: home-assistant.log

My Asus is running on the latest Merlin custom firmware and there are no related information on its logs.

I had this turned on in logger:

default: error
logs:
  homeassistant.components.zeroconf: debug
  homeassistant.components.homekit_controller.config_flow: debug

Thanks!

Jc2k commented 5 years ago

Any chance you can run wireshark/tshark/tcpdump on the HA because and sniff the traffic between it and the TV?

Any idea what this is all about?

2019-08-01 21:57:12 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for homekit which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you do experience issues with Home Assistant.

I can only see zeroconf detect homekit devices at 2 points:

2019-08-01 21:57:32 DEBUG (zeroconf-ServiceBrowser__hap._tcp.local.) [homeassistant.components.zeroconf] Discovered new device LG webOS TV 7492._hap._tcp.local. {'host': '192.168.1.168', 'port': 38619, 'hostname': 'LGwebOSTV.local.', 'type': '_hap._tcp.local.', 'name': 'LG webOS TV 7492._hap._tcp.local.', 'properties': {'c#': '1', 'ff': '8', 'id': 'C7:BB:F3:2E:BB:59', 'md': 'WEBOS', 'pv': '1.1', 's#': '1', 'sf': '0', 'ci': '31', 'sh': '0WjAaw=='}}

2019-08-01 21:59:31 DEBUG (zeroconf-ServiceBrowser__hap._tcp.local.) [homeassistant.components.zeroconf] Discovered new device Home Assistant Bridge._hap._tcp.local. {'host': '192.168.1.12', 'port': 51827, 'hostname': 'homeassistant.local.', 'type': '_hap._tcp.local.', 'name': 'Home Assistant Bridge._hap._tcp.local.', 'properties': {'md': 'Home Assistant Bridge', 'pv': '1.0', 'id': 'AB:A3:B8:87:06:CC', 'c#': '2', 's#': '1', 'ff': '0', 'ci': '2', 'sf': '0', 'sh': 'FUN5cw=='}}

Obviously only the first one is related to the TV.

With the logging config in place you should see:

2019-08-02 10:11:31 DEBUG (MainThread) [homeassistant.components.homekit_controller.config_flow] Discovered device DemoAccessory (DemoAccessory - 10:30:10:00:00:00)

But i can't see anything like that.

What i need to figure out is if home assistant is making homekit TCP connections to the TV. That doesn't happen with any of the devices I have to test with - it only connects when you initiate pairing. I don't suppose you have paired with it at any point?

ASchneiderBR commented 5 years ago

Hello sir!

Any chance you can run wireshark/tshark/tcpdump on the HA because and sniff the traffic between it and the TV?

I have the knowledge of what it is and what it does but never done it before, I'll need to study and figure it out, no problem Any idea what this is all about?
2019-08-01 21:57:12 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for homekit which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you do experience issues with Home Assistant.
Sorry about that, forgot to tell you that I was experimenting with the latest beta version (0.97) of these components... I'll remove them and use the latest stable release. I can only see zeroconf detect homekit devices at 2 points:
2019-08-01 21:57:32 DEBUG (zeroconf-ServiceBrowser__hap._tcp.local.) [homeassistant.components.zeroconf] Discovered new device LG webOS TV 7492._hap._tcp.local. {'host': '192.168.1.168', 'port': 38619, 'hostname': 'LGwebOSTV.local.', 'type': '_hap._tcp.local.', 'name': 'LG webOS TV 7492._hap._tcp.local.', 'properties': {'c#': '1', 'ff': '8', 'id': 'C7:BB:F3:2E:BB:59', 'md': 'WEBOS', 'pv': '1.1', 's#': '1', 'sf': '0', 'ci': '31', 'sh': '0WjAaw=='}}
2019-08-01 21:59:31 DEBUG (zeroconf-ServiceBrowser__hap._tcp.local.) [homeassistant.components.zeroconf] Discovered new device Home Assistant Bridge._hap._tcp.local. {'host': '192.168.1.12', 'port': 51827, 'hostname': 'homeassistant.local.', 'type': '_hap._tcp.local.', 'name': 'Home Assistant Bridge._hap._tcp.local.', 'properties': {'md': 'Home Assistant Bridge', 'pv': '1.0', 'id': 'AB:A3:B8:87:06:CC', 'c#': '2', 's#': '1', 'ff': '0', 'ci': '2', 'sf': '0', 'sh': 'FUN5cw=='}}
Obviously only the first one is related to the TV.

Yep, the other one is the homekit component or the Homekit Hub I run on my iPad, so I can access the Home App outside my house. With the logging config in place you should see:
2019-08-02 10:11:31 DEBUG (MainThread) [homeassistant.components.homekit_controller.config_flow] Discovered device DemoAccessory (DemoAccessory - 10:30:10:00:00:00)
But i can't see anything like that.

What i need to figure out is if home assistant is making homekit TCP connections to the TV. That doesn't happen with any of the devices I have to test with - it only connects when you initiate pairing. I don't suppose you have paired with it at any point?

Yes, I believe this is a new thing because of the LG SM 2019 series that has HomeKit and AirPlay 2, the first set of TVs that apple allows it to use. There a few other TVs on the market that will have these features, like Samsung and other brands, you can find them here: https://www.apple.com/ios/home/accessories/#section-tv

I fell bad that this is happening but I think it is a great opportunity for testing and preparing this great project for these new TVs :)

Is there a way to completely disable homekit_controller component or its discovery method? I really don't intent to use it since all my entities needed on HomeKit comes from HA. I don't even pair the TV on HomeKit because not all features are shown on the app. I get a lot more using HA (media_player and added tv on class) :)

Thanks a lot!

Jc2k commented 5 years ago

Nothing to be sorry about - I actually only look after homekit_controller anyway, so i'm intrigued by these devices. I was actually hoping that after we'ved figured this out you would be able to pair with it for me and extract the JSON for me so I can maybe add support for all HomeKit TV's.

Not really anyway to disable apart from removing the zeroconf line and disabling all mDNS based discovery. But its not supposed to trigger unless you initiate pairing, so if we can find out what the traffic actually is we can fix it and not need to disable it.

And as i've said, the logs i've seen so far don't show any evidence that homekit_controllr is even getting triggered which is really confusing because the screenshots show that it is.

ASchneiderBR commented 5 years ago

Hello again @Jc2k! How are you today?

A friend of mine help me today with the network sniffing and I would like to share them with you, if possible.

Are you on Discord? So I can send this logs on private...

Thanks a lot!

PS: just sent you a message on HA main forum :)

ASchneiderBR commented 5 years ago

Hello @Jc2k, how are you today?

Terrible sorry to bother you sir, but, I wonder if as a temporary solution, If I copy both homekit_controller and zeroconfig components to my custom_components folder with a blank _init.py?

I wonder if there is way of "messing up" the entire discovery service on HA since I don't really need it.

Yesterday I've changed the TV name and repaired with my HomeKit Hub and the discovery alert on my HA has stopped showing up every few seconds, so that's a good thing.

After a few hours of stable use of the TV connected to my network, watching YouTube and playing some local Plex, strangely the TV started messing up my network again :(

When I plug the TV back on the network again, after a few seconds all of my ESPHome devices starts showing as unavailable and high CPU usage again.

Also, I was not able to figure out how can I disable mDNS discovery on HA.

Thank you very much!

Jc2k commented 5 years ago

If you don't have default_config: and you don't have zeroconf: in your config at all then i believe the zeroconf/mdns discovery won't load at all.

I don't know if your idea about dummy custom components will work - try it and let me know. Failing that, you could find the homekit_controller and zeroconf folders and delete them. If you could delete homekit_controller first and see if the problem still occurs. Then delete zeroconf and see if it still occurs.

ASchneiderBR commented 5 years ago

That is the odd part: I do have zeronconf: commented ou and no default_config: at all on my configuration yaml and still the component loads. The moment I plug the cable of my TV, ESPHome starts showing as unavailable, that is incredible haha

Failing that, you could find the homekit_controller and zeroconf folders and delete them

What do mean about that? Deleting these folder outside de main config folder of Hassio?

Thanks.

Jc2k commented 5 years ago

Just to check you have zeroconf commented out and not zeronconf :) When it is commented out do you see messages from homeassistant.components.zeroconf in your logfile?

Yes - deleting zeroconf from the main installation on container should be a pretty effective way of ruling out those components. It's hard to give exact instructions for deployment styles i am not familiar with. On my system i would be able to do find / -name homekit_controller and after a while it would find out where my home-assistant is installed and i'd be able to delete that folder. It would come back on the next upgrade, but at least we would confirm which components were involved.

ASchneiderBR commented 5 years ago

Just to check you have zeroconf commented out and not zeronconf :)

Yes! sorry, mistyped it :)

Here is my current config file:

homeassistant:
  name: Casa
  latitude: !secret latitude
  longitude: !secret longitude
  elevation: 30
  unit_system: metric
  time_zone: America/Sao_Paulo
  customize: !include includes/customize.yaml
  packages: !include_dir_named includes/packages/
  auth_providers: !include includes/auth_providers.yaml
  whitelist_external_dirs:
    - /tmp

zone:
  name: Home
  latitude: !secret latitude_home
  longitude: !secret longitude_home
  icon: mdi:home
  radius: 18
zone 2:
  name: Trabalho
  latitude: !secret latitude_work
  longitude: !secret longitude_work
  icon: mdi:home-modern
  radius: 18

api:
config:
#conversation:
ffmpeg:
hassio:
history:
logbook:
map:
stream:
sun:
system_health:
updater:
wake_on_lan:
#zeroconf:
#ssdp:

alarm_control_panel: !include includes/alarm.yaml
asuswrt: !include includes/asuswrt.yaml
automation: !include includes/automation.yaml
binary_sensor: !include includes/binary_sensor.yaml
camera: !include includes/camera.yaml
climate: !include includes/climate.yaml
cover: !include includes/cover.yaml
device_tracker: !include includes/device_tracker.yaml
#discovery: !include includes/discovery.yaml
fastdotcom: !include includes/fastdotcom.yaml
frontend: !include includes/frontend.yaml
google_assistant: !include includes/google_assistant.yaml
#googlehome: !include includes/googlehome.yaml
group: !include includes/group.yaml
hacs: !include includes/hacs.yaml
homekit: !include includes/homekit.yaml
http: !include includes/http.yaml
input_boolean: !include includes/input_boolean.yaml
input_number: !include includes/input_number.yaml
input_select: !include includes/input_select.yaml
ifttt: !include includes/ifttt.yaml
ios: !include includes/ios.yaml
light: !include includes/light.yaml
logger: !include includes/logger.yaml
media_player: !include includes/media_player.yaml
notify: !include includes/notify.yaml
octoprint: !include includes/octoprint.yaml
panel_iframe: !include includes/panel_iframe.yaml
person: !include includes/person.yaml
recorder: !include includes/recorder.yaml
rest_command: !include includes/rest_command.yaml
scene: !include includes/scene.yaml
script: !include includes/script.yaml
sensor: !include includes/sensor.yaml
shell_command: !include includes/shell_command.yaml
smartir: !include includes/smartir.yaml
#spotcast: !include includes/spotcast.yaml
switch: !include includes/switch.yaml
timer: !include includes/timer.yaml
tts: !include includes/tts.yaml
tuya: !include includes/tuya.yaml
vacuum: !include includes/vacuum.yaml
weather: !include includes/weather.yaml
xiaomi_aqara: !include includes/xiaomi_aqara.yaml

When it is commented out do you see messages from homeassistant.components.zeroconf in your logfile?

I've just created a dummy component to test it out and set those components on debug mode on logger, I'll get back to you with the results.

Thanks!

ASchneiderBR commented 5 years ago

So... Yeah... The dummy component idea did not worked haha

2019-08-12 10:49:26 ERROR (MainThread) [homeassistant.setup] Setup failed for zeroconf: No setup function defined.
2019-08-12 10:50:14 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of ios. Setup failed for dependencies: zeroconf
2019-08-12 10:50:14 ERROR (MainThread) [homeassistant.setup] Setup failed for ios: Could not set up all dependencies.
2019-08-12 10:50:14 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of ios. Setup failed for dependencies: zeroconf
2019-08-12 10:50:14 ERROR (MainThread) [homeassistant.setup] Unable to prepare setup for platform ios.notify: Could not set up all dependencies.
2019-08-12 10:50:14 ERROR (MainThread) [homeassistant.components.notify] Unknown notification service specified

It broke other components like HomeKit that I use a lot.

Also, restarted with only the homekit_controller as a dummy component and it did not worked as well.

ASchneiderBR commented 5 years ago

@Jc2k, I think this problem is not related to HA...

I've unplugged the TV from the LAN, stopped HA entirely, started pinging an ESPHome device, plugged in the TV and this happened:

Damn... What a mess here! haha

Sorry to bother you, again.

Jc2k commented 5 years ago

Yep looks that way. I wonder whats happening! Anyway we should probably close this ticket. But if you get to the bottom of it let me know on the forums - i'd love to gather some info on a HomeKit TV so I can add it to homekit_controller properly.

ASchneiderBR commented 5 years ago

Thanks a lot! At the end, the TV was guilty of spamming the entire network, crazy days we live in: a TV can now take down your local network by just turning it on haha

Thanks!

ASchneiderBR commented 4 years ago

Hello again @Jc2k! How are you?

I've upgraded my entire network to Ubiquiti Unifi HW with this problem in mind, among other nice cool features/upgrades.

Can you believe that this problem still persists? Just to give a heads up...

I've managed to run a network dump and I can see hundreds of packets sent from my TV's IP (192.168.20.41) to 224.0.0.251:5353 and dozens of ESP devices replies back, spamming the entire network.

These are a few packets, in case you are interest in:

10:42:13.362927 IP 192.168.20.41.5353 > 224.0.0.251.5353: 0 [3q] PTR (QU)? LGwebOSTV.local. PTR (QU)? _gasetup._udp.local. PTR (QU)? TV da sala._gasetup._udp.local. (94)
10:42:13.402013 IP 192.168.20.41.35042 > 52.43.62.74.443: Flags [S], seq 3458915456, win 29200, options [mss 1460,sackOK,TS val 1897023 ecr 0,nop,wscale 7], length 0
10:42:13.423813 IP 192.168.20.41.5353 > 224.0.0.251.5353: 0 [2q] PTR (QU)? _esphomelib._tcp.local. PTR (QU)? casa_magicled_suite_tv._esphomelib._tcp.local. (91)
10:42:13.499632 IP 192.168.20.41.5353 > 224.0.0.251.5353: 0 [2q] PTR (QU)? _esphomelib._tcp.local. PTR (QU)? casa_sonoffbasic_chuveiro_social._esphomelib._tcp.local. (101)
10:42:13.523151 ARP, Request who-has 192.168.20.41 tell 192.168.20.8, length 46
10:42:13.564733 IP 192.168.20.41.5353 > 224.0.0.251.5353: 0 [2q] PTR (QU)? _esphomelib._tcp.local. PTR (QU)? casa_sonoffbasic_ventilador_casa._esphomelib._tcp.local. (101)
10:42:13.623820 IP 192.168.20.41.35042 > 52.43.62.74.443: Flags [.], ack 1236021248, win 229, options [nop,nop,TS val 1897045 ecr 199949411], length 0
10:42:13.633785 IP 192.168.20.41.5353 > 224.0.0.251.5353: 0 [2q] PTR (QU)? _esphomelib._tcp.local. PTR (QU)? casa_sonoffbasic_principal_suite._esphomelib._tcp.local. (101)
10:42:13.705433 IP 192.168.20.41.5353 > 224.0.0.251.5353: 0 [2q] PTR (QU)? _esphomelib._tcp.local. PTR (QU)? casa_sonoffdual_banheiro_social._esphomelib._tcp.local. (100)
10:42:13.714032 IP 192.168.20.41.56816 > 54.164.96.158.443: Flags [.], seq 1756030396:1756031796, ack 3343206514, win 385, options [nop,nop,TS val 1897054 ecr 1305852132], length 1400
10:42:13.746693 IP 35.167.66.54.443 > 192.168.20.41.39142: Flags [.], ack 518, win 106, options [nop,nop,TS val 753659948 ecr 1897035], length 0
10:42:13.829369 IP 192.168.20.41.5353 > 224.0.0.251.5353: 0 [2q] PTR (QU)? _esphomelib._tcp.local. PTR (QU)? casa_sonoffbasic_cozinha_cafeteira._esphomelib._tcp.local. (103)
10:42:13.862642 IP 54.164.96.158.443 > 192.168.20.41.56816: Flags [R], seq 3343206514, win 0, length 0
10:42:13.864844 IP 192.168.20.41.56404 > 52.22.214.231.443: Flags [S], seq 2045869871, win 29200, options [mss 1460,sackOK,TS val 1897069 ecr 0,nop,wscale 7], length 0
10:42:13.901878 IP 192.168.20.41.5353 > 224.0.0.251.5353: 0 [2q] PTR (QU)? _esphomelib._tcp.local. PTR (QU)? casa_magicled_sala_painel._esphomelib._tcp.local. (94)
10:42:13.927454 IP 192.168.20.41.5353 > 224.0.0.251.5353: 0*- [0q] 5/0/2 (Cache flush) TXT "c#=1" "ff=8" "id=79:2C:BC:A2:D5:41" "md=WEBOS" "pv=1.1" "s#=1" "sf=0" "ci=31" "sh=2gfDJQ==", PTR _hap._tcp.local., PTR LG webOS TV 7492._hap._tcp.local., (Cache flush) SRV LGwebOSTV.local.:33568 0 0, (Cache flush) A 192.168.20.41 (266)
10:42:13.964284 IP 192.168.20.41.5353 > 224.0.0.251.5353: 0 [2q] PTR (QU)? _esphomelib._tcp.local. PTR (QU)? casa_sonoffbasic_principal_quarto._esphomelib._tcp.local. (102)
10:42:14.013633 IP 52.22.214.231.443 > 192.168.20.41.56404: Flags [S.], seq 1470254237, ack 2045869872, win 26847, options [mss 1412,sackOK,TS val 1248764126 ecr 1897069,nop,wscale 8], length 0
10:42:14.014839 IP 192.168.20.41.56404 > 52.22.214.231.443: Flags [.], ack 1, win 229, options [nop,nop,TS val 1897084 ecr 1248764126], length 0
10:42:14.091961 IP 192.168.20.41.44944 > 201.48.44.213.443: Flags [S], seq 2329670791, win 29200, options [mss 1460,sackOK,TS val 1897092 ecr 0,nop,wscale 7], length 0
10:42:14.092395 IP 192.168.20.41.44946 > 201.48.44.213.443: Flags [S], seq 697665347, win 29200, options [mss 1460,sackOK,TS val 1897092 ecr 0,nop,wscale 7], length 0
10:42:14.092826 IP 192.168.20.41.44948 > 201.48.44.213.443: Flags [S], seq 2280841571, win 29200, options [mss 1460,sackOK,TS val 1897092 ecr 0,nop,wscale 7], length 0
10:42:14.115801 IP 192.168.20.41.5353 > 224.0.0.251.5353: 0 [2q] PTR (QU)? _esphomelib._tcp.local. PTR (QU)? casa_magicled_cozinha_chao._esphomelib._tcp.local. (95)
10:42:14.118782 IP 201.48.44.213.443 > 192.168.20.41.44944: Flags [S.], seq 3891387004, ack 2329670792, win 65535, options [mss 1412,nop,wscale 9,sackOK,TS val 2408394841 ecr 1897092], length 0
10:42:14.120089 IP 192.168.20.41.44944 > 201.48.44.213.443: Flags [.], ack 1, win 229, options [nop,nop,TS val 1897095 ecr 2408394841], length 0
10:42:14.128003 IP 201.48.44.213.443 > 192.168.20.41.44948: Flags [S.], seq 1418639055, ack 2280841572, win 65535, options [mss 1412,nop,wscale 9,sackOK,TS val 3204294404 ecr 1897092], length 0
10:42:14.128280 IP 201.48.44.213.443 > 192.168.20.41.44946: Flags [S.], seq 2241073694, ack 697665348, win 65535, options [mss 1412,nop,wscale 9,sackOK,TS val 118841811 ecr 1897092], length 0
10:42:14.129608 IP 192.168.20.41.44948 > 201.48.44.213.443: Flags [.], ack 1, win 229, options [nop,nop,TS val 1897096 ecr 3204294404], length 0
10:42:14.130145 IP 192.168.20.41.44946 > 201.48.44.213.443: Flags [.], ack 1, win 229, options [nop,nop,TS val 1897096 ecr 118841811], length 0
10:42:14.147320 IP 201.48.44.213.443 > 192.168.20.41.44944: Flags [.], ack 1, win 2049, options [nop,nop,TS val 2408394870 ecr 1897095], length 0
10:42:14.165023 IP 201.48.44.213.443 > 192.168.20.41.44948: Flags [.], ack 1, win 2049, options [nop,nop,TS val 3204294440 ecr 1897096], length 0
10:42:14.165415 IP 201.48.44.213.443 > 192.168.20.41.44946: Flags [.], ack 1, win 2049, options [nop,nop,TS val 118841848 ecr 1897096], length 0
10:42:14.167942 IP 52.22.214.231.443 > 192.168.20.41.56404: Flags [.], ack 232, win 110, options [nop,nop,TS val 1248764165 ecr 1897084], length 0
10:42:14.192590 IP 192.168.20.41.5353 > 224.0.0.251.5353: 0 PTR (QU)? _teamviewer._tcp.local. (40)
10:42:14.263204 IP 192.168.20.41.5353 > 224.0.0.251.5353: 0 [2q] PTR (QU)? _esphomelib._tcp.local. PTR (QU)? casa_sonoffbasic_area_servico._esphomelib._tcp.local. (98)
10:42:14.298075 IP 192.168.20.41.54136 > 192.168.21.1.53: 38561+ A? api-global.netflix.com. (40)
10:42:14.328704 IP 52.43.62.74.443 > 192.168.20.41.35042: Flags [.], ack 517, win 110, options [nop,nop,TS val 199949588 ecr 1897093], length 0
10:42:14.337237 IP 192.168.20.41.5353 > 224.0.0.251.5353: 0 [2q] PTR (QU)? _esphomelib._tcp.local. PTR (QU)? casa_magicled_cozinha_balcao._esphomelib._tcp.local. (97)
10:42:14.412311 IP 192.168.20.41.5353 > 224.0.0.251.5353: 0 [2q] PTR (QU)? _esphomelib._tcp.local. PTR (QU)? casa_sonoffbasic_sala_luz_mesa_jantar._esphomelib._tcp.local. (106)
10:42:14.480083 IP 192.168.20.41.5353 > 224.0.0.251.5353: 0 [2q] PTR (QU)? _esphomelib._tcp.local. PTR (QU)? casa_d1mini_controle_garagem._esphomelib._tcp.local. (97)
10:42:14.500941 IP 35.167.66.54.443 > 192.168.20.41.39142: Flags [FP.], seq 16506:16525, ack 1772, win 115, options [nop,nop,TS val 753660136 ecr 1897110], length 19
10:42:14.516204 IP 192.168.20.41.60974 > 31.13.85.8.443: Flags [P.], seq 763241787:763241818, ack 4029123730, win 317, options [nop,nop,TS val 1897134 ecr 880721575], length 31
10:42:14.516936 IP 192.168.20.41.60974 > 31.13.85.8.443: Flags [F.], seq 31, ack 1, win 317, options [nop,nop,TS val 1897135 ecr 880721575], length 0
10:42:14.530181 IP 192.168.20.41.39142 > 35.167.66.54.443: Flags [R.], seq 1803, ack 16526, win 601, options [nop,nop,TS val 1897136 ecr 753660136], length 0
10:42:14.543968 IP 31.13.85.8.443 > 192.168.20.41.60974: Flags [R], seq 4029123730, win 0, length 0

I am still working on it, still no luck. Two months with a brand new TV without local/WAN connection, really sad...

Thanks!

home-assistant / core

2019 LG TV with HomeKit and AirPlay 2 #25637