New RCA HSDB2A 3MP Doorbell IP Camera

[jacha]

What Doorbell camera model are you using? What is the hardware and firmware version that you have installed?

The firmware has to have the ability to do ONVIF and I enabled that with the Batch Configuration program. Off the shelf some firmware is documented already to include ONVIF.

IE: Here have a Nelly DB with Hikvision firmware installed on it as noted in my sig.

You have to use the older build of Batch Configuration to make this work. Noticed that the newer version did not work.

I am using Batch Configuration V3.0.26 from 2019. Will post it on my MS Drive with a link to it.

Microsoft OneDrive

1drv.ms

You see that in the picture, DS-HD1 5.2.4 build 211101
Can you downgrade the firmware on the doorbell?

 

[David L]

You see that in the picture, DS-HD1 5.2.4 build 211101
Can you downgrade the firmware on the doorbell?

Not sure how you got the EZVIZ (DB1) firmware build 211011 since you have the DS-HD1, The EZVIZ firmware does Not support ONVIF, that is your problem. You need to be running the latest Hikvision firmware build 200321:

This is our chart from our 101:

FIRMWARE LIST (DOWNLOAD LINKS INCLUDED):

DOORBELL MODEL	PREVIOUS FIRMWARE	LATEST FIRMWARE	ONVIF	ALEXA	GOOGLE	OUTDOOR BELL SOUND (ON/OFF)	MOTION DETECTION CONFIGURABLE
HIKVISION (DS-HD1)	191017	200321 (2020-03-31)	YES	NO	NO	???	YES
RCA (HSDB2A)	180809 (????-??-??), 180703 (????-??-??)	190124 (2019-01-30)	NO	NO	NO	NO
EZVIZ (DB1)	191211 (2020-01-05), 190708 (2019-07-21), 190304 (????-??-??), 181024 (????-??-??), 200904 (2020-10-21) US Firmware, 200220 (2020-04-02) EUR Firmware	211011 (2021-11-01)	NO	YES	YES	YES	NO
LAVIEW (LV-PDB1630-U)	190103 (????-??-??)	190716 (2019-07-29)	YES	YES	NO	NO	NO
NELLY'S (NSC-DB2)	190122 (2019-03-04), 190412 (2019-??-??), 190625 (2019-06-25)&(2019-11-22)	191216 (2019-12-16)	YES	NO	NO	NO
LTS (LTH-7132-WIFI)		??????	???	???	???	???	???

Click on the 200321 link to download the .dav file and use the Batch Config Tool to change your firmware...Make sure you have a good WiFi connection...

Noticed you are in Sweden, this is a US firmware fyi, not sure if it matters. If you don't mine me asking how did you get your DS-HD1, we mainly see EZVIZ DBs here on the Forum/Thread from Europe.

 

[pete_c]

@jacha

What is the model number of your NVR?

BTW here using Opex combo PIR / Cameras modified with Hikvision POE Camera boards. The camera is very old and has weathered fine and very modular.

Very stealthy and looks like an oversized PIR. I put 5MP 38mm board inside. Using two catxx cables to it. It has an out door analog PIR, night dark sensor and case sensor going to the alarm panel. Plus can add a geophone sensor to it.

 

[jacha]

Not sure how you got the EZVIZ (DB1) firmware build 211011 since you have the DS-HD1, The EZVIZ firmware does Not support ONVIF, that is your problem. You need to be running the latest Hikvision firmware build 200321:

This is our chart from our 101:

FIRMWARE LIST (DOWNLOAD LINKS INCLUDED):

DOORBELL MODEL	PREVIOUS FIRMWARE	LATEST FIRMWARE	ONVIF	ALEXA	GOOGLE	OUTDOOR BELL SOUND (ON/OFF)	MOTION DETECTION CONFIGURABLE
HIKVISION (DS-HD1)	191017	200321 (2020-03-31)	YES	NO	NO	???	YES
RCA (HSDB2A)	180809 (????-??-??), 180703 (????-??-??)	190124 (2019-01-30)	NO	NO	NO	NO
EZVIZ (DB1)	191211 (2020-01-05), 190708 (2019-07-21), 190304 (????-??-??), 181024 (????-??-??), 200904 (2020-10-21) US Firmware, 200220 (2020-04-02) EUR Firmware	211011 (2021-11-01)	NO	YES	YES	YES	NO
LAVIEW (LV-PDB1630-U)	190103 (????-??-??)	190716 (2019-07-29)	YES	YES	NO	NO	NO
NELLY'S (NSC-DB2)	190122 (2019-03-04), 190412 (2019-??-??), 190625 (2019-06-25)&(2019-11-22)	191216 (2019-12-16)	YES	NO	NO	NO
LTS (LTH-7132-WIFI)		??????	???	???	???	???	???

Click on the 200321 link to download the .dav file and use the Batch Config Tool to change your firmware...Make sure you have a good WiFi connection...



Noticed you are in Sweden, this is a US firmware fyi, not sure if it matters. If you don't mine me asking how did you get your DS-HD1, we mainly see EZVIZ DBs here on the Forum/Thread from Europe.

It came in the hikvison app that an update was avaible. So I updated from the hikvison app.

And i got build 211101 not ezviz 211011

 

[pete_c]

Personally I would use the Hikvision firmware that I have on mine as it has worked now fine for about a year or so. (its in my signature)

NOTE here started with a Nelly DB1 doorbell which is the same hardware as RCA, EZViz, et al.

V5.2.4 HikVision FW build 200321

I know for a fact that the newest Hikvision Batch Configuration program doesn't have the features of the one that I posted so do not use the new one...used the old one I posted. Hopefully you can downgrade to the above mentioned firmware using the old Batch Configuration (2019) program. The new one doesn't include the ONVIF stuff.

BTW this is my first venture to a Wireless camera as I am not a wireless camera person and I dislike using wireless for media or automation. I am old school here.

 

[David L]

It came in the hikvison app that an update was avaible. So I updated from the hikvison app.

And i got build 211101 not ezviz 211011

Sorry I did not look close enough, so apparently there is a DS-HD1 newer firmware version, 211101. I am trying to see if it is out there but from the US site it still has the older version from April 1, 2020



Same File Size / Date:


I tried the EU Site but no luck.

 

[David L]

It came in the hikvison app that an update was avaible. So I updated from the hikvison app.

And i got build 211101 not ezviz 211011

So here is the previous version:

 

[David L]

I believe this is where I got it

Access Control and Intercom

By downloading the firmware from this web page you are agreeing to Hikvision's Software User License Agreement.Please be aware that Hikvision products are region-specific and regionally supported. If you have purchased your Hikvision products from an online source or unauthorized distributor...

us.hikvision.com

But it only has the older firmware 200321 available...

 

[jacha]

I believe this is where I got it

Access Control and Intercom

By downloading the firmware from this web page you are agreeing to Hikvision's Software User License Agreement.Please be aware that Hikvision products are region-specific and regionally supported. If you have purchased your Hikvision products from an online source or unauthorized distributor...

us.hikvision.com

But it only has the older firmware 200321 available...

Thank you how do I downgrade?

 

[pete_c]

With the above linked OLD Hikvision Batch Configuration program.

Microsoft OneDrive

1drv.ms

See attached image.

System==> System Maintainance ==> Remote Upgrade ==> Select Type: Upgrade File==> Select File ==> pick the downloaded firmware.



Here is the Windows ONVIF manager. Note it locks up and does not work well with the Hikvision Doorbell.

It will see the camera fine. BUT you cannot change the mobile application stuff that is built in to the camera with this application.

ONVIF Device Manager

Personally here have disconnected the doorbell from the cloud app and removed the cloud app on my Android phone. I use only VPN to access the camera at home and the old Hikvision Mobile app which direct connects to the DB and sees the recordings on the SD card.

 

