Logs: 1784119323646.tar.gz
After a while, CubeOS stops playing video camera feeds in Docker. It only works for a few hours after a restart before failing again.
@Milk I am expected that something wouldn’t work, and you didn’t disappoint me again.
Thank you for your feedback and for uploading the logs. We’ve received them and passed the issue along to our technical team for investigation.
Since this involves video stream stability in a Docker environment, it may take some time to reproduce and pinpoint the root cause. We’ll analyze it thoroughly and work on a fix as quickly as we can.
We’ll keep you updated on any progress right here in this thread. Thanks again for your patience and support!
Hello, thank you for your patience and understanding. To help us locate the issue more quickly, we would appreciate it if you could provide the following information:
-
The device model running Docker CUBEOS, its architecture (e.g., x86_64, arm64), and the amount of RAM.
-
The network connection method: Ethernet or Wi‑Fi?
-
How the camera was added: via automatic scanning, or by manually entering the RTSP address?
I am using a Raspberry Pi 5, which is 64bit. The connection is a Gigabit 5E wired connection.
And the cameras were automatically detected during the device scan.
Additionally, after restarting Docker via sudo docker restart cubeos, the cameras run much more stably in the long run.
@Milk Yesterday, the mysterious eWeLink Smart Home add-on logged itself out, and the entire home automation system was down for a few hours.
The cameras running on CubeOS are dropping out again and are unusable. I am really fed up with being made a tester without my consent for updates that might or might not work. They keep repeating the same mistakes over and over; it’s only a matter of time before the entire Zigbee network fails again.
You’re just creating problems for me, and then I have to spend my free time going from house to house fixing the mess you’ve caused.
Hello, thank you for your feedback. We have reproduced the issue and are actively investigating it. To help us resolve it more quickly, could you please provide the following clarification:
When you mentioned that “eWeLink Smart Home add-on logged itself out,” were you referring to the built-in add-on or the legacy add-on? If it is the legacy one, please follow the instructions in the figure below to obtain the legacy add-on logs and send them to us via the iHost feedback feature or forum private message. If it is the built-in add-on, no further information is required from you.
We will keep you updated on our progress. Thank you for your patience.
It is eWeLink Smart Home.
Hello, @Jojkoba
Regarding the auto-logout issue with the Docker version of the Cube OS add-on, we would like to request the following information to help us locate the problem more quickly:
-
Does the “auto-logout” issue you are experiencing occur on the built-in add-on shown in the screenshot below? According to your description, you are running Cube OS via Docker on a Raspberry Pi, and that version does not include the Docker function menu. Therefore, we would like to confirm whether you are actually using the built-in add-on.
-
The log files you provided cover the time period from 07-11 04:00 to 07-15 13:00. Based on our initial analysis, we did not find any auto-logout events in the logs during this period, but we did notice multiple service restarts. Due to the system log size limitation, the logs related to auto-logout may have already been overwritten.
If the auto-logout issue occurs again, we recommend that you download a fresh log immediately and share it with us for further investigation.
Thank you for your understanding and support.
I am using the integrated plugin. The restarts occurred because the cameras in CubeOS stop working.