[enhancement]: Ability to manually set RTSP transport type #181
Labels
Comments
|
Did you check this Road Map pages ? |
|
Hi @apollo316 this would be out of scope of this plugin. You could try and ask this question at eufy-security-client since this library is used to get the data from the cameras. However looking at that codebase I don't recall stumbling on a feature like that. Also I don't think that this is supported by eufy. |
|
Well with homebridge-camera-ffmpeg v3.1.4 in Homebridge and the following
config, my eufy camera's work just fine. But with the Eufy-security plugin
I get no feed from the cameras. Homekit has the camera's and they just spin
when trying to connect.
The debugging logs aren't terribly helpful, and I've done well over 30
Google searches for various "[error] method SETUP failed: 461 Unsupported
transport." I couldn't get them working in streaming/internet mode either,
though I prefer RTSP for local security. I've removed the cached device and
from homebridge entirely, and from Homekit on my device. I can pull up the
direct RTSP link in VLC, as well, without issue.
I've tried all the troubleshooting steps on the plugin page and the only
thing I can figure is it needs the TCP connection type. I'm at a loss on
this and had to disable the plugin for the time being but I was really
excited to have *actual* Eufy functions within Homekit. Please let me know
if you have any thoughts and thank you!
[image: image.png]
…On Tue, Oct 11, 2022 at 1:06 AM thieren ***@***.***> wrote:
Hi @apollo316 <https://github.com/apollo316>
this would be out of scope of this plugin.
You could try and ask this question at eufy-security-client
<https://github.com/bropat/eufy-security-client> since this library is
used to get the data from the cameras.
However looking at that codebase I don't recall stumbling on a feature
like that. Also I don't think that this is supported by eufy.
—
Reply to this email directly, view it on GitHub
<#181 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHDWPA7VPWWF772WEMHIS4LWCUGY7ANCNFSM6AAAAAARBVIY7A>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
Maybe I don't really get what you're trying to do. In principle the way that home bridge-camera-ffmpeg and this plugin utilise the stream are not that different. But I have to say that there were some changes made in the past. With home bridge-camera-ffmpeg you'll have to manually set the rtsp stream url. What are you setting there? I'd assume it is the exact same url that is used by this plugin. Where does TCP come into play? Apart from TCP being the default protocol for rtsp streams. I didn't check which is used for Dufts RTSP, but I'd assume it's the default. |
|
Thank you for the explanation! I'm just trying to use the Eufy-security
plugin to view the RTSP streams from my Eufy camera's. Where would I
"manually enter the RTSP stream URL" in the Eufy-security config? I have
the full URL from the Eufy app but I don't see a place to manually enter it
in the config, and when Homebridge launches it's automatically catching the
RTSP URL's and username/pw from the Eufy account login:
[image: image.png]
What it grabbed is correct, but in Homekit I just get a spinning wheel when
trying to launch the feed, the error in my last post, and then Connection
Error in Homekit.
…On Wed, Oct 12, 2022 at 10:55 PM thieren ***@***.***> wrote:
Maybe I don't really get what you're trying to do.
In principle the way that home bridge-camera-ffmpeg and this plugin
utilise the stream are not that different. But I have to say that there
were some changes made in the past.
With home bridge-camera-ffmpeg you'll have to manually set the rtsp stream
url. What are you setting there? I'd assume it is the exact same url that
is used by this plugin. Where does TCP come into play? Apart from TCP being
the default protocol for rtsp streams. I didn't check which is used for
Dufts RTSP, but I'd assume it's the default.
—
Reply to this email directly, view it on GitHub
<#181 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHDWPA2VWZNGUM64T3NTI2TWC6I25ANCNFSM6AAAAAARBVIY7A>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
Hi @apollo316 Sry for letting you wait so long. Did you figure it out in the meantime? If not: you don't have to input the rtsp url anywhere as (like you have observed) the plugin gets it automatically. So the question is why the streaming fails. For that I'd need the log files for a streaming attempt. Can you provide these? |
|
@thieren I get this problem too:
I support @apollo316 s request: Please allow adding the RTSP source. Use case: I use the rtsp-simple-server to proxy the eufy RTSP stream. This allows me to use the RTSP stream also in home-assistant, synology and co. |
|
Thx for your input and investigation in the matter. Am I getting it right that you'd want two additional options:
What exactly is the benefit of the second? Couldn't you just use the native rtsp stream from the cameras for all your smartphone software? |
|
@thieren thx for the summary. |
|
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the solution you'd like
Can we get the option in advanced to set RTSP transport type to TCP or UDP?
The text was updated successfully, but these errors were encountered: