Not working with newest version of Companion

[peternewman]

This plug in for sure does not work with the newest version of companion. It wasn't exactly stable before but now it won't connect at all.

Originally posted by @jwiggy in #23

Sorry to hear this @jwiggy . Please can you confirm the version of Companion your running, your OS, the version of the module/connection you're running and what it says in the log file for the connection when it doesn't work.

Do control commands not work, or is it just status/feedback is broken?

Have you confirmed your display and the connection have a matching ID set?

[jwiggy]

The somewhat stable version of companion is 3.5.3. If I upgrade to 4.1.1 the displays won’t connect at all. In 3.5.3 about 80% of my displays will function and a few that are problems connecting. It’s always inconsistent when it works and when it doesn’t. I’m attempting to connect displays to the target IP address they are set to. I likely have two issues. One is a networking problem and the other, the module just isn’t working or is buggy. I currently can not see the version info for the module for some reason but I believe it is V 2 Jessie Wigginton Minister of Technical Arts 432.337.1524 ***@***.******@***.***> 709 N Lee Ave Odessa, TX 79761

…

________________________________ From: Peter Newman ***@***.***> Sent: Monday, October 6, 2025 12:40:58 PM To: bitfocus/companion-module-samsung-display ***@***.***> Cc: Jessie Wigginton ***@***.***>; Mention ***@***.***> Subject: [bitfocus/companion-module-samsung-display] Not working with newest version of Companion (Issue #24) You don't often get email from ***@***.*** Learn why this is important<https://aka.ms/LearnAboutSenderIdentification> [https://avatars.githubusercontent.com/u/6216436?s=20&v=4]peternewman created an issue (bitfocus/companion-module-samsung-display#24)<#24> This plug in for sure does not work with the newest version of companion. It wasn't exactly stable before but now it won't connect at all. Originally posted by @jwiggy<https://github.com/jwiggy> in #23<#23 (comment)> Sorry to hear this @jwiggy<https://github.com/jwiggy> . Please can you confirm the version of Companion your running, your OS, the version of the module/connection you're running and what it says in the log file for the connection when it doesn't work. Do control commands not work, or is it just status/feedback is broken? Have you confirmed your display and the connection have a matching ID set? — Reply to this email directly, view it on GitHub<#24>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BM4LLVRCHPIXVDVIT3KXBX33WKSSVAVCNFSM6AAAAACINZERBKVHI2DSMVQWIX3LMV43ASLTON2WKOZTGQ4DQMZWGU2TEMY>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[peternewman]

The somewhat stable version of companion is 3.5.3. If I upgrade to 4.1.1 the displays won’t connect at all.

In 3.5.3 about 80% of my displays will function and a few that are problems connecting. It’s always inconsistent when it works and when it doesn’t. I’m attempting to connect displays to the target IP address they are set to.

Is it always the same displays that have issues? Or is it just intermittent on all of them? Approximately how many displays do you have?

Do the control commands not work even when the display says its having problems connecting? They should potentially be somewhat independent.

I likely have two issues. One is a networking problem and the other, the module just isn’t working or is buggy.

Can you ping the problematic displays from the machine running Companion?

I currently can not see the version info for the module for some reason but I believe it is V 2

You should be able to see it in the section where you select modules in 4.1.1 I believe.

I'd still like to know the following:

your OS, the version of the module/connection you're running and what it says in the log file for the connection when it doesn't work.

Do control commands not work, or is it just status/feedback is broken?

If so, which commands are you using, just power on and off as the original module provided?

Have you confirmed your display and the connection have a matching ID set?

[pedrag8]

Hi, I am facing basically the same problems as I tried to install the version 4.1.4, to test it on an installation already running with version 3.2.0.
Just to see what's changed for the version 4 upgrade.
Basically the module "Samsung: MD Display" is not working, you can't even create a new one and just be able to insert an IP address of the monitor.
In the previous versions, at least the two and only commands worked ( ON and OFF), a lot of strange behaviour is occurring in the log, like impossibility to reach the monitors with some "Network error : read ECONNRESET", or only one monitor in all my exhibition is actually reporting a feedback in the log section for recieving a command, with the specific command name, the monitor settings are the same of a bunch of them in the same exhibition, of course the same model of a Samsung monitor.
Sometimes they just loose the command even if the staff repeat the same procedure for turning on the exhibition, I took a look to some network issues too, and I hope it's can help
The monitors are always shown in the IP scanner app when launched, or they are fine with ping command from CMD.
In 90% of the cases this is happening to the same two monitors, but when it's happen and 8 have the possibility to check on them via Anydesk, I can ping them and control them...

Two considerations:
I don't understand why in the version 4 it's just not working at all.
And I think it should be released an update of the module just with few other actions, and specifically with feedbacks about on/off status and the mute status

It's really useful to be able to trigger from companion the basic actions of turning on off monitors, specially where spaces are big, the number of monitor is high and there's no possibility to have separate electric circuits....

The version of the Samsung module in my test of companion 4.1.4 is v2.0.0, but as I mentioned before it's even not possible to insert it check the IP address of the connection, the operating system is Windows 10 enterprise 64 bit.

Thanks in advance

[peternewman]

Thanks for your bug report and sorry to hear you are having issues too @pedrag8 . I guess this probably confirms its a bug despite it working fine on Linux since before release. Sadly @jwiggy still hasn't confirmed their OS so I can't tell if this is exclusively a Windows issue for example.

Hi, I am facing basically the same problems as I tried to install the version 4.1.4, to test it on an installation already running with version 3.2.0. Just to see what's changed for the version 4 upgrade. Basically the module "Samsung: MD Display" is not working, you can't even create a new one and just be able to insert an IP address of the monitor.

Please can you share this log file when it's doing this behaviour? Is it that upgraded ones work fine, but you can't add new connections?

In the previous versions, at least the two and only commands worked ( ON and OFF), a lot of strange behaviour is occurring in the log, like impossibility to reach the monitors with some "Network error : read ECONNRESET"

Please can you share those logs too.

, or only one monitor in all my exhibition is actually reporting a feedback in the log section for recieving a command, with the specific command name, the monitor settings are the same of a bunch of them in the same exhibition, of course the same model of a Samsung monitor.

So only one monitor ever reports feedback, or the monitor reporting feedback changes randomly each time? Have you checked the Target ID field matches between the monitor and Companion for non-working ones? Are they all individually connected via IP?

Sometimes they just loose the command even if the staff repeat the same procedure for turning on the exhibition, I took a look to some network issues too, and I hope it's can help The monitors are always shown in the IP scanner app when launched, or they are fine with ping command from CMD. In 90% of the cases this is happening to the same two monitors, but when it's happen and 8 have the possibility to check on them via Anydesk, I can ping them and control them...

Do you get the connection issues if you use other commands that don't involve turning the monitors on and off? E.g. mute and unmute.

Two considerations: I don't understand why in the version 4 it's just not working at all.

I don't either, and haven't yet received sufficient logs to diagnose it or I'd have hopefully fixed it by now.

And I think it should be released an update of the module just with few other actions, and specifically with feedbacks about on/off status and the mute status

The issue here, and it's confirmed by the issues and is the sort of thing that's always the case is that everyone wants a subset of different features, so you'll never keep everyone happy. The module is now at the point where it's pretty trivial to add additional commands (which is obviously a good thing), we just need to find out why some people are seeing some stability issues.

The version of the Samsung module in my test of companion 4.1.4 is v2.0.0, but as I mentioned before it's even not possible to insert it check the IP address of the connection, the operating system is Windows 10 enterprise 64 bit.

If you're on a recent Companion like that, have you tried/could you try temporarily switching to v1.0.5 of the module to confirm the connectivity/commands are stable at that point?

[pedrag8]

Hi and thanks so much for your reply!

I will write my answers to your answers inside a #----#, so you can understand better, and I will attach two folders with the logs, one for the version 3.2.0, the one actually is working but the one I am having some times some issue with delivering my two commands, the second folder with logs is from version 4.1.4 and is the one I tried to test in the spare PC, just to see if there was some new thing for the module SAMSUNG MD DISPLAY.

Thanks for your bug report and sorry to hear you are having issues too @pedrag8 . I guess this probably confirms its a bug despite it working fine on Linux since before release. Sadly @jwiggy still hasn't confirmed their OS so I can't tell if this is exclusively a Windows issue for example.

Hi, I am facing basically the same problems as I tried to install the version 4.1.4, to test it on an installation already running with version 3.2.0. Just to see what's changed for the version 4 upgrade. Basically the module "Samsung: MD Display" is not working, you can't even create a new one and just be able to insert an IP address of the monitor.

Please can you share this log file when it's doing this behaviour? Is it that upgraded ones work fine, but you can't add new connections?

#I will attach a zip folder named : logs from ver 4.1.4.zip#

logs from ver 4.1.4.zip

In the previous versions, at least the two and only commands worked ( ON and OFF), a lot of strange behaviour is occurring in the log, like impossibility to reach the monitors with some "Network error : read ECONNRESET"

Please can you share those logs too.

#I will attach a zip folder too for these logs, the folder name is : LOGS FROM VER 3.2.0.ZIP#

LOGS FROM VER 3.2.0.zip

, or only one monitor in all my exhibition is actually reporting a feedback in the log section for recieving a command, with the specific command name, the monitor settings are the same of a bunch of them in the same exhibition, of course the same model of a Samsung monitor.

So only one monitor ever reports feedback, or the monitor reporting feedback changes randomly each time? Have you checked the Target ID field matches between the monitor and Companion for non-working ones? Are they all individually connected via IP?

#Yes, only one monitor is always providing me a feedback in the log correcly after recieving a command, and he never change the behavior, all the rest of monitors do not send a similar feddback in the log.
The settings of ip address for all the monitors are corrects, and checcked, in fact they all are working correctly in the version 3.2.0
It’s already a year that the turning on and off is performed via companion version 3.2.0, just some times some one miss the commands, and just one report feddbacks in the log section.#

Sometimes they just loose the command even if the staff repeat the same procedure for turning on the exhibition, I took a look to some network issues too, and I hope it's can help The monitors are always shown in the IP scanner app when launched, or they are fine with ping command from CMD. In 90% of the cases this is happening to the same two monitors, but when it's happen and 8 have the possibility to check on them via Anydesk, I can ping them and control them...

Do you get the connection issues if you use other commands that don't involve turning the monitors on and off? E.g. mute and unmute.

#In the module there is just the two commands for ON and OFF#

Two considerations: I don't understand why in the version 4 it's just not working at all.

I don't either, and haven't yet received sufficient logs to diagnose it or I'd have hopefully fixed it by now.

#I hope you can get more informations with the logs folders i attached to you#

And I think it should be released an update of the module just with few other actions, and specifically with feedbacks about on/off status and the mute status

The issue here, and it's confirmed by the issues and is the sort of thing that's always the case is that everyone wants a subset of different features, so you'll never keep everyone happy. The module is now at the point where it's pretty trivial to add additional commands (which is obviously a good thing), we just need to find out why some people are seeing some stability issues.

#Of course, and I understand perfectly the situation, I am already grateful for your help and response.#

The version of the Samsung module in my test of companion 4.1.4 is v2.0.0, but as I mentioned before it's even not possible to insert it check the IP address of the connection, the operating system is Windows 10 enterprise 64 bit.

If you're on a recent Companion like that, have you tried/could you try temporarily switching to v1.0.5 of the module to confirm the connectivity/commands are stable at that point?

#I have no other option availble for the module version, just the v2.0.0#

Thanks so much in advance!

[peternewman]

Unfortunately both your log file zips are empty, but I've managed to run it up on a later Companion and seen the issue for myself:

system: Starting log. Only lines generated since opening the page are shown here
system: ** Starting Connection from "C:\Users\user\AppData\Roaming\companion\modules\samsung-display-2.0.0\main.js" **
system: ** Connection started **
Starting up module class: 
Module-host accepted registration
{"updatedConfig":null,"updatedActions":[],"updatedFeedbacks":[]}
{"updatedConfig":{"port":"1515","id":1},"updatedActions":[],"updatedFeedbacks":[]}
error: Trace: Init failed: Error: ENOENT: no such file or directory, open 'C:\Users\user\AppData\Roaming\companion\modules\samsung-display-2.0.0/samsungd.xml'
    at C:\Users\user\AppData\Roaming\companion\modules\samsung-display-2.0.0\main.js:2:217366
    at C:\Users\user\AppData\Roaming\companion\modules\samsung-display-2.0.0\main.js:2:75289
    at e.default._tryToStartAnother (C:\Users\user\AppData\Roaming\companion\modules\samsung-display-2.0.0\main.js:2:74336)
    at C:\Users\user\AppData\Roaming\companion\modules\samsung-display-2.0.0\main.js:2:75496
    at new Promise (<anonymous>)
    at e.default.add (C:\Users\user\AppData\Roaming\companion\modules\samsung-display-2.0.0\main.js:2:75139)
    at e.InstanceBase._handleInit (C:\Users\user\AppData\Roaming\companion\modules\samsung-display-2.0.0\main.js:2:216746)
    at e.IpcWrapper.receivedMessage (C:\Users\user\AppData\Roaming\companion\modules\samsung-display-2.0.0\main.js:2:200450)
    at process.<anonymous> (C:\Users\user\AppData\Roaming\companion\modules\samsung-display-2.0.0\main.js:2:216230)
    at process.emit (node:events:517:28)
error: Failed to init: Error: ENOENT: no such file or directory, open 'C:\Users\user\AppData\Roaming\companion\modules\samsung-display-2.0.0/samsungd.xml' Error: ENOENT: no such file or directory, open 'C:\Users\user\AppData\Roaming\companion\modules\samsung-display-2.0.0/samsungd.xml'
    at Object.openSync (node:fs:596:3)
    at Object.readFileSync (node:fs:464:35)
    at new s (C:\Users\user\AppData\Roaming\companion\modules\samsung-display-2.0.0\main.js:2:86510)
    at e.InstanceBase.init (C:\Users\user\AppData\Roaming\companion\modules\samsung-display-2.0.0\main.js:2:264305)
    at C:\Users\user\AppData\Roaming\companion\modules\samsung-display-2.0.0\main.js:2:217302
    at C:\Users\user\AppData\Roaming\companion\modules\samsung-display-2.0.0\main.js:2:75289
    at e.default._tryToStartAnother (C:\Users\user\AppData\Roaming\companion\modules\samsung-display-2.0.0\main.js:2:74336)
    at C:\Users\user\AppData\Roaming\companion\modules\samsung-display-2.0.0\main.js:2:75496
    at new Promise (<anonymous>)
    at e.default.add (C:\Users\user\AppData\Roaming\companion\modules\samsung-display-2.0.0\main.js:2:75139)
system: ** Connection stopped **

It looks like it's not including the standalone XML file from one of the dependencies as part of the bundling.

[peternewman]

#I have no other option availble for the module version, just the v2.0.0#

Thanks so much in advance!

If you go to Modules (rather than Connections) and select Samsung, you should be able to add the downgraded 1.0.5 module and switch a connection to that for now.

[pedrag8]

Thanks for your response.
I am surprised about the two empty folders, I don't know what happens in the GitHub attachment system, as soon as I am in possession of my PC I'll try to upload you again the two folders.
And as soon as I can access the PC running version 4 for the exhibition, I will try what you suggested to me about going to modules rather than connections.
Thanks again

[peternewman]

There's probably no need to upload the logs now @pedrag8 unless they say something different.I think I know what the issue is now. I'm just not yet sure how to solve it.