[Bug]: eufy-security-ws not communicating with integration HomeAssistant

[Ascariota]

Version

1.8.0-2

Node version

not found

Operating System type

Linux

Operating system version

Core 2024.7.2 Operating System 12.4

Describe the bug

Hello,

I see updated information in the eufy-security-ws logs. There is a 2 hour difference between the displayed time and the real time (probably UTC). But on the other hand in the Eufy Security integration the camera previews are never updated. Strangely if I have an alert on the doorbell I have the ringing information, so part of the communication goes through. If I restart the WS I have a new updated image from the camera.

Material: T8134 + T8030 + T8210

Can you help me ?

My logs

2024-07-19 08:40:34.923 DEBUG   eufy-security-ws:eufy-security-client   [p2p] [P2PClientProtocol.handleDataControl] Station Handle DATA CONTROL - CMD_NOTIFY_PAYLOAD {
  stationSN: 'T8030P2323******',
  payload: '{"cmd":1307,"payload":{"cmd":11001,"version":127,"mIntRet":0,"msg":"","old_storage_label":"","cur_storage_label":"","body":{"body_version":1,"storage_days":216,"storage_events":41405,"con_video_hours":0,"format_transaction":"","format_errcode":0,"hdd_info":{"serial_number":"50026B775409B4C3","disk_path":"/dev/sda","disk_size":122880,"system_size":2099,"disk_used":60135,"video_used":54515,"video_size":105937,"cur_temperate":43,"parted_status":1,"work_status":0,"hdd_label":"hdd_157CDA432ED504F970B534445AA954D3","health":0,"device_module":"KINGSTONSV300S37A120G","hdd_type":1},"move_disk_info":{"disk_path":"","disk_size":0,"disk_used":0,"part_layout_arr":[],"data":[]},"emmc_info":{"disk_nominal":0,"disk_size":15974,"system_size":3158,"disk_used":2923,"data_used_percent":19,"swap_size":2048,"video_size":10328,"video_used":22,"data_partition_size":12932,"eol_percent":1,"work_status":0,"health":0}}}}\x00":204'
}
2024-07-19 08:40:34.924 DEBUG   eufy-security-ws:eufy-security-client   [p2p] [P2PClientProtocol.handleDataControl] Handle DATA CONTROL - CMD_NOTIFY_PAYLOAD StorageInfo HB3 update {
  stationSN: 'T8030P23******',
  body: {
    body_version: 1,
    storage_days: 216,
    storage_events: 41405,
    con_video_hours: 0,
    format_transaction: '',
    format_errcode: 0,
    hdd_info: {
      serial_number: '50026B7754******',
      disk_path: '/dev/sda',
      disk_size: 122880,
      system_size: 2099,
      disk_used: 60135,
      video_used: 54515,
      video_size: 105937,
      cur_temperate: 43,
      parted_status: 1,
      work_status: 0,
      hdd_label: 'hdd_157CDA432ED504F970B534445AA954D3',
      health: 0,
      device_module: 'KINGSTONSV300S37A120G',
      hdd_type: 1
    },
    move_disk_info: {
      disk_path: '',
      disk_size: 0,
      disk_used: 0,
      part_layout_arr: [],
      data: []
    },
    emmc_info: {
      disk_nominal: 0,
      disk_size: 15974,
      system_size: 3158,
      disk_used: 2923,
      data_used_percent: 19,
      swap_size: 2048,
      video_size: 10328,
      video_used: 22,
      data_partition_size: 12932,
      eol_percent: 1,
      work_status: 0,
      health: 0
    }
  }
}
2024-07-19 08:40:34.926 DEBUG   eufy-security-ws:eufy-security-client   [p2p] [P2PClientProtocol.handleMsg] Received message - DATA CONTROL - Processing sequence 84... {
  stationSN: 'T8030P232******',
  remoteAddress: '10.0.4.27',
  remotePort: 19522,
  dataType: 'CONTROL',
  seqNo: 84
}
2024-07-19 08:45:27.332 DEBUG   eufy-security-ws:eufy-security-client   [push] [PushClient.sendHeartbeat] Push client - Sending heartbeat... {
  streamId: 12
}
2024-07-19 08:45:27.333 DEBUG   eufy-security-ws:eufy-security-client   [push] [PushClient.buildHeartbeatPingRequest] Push client - heartbeatPingRequest {
  streamId: 12,
  request: '{"last_stream_id_received":12}'
}
2024-07-19 08:45:27.354 DEBUG   eufy-security-ws:eufy-security-client   [push] [PushClient.handleHeartbeatAck] Push client - Heartbeat acknowledge {
  message: '{"tag":1,"object":{"lastStreamIdReceived":12}}'
}

To reproduce

1. Go to '...'
2. Click on '...'
3. Scroll down to '....'
4. See error

Screenshots & Logfiles

No response

Additional context

No response

[bropat]

Wrong repo. Ask here;