Lightrun
question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[Bug]: T8410 disconnects throughout the day

See original GitHub issue

Client version

develop branch

Node version

v16.17.0

Operating System type

Linux

Operating system version

Dockerfile through eufy-security-client-ws

Describe the bug

According to my logging, the T8410 PT device disconnects numerous times throughout the day:

== THIS IS GMT+2 ==
2022-09-16 19:41:18.752 INFO  ---- EventPublisher - Publishing event: [type=STATION_DISCONNECTED,payload={serial_number=T8410PXXXXXXXXX}]
2022-09-16 19:41:23.831 INFO  ---- EventPublisher - Publishing event: [type=STATION_CONNECTED,payload={serial_number=T8410PXXXXXXXXX}]
2022-09-16 19:46:25.515 INFO  ---- EventPublisher - Publishing event: [type=STATION_DISCONNECTED,payload={serial_number=T8410PXXXXXXXXX}]
2022-09-16 19:46:31.572 INFO  ---- EventPublisher - Publishing event: [type=STATION_CONNECTED,payload={serial_number=T8410PXXXXXXXXX}]
2022-09-16 19:49:48.671 INFO  ---- EventPublisher - Publishing event: [type=STATION_DISCONNECTED,payload={serial_number=T8410PXXXXXXXXX}]
2022-09-16 19:49:53.713 INFO  ---- EventPublisher - Publishing event: [type=STATION_CONNECTED,payload={serial_number=T8410PXXXXXXXXX}]
2022-09-16 19:51:03.720 INFO  ---- EventPublisher - Publishing event: [type=STATION_DISCONNECTED,payload={serial_number=T8410PXXXXXXXXX}]
2022-09-16 19:51:08.957 INFO  ---- EventPublisher - Publishing event: [type=STATION_CONNECTED,payload={serial_number=T8410PXXXXXXXXX}]
2022-09-16 19:52:48.965 INFO  ---- EventPublisher - Publishing event: [type=STATION_DISCONNECTED,payload={serial_number=T8410PXXXXXXXXX}]
2022-09-16 19:52:54.044 INFO  ---- EventPublisher - Publishing event: [type=STATION_CONNECTED,payload={serial_number=T8410PXXXXXXXXX}]
2022-09-16 20:00:54.080 INFO  ---- EventPublisher - Publishing event: [type=STATION_DISCONNECTED,payload={serial_number=T8410PXXXXXXXXX}]
2022-09-16 20:00:59.124 INFO  ---- EventPublisher - Publishing event: [type=STATION_CONNECTED,payload={serial_number=T8410PXXXXXXXXX}]
2022-09-16 20:02:09.553 INFO  ---- EventPublisher - Publishing event: [type=STATION_DISCONNECTED,payload={serial_number=T8410PXXXXXXXXX}]
2022-09-16 20:02:14.645 INFO  ---- EventPublisher - Publishing event: [type=STATION_CONNECTED,payload={serial_number=T8410PXXXXXXXXX}]
(...)
2022-09-16 21:24:43.524 INFO  ---- EventPublisher - Publishing event: [type=STATION_DISCONNECTED,payload={serial_number=T8410PXXXXXXXXX}]
2022-09-16 21:24:48.718 INFO  ---- EventPublisher - Publishing event: [type=STATION_CONNECTED,payload={serial_number=T8410PXXXXXXXXX}]
2022-09-16 21:27:13.944 INFO  ---- EventPublisher - Publishing event: [type=STATION_DISCONNECTED,payload={serial_number=T8410PXXXXXXXXX}]
2022-09-16 21:28:19.056 INFO  ---- EventPublisher - Publishing event: [type=STATION_CONNECTED,payload={serial_number=T8410PXXXXXXXXX}]
2022-09-16 21:30:49.069 INFO  ---- EventPublisher - Publishing event: [type=STATION_DISCONNECTED,payload={serial_number=T8410PXXXXXXXXX}]
2022-09-16 21:30:54.114 INFO  ---- EventPublisher - Publishing event: [type=STATION_CONNECTED,payload={serial_number=T8410PXXXXXXXXX}]
2022-09-16 21:33:29.132 INFO  ---- EventPublisher - Publishing event: [type=STATION_DISCONNECTED,payload={serial_number=T8410PXXXXXXXXX}]
2022-09-16 21:33:59.215 INFO  ---- EventPublisher - Publishing event: [type=STATION_CONNECTED,payload={serial_number=T8410PXXXXXXXXX}]
2022-09-16 21:36:09.298 INFO  ---- EventPublisher - Publishing event: [type=STATION_DISCONNECTED,payload={serial_number=T8410PXXXXXXXXX}]
2022-09-16 21:37:16.058 INFO  ---- EventPublisher - Publishing event: [type=STATION_CONNECTED,payload={serial_number=T8410PXXXXXXXXX}]
2022-09-16 21:43:01.089 INFO  ---- EventPublisher - Publishing event: [type=STATION_DISCONNECTED,payload={serial_number=T8410PXXXXXXXXX}]
2022-09-16 21:43:06.164 INFO  ---- EventPublisher - Publishing event: [type=STATION_CONNECTED,payload={serial_number=T8410PXXXXXXXXX}]

