Samsung The Frame plugin

[rubenvw]

Not sure what I should do to make my plugin visible in the plugin list, but I created a loxberry plugin that allows to interact with samsung tv's (I focussed on samsung the frame, because that is what I have, but probably most controls will also work on other samsung tv's)

If you want to use it, I just released a stable version:

https://github.com/rubenvanwanzeele/loxberry-plugin-samsung-frame-tv/releases/tag/v1.0.0

[Prof.Mobilux]

Hi,

I created a Wiki pgae for your plugin. You can edit/modify it at any time with a free account in the wiki.

https://wiki.loxberry.de/plugins/sam...e-plugin/start

[Bstaes]

Works great, thanks!

But is there a way to add more then 1 tv?

[rubenvw]

Works great, thanks!

But is there a way to add more then 1 tv?

Haven't thought about multiple tv's. I'll implement that and will release a v2 for that soon. Do you mind beta testing the functionality for me? (I only have one tv)?

[rubenvw]

Works great, thanks!

But is there a way to add more then 1 tv?

This should contain multi tv support.

https://github.com/rubenvanwanzeele/loxberry-plugin-samsung-frame-tv/archive/refs/heads/master.zip

Any feedback welcome. If you confirm the functionality is working correctly, I will release this into the v2.0.0 version

[Bstaes]

Works perfectly!

I currently have 2 tv's connected without any problems.
-Samsung S95F
-Samsung S94F

If there is anything I can test/help you with let me know!

[SchmuFoo]

Looking very interesting and pairing and testing via plugin page worked! But Sorry that I have to asked, but where do I configure the Output in Loxone? As an Virtual Output and if yes how or via the MQTT Publish Config in Loxone?

[Bstaes]

You wil need to use MQTT , not Virtuals.


loxberry/plugin/samsungtvslkmaster/cmd

[SchmuFoo]

You wil need to use MQTT , not Virtuals.


loxberry/plugin/samsungtvslkmaster/cmd

Thanks I was able to get this (Art On/Off) working yesterday with Virtuals to the Loxberry I am using.

Only thing which is not working even trough the plugin page http://loxberry2/admin/plugins/samsungframe/index.php ist power_off and power_on.

