-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
[Config Support]: RTMP stream nog working #5002
Comments
Your config looks incorrect cameras:
voortuin:
ffmpeg:
inputs:
- path: rtsp://name:[email protected]:554/h264Preview_01_sub
roles:
- detect
- path: rtsp://name:[email protected]:554/h264Preview_01_main
roles:
- record
- rtmp
detect:
width: 3840
height: 2160
fps: 5
you are using the sub stream and yet you are telling frigate to scale that stream up to 4k, that is entirely incorrect. also for the RTMP issue we need logs otherwise there is no way to help |
My bad. I corrected this.
|
Please provide frigate logs |
Quite new here so need some help.
were can i find these logs?, or do you mean something else? |
Your config post says you're running the addon so just go to the add on and there will be a button to view logs. |
Thanks. Found it i ques.
|
No those are diagnostics from the integrations setting we are looking for logs from the addons. |
That's expected given that one is streaming and one isn't. |
|
Have you enabled port 5000 and port 1935 in the addon configuration? |
It has been working flawlesly for months. Just added a second camera and it stopped. Even in the frigate dashboard they both don't show live feed. I don't know if that's normal?. |
what do you mean by that? |
that is how frigate works, you have to click on the camera to view the live feed.
so to be clear you selected HA addon as your install method but that is incorrect which is what caused the confusion |
the frigate integration is required for watching the live stream. The frigate integration now shows logs saying it is unable to connect to your frigate instance so you will need to figure out why. Maybe the IP is wrong |
addon and integration are two completely different things.
yes, and based on the logs this is because it can't find frigate where you are telling it to look, so something is incorrect
|
Alright. So i'm simply going to restore my LXC with frigate on it to a backup when it was working. |
I think all of this would be more helpful if you had the actual frigate logs from the LXC |
Alright. So my restore fixed it. |
This is my original config. Did i mess something up when adding the second one?
|
Nothing is immediately obvious but logs would make it clear. |
I don't know I don't use proxmox and am not familiar with it but I imagine logs should be quite accessible. I found https://linuxcontainers.org/lxc/manpages/man1/lxc-monitor.1.html |
Wow. I've forgot about portainer. It's getting nuts: [2023-01-10 21:38:57] ffmpeg.achtertuin.record_rtmp ERROR : [flv @ 0x55b080bca700] Video codec hevc not compatible with flv |
Your camera is h.265 which is not compatible with the rtmp restream You should disable it. In the next version of frigate (0.12, currently in beta) we are moving to a new restream that uses rtsp for this and many other reasons. |
How can i disable this?. |
That's probably a separate issue given that the integration said it couldn't connect to frigate at all. You disable with rtmp:
enabled: false |
Turned it off and portainer is running normal now. |
Yes reolink may still send h265, once you update to 0.12 can use the new restream with that without issue. Seems this can be closed now, feel free to create a new issue if something else comes up |
Describe the problem you are having
The RTMP stream has always been working fine.
Recently i updated Frigate to the latest version and added a second camera.
After one of those changes the Home Assistant stream is just a still image. Even after restarting everything.
Version
0.11.1-2eada21
Frigate config file
Relevant log output
Frigate stats
No response
Operating system
Proxmox
Install method
HassOS Addon
Coral version
USB
Any other information that may be helpful
No response
The text was updated successfully, but these errors were encountered: