Upgraded to Tahoe 26.2 - Security Spy Shows Enable Local Network Access - But it's enabled

jrosinski
jrosinski
in SecuritySpy

Everything was great until I upgraded. Now I have to go to local network access, toggle it off and then back on in order for Security Spy to be able to connect to my cameras.

Any ideas?

Comments

  • Ben
    Ben

    Unfortunately this still comes up as a problem from time to time. It's macOS that's blocking this, and we have limited control over it. Our best advice is posted in this other discussion on the same topic: https://bensoftware.com/forum/discussion/4774/still-having-local-network-access-problems-on-sequioa-15-7-2

  • rapyt
    rapyt

    This might also be hardware-dependent.

    In my case, after upgrading from Sequoia to Tahoe, I haven’t seen this prompt even once. However, I do remember that on Sonoma and Sequoia it used to appear much more frequently.

    So it seems the behaviour can vary depending on the specific machine and macOS version.

  • Ben
    Ben

    Yes, this does seem to vary depending on the specific system, though we haven't managed to pin down exactly what factors are at play here. Most users never see this problem, but one or two see it frequently and it's not clear why. There's quite a bit of chatter on the developer forums about others seeing this issue with their applications, with useful responses from Apple engineers, but nothing definitive.

  • guykuo
    guykuo

    I'm going to bet this turns out to be a timing issue between MacOS processes creating a tough to reliably reproduce bug.

  • meehollak
    meehollak

    I have been getting this error with Tahoe and SS 6.2.1 but not on Tahoe with SS 5.5.0

    I fed the SS debug file into chatGPT and it seems to think the issue is my cameras that are currently offline are the error. If it's the case, it would be great to silence this as I am often pulling cameras on and offline intentionally.


    https://chatgpt.com/share/6a88d488-6348-83e8-815a-2df662702a20

  • Ben
    Ben

    Hi @meehollak the message about the local network permission could indeed be a false diagnosis by SecuritySpy. The issue is that SecuritySpy doesn't have access to information about whether it actually has permission or not - it just sees "Host is down" / "No route to host" errors when it attempts to make network connections. It's almost always the case that when multiple cameras show this error, it's the "Local Network" permission option causing it, hence SecuritySpy informs you of this. But, it's also possible that this is genuinely a network or other problem that is unrelated to the permission setting.

    If it's the case that the affected cameras are actually offline, or the network address given to SecuritySpy could be wrong, or there is actually no network route to the camera, then either you should fix the underlying issue or simply disable the camera in SecuritySpy if you don't need it anymore.

    If you need more help with further diagnosis, feel free to email us and please include a debug file.

Categories