I have captured logging of an two instances where this happened. Note that the first time it happens is around 19:24 hrs and the next time it happens is at 19:27 hrs. I don’t know if this is related to the develop branch and whether it is related to https://github.com/bropat/eufy-security-ws/issues/135

It appears to happen only to one device at a time. I own several T8410’s and during the day it was a different device than this one that keeps disconnecting.

== THIS IS GMT-0 ==
2022-09-16 19:24:43.516  WARN [P2PClientProtocol.sendPing] Station T8410PXXXXXXXXX - Heartbeat check failed. Connection seems lost. Try to reconnect... 
2022-09-16 19:24:43.519  INFO  [Station.onDisconnect] Disconnected from station T8410PXXXXXXXXX 
2022-09-16 19:24:43.522  DEBUG [Station.scheduleReconnect] Schedule reconnect to station T8410PXXXXXXXXX... 
{
  delay: 5000
}
2022-09-16 19:24:48.525  DEBUG [Station.connect] Connecting to station T8410PXXXXXXXXX... 
{
  p2pConnectionType: 'QUICKEST'
}
2022-09-16 19:24:48.527  DEBUG [P2PClientProtocol.renewDSKKey] Station T8410PXXXXXXXXX DSK keys not present or expired, get/renew it 
{
  dskKey: 'qwerty',
  dskExpiration: 2022-09-16T19:16:17.000Z
}
2022-09-16 19:24:48.528  DEBUG [HTTPApi.request] Request: 
{
  method: 'post',
  endpoint: 'v1/app/equipment/get_dsk_keys',
  token: '598a5a8436e498dae3af2f89e089dc880258ad281cdd015d',
  data: {
    invalid_dsks: {
      T8410PXXXXXXXXX: ''
    },
    station_sns: [
      'T8410PXXXXXXXXX'
    ],
    transaction: '1663356288528'
  }
}
2022-09-16 19:24:48.624  DEBUG [HTTPApi.request] Response: 
{
  response: {
    code: 0,
    msg: 'Succeeded.',
    data: {
      enabled: true,
      dsk_keys: [
        {
          station_sn: 'T8410PXXXXXXXXX',
          dsk_key: 'qwerty',
          expiration: 1663358088,
          about_to_be_replaced: false
        }
      ]
    }
  }
}
2022-09-16 19:24:48.626  DEBUG [P2PClientProtocol.getDSKKeys] Station T8410PXXXXXXXXX - Response: 
{
  code: 0,
  msg: 'Succeeded.',
  data: {
    enabled: true,
    dsk_keys: [
      {
        station_sn: 'T8410PXXXXXXXXX',
        dsk_key: 'qwerty',
        expiration: 1663358088,
        about_to_be_replaced: false
      }
    ]
  }
}
2022-09-16 19:24:48.628  DEBUG [undefined.<anonymous>] P2PClientProtocol.getDSKKeys(): dskKey: qwerty dskExpiration: Fri Sep 16 2022 19:54:48 GMT+0000 (Coordinated Universal Time) 
2022-09-16 19:24:48.629  DEBUG [P2PClientProtocol.localLookup] Trying to local lookup address for station T8410PXXXXXXXXX with host 192.168.x.x 
2022-09-16 19:24:48.646  DEBUG [P2PClientProtocol.handleMsg] Station T8410PXXXXXXXXX - LOOKUP_RESP - Got response 
{
  remoteAddress: '18.197.212.165',
  remotePort: 32100,
  response: {
    responseCode: 0
  }
}
2022-09-16 19:24:48.648  DEBUG [P2PClientProtocol.handleMsg] Station T8410PXXXXXXXXX - LOOKUP_ADDR - Got response 
{
  remoteAddress: '18.197.212.165',
  remotePort: 32100,
  response: {
    ip: 'X.X.X.X',
    port: 23728
  }
}
2022-09-16 19:24:48.650  DEBUG [P2PClientProtocol.handleMsg] Station T8410PXXXXXXXXX - QUICKEST - Try to connect to X.X.X.X:23728... 
2022-09-16 19:24:48.651  DEBUG [P2PClientProtocol._connect] Station T8410PXXXXXXXXX - CHECK_CAM - Connecting to host X.X.X.X on port 23728... 
2022-09-16 19:24:48.653  DEBUG [P2PClientProtocol.handleMsg] Station T8410PXXXXXXXXX - LOOKUP_ADDR - Got response 
{
  remoteAddress: '18.197.212.165',
  remotePort: 32100,
  response: {
    ip: '192.168.x.x',
    port: 23728
  }
}
2022-09-16 19:24:48.655  DEBUG [P2PClientProtocol.handleMsg] Station T8410PXXXXXXXXX - QUICKEST - Try to connect to 192.168.x.x:23728... 
2022-09-16 19:24:48.658  DEBUG [P2PClientProtocol._connect] Station T8410PXXXXXXXXX - CHECK_CAM - Connecting to host 192.168.x.x on port 23728... 
2022-09-16 19:24:48.660  DEBUG [P2PClientProtocol.handleMsg] Station T8410PXXXXXXXXX - LOOKUP_ADDR2 - Got response 
{
  remoteAddress: '18.197.212.165',
  remotePort: 32100,
  response: {
    ip: '52.58.242.75',
    port: 10000,
    data: '6b8ac0fe'
  }
}
2022-09-16 19:24:48.662  DEBUG [P2PClientProtocol.handleMsg] Station T8410PXXXXXXXXX - CHECK_CAM2 - Connecting to host 52.58.242.75 on port 10000... 
2022-09-16 19:24:48.667  DEBUG [P2PClientProtocol.handleMsg] Station T8410PXXXXXXXXX - received unknown message 
{
  remoteAddress: '18.197.212.165',
  remotePort: 32100,
  response: {
    message: 'f169008408000000000210274bf23a340000000000000000000210274bf23a340000000000000000000210274bf23a340000000000000000000210274bf23a340000000000000000000210274bf23a340000000000000000000210274bf23a340000000000000000000210274bf23a340000000000000000000210274bf23a340000000000000000',
    length: 136
  }
}
2022-09-16 19:24:48.702  DEBUG [P2PClientProtocol.handleMsg] Station T8410PXXXXXXXXX - CAM_ID - Connected to station T8410PXXXXXXXXX on host 192.168.x.x port 23728 
2022-09-16 19:24:48.705  INFO  [Station.onConnect] Connected to station T8410PXXXXXXXXX on host 192.168.x.x and port 23728 

2022-09-16 19:27:13.936  INFO  [Station.onDisconnect] Disconnected from station T8410PXXXXXXXXX 
2022-09-16 19:27:13.941  DEBUG [Station.scheduleReconnect] Schedule reconnect to station T8410PXXXXXXXXX... 
{
  delay: 5000
2022-09-16 19:27:13.935  WARN [P2PClientProtocol.sendPing] Station T8410PXXXXXXXXX - Heartbeat check failed. Connection seems lost. Try to reconnect... 
}
2022-09-16 19:27:18.943  DEBUG [Station.connect] Connecting to station T8410PXXXXXXXXX... 
{
  p2pConnectionType: 'QUICKEST'
}
2022-09-16 19:27:18.944  DEBUG [P2PClientProtocol.localLookup] Trying to local lookup address for station T8410PXXXXXXXXX with host 192.168.X.X 
2022-09-16 19:27:18.963  DEBUG [P2PClientProtocol.handleMsg] Station T8410PXXXXXXXXX - LOOKUP_RESP - Got response 
{
  remoteAddress: '18.197.212.165',
  remotePort: 32100,
  response: {
    responseCode: 0
  }
}
2022-09-16 19:27:18.964  DEBUG [P2PClientProtocol.handleMsg] Station T8410PXXXXXXXXX - LOOKUP_ADDR - Got response 
{
  remoteAddress: '18.197.212.165',
  remotePort: 32100,
  response: {
    ip: 'X.X.X.X',
    port: 23966
  }
}
2022-09-16 19:27:18.965  DEBUG [P2PClientProtocol.handleMsg] Station T8410PXXXXXXXXX - QUICKEST - Try to connect to X.X.X.X:23966... 
2022-09-16 19:27:18.966  DEBUG [P2PClientProtocol._connect] Station T8410PXXXXXXXXX - CHECK_CAM - Connecting to host X.X.X.X on port 23966... 
2022-09-16 19:27:18.967  DEBUG [P2PClientProtocol.handleMsg] Station T8410PXXXXXXXXX - LOOKUP_ADDR - Got response 
{
  remoteAddress: '18.197.212.165',
  remotePort: 32100,
  response: {
    ip: '192.168.X.X',
    port: 23966
  }
}
2022-09-16 19:27:18.968  DEBUG [P2PClientProtocol.handleMsg] Station T8410PXXXXXXXXX - QUICKEST - Try to connect to 192.168.X.X:23966... 
2022-09-16 19:27:18.969  DEBUG [P2PClientProtocol._connect] Station T8410PXXXXXXXXX - CHECK_CAM - Connecting to host 192.168.X.X on port 23966... 
2022-09-16 19:27:18.973  DEBUG [P2PClientProtocol.handleMsg] Station T8410PXXXXXXXXX - LOOKUP_ADDR2 - Got response 
{
  remoteAddress: '18.197.212.165',
  remotePort: 32100,
  response: {
    ip: '52.58.242.75',
    port: 10000,
    data: '6b8af77c'
  }
}
2022-09-16 19:27:18.976  DEBUG [P2PClientProtocol.handleMsg] Station T8410PXXXXXXXXX - CHECK_CAM2 - Connecting to host 52.58.242.75 on port 10000... 
2022-09-16 19:27:18.980  DEBUG [P2PClientProtocol.handleMsg] Station T8410PXXXXXXXXX - received unknown message 
{
  remoteAddress: '18.197.212.165',
  remotePort: 32100,
  response: {
    message: 'f169008408000000000210274bf23a340000000000000000000210274bf23a340000000000000000000210274bf23a340000000000000000000210274bf23a340000000000000000000210274bf23a340000000000000000000210274bf23a340000000000000000000210274bf23a340000000000000000000210274bf23a340000000000000000',
    length: 136
  }
}
2022-09-16 19:27:19.502  DEBUG [P2PClientProtocol.scheduleHeartbeat] Station T8410PXXXXXXXXX - Heartbeat disabled! 
2022-09-16 19:27:33.967  WARN [Timeout._onTimeout] Station T8410PXXXXXXXXX - Tried all hosts, no connection could be established 
2022-09-16 19:27:33.978  INFO  [Station.onTimeout] Timeout connecting to station T8410PXXXXXXXXX 
2022-09-16 19:27:33.982  DEBUG [Station.scheduleReconnect] Schedule reconnect to station T8410PXXXXXXXXX... 
{
  delay: 10000
}
2022-09-16 19:27:43.985  DEBUG [Station.connect] Connecting to station T8410PXXXXXXXXX... 
{
  p2pConnectionType: 'QUICKEST'
}
2022-09-16 19:27:43.985  DEBUG [P2PClientProtocol.localLookup] Trying to local lookup address for station T8410PXXXXXXXXX with host 192.168.X.X 
2022-09-16 19:27:44.003  DEBUG [P2PClientProtocol.handleMsg] Station T8410PXXXXXXXXX - LOOKUP_RESP - Got response 
{
  remoteAddress: '18.197.212.165',
  remotePort: 32100,
  response: {
    responseCode: 254
  }
}
2022-09-16 19:27:58.989  ERROR [Timeout._onTimeout] Station T8410PXXXXXXXXX - All address lookup tentatives failed. 
2022-09-16 19:27:58.990  INFO  [Station.onTimeout] Timeout connecting to station T8410PXXXXXXXXX 
2022-09-16 19:27:58.993  DEBUG [Station.scheduleReconnect] Schedule reconnect to station T8410PXXXXXXXXX... 
{
  delay: 20000
}
2022-09-16 19:28:18.996  DEBUG [Station.connect] Connecting to station T8410PXXXXXXXXX... 
{
  p2pConnectionType: 'QUICKEST'
}
2022-09-16 19:28:19.001  DEBUG [P2PClientProtocol.localLookup] Trying to local lookup address for station T8410PXXXXXXXXX with host 172.27.0.255 
2022-09-16 19:28:19.022  DEBUG [P2PClientProtocol.handleMsg] Station T8410PXXXXXXXXX - LOOKUP_RESP - Got response 
{
  remoteAddress: '18.197.212.165',
  remotePort: 32100,
  response: {
    responseCode: 0
  }
}
2022-09-16 19:28:19.024  DEBUG [P2PClientProtocol.handleMsg] Station T8410PXXXXXXXXX - LOOKUP_ADDR - Got response 
{
  remoteAddress: '18.197.212.165',
  remotePort: 32100,
  response: {
    ip: 'X.X.X.X',
    port: 44708
  }
}
2022-09-16 19:28:19.026  DEBUG [P2PClientProtocol.handleMsg] Station T8410PXXXXXXXXX - QUICKEST - Try to connect to X.X.X.X:44708... 
2022-09-16 19:28:19.028  DEBUG [P2PClientProtocol._connect] Station T8410PXXXXXXXXX - CHECK_CAM - Connecting to host X.X.X.X on port 44708... 
2022-09-16 19:28:19.031  DEBUG [P2PClientProtocol.handleMsg] Station T8410PXXXXXXXXX - LOOKUP_ADDR - Got response 
{
  remoteAddress: '18.197.212.165',
  remotePort: 32100,
  response: {
    ip: '192.168.X.X',
    port: 15922
  }
}
2022-09-16 19:28:19.033  DEBUG [P2PClientProtocol.handleMsg] Station T8410PXXXXXXXXX - QUICKEST - Try to connect to 192.168.X.X:15922... 
2022-09-16 19:28:19.035  DEBUG [P2PClientProtocol._connect] Station T8410PXXXXXXXXX - CHECK_CAM - Connecting to host 192.168.X.X on port 15922... 
2022-09-16 19:28:19.038  DEBUG [P2PClientProtocol.handleMsg] Station T8410PXXXXXXXXX - LOOKUP_ADDR2 - Got response 
{
  remoteAddress: '18.197.212.165',
  remotePort: 32100,
  response: {
    ip: '52.58.242.75',
    port: 10000,
    data: '6b8b0a21'
  }
}
2022-09-16 19:28:19.040  DEBUG [P2PClientProtocol.handleMsg] Station T8410PXXXXXXXXX - CHECK_CAM2 - Connecting to host 52.58.242.75 on port 10000... 
2022-09-16 19:28:19.044  DEBUG [P2PClientProtocol.handleMsg] Station T8410PXXXXXXXXX - received unknown message 
{
  remoteAddress: '18.197.212.165',
  remotePort: 32100,
  response: {
    message: 'f169008408000000000210274bf23a340000000000000000000210274bf23a340000000000000000000210274bf23a340000000000000000000210274bf23a340000000000000000000210274bf23a340000000000000000000210274bf23a340000000000000000000210274bf23a340000000000000000000210274bf23a340000000000000000',
    length: 136
  }
}
2022-09-16 19:28:19.046  DEBUG [P2PClientProtocol.handleMsg] Station T8410PXXXXXXXXX - CAM_ID - Connected to station T8410PXXXXXXXXX on host 192.168.X.X port 15922 
2022-09-16 19:28:19.048  INFO  [Station.onConnect] Connected to station T8410PXXXXXXXXX on host 192.168.X.X and port 15922

To reproduce

f

Screenshots & Logfiles

No response

Additional context

No response

Issue Analytics

  • State:closed
  • Created a year ago
  • Comments:7 (7 by maintainers)

github_iconTop GitHub Comments

1reaction
Palmkecommented, Nov 2, 2022

Still getting these disconnects. It went from 1/3 devices last week to all 3 devices this week. I think you should reject all the issues mentioning Station T8410PXXXXXXXXX - Tried all hosts, no connection could be established because it really is a eufy issue.

I’m getting timeouts when starting to stream, “network not available” notifications and just plain “Camera is offline” in the eufy Security app.

1reaction
Palmkecommented, Sep 21, 2022

Sent in a support request and I also see an additional report here: https://github.com/fuatakgun/eufy_security/issues/448 https://github.com/fuatakgun/eufy_security/issues/426

Perhaps it’s eufy server configuration causing problems.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Repeatedly disconnects throughout the day #5329 - GitHub
Issue Type: Bug I wish I knew. It started relatively recently. I start VSCode in windows and open one of my projects existing...
Read more >
[SOLVED] Internet Randomly Disconnects - Why and How to Fix
If your Internet randomly disconnects and reconnects, you have an issue with your network or ISP. Find out how to get stable Internet...
Read more >
5 Reasons Why Your Internet Keeps Disconnecting—and ...
The network cabling in your home can cause your internet connection to disconnect if it's damaged, loose, or configured poorly. Here's what to ......
Read more >
WiFi Keeps Disconnecting All The Time? Here's How To Fix It
A recent update created bugs that disrupt the WiFi connection; Power management issues; Poorly configured wireless adapter; Router is out of ...
Read more >
6 Reasons Your WiFi Keeps Disconnecting and How to Fix It
1. Too Many Devices Are Connected. Back in the day, the average household had a computer or two to connect. · 2. The...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found
Previous page

[Feature request]: Support for Eufy Starlight 4G (T8151)

Next page

[Bug]: Mismatched sequence numbers