rtsp stream command doesn't start stream #886
Closed
stratacorps
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
In testing I have found that, at least for the T8160 cameras and homebase the device command to start the rtsp stream isn't enough to actually get the stream started.
For example:
device.start_rtsp_livestream T8160XXXXXXXXXXXXX
eufy-security> { type: 'result', success: true, messageId: 'start_rtsp_livestream', result: {} } eufy-security> { type: 'event', event: { source: 'device', event: 'rtsp livestream started', serialNumber: 'T8160XXXXXXXXXXXX' } } eufy-security> { type: 'event', event: { source: 'device', event: 'command result', serialNumber: 'T8160XXXXXXXXXXXXXX', command: 'set_property', returnCode: 0, returnCodeName: 'ERROR_PPCS_SUCCESSFUL', customData: { property: { name: 'rtspStream', value: true } } } }
However, there is no data coming from the stream (Using VLC to test)
device.is_rtsp_livestreaming T8160.... gets the status as true:
{ type: 'result', success: true, messageId: 'is_rtsp_livestreaming', result: { serialNumber: 'T8160...', livestreaming: true } }
The work-around I have found that works comes from the behavior of the camera physically--that is, when I enabled RTSP on the camera there is a brief moment in time that the stream is started (I presume for testing if I were using a NAS client, etc.)
So, if I enable rtsp streaming with the above, and then immediately follow up with and wait for the async response of the
device.set_property T8160... rtspStream true
command, the stream is successfully started.
Am I doing something wrong or is this the expected behavior, or at least what everyone else is seeing.
Beta Was this translation helpful? Give feedback.
All reactions