[Bug]: No video on Doorbell E340. #475
Description
Adapter version
v1.3.3
JS-Controller version
v20.19.0
Node version
v20.19.0
Operating System type
Linux
Operating system version
Debian 11.11 bullseye
Describe the bug
Hello Brobat,
First of all, thank you very much for all the work on the adapter.
After my first error message (#343), I got your adapter working with version 1.3.0. The doorbell control works flawlessly.
The video image also worked flawlessly; the URL was specified in the "Lifestream" object, and I was able to display the video image in my visualization.
So, everything's great.
However, for some time now, the video transmission has failed; no URL is entered in the "Lifestream" object. This is not the case when the video is started via the "StartStream" object or with the doorbell button.
For diagnostic purposes, I installed a new version of IoBroker on a Tinkerboard.
The go2rtc tool (see log file go2rtc_gestartet.txt) is running; the data under username and password match the configuration interface of the IoBroker adapter.
I've attached the adapter log in maximum mode and a capture file of the network traffic on the Tinkerboard interface.
The adapter log states that no video data is arriving from the camera. The tcpdump file shows that my network is working and transmitting UDP data to the adapter. I assume the P2P protocol is using UDP, is that correct?
I get the same behavior when I install Home Assistant and use your adapter there.
However, the video works flawlessly with the EUFY app on my tablet. So it's not a doorbell problem.
BS: Debian 11.11 bullseye
Node: v20.19.0
Nodejs: v20.19.0
IoBroker: v7.6.3
eusec.0: v1.3.3
Eufy Doorbell: 3.1.2.4 22.02.2025
To reproduce
- Go to eusec.0.T8214510xxxxxxxx.cameras.T8214510xxxxxxxx.start_stream
- Change Object startStream to true
- Look in the Object eusec.0.T8214510xxxxxxxx.cameras.T8214510xxxxxxxx.livestream
- object "livestream" is emty
Screenshots & Logfiles
Additional context
No response
P.S. The message about the firmware update on February 22, 2025 (3.1.2.4) fits in here. It's possible that the adapter isn't able to handle the firmware. Does anyone have the adapter running with this firmware?