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]: Mismatched sequence numbers

See original GitHub issue

Client version

2.2.0.rc.2

Node version

16.16.0

Operating System type

Mac OS X

Operating system version

macOS Monterey 12.5.1

Describe the bug

I’m using the eufy-security plugin on Homebridge and I’m seeing the following issue in the log:

2022-08-31 17:54:34.068  DEBUG [Station.startLivestream] Sending start livestream command to station T8010T1321520EA2 for device T8113T9321523513 
2022-08-31 17:54:34.069  DEBUG [Station.startLivestream] Using CMD_SET_PAYLOAD for station T8010T1321520EA2 (main_sw_version: 3.1.9.0h) 
2022-08-31 17:54:34.070  DEBUG [P2PClientProtocol._sendCommand] Sending p2p command... 
{
  station: 'T8010T1321520EA2',
  sequence: 6,
  commandType: 1350,
  channel: 0,
  retries: 0,
  messageStatesSize: 2
}
2022-08-31 17:54:34.070  DEBUG [P2PClientProtocol._sendCommand] Sending p2p command... 
{
  station: 'T8010T1321520EA2',
  sequence: 7,
  commandType: 1045,
  channel: 0,
  retries: 0,
  messageStatesSize: 3
}
2022-08-31 17:54:34.083  DEBUG [P2PClientProtocol.handleMsg] Station T8010T1321520EA2 - DATA DATA - received from host 192.168.109.123:14596 - Processing sequence 5... 
2022-08-31 17:54:34.083  DEBUG [P2PClientProtocol.parseDataMessage] Station T8010T1321520EA2 - Received data 
{
  seqNo: 5,
  header: {
    commandId: 1350,
    bytesToRead: 132,
    channel: 0,
    signCode: 0,
    type: 1
  },
  bytesRead: 132,
  bytesToRead: 132,
  firstPartMessage: true,
  messageSize: 148
}
2022-08-31 17:54:34.085  DEBUG [P2PClientProtocol.handleData] Station T8010T1321520EA2 - Received data 
{
  commandIdName: 'CMD_SET_PAYLOAD',
  commandId: 1350,
  resultCodeName: 'ERROR_PPCS_NOT_INITIALIZED',
  resultCode: -1,
  message: '\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00',
  data: 'ffffffff0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000'
}
2022-08-31 17:54:34.086  DEBUG [P2PClientProtocol.handleData] Station T8010T1321520EA2 - dataType: DATA commandtype and sequencenumber different! 
{
  msg_sequence: 5,
  msg_channel: 1,
  msg_commandType: 1056,
  message: {
    commandId: 1350,
    bytesToRead: 132,
    channel: 0,
    signCode: 0,
    type: 1,
    seqNo: 5,
    dataType: 0,
    data: <Buffer ff ff ff ff 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ... 82 more bytes>
  }
}
2022-08-31 17:54:34.087  WARN [P2PClientProtocol.handleData] P2P protocol instability detected for station T8010T1321520EA2. Please reinitialise the connection to solve the problem! 
2022-08-31 17:54:34.088  DEBUG [P2PClientProtocol.handleMsg] Station T8010T1321520EA2 - DATA DATA - Received expected sequence (seqNo: 5 queuedData.size: 0) 
2022-08-31 17:54:34.089  DEBUG [P2PClientProtocol.handleMsg] Station T8010T1321520EA2 - ACK DATA - received from host 192.168.109.123:14596 for sequence 6 
2022-08-31 17:54:34.089  DEBUG [P2PClientProtocol.handleMsg] Station T8010T1321520EA2 - ACK DATA - received from host 192.168.109.123:14596 for sequence 7 
2022-08-31 17:54:34.836  DEBUG [P2PClientProtocol.handleMsg] Station T8010T1321520EA2 - DATA DATA - received from host 192.168.109.123:14596 - Processing sequence 6... 
2022-08-31 17:54:34.837  DEBUG [P2PClientProtocol.parseDataMessage] Station T8010T1321520EA2 -2022-08-31 17:54:34 Received data 
{
  seqNo: 6,
  header: {
    commandId: 1045,
    bytesToRead: 132,
    channel: 0,
    signCode: 0,
    type: 1
  },
  bytesRead: 132,
  bytesToRead: 132,
  firstPartMessage: true,
  messageSize: 148
}
2022-08-31 17:54:34.837  DEBUG [P2PClientProtocol.handleData] Station T8010T1321520EA2 - Received data 
{
  commandIdName: 'CMD_DEV_LED_SWITCH',
  commandId: 1045,
  resultCodeName: 'ERROR_PPCS_SUCCESSFUL',
  resultCode: 0,
  message: '\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00',
  data: '000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000'
}
2022-08-31 17:54:34.838  DEBUG [P2PClientProtocol.handleData] Station T8010T1321520EA2 - dataType: DATA commandtype and sequencenumber different! 
{
  msg_sequence: 6,
  msg_channel: 0,
  msg_commandType: 1350,
  message: {
    commandId: 1045,
    bytesToRead: 132,
    channel: 0,
    signCode: 0,
... (21 lines left)

I currently have six cameras and a doorbell, three + doorbell on one Homebase2, the other three on a second Homebase2.

To reproduce

Not sure how to reproduce as I’m using a library via the homebridge-eufy-security plugin.

Screenshots & Logfiles

No response

Additional context

No response

Issue Analytics

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

github_iconTop GitHub Comments

1reaction
cbwilliamsnhcommented, Sep 5, 2022

My bad!! I’ll check the log when I’m back at my computer and let you know.

1reaction
cbwilliamsnhcommented, Sep 2, 2022

Just sent you an invite to my outdoor cams. There are three as you’ll see. All of my cameras on both Homebase2 now show no response in the Home app. None of them are using RTP Streaming.

Read more comments on GitHub >

github_iconTop Results From Across the Web

01071be0:4: CMI Heartbeat Response <IP address> - AskF5
The Mismatched sequence numbers log occurs when the connection to the peer has been briefly interrupted (such as during the sync of a...
Read more >
cannot understand this "message sequence mismatch error"
The next step is to check the sequence number of the message against the currently expected sequence number. The application may provide its ......
Read more >
Sequence number mismatch and time schedule is too fast #20
Running the test applications shows a lot of error messages like: “dbc ... Sequence number mismatch The test app stopps after some seconds....
Read more >
IgnoreSeqNumberMismatch writes an AMQ9703 error ... - IBM
Enabling IgnoreSeqNumberMismatch allows a channel to start if it has a sequence number mismatch. However, the AMQ9703 error.
Read more >
Sequence mismatch when sender sends message before ...
I noticed one issue with the client , it sends a 35=A to the fix8 server & instead of waiting for a response,...
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

[Bug]: T8410 disconnects throughout the day

Next page

[Bug]: changing guard mode to HOME results in crash