Samsung Smart Device extension stopped working

[V4N089]

Hi,
I know it's labelled as Experimental so it's still WIP but it was working fine a couple of days ago and now it seems the connection between the monitor and the app is not establishing anymore

No matter what I do Connection Status doesn't budge from Disconnected, as far as I can see macOS permissions are fine and IP hasn't changed (is set to static and I can ping the monitor from my machine)

Ive tried clicking the Retry button and capturing the logs from Console, dont think there's anything helpful but who knows? 😄
logs.rtf

Thanks a lot!

DETAILS

• Mac mini M4 (macOS 15.7.2)
• Samsung G85SB (ver 1664)

[waydabber]

You can try running the app from /Applications/BetterDisplay.app/Contents/MacOS/BetterDisplay -v to see if there is any issue.

Are you sure the IP address is fine and the connection request wasn't denied accidentally on the TV? If so, you should be able to reset the connection data for all devices using the TV OSD.

Does ping-ing the TV from Terminal work?

[V4N089]

Yep I can ping the monitor all right from my Mac and permissions are Ok, I have BetterDisplay listed in the allowed devices

I also have HomeAssistant in my home network and it has no issues controlling the monitor

Strangely enough when I start the app using /Applications/BetterDisplay.app/Contents/MacOS/BetterDisplay -v it all works fine! But as soon as I reboot the machine and I let the app start by itself it doesn't work anymore
Here's the terminal window entries:
verbose logs.rtf
And here console logs when starting the app with verbose:
console logs with verbose.rtf

[waydabber]

I am not sure what could be the issue. Maybe it's a security problem of some sorts where macOS does not allow the app to communicate with the device. 😕 In the original console log I see a bunch of "Local network prohibited" messages. Maybe the app does not have Local Network Access (under Privacy & Security).

[V4N089]

I thought as well but the permission is there, I’ll try deleting it and adding it manually

I really don’t understand what changes between starting it manually and the automatic startup at login, shouldn’t it be the same thing in terms of permissions?

[waydabber]

I think it should be the same. I am sorry about the issue, I don't really know why it says it has no permission - especially as you say it worked before.

I'll convert this to a Discussion, let's see if others have similar issues with this.

[V4N089]

It's related to Local Network Access permission in macOS it seems, if I toggle it off an on again then click on the reconnect button in BetterDisplay the feature works correctly again 😕 no idea what could be the reason behind it!

All other apps that have local network permissions seem to work fine and dont require this procedure to work

[V4N089]

I think I've fixed it! It's now been one week and the feature works great ✌️ for some reason I had to disable the local network permission, reboot my machine and then re-enable it - this somehow made the permission "work" finally!

Only thing I noticed is that after my Mini goes in standby for a while (like an hour) I have to manually go in BD settings and refresh the connection, it goes to authorised right away and the feature works again - does this happen to anyone else?

[V4N089]

Stopped working again and the "fix" I used before doesn't work anymore, that's a shame... tried resetting tcutil globally hoping it would help but local network permissions isn't handled by it unfortunately

[waydabber]

Hi - I should probably make the connection a bit more reliable + provide an option to auto-reconnect option if needed instead of things just stop working with a need to hit that reconnect button.

I added an issue about this:

#4974