(BTW: And from time to time my 2022 65" Frame is showing the "LoxBerry Allow/Deny Popup" again in the top right although the pairing is stable)

[rubenvw]

Hi everybody, I'm happy to see how many of you are using the plugin already.

SchmuFoo The plugin caches and stores the token, so it shouldn't ask to allow after initial pairing. I have no such issues with it at least.
I also have the 2022 frame version, and I am using power_off command without issues. (I use it in combination with all off button)

Regarding the power off/ on not working, that's strange, because it's one of the most basic functionalities. But if it's not working from the app, it wont work from loxone either. Are you on the latest version?

Best is to switch to the latest (unreleased version). It has some more logging and might have some bugfixes (can't remember, but I think I fixed some smaller issues in that version). I will release is soon enough.
On that latest version, there is quite some info added to the logging, which comes in handy to identify issues.
I did configure everything using virtual inputs/outputs (see https://wiki.loxberry.de/konfigurati...lp/widget_mqtt for details). For me the integrated loxone mqtt functionality didn't work stable.

Side track, it would be cool to hear what you are using the plugin for, could inspire others and myself.
I mainly use it to enter/exit a tv mode when the tv turns on/off (turning off other audio in the living room and adjusting the lights)
Other sidetracks:
* turn tv off when leaving the house
* turn tv off when no presence was detected in the room for 1 hour (just wanted to test this in case someone fell asleep in front of the tv, but still need to check if it won't kill the tv in the middle of a movie)

[Bütti]

Hi, first of all: Great work!
But...I have some problems with the power_off function.
The TV doesn't change to standyby mode. Instead of that, it is switching between art_mode, main menue and tv-program with every new power_off command.
Does anyone have the same problem?
TV is the version of 2025.
Thanks for help.

[SchmuFoo]

Hi everybody, I'm happy to see how many of you are using the plugin already.

SchmuFoo The plugin caches and stores the token, so it shouldn't ask to allow after initial pairing. I have no such issues with it at least.
I also have the 2022 frame version, and I am using power_off command without issues. (I use it in combination with all off button)

Regarding the power off/ on not working, that's strange, because it's one of the most basic functionalities. But if it's not working from the app, it wont work from loxone either. Are you on the latest version?

Best is to switch to the latest (unreleased version). It has some more logging and might have some bugfixes (can't remember, but I think I fixed some smaller issues in that version). I will release is soon enough.
On that latest version, there is quite some info added to the logging, which comes in handy to identify issues.
I did configure everything using virtual inputs/outputs (see https://wiki.loxberry.de/konfigurati...lp/widget_mqtt for details). For me the integrated loxone mqtt functionality didn't work stable.

Side track, it would be cool to hear what you are using the plugin for, could inspire others and myself.
I mainly use it to enter/exit a tv mode when the tv turns on/off (turning off other audio in the living room and adjusting the lights)
Other sidetracks:
* turn tv off when leaving the house
* turn tv off when no presence was detected in the room for 1 hour (just wanted to test this in case someone fell asleep in front of the tv, but still need to check if it won't kill the tv in the middle of a movie)

Hi Ruben,

Thanks for the awesome plugin and the recommendation to switch to the master branch! I successfully upgraded to the unreleased v1.1.0. The "Quick Test Commands" on the plugin page work flawlessly now and the monitor.log is completely silent.

Regarding the recurring "Allow/Deny" popup problem, I did some deep-dive debugging using inotifywait and md5sum on the token.txt, and I finally found the root cause:

TL;DR Fix for the Popup Issue:

• The Token was fine: The plugin never lost or modified the token.txt. The file remained untouched with the exact same MD5 hash.
• TV Settings Glitch: The culprit was a native Samsung TV setting. Under Settings → General → Network → Expert Settings → Device Connection Manager, the "Access Notification" (Zugriffsbenachrichtigung) was set to "Always On" (Immer Ein) instead of "First Time Only" (Nur beim ersten Mal).
• The Result: Even with a valid token sent by the plugin, the TV forced a visual popup every time a command or status poll hit a certain state transition. This caused the WebSocket connection to run into a timeout while the TV waited for manual remote input.

After clearing out old duplicate "LoxBerry" entries in the TV's device list and switching the notification to "First Time Only", Tizen OS now silently accepts the token in the background. No more popups, no more timeouts!

My Use Case / Inspiration:
You asked what we use the plugin for: I have integrated the Frame into my Loxone "Dinner Scene" (Abendessen-Szene). The built-in motion sensor of the Frame is a bit weak and doesn't reliably detect us while we are sitting at the dining table, which previously caused the Art Mode to turn off way too early. Now, Loxone overrides this and explicitly manages the art_on / art_off commands during dinner time to keep the artwork alive precisely when we are in the room.

Keep up the great work!

[rubenvw]

Hi, first of all: Great work!
But...I have some problems with the power_off function.
The TV doesn't change to standyby mode. Instead of that, it is switching between art_mode, main menue and tv-program with every new power_off command.
Does anyone have the same problem?
TV is the version of 2025.
Thanks for help.

Hi,

I'm sorry to hear the power off is not working as intended on your 2025 model. Are you sure you are using the latest (unreleased) version of the plugin? There were others having issues with the released version and the power_on/power_off commands (see above).
If it is realy a model 2025 issue, I have a 2022 tv so it is hard for me to add support for the 2025 model without being able to test it.

If you are able to add proper support for your tv yourself, I'm ready to accept a pull request for it (If you're not a coder, you can always try and use a AI agent to help you find a fix).

[rubenvw]

FYI, I released v1.1.0, see https://wiki.loxberry.de/plugins/sam...e-plugin/start