Not able to select HMDI3 as Input Source

[OneCreek]

After [marian-t-web-de] (updated) (https://github.com/mcm1957) fixed #138 after a very long time of waiting (big thanks for that!), turning off and menu navigation works now with my SamsungHJ with model 2015: UE55ju6850.

What's not working is turning the TV on (which might be hardware related?) and choosing HMDI3 as imput source. # . samsung.1.Input.Source . samsung.1.Input.TV . samsung.1.Input.Contents . samsung.1.Volume.xxx . samsung.1.Navigation.xxx -> Buttons all work . samsung.1.Input.HDMI3 -> Button doesn't work somehow... No reaction.

Describe the bug
Nothing happens.

To Reproduce
Modus API: SamsungHJ (for UE55ju6850) Pressing Button in objects: samsung.1.Input.HDMI3 What works:... samsung.1.Input.Source, samsung.1.Navigation.Right, samsung.1.Navigation.Right, samsung.1.Navigation.Enter which is a really bad workaround :D

Expected behavior
TV should change to source HDMI3

Screenshots & Logfiles

19:20:11.962 | debug | stateChange  samsung.1.Input.HDMI3 =  {"val":false,"ack":true,"ts":1727630411957,"q":0,"from":"system.adapter.samsung.1","user":"system.user.admin","lc":1727630411957}
19:20:11.909 | debug | Executing command: KEY_HDMI3
19:20:11.904 | debug | stateChange  samsung.1.Input.HDMI3 =  {"val":true,"ack":false,"ts":1727630411901,"q":0,"from":"system.adapter.admin.0","user":"system.user.admin","lc":1727630411901}

Versions:

• Adapter version: 0.6.1
• JS-Controller version: 6.0.11
• Node version: v20.17.0
• NMP: 10.8.2
• Operating system: ubuntu with docker (official image - v10.0.0)

[mcm1957]

Important correction: I did NOT fix the problems, All code changes have been investigated and provided by @marian-t-web-de. Please address Thanls to him. He did a good job although I (and others) did mot have time and equipment to support him.

@marian-t-web-de Could you spent some time to investigate this hdmi3 Problem? Thanks in advance.

[mcm1957]

@OneCreek Please specify / confirm API selection. I assume you have configutred "SamsungHJ".

[OneCreek]

@OneCreek Please specify / confirm API selection. I assume you have configutred "SamsungHJ".

Yes, sorry for missing out on that detail. SamsungHJ with IP address, Pin (and Mac address) fields filled out.

[marian-t-web-de]

Hello, all changes I've provided are SamsungHJ relevant - see code.

By the way, reg. Power On pls. check other user- discuss- platforms. This TV model cannot be switched on via app/Adapter; after turned off there is no network connection. It is only from standby modus possible, some ver. via WoL. I'II Check the HDMI3 asap. MfG Marian T. Von Samsung Galaxy gesendet.

[mcm1957]

@marian-t-web-de Could you spent some time to investigate this hdmi3 Problem? Thanks in advance.

Thats clear in my oppinion.

@marian-t-web-de BUT there still seems to be a problem with hdmi3. As otehr hdmix work, this could be another typo ... I do not have time to analyze hwo ths keys are handled but I thiunk you know the basics as you fixed somthiung at key area. Could you spent some time to investigate this hdmi3 Problem? Thanks in advance.

[marian-t-web-de]

There is no HDMI Problem. The KEY-list is a merge of Samsung-TV's produced btw. about 2010-2018. My TV, model UE55JS8590 also cannot be switched to HDMI neither via remote nor via Smart-App or ioB-Adapter. It is by this model only via Source meue working (KEY_SOURCE). Unfortunately, which Keys are by Your TV working can You try yourself only. I also cannot switch my TV On via Adapter, the reason see answer before.

Moreover, the Keys In ioBroker Adapter are send 1:1 to the TV, there is no function to check which one is working. I'm not shure if we get an error from TV by wrong Key, if yes, maybe one of the creators of this Adapter could implement it. For me no reaction on TV is actually enough.

Remark: all this has nothing together with the actuall changes, with 'Key area' (I didn't found such one) also not.

[mcm1957]

I do not think that the problem has anything to do with your changes. I only asked you to do a review if you can detect the source for the problem. It's clear that some TVs cannot be controlled. But its very unlikely that switching to HMS 1, 2 and 4 works for a unit but hdmi 3 does not :-). For this behavior a problem in the adapter is much more likely.

Anway THANKS for the fixes you provided already

[mcm1957]

@OneCreek As you did not state at this issue (but I think you did at forum) let me ask :

• samsung.1.Input.HDMI3 - button does not work

-. samsung.1.Input.HDMI1 / 2 / 4 - do those buttons work or does none of these buttons work ?

[marian-t-web-de]

@OneCreek one more question from me: KEY_HDMI1 seems not to be implemented neither as standalone SP nor in the SP-object states of command SP, there is HDMI SP/KEY_HDMI only. How du You set it?

With my TV model are keys KEY_HDMI1 till -4 defitely not working. But... KEY_HDMI switches to HDMI2. It is surely not self-explaining :-(

[OneCreek]

@OneCreek As you did not state at this issue (but I think you did at forum) let me ask : -. samsung.1.Input.HDMI1 / 2 / 4 - do those buttons work or does none of these buttons work ?

None of these work. Sorry for the confusion. So I think it's a TV Issue and the issue can be closed... Thanks for clarifying anyhow!

[marian-t-web-de]

@mcm1957 maybe we should change the HDMI SP/KEY_HDMI to HDMI1 SP/KEY_HDMI1 ( or add the second) - for TV models with which it is working? But I cannot test it.

[OneCreek]

@mcm1957 maybe we should change the HDMI SP/KEY_HDMI to HDMI1 SP/KEY_HDMI1 ( or add the second) - for TV models with which it is working? But I cannot test it.

I just checked with my TV. samsung.1.Input.HDMI button works and changes to HDMI1.