@Kyle
thanks. its not only related to samsung, i think its related to android 11 ... the push notification only works, when the app was recently open. after a longer period of standby its not pushing anymore until you open hikconnect... but its seems only on 4.15.1 not on 4.14.1 , what is really strange. i tried to complete purge all files which are related to hik connect, install 4.15.1 again and set the battery-settings all to manual (that it can control itself to start, start from other apps etc.) ... still no luck. its on pixel phone and samsung which i could test.
- another interesting problem... they made an update of some of the devices to run standalone WITHOUT a indoor station earlier. you cannot turn hikconnect p2p cloud on the outdoor station off, even if you have a indoor station connected. you have to manual block it in the router or change the server to a custom. not sure why the outdoor station needs internet,... if you have indoor stations you pair the indoor station with the app...
- the notification ringtone is really annoying. you can change the ringtone (or even the setting for vibrate) but it will change back on the next call to their own settings. i dont know why the app has even permission to do it
- another REALLY annoying bug is with the indoor stations. i already tried to reach out to hikvision, but they dont understand. i am lost in level1 support ...
i am using the DS-KH6320-WTE1 (but they should all the same) model as indoor ... it can use other cameras to show on display... this is really nice.. theoretical. hik claim that it has the ability to use any onvif camera. i already hook it up on a usb-ttl interface to see the debug log. its clearly a firmware bug.
1) if you add the onvif camera in the menu, it seems that port is set to "00", but you can not change it manually.
see here:
DEBUG LOG when trying to connect:
[CRIT][2021-06-28 16:37:25][net/ipc/ipcService/ipcamera.c #3728][@getTalkBackVideo]: *****videomsginfo streamtype=0, msgtype=2
[ERR][2021-06-28 16:37:25][ipc/talkBack/talkBackHikDevice.cpp #74][@openStreamingRtsp]: szPath []
[ERR][2021-06-28 16:37:25][ipc/talkBackStreaming.cpp #179][@init_rtsp_info]: port = 00\n
[ERR][2021-06-28 16:37:25][ipc/talkBack/talkBackHikDevice.cpp #79][@openStreamingRtsp]: init_rtsp_info error!
[ERR][2021-06-28 16:37:25][ipc/talkBack/talkBackHikDevice.cpp #130][@talkBack_openStreaming]: openStreamingRtsp error
[ERR][2021-06-28 16:37:25][ipc/talkBackApi.cpp #63][@talkBackOpenStreaming]: guiId=0
[ERR][2021-06-28 16:37:25][ipc/talkBackApi.cpp #71][@talkBackOpenStreaming]: open_streaming not success!
[ERR][2021-06-28 16:37:25][net/ipc/ipcService/ipcamera.c #3734][@getTalkBackVideo]: *****talkBackOpenStreaming ERROR*****0x10000
[ERR][2021-06-28 16:37:25][net/ipc/ipcService/ipcamera.c #3876][@talkBackVideoProcess]: getTalkBackVideo ERROR
[ERR][2021-06-28 16:37:25][ipc/talkBackApi.cpp #97][@talkBackCloseStream]: NULL == g_talkBackStreaming close error
2) you can export the ip cameras as an XML file in ivms 4200 , then change the port and import it again (there is no port setting in the normal menu when using onvif protocol... only when using HIK protocol) ...
BUT you cannot change the
PATH of the stream url... the indoor station tries to connect to "rtsp.//
username.password@ip.port/" ..
no onvif camera is using just /
see:
DEBUG LOG :
[CRIT][2021-06-28 16:40:56][net/ipc/ipcService/ipcamera.c #3728][@getTalkBackVideo]: *****videomsginfo streamtype=0, msgtype=2
[ERR][2021-06-28 16:40:56][ipc/talkBack/talkBackHikDevice.cpp #74][@openStreamingRtsp]:szPath []
Err:rtspc_create_session() :426:Connect end ,now have clients 1!
[ERR][2021-06-28 16:40:56][src/gui_oversee.c #920][@gui_oversee_handle_msg_vis_stream_error]: Receive vis_stream_error, the reason is:0x10c02, data:0, s_streamInfo.streamId:1
Err:start() :4978:Failed recv OPTIONS! 4,Protocol Error, [10]
Err:start() :5118: res is [0x10900][401], [10]
Err:start() :5123:[--------------------------------------------
RTSP SessionID : [10]
RTSP host : [192.168.0.55][554][][IPv4]
RTSP USR : [viewer]
RTSP transmode : [OVER][OPTIONS]
RTSP HB: [] RTCP: [yes]
RTSP Auto Reconnect : [yes] offtime[0]
Client status : [IDLE]
m_uCSeq : [3]
Session fd : [60] S[] timeout[30000]
Is quit : [no]
-----------------
IsNewVersion : [no]
]
Err:rtspc_start() :688:rtspc_start ERROR :,[10]
Err:rtspc_start() :691:RTSPC_ERROR! start rtsp client fail ret =0x10900, [10]
3) if you change the protocol to hikvision instead of onvif, you see how the log should look.
DEBUG LOG:
[CRIT][2021-06-28 16:52:43][net/ipc/ipcService/ipcamera.c #3728][@getTalkBackVideo]: *****videomsginfo streamtype=0, msgtype=1
[ERR][2021-06-28 16:52:43][ipc/talkBack/talkBackHikDevice.cpp #74][@openStreamingRtsp]: szPath [/streaming/channels/101]
Err:rtspc_create_session() :426:Connect end ,now have clients 1!
Err:start() :4978:Failed recv OPTIONS! 4,Protocol Error, [13]
Err:start() :5118: res is [0x10900][401], [13]
Err:start() :5123:[--------------------------------------------
RTSP SessionID : [13]
RTSP host : [192.168.0.55][554][/streaming/channels/101][IPv4]
RTSP USR : [viewer]
RTSP transmode : [OVER][OPTIONS]
RTSP HB: [] RTCP: [yes]
RTSP Auto Reconnect : [yes] offtime[0]
Client status : [IDLE]
m_uCSeq : [3]
Session fd : [63] S[] timeout[30000]
Is quit : [no]
-----------------
IsNewVersion : [no]
]
Err:rtspc_start() :688:rtspc_start ERROR :,[13]
Err:rtspc_start() :691:RTSPC_ERROR! start rtsp client fail ret =0x10900, [13]
[ERR][2021-06-28 16:52:44][ipc/talkBackStreaming.cpp #296][@start]: rtspc_start error! rtspHandle[13]
[ERR][2021-06-28 16:52:44][ipc/talkBack/talkBackHikDevice.cpp #92][@openStreamingRtsp]: Start error!
but if you want to use any other brand you are lost because you cannot change the szPath variable, which is the stream URL path.
4) there was an option in 1st gen devices to give a full stream URL which is still implemented in device firmware and ivms 4200. you can change the exported XML to connect to a URL, but you cannot give the username and password and if you use rtsp.//username.password@ it just wont work, because it will break the connection script of the device. the username and password variable is not used when using URL-Mode
DEBUG LOG:
[CRIT][2021-06-28 16:47:48][net/ipc/ipcService/ipcamera.c #3728][@getTalkBackVideo]: *****videomsginfo streamtype=0, msgtype=2
[ERR][2021-06-28 16:47:48][ipc/talkBack/talkBackHikDevice.cpp #74][@openStreamingRtsp]: szPath [rtsp://192.168.0.55:554/cam/realmonitor?channel=1&subtype=2&proto=Onvif]
Err:rtspc_create_session() :426:Connect end ,now have clients 1!
Err:updata_digest_authen() :2169:not get auth info
Err:start() :4978:Failed recv OPTIONS! 4,Protocol Error, [11]
Err:start() :5118: res is [0x10900][401], [11]
Err:start() :5123:[--------------------------------------------
RTSP SessionID : [11]
RTSP host : [192.168.0.55][554][rtsp://192.168.0.55:554/cam/realmonitor?channel=1&subtype=2&proto=Onvif][IPv4]
RTSP USR : []
RTSP transmode : [OVER][OPTIONS]
RTSP HB: [] RTCP: [yes]
RTSP Auto Reconnect : [yes] offtime[0]
Client status : [IDLE]
m_uCSeq : [3]
Session fd : [61] S[] timeout[30000]
Is quit : [no]
-----------------
IsNewVersion : [no]
]
Err:rtspc_start() :688:rtspc_start ERROR :,[11]
Err:rtspc_start() :691:RTSPC_ERROR! start rtsp client fail ret =0x10900, [11]
[ERR][2021-06-28 16:47:49][ipc/talkBackStreaming.cpp #296][@start]: rtspc_start error! rtspHandle[11]
only way out is to turn off the auth on the camera you want to use, but that is a not acceptable security flaw. if you do, it works fine... so the indoor monitor has the ability to see any rtsp stream (with h264 and max 720p) but the firmware is to buggy to do it the right way.