AlexxIT
Problems with onvif source after v1.9.11
After updating to 1.9.11, three out of four cameras are currently working.
Original configuration:
streams:
input: “onvif://admin:[email protected]:8000?profile=IPCProfilesToken1&subtype=1&transport=tcp#audio=opus”
Unfortunately, this no longer works. No image.
Can you provide remote access to your camera? If you can, you can do it in Telegram PM.
The camera is a doorbell from Weber Protect, model Cardea. My older version is no longer sold; they are now on version 3.
The doorbell/camera does not have a web GUI, only an app where you can activate ONVIF.
I could pass port forwarding to the doorbell, but to be honest, that doesn't feel right to me.
I'm struggling with the same issue using a Vimtag 8310 cam. Let me know if you still need remote access.
@Shadow27374 I understand your concerns. You can continue to use the old version of go2rtc where onvif worked with your camera.
There are tens of thousands of brands in the world of cameras. The implementation of standards and protocols leaves much to be desired.
The latest release fixed a buggy protocol implementation from TP-Link - https://github.com/AlexxIT/go2rtc/pull/1589 At the same time, it continues to work with popular cameras Dahua, Reolink, OpenIPC.
Unless you're a programmer, I don't see a way to fix the problem without looking at the data being transmitted by the camera.
@bandeirad Yes, access is still required.
I have a fix. But I need to wait for @seydx to see if it works with broken TP-Link cameras.
I have a fix. But I need to wait for @seydx to see if it works with broken TP-Link cameras.
Unfortunately, I can no longer reproduce the "malformed response" problem with my Tapo cameras, which have received a firmware upgrade in the meantime.
And I didn't want to accept this PR. But @felipecrs talked me out of it :) And now several cameras have fallen off because of this. Even such a harmless decision has its consequences. But no worries. It will be fixed in the next version.
@AlexxIT, I apologize. I'm certainly not happy about that.
I would offer help fixing it, but I cannot reproduce the issue with any of my cameras. ONVIF source is still working for my two generic Tuya cameras of different models, one Dahua, and two Thingino-based.
I'm curious, and we'll see. maybe I'll overcome my mistrust.
I don't mean to be rude, but sharing cameras just doesn't feel right.
That is ok, you should indeed not trust random internet people.
Too bad we cannot do much unless we are able to reproduce the issue.
@felipecrs Don't worry. Everything's already been fixed. I just didn't have time to publish it.
It was actually quite interesting. And it shows that glitches aren't limited to TP-Link cameras.
can you publish the fix in the master version, that way we can confirm if onvif is fixed :D
There is no need to wait:
https://github.com/AlexxIT/go2rtc#go2rtc-dev-version
There is no need to wait:
https://github.com/AlexxIT/go2rtc#go2rtc-dev-version
How can I use this directly in Home Assistant? It looks like it's not for the add-on that can be obtained directly via HA.
The link I sent literally says there's an add-on variant called master you can use.
Or do you mean the WebRTC Camera integration?
Nice, i just added the (master) version on HA and feed is working again :) cheers
I didn't realize it right away... you can install this version separately from the old one via add-ons in HA.
I can say that my camera works again with the change, but another one doesn't. So I'm sticking with 1.9.10.
I just installed the official update via Home Assistant. My affected camera is working again, but another one is no longer working. I was able to control it via another RTSP stream, so I can still use it.
The old URL that no longer works was: “onvif://admin:@192.168.0.101?subtype=Profile1”. The new working URL is: “rtsp://admin:[email protected]:554/live.sdp”.
So there is still something wrong with ONVIF. If I can contribute logs, I would be happy to do so.
Strange, because I can't actually change anything in the ONVIF settings. There are four streams, two via ONVIF and two via RTSP. So my only options are four URLs. The RTSPs are working, so I don't have a problem at the moment.
If only I can do something about it, it would be cool to know what I should do.
I've already offered to grant access, but you don't want to grant it. Perhaps someday someone with a similar problem will come along and grant access.
Oh, that's what it's about. It sounded a little different.
Well, it was more intended as a help for others because I have my streams. But there's nothing more than logs, especially not with this camera. The other one was harmless. The other one would have been less private.