The Amcrest API is also used for their DVRs/NVRs. Assuming this the interface used by HA, adding an option to specify the channel number will allow us to use their NVRs as a source. If no channel is specified, the default channel of 1 is assumed.
I have not used a DVR/NVR as a stream source - but for camera’s you can specify the channel in the URL. I would think with NVR you can do the same thing.
should be something like:
rtsp://[username]:[password]@[IPaddress]:[port]/cam/realmonitor?channel=[channel]&subtype=[stream]
I found one forum where someone found they had to change the last & to a ?
rtsp://[username]:[password]@[IPaddress]:[port]/cam/realmonitor?channel=[channel]?subtype=[stream]
Since this is coming from the NVR - you might be able to leave the subtype off completely…
FWIW, I’ve been making a lot of enhancements to the amcrest component lately, and I have more on my to-do list. I’m aware of this type of request. E.g., I had a custom version of this component for a while that I and others have used, and I’ve had the same request relative to that. See here. If you look at that (and possibly other discussions on the topic), it’s not as straightforward as one might like. At least not from my perspective.
Of course others are free to make whatever enhancements they’d like, too. Just an FYI that I’m aware of the request, and if possible, I might try to add support for NVRs. The hardest part is I don’t happen to have one!
I gave up waiting on NVR support. Seems like it will take a while for devs because of complexity and low priority
I was able to get things going by setting my cameras as generic cameras. I dont have control and for whatever reason the snapshots do not work; however the new stream function works fine and I can do live views in cards with no problem