Transport endpoint is not connected

Configuration
1

After a reboot of HA i get this every minute in my ASUS RT-AC68U log:
Is it something wrong or something to worry about?

Sep 22 11:18:28 dropbear[7687]: Child connection from 192.168.1.85:46934
Sep 22 11:18:28 dropbear[7687]: Early exit: Failed socket address: Transport endpoint is not connected
Sep 22 11:18:28 login[7688]: root login on 'pts/0'
Sep 22 11:18:29 login[7694]: root login on 'pts/0'
Sep 22 11:20:00 login[7764]: root login on 'pts/0'
Sep 22 11:21:00 login[7812]: root login on 'pts/0'
Sep 22 11:21:03 dropbear[7829]: Child connection from 192.168.1.85:53364
Sep 22 11:21:03 dropbear[7829]: Early exit: Failed socket address: Transport endpoint is not connected
Sep 22 11:22:00 login[7865]: root login on 'pts/0'
Sep 22 11:23:01 login[7913]: root login on 'pts/0'
Sep 22 11:24:00 login[7960]: root login on 'pts/0'
Sep 22 11:24:03 dropbear[7977]: Child connection from 192.168.1.85:60066
Sep 22 11:24:03 dropbear[7977]: Early exit: Failed socket address: Transport endpoint is not connected
Sep 22 11:25:00 login[8010]: root login on 'pts/0'
Sep 22 11:26:00 login[8057]: root login on 'pts/0'
Sep 22 11:27:00 login[8104]: root login on 'pts/0'
Sep 22 11:27:03 dropbear[8121]: Child connection from 192.168.1.85:36416
Sep 22 11:27:03 dropbear[8121]: Early exit: Failed socket address: Transport endpoint is not connected
Sep 22 11:28:00 login[8154]: root login on 'pts/0'
Sep 22 11:29:00 login[8201]: root login on 'pts/0'
Sep 22 11:30:00 login[8248]: root login on 'pts/0'
Sep 22 11:30:02 dropbear[8265]: Child connection from 192.168.1.85:41180
Sep 22 11:30:03 dropbear[8265]: Early exit: Failed socket address: Transport endpoint is not connected
Sep 22 11:31:00 login[8298]: root login on 'pts/0'
Sep 22 11:32:00 login[8348]: root login on 'pts/0'
Sep 22 11:33:00 login[8472]: root login on 'pts/0'
Sep 22 11:33:03 dropbear[8495]: Child connection from 192.168.1.85:47872
Sep 22 11:33:03 dropbear[8495]: Early exit: Failed socket address: Transport endpoint is not connected
Sep 22 11:34:00 login[8528]: root login on 'pts/0'
Sep 22 11:35:00 login[8575]: root login on 'pts/0'
Sep 22 11:36:00 login[8622]: root login on 'pts/0'
Sep 22 11:36:03 dropbear[8639]: Child connection from 192.168.1.85:53028
Sep 22 11:36:03 dropbear[8639]: Early exit: Failed socket address: Transport endpoint is not connected
Sep 22 11:37:00 login[8672]: root login on 'pts/0'
Sep 22 11:38:00 login[8719]: root login on 'pts/0'
Sep 22 11:39:00 login[8766]: root login on 'pts/0'
Sep 22 11:39:03 dropbear[8781]: Child connection from 192.168.1.85:59676
Sep 22 11:39:03 dropbear[8781]: Early exit: Failed socket address: Transport endpoint is not connected
Sep 22 11:40:00 login[8816]: root login on 'pts/0'
Sep 22 11:41:00 login[8863]: root login on 'pts/0'
Sep 22 11:42:00 login[8917]: root login on 'pts/0'
Sep 22 11:42:03 dropbear[8934]: Child connection from 192.168.1.85:38338
Sep 22 11:42:03 dropbear[8934]: Early exit: Failed socket address: Transport endpoint is not connected
Sep 22 11:43:00 login[8967]: root login on 'pts/0'
Sep 22 11:44:00 login[9014]: root login on 'pts/0'
Sep 22 11:45:00 login[9061]: root login on 'pts/0'
Sep 22 11:45:03 dropbear[9067]: Child connection from 192.168.1.85:45334
Sep 22 11:45:03 dropbear[9067]: Early exit: Failed socket address: Transport endpoint is not connected
2

I found that error too.

I’m pretty sure its the nmap_tracker platform for the device tracker.

It looks like I stopped it by adding my router to the exclude list. Though maybe there’s a way to change the device tracker to just do a ping test instead of an nmap.

In the example below 192.168.11,192.168.0.22,192.168.0.33 are servers with proper logging that get cluttered up with the device scanner.

device_tracker:
    - platform: nmap_tracker
      interval_seconds: 300
      hosts: 192.168.0.0/24
      exclude:
        - 192.168.0.11
        - 192.168.0.22
        - 192.168.0.33