[gnuB]

For those of you using the GuardingVision or Hik-Connect app, have you ever run into an issue where you cannot play video notifications from bell presses?




I have rebooted my NVR as someone elsewhere on forum notes but it did not solve the issue. The db has micro sd card but I have the feed going to NVR so I can review footage there but I’d still like to be able to review db presses in the cloud app.

 

[pete_c]

I see the same exact message VPNing to my DB via Android IVMS4500. This is with a JPG connection to my touchscreens, RTSP to Zoneminder and to Blue Iris.

I am not using the cloud app here on my Android phone.

A DB reboot will solve the issue temporarily.

 

[gnuB]

I see the same exact message VPNing to my DB via Android IVMS4500. This is with a JPG connection to my touchscreens, RTSP to Zoneminder and to Blue Iris.

I am not using the cloud app here on my Android phone.

A DB reboot will solve the issue temporarily.

I wonder what it is that causes this issue.

 

[pete_c]

Could be that the firmware is caching a few sessions and not releasing them. I have never seen an issue like this until I used a WiFi Doorbell Video Camera.

 

[pete_c]

@gnuB

Tinkering today based on:

What is RTSP?

RTSP performance
Fetching the RTSP stream from a security camera or recorder involves transcoding the native stream. This transcoding not only has a CPU overhead on the device you are fetching the stream from, it introduces a delay or lag in the video stream. While IP cameras are not lag-free when compared to real-time live action, RTSP increases that lag.

and inability to capture streams as demonstrated above.

WAP utilized - Ruckus - dedicated SSID set to using 2.4Ghz radio only.

Tool used:

Hikvision Batch Configuration V3.0.23 (2018-2019)

NOTE: originally used this version of Batch Configuration to enable ONVIF on Hikvision Firmware in sig.

Using Onvif device manager (2016) there are a number of settings that I cannot change. Specifically mobile settings. Not recommended.

Video Doorbell utilized: Nelly's Security NSC-DB2 NDB313-W V5.2.4 HikVision FW build 200321

1 - unregistered DB from cloud app and removed cloud app from Android V.11 smart phone * using Hikvision iVMS 4500 + OpenVPN client to OpenVPN server running on Firewall (PFSense).
2 - 24/7 RTSP streaming connection to Zoneminder and Blue Iris and on demand Monocle reverse proxy connection (for Amazon Alexa). Note Monocle is slow with Amazon Alexa Show.
3 - 24/7 JGP snapshot connection to Windows embedded touchscreens

4 - Batch Configuration settings - test and saved configuration from default. (will follow up continuing this post)


Android 11 Hikvision iVMS 4500 - tested December 21, 2021 -

• • tested locally and via VPN to Doorbell - no longer connects - there are historical videos saved from app which I can see - it did work.
  • works fine with 3 other testing Hikvision camera boards

Android 11 zmNinja - works fine with connection to Zoneminder locally and via VPN - tested December 21, 2021

Android 11 Leviton Snaplink (for Windows, Android or iOS)- video works fine with JPG connection to Doorbell camera - locally and via VPN - tested December 21, 2021

Ubuntu-Windows VLC - RTSP video works fine locally and via VPN - tested December 21, 2021

Android 11 Blue Iris App - used via VPN -

 

[gnuB]

@gnuB

Tinkering today based on:

What is RTSP?

RTSP performance
Fetching the RTSP stream from a security camera or recorder involves transcoding the native stream. This transcoding not only has a CPU overhead on the device you are fetching the stream from, it introduces a delay or lag in the video stream. While IP cameras are not lag-free when compared to real-time live action, RTSP increases that lag.

and inability to capture streams as demonstrated above.

WAP utilized - Ruckus - dedicated SSID set to using 2.4Ghz radio only.

Tool used:

Hikvision Batch Configuration V3.0.23 (2018-2019)

NOTE: originally used this version of Batch Configuration to enable ONVIF on Hikvision Firmware in sig.

Using Onvif device manager (2016) there are a number of settings that I cannot change. Specifically mobile settings. Not recommended.

Video Doorbell utilized: Nelly's Security NSC-DB2 NDB313-W V5.2.4 HikVision FW build 200321

1 - unregistered DB from cloud app and removed cloud app from Android V.11 smart phone * using Hikvision iVMS 4500 + OpenVPN client to OpenVPN server running on Firewall (PFSense).
2 - 24/7 RTSP streaming connection to Zoneminder and Blue Iris and on demand Monocle reverse proxy connection (for Amazon Alexa)
3 - 24/7 JGP snapshot connection to Windows embedded touchscreens

4 - Batch Configuration settings - test and saved configuration from default. (will follow up continuing this post)

I’m using Camect in addition to NVR so I’m going to do some testing this week to see if this is what is causing my issue. I’ve been running this setup for several months and this issue only started happening recently.

 

[pete_c]

Just noticed that the Android Hikvision iVMS 4500 app does not work any more with the Doorbell. It works fine with 3 other Hikvision cameras on the network. The Hikvision iVMS 4500 app was working fine with the doorbell.

 

[john5788]

I have an RCA doorbell and it had firmware 190124 on it. I used Batch Configurator 3.0.2.6 to update the firmware with the latest hikvision 200321. This ended up in a brick.

No fear, I read that bricks can be recovered. I soldered my serial connection and powered the device on with terminal listening and I was able to see the device. CTRL+U to break the autoboot and with sdcard contents digicap.dav, which was just a renamed hikvision firmware, I issued the format and update command. Device seemed to be ok, but upon reboot the red LEDs were still on and my terminal was looping this:

[WIFI]exec_app_msg-1202 conf_type 6
[WIFI*dbg]wifi_mgmt_handle_msg-982: msg->msg_type(0)
wlan_sta_sel_ap-778: conn_ap_id -1 id 0
wlan_sta_sel_ap-790: fail, please add ap 0 first!
[WIFI]wifi_mgmt_handle_msg-1117: msg->app_conf.conf_type 6 ret -2
exec_app_msg-1231: wifi_msg_t(conf_type 6) ret -2
w_sta_sel_ap_again-1421: exec_app_msg(STA_SEL_AP) ret -2
[WIFI]timeout_sta_sel_ap-163 w_sta_sel_ap_again (ap_id 0) ret -2

[WIFI]wifi_mgmt_thread_func-1153 to rt_timer_start(&(timer_sta_sel_ap[0]))
timeout_sta_sel_ap-157: enter
w_sta_sel_ap_again-1413: enter

[WIFI]exec_app_msg-1202 conf_type 6
[WIFI*dbg]wifi_mgmt_handle_msg-982: msg->msg_type(0)
wlan_sta_sel_ap-778: conn_ap_id -1 id 0
wlan_sta_sel_ap-790: fail, please add ap 0 first!
[WIFI]wifi_mgmt_handle_msg-1117: msg->app_conf.conf_type 6 ret -2
exec_app_msg-1231: wifi_msg_t(conf_type 6) ret -2
w_sta_sel_ap_again-1421: exec_app_msg(STA_SEL_AP) ret -2
[WIFI]timeout_sta_sel_ap-163 w_sta_sel_ap_again (ap_id 0) ret -2

[WIFI]wifi_mgmt_thread_func-1153 to rt_timer_start(&(timer_sta_sel_ap[0]))
no ap cfg
timeout_sta_sel_ap-157: enter
w_sta_sel_ap_again-1413: enter

[WIFI]exec_app_msg-1202 conf_type 6
[WIFI*dbg]wifi_mgmt_handle_msg-982: msg->msg_type(0)
wlan_sta_sel_ap-778: conn_ap_id -1 id 0
wlan_sta_sel_ap-790: fail, please add ap 0 first!
[WIFI]wifi_mgmt_handle_msg-1117: msg->app_conf.conf_type 6 ret -2
exec_app_msg-1231: wifi_msg_t(conf_type 6) ret -2
w_sta_sel_ap_again-1421: exec_app_msg(STA_SEL_AP) ret -2
[WIFI]timeout_sta_sel_ap-163 w_sta_sel_ap_again (ap_id 0) ret -2

[WIFI]wifi_mgmt_thread_func-1153 to rt_timer_start(&(timer_sta_sel_ap[0]))
timeout_sta_sel_ap-157: enter
w_sta_sel_ap_again-1413: enter

[WIFI]exec_app_msg-1202 conf_type 6
[WIFI*dbg]wifi_mgmt_handle_msg-982: msg->msg_type(0)
wlan_sta_sel_ap-778: conn_ap_id -1 id 0
wlan_sta_sel_ap-790: fail, please add ap 0 first!
[WIFI]wifi_mgmt_handle_msg-1117: msg->app_conf.conf_type 6 ret -2
exec_app_msg-1231: wifi_msg_t(conf_type 6) ret -2
w_sta_sel_ap_again-1421: exec_app_msg(STA_SEL_AP) ret -2
[WIFI]timeout_sta_sel_ap-163 w_sta_sel_ap_again (ap_id 0) ret -2

Attaching full log to this post as text file.

I've tried every firmware on the 101 table and they all wind up with this loop about how "please add ap 0 first!". The RTOS seems to have a terminal and I can issue commands while the system is running, but there aren't any useful commands.

help             - RT-Thread shell help.
exit             - return to RT-Thread shell mode.
wrbootconfig     - write boot_config
rdbootconfig     - read boot_config
md               - disp memory
free             - Show the memory usage in the system.
time             - Execute command with time.
ps               - List threads in the system.
netstat          - list the information of TCP / IP
dns              - list the information of dns
ping6            - ping network host
ping             - ping network host
ifconfig         - list the information of network interfaces
echo             - echo string to file
mkfs             - format disk with file system
mkdir            - Create the DIRECTORY.
pwd              - Print the name of the current working directory.
df               - get disk free
cd               - Change the shell working directory.
rm               - Remove(unlink) the FILE(s).
touch            - touch a file
cat              - Concatenate FILE(s)
mv               - Rename SOURCE to DEST.
cp               - Copy SOURCE to DEST.
ls               - List information about the FILEs.
set_interval     - set_interval
get_interval     - get_interval
powersave        - powersave
hik_sc_set       - hik_sc_set
save_scan_nvm    - save_scan_nvm
keep_alive       - keep_alive
getlumadc        - cmd_getlumadc
wifi_test        - wifi_test
prof_view        - prof_view
prof_init        - prof_init
reboot           - reboot fh system
list_symbol      - list symbol for module

The softap_ access point does not show up when I search for it.

Any ideas before I throw this in the garbage and buy another?

Edit: Did some more testing, my unit just might be corrupted/damaged. There was a simple mtest function in the bootloader that fails to pass:

Pattern 00004987  Writing...  Reading...
Mem error @ 0x001EB898: found 000034EC, expected 00004987
Pattern FFFFB678  Writing...  Reading...
Mem error @ 0x001EB898: found 000034EC, expected FFFFB678
Pattern 00004988  Writing...  Reading...
Mem error @ 0x001EB898: found 000034EC, expected 00004988
Pattern FFFFB677  Writing...  Reading...
Mem error @ 0x001EB898: found 000034EC, expected FFFFB677
Pattern 00004989  Writing...  Reading...
Mem error @ 0x001EB898: found 000034EC, expected 00004989
Pattern FFFFB676  Writing...  Reading...
Mem error @ 0x001EB898: found 000034EC, expected FFFFB676
Pattern 0000498A  Writing...  Reading...
Mem error @ 0x001EB898: found 000034EC, expected 0000498A
Pattern FFFFB675  Writing...  Reading...
Mem error @ 0x001EB898: found 000034EC, expected FFFFB675
Pattern 0000498B  Writing...  Reading...
Mem error @ 0x001EB898: found 000034EC, expected 0000498B
Pattern FFFFB674  Writing...  Reading...
Mem error @ 0x001EB898: found 000034EC, expected FFFFB674
Pattern 0000498C  Writing...  Reading...
Mem error @ 0x001EB898: found 000034EC, expected 0000498C
Pattern FFFFB673  Writing...  Reading...
Mem error @ 0x001EB898: found 000034EC, expected FFFFB673
Pattern 0000498D  Writing...  Reading...
Mem error @ 0x001EB898: found 000034EC, expected 0000498D
Pattern FFFFB672  Writing...  Reading...
Mem error @ 0x001EB898: found 000034EC, expected FFFFB672
Pattern 0000498E  Writing...  Reading...
Mem error @ 0x001EB898: found 000034EC, expected 0000498E
Pattern FFFFB671  Writing...  Reading...
Mem error @ 0x001EB898: found 000034EC, expected FFFFB671
Pattern 0000498F  Writing...  Reading...
Mem error @ 0x001EB898: found 000034EC, expected 0000498F
Pattern FFFFB670  Writing...  Reading...
Mem error @ 0x001EB898: found 000034EC, expected FFFFB670
Pattern 00004990  Writing...  Reading...
Mem error @ 0x001EB898: found 000034EC, expected 00004990
Pattern FFFFB66F  Writing...  Reading...
Mem error @ 0x001EB898: found 000034EC, expected FFFFB66F
Pattern 00004991  Writing...  Reading...
Mem error @ 0x001EB898: found 000034EC, expected 00004991
Pattern FFFFB66E  Writing...  Reading...
Mem error @ 0x001EB898: found 000034EC, expected FFFFB66E

I tried to manually read/write memory at that address (I didnt try other addresses since I don't know the memory map, I just know this range is for the test). mw is memory write. I am trying to write 0xFFFFFFF to 0x1eb898, but memory wont change. Tried to write it count of 2 (incrementing address) still no change. corrupt SOC?

HKVS # mw 0x001eb898 0xffffff 1
HKVS # md 0x001eb898
001eb898: 000034ec 00003524 0000455c 00004370    .4..$5..\E..pC..
001eb8a8: 000044e0 000043bc 0000439c 00004828    .D...C...C..(H..
001eb8b8: 0000468c 0000476c 00004708 000046d8    .F..lG...G...F..
001eb8c8: 000078b4 100028dc e59f2024 e59f3024    .x...(..$ ..$0..
001eb8d8: e1a00002 e5823000 e3a03010 e5823004    .....0...0...0..
001eb8e8: e3a03007 e5823008 e283303a e582300c    .0...0..:0...0..
001eb8f8: eafff5aa 10002400 f0700000 e1a02001    .....$....p.. ..
001eb908: e200101f e1a002a0 eafff1ef e200101f    ................
001eb918: e1a002a0 eafff1dc e200101f e3a02001    ............. ..
001eb928: e1a002a0 eafff1fc e200101f e3a02000    ............. ..
001eb938: e1a002a0 eafff1f8 e52de004 e3a0002e    ..........-.....
001eb948: e24dd004 e3a01000 ebffffeb e3a01000    ..M.............
001eb958: e3a0002f ebffffe8 e3a0002e ebffffed    /...............
001eb968: e3a0002f ebffffeb e3a00030 ebffffed    /.......0.......
001eb978: e3a00031 ebffffeb e3a00032 ebffffe9    1.......2.......
001eb988: e3a00033 ebffffe7 e3a00033 ebffffe5    3.......3.......
HKVS # mw 0x001eb898 0xffffff 2
HKVS # md 0x001eb898
001eb898: 000034ec 00003524 0000455c 00004370    .4..$5..\E..pC..
001eb8a8: 000044e0 000043bc 0000439c 00004828    .D...C...C..(H..
001eb8b8: 0000468c 0000476c 00004708 000046d8    .F..lG...G...F..
001eb8c8: 000078b4 100028dc e59f2024 e59f3024    .x...(..$ ..$0..
001eb8d8: e1a00002 e5823000 e3a03010 e5823004    .....0...0...0..
001eb8e8: e3a03007 e5823008 e283303a e582300c    .0...0..:0...0..
001eb8f8: eafff5aa 10002400 f0700000 e1a02001    .....$....p.. ..
001eb908: e200101f e1a002a0 eafff1ef e200101f    ................
001eb918: e1a002a0 eafff1dc e200101f e3a02001    ............. ..
001eb928: e1a002a0 eafff1fc e200101f e3a02000    ............. ..
001eb938: e1a002a0 eafff1f8 e52de004 e3a0002e    ..........-.....
001eb948: e24dd004 e3a01000 ebffffeb e3a01000    ..M.............
001eb958: e3a0002f ebffffe8 e3a0002e ebffffed    /...............
001eb968: e3a0002f ebffffeb e3a00030 ebffffed    /.......0.......
001eb978: e3a00031 ebffffeb e3a00032 ebffffe9    1.......2.......
001eb988: e3a00033 ebffffe7 e3a00033 ebffffe5    3.......3.......

Futhermore, I expected some sort of different failure if I issued format followed by a reset to allow the system to boot without firmware. This was not the case. The system continued to boot and showed the same failure and not starting the AP. However, issuing the wifi_test command in the OS brings up a test AP that I cannot connect to, but my mobile devices can scan and pick it up.

WIFI]exec_app_msg-1202 conf_type 6
[WIFI*dbg]wifi_mgmt_handle_msg-982: msg->msg_type(0)
wlan_sta_sel_ap-778: conn_ap_id -1 id 0
wlan_sta_sel_ap-790: fail, please add ap 0 first!
[WIFI]wifi_mgmt_handle_msg-1117: msg->app_conf.conf_type 6 ret -2
exec_app_msg-1231: wifi_msg_t(conf_type 6) ret -2
w_sta_sel_ap_again-1421: exec_app_msg(STA_SEL_AP) ret -2
[WIFI]timeout_sta_sel_ap-163 w_sta_sel_ap_again (ap_id 0) ret -2

[WIFI]wifi_mgmt_thread_func-1153 to rt_timer_start(&(timer_sta_sel_ap[0]))

open file for read failed
[WIFI]wwd_ethernetif_init-327
[WIFI]wwd_ethernetif_init-357 CALL low_level_init
[WIFI]low_level_init-169 netif->flags:0x2f (ap)
assert wwd_sdpcm_send_ioctl-1129 IOCTL failed


==============================
ap: UP
ssid:tBŠ
channel: 9
security: Open
password:
msh />timeout_sta_sel_ap-157: enter
w_sta_sel_ap_again-1413: enter

[WIFI]exec_app_msg-120

I have a new hikvision unit on order.

 

[auzzzie]

I can second what @jacha is seeing,

Hikvision DS-HD1 Hardware
Running Hikvision 5.2.4 Build 200321 FW ONVIF snapshot was available at

http://IP/onvif/snapshot.jpg

Updated to the latest 5.2.4 Build 211101 that appeared in Hik-Connect and the ONVIF snapshot URL no longer works.

ONVIF is still enabled according to Batch Config. If you you need ONVIF snapshot, don't update.

RTSP still works for the record.

UPDATE
I can confirm that using Batch Config 3.0.2.6 I was able to downgrade the FW back to 5.2.4 Build 200321 and my ONVIF is working again.

 

[EricLEE]

Is it possible not to get a compressed image from the RTSP stream.. can I change the resolution somehow or use a stream command line to fix? guess what I really want to do is change the Aspect Ratio when viewing using FFMPEG / Home Assistant