Connection/Authentication issues with recent build(s)?

I have a couple Amcrest cameras that have "just worked" but noticed recently that they will error out with an authentication error and when they are connected, will go down to little to no FPS. I haven't changed any configs on my side and have two of these cameras, so not thinking it's a bad cable, etc.


Also have other manufacturer cameras on the network, none are showing any change in behavior.


I rarely touch this setup, it runs at home and has just worked. Not sure if a recent SS update changed something? I've tried to change slight configs, like standard ONVIF profile to the Amcrest profile, no change in performance.


Just not sure how to further troubleshoot.

Comments

  • There have been no recent changes in SecuritySpy that should be causing these issues. Here's what I recommend:

    • Use the Amcrest profile rather than the ONVIF profile (it's simpler; less to go wrong).
    • Don't use WiFi if at all possible. Ideally, the Mac, cameras, and router should be all connected into a central high-quality Gigabit-speed Ethernet switch.
    • Update the firmware on these cameras to the latest version offered by Amcrest.
    • Check for packet loss from these cameras in the Dashboard (available from the Window menu) - this could be the cause of the low fps you are seeing - if you see significant packet loss this generally indicates a network issue.

    If this doesn't solve it and you need further help, please email us and include a debug file (SecuritySpy menu > Debug > Create Debug File On Desktop) and we will assist you directly.

  • Thanks. Checked out everyone, didn't make any difference. But then, I rebooted the mini and things are back working. Even looked at hung processes, etc. Plenty of memory available, and the network (all wried cameras) were not showing any straiin.


    Not even sure why that would be the solution, but I'll take it. Thanks much.

  • Well, this just happened to me after updating to the latest version of SecuritySpy (6.15) and I had to temporarily disable ONVIF verification to just get things going. I use Amcrest profile for all my cameras except for two where I have to use both Stream 1 and Stream 3. Stream 3 only ever worked with ONVIF instead of Amcrest profile. After update it stopped working which prompted me to start looking.

    Things I noticed:

    • Stream 1 seems to work without a problem with Amcrest profile, it will fail authentification with ONVIF profile though.
    • Stream 3 does not work with Amcrest profile, it did not seem to work properly before either and I used to set ONVIF for Stream 3 to get things going. After the update ONVIF throws authentification fail.
    • Every time I save camera settings in SecuritySpy now I see the 'Manual Profile Path' changes to 'cam/realmonitor?channel=1&subtype=0&unicast=true&proto=Onvif'. This only seems to happen for the two cameras where I use Stream 1 for motion detection and lower resolution Stream 3 for continuous recording in SecuritySpy. I did not see this happening for the cameras where I only use Stream 1.
    • All the other Amcrest cameras I have now also fail ONVIF authentification if I try it instead of Amcrest profile. Those only use Stream 1.
    • No firmware changes happened. I did try to update MacOS to 15.7.1 and it did not fix it nor made worse.

    I'm not sure what to try next. The cameras are LAN-Only so I could run without ONVIF authentification, still it's not something I'd like to keep for extended period of time.

    cheers, Michal

  • After reviewing authentication mechanism, we have discovered a potential bug that could cause this problem with certain cameras in certain circumstances. This issue is specific to the ONVIF negotiation, which is consistent with your report that switching to the Amcrest profile fixes it. Please test the latest beta version of SecuritySpy (currently 6.16b7), try the ONVIF profile again, and let me know if you now see any authentication issues.