-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Yahka 1.0.9 problem with RTSP stream cameras #502
Comments
Do you have some log-entries you may post here? It may be easier to fix then. Thank you! |
Hey, still did not receive any logs yet. Do you have more information about the problem? Maybe I can create a test-stream to be able to even reproduce the problem. Thank you! |
Unfortunately, I don't have any log entries that capture the issue yet. The error occurs only after some time when using version 1.0.9. Are there any specific settings or additional debug options I could enable to gather more information? Thank you for your help! |
Here are the current log entries I have and it is still running: yahka.0 | 2024-12-03 12:41:24.911 | info | publishing camera Camera1 on 0.0.0.0 using avahi |
Hmm, you may enable the "debug" level for the adapter (go to instances and change the "level" from info to "debug). Thank you! |
Thanks! I'll enable the "debug" level and share more detailed logs as soon as the error occurs again. |
I encountered the issue again. I couldn't connect to the camera, and the log didn't show anything. On my iPhone, I got an error message saying that the camera was unavailable. On the second attempt, it worked, and the log showed the following: |
I have an issue with the Yahka 1.0.9 iobroker adapter. After some time, I can't access my RTSP stream cameras anymore. Restarting the Yahka adapter fixes it for a few hours, but the 1.0.3 version works fine. I have the latest FFmpeg version installed.
I don't think version 1.0.9 should be released as stable yet because of this issue. Is this a known problem? Anyone else experiencing this?
The text was updated successfully, but these errors were encountered: