Using both samsung drivers simultaneously. How to programatically select each?

Hi!

A while back I mentioned having some power issues with my samsung tv (namely, sending a Power ON to the tv when already on would turn it off)...

Today I was re-installing myServer due to hardware changes and I decided to try the non-tizen driver.  The power control for my TV seems to work correctly with that driver... Nonetheless, the Volume & Mute controls dont...

A bit of an unorthodox solution I'm pursuing is to add both Drivers, connect the TV on both drivers and use the command from each driver for different functions...

The issue I have is I'm unsure how to target the different drivers?  I currently use something like: AV|{{active_tv_{{clientname}}}}~Power~Off, but this doesnt let me select the driver as it will get the TV it thinks is on...  Is there any way of getting the ID of each driver separately?  If this isnt easy I'll end up duplicating the HTMLs for each room (I only use 2 rooms right now so it wont be too bad) but if there is an "elegant" way of doing this I'd prefer so I dont need to keep multiple html files updated for the same device

thanks!

RoyN wrote:

Hi!

A while back I mentioned having some power issues with my samsung tv (namely, sending a Power ON to the tv when already on would turn it off)...

Today I was re-installing myServer due to hardware changes and I decided to try the non-tizen driver.  The power control for my TV seems to work correctly with that driver... Nonetheless, the Volume & Mute controls dont...

A bit of an unorthodox solution I'm pursuing is to add both Drivers, connect the TV on both drivers and use the command from each driver for different functions...

The issue I have is I'm unsure how to target the different drivers?  I currently use something like: AV|{{active_tv_{{clientname}}}}~Power~Off, but this doesnt let me select the driver as it will get the TV it thinks is on...  Is there any way of getting the ID of each driver separately?  If this isnt easy I'll end up duplicating the HTMLs for each room (I only use 2 rooms right now so it wont be too bad) but if there is an "elegant" way of doing this I'd prefer so I dont need to keep multiple html files updated for the same device

thanks!

Best would be to provide the specifics of which TV, which driver provides which features and doesn't provide which other features.  Then, we can add the features to the appropriate driver for completeness.
Note that historically, for commercial projects, we don't typically use audio on the TV so less effort has been spent on audio testing.

If it's only the volume and mute that don't work then couldn't you just replace the command in the volume macro to use the specific driver id that does the volume correctly and use the other driver as the default driver for the power commands?

Hi, sure!

Yes I apologize as I didnt include all the "issues" as my post was more centered around tailoring a workaround for my own use...

I have 2 different Tizen TVs. One is a newer series (lets say TV1) , and one is a bit older (TV2).

What I have noticed:
Volume & Tizen Driver - Works correctly for both of my TVs.
Power & TIZEN Driver: TV1 (newer) OK! / TV2 (older) Discreet ON command toggles the power.  OFF command is correct.
Samsung Driver - Power discreet commands work OK for TV2, Volume doesnt work at all.

In summary my "issue" is only with 1 TV, with the Power... Thats why I thought about using the alternate driver for that one only... Maybe I can alter the macros for the Living room only (where the older TV2 is), as was suggested... I'm thinking what path is easiest and wont give more headache in the future... It seems to be only 1 TV giving me issues, so I also dont want you to waste time as I'm unsure there is a fix on the driver side... (at risk of breaking other TVs which now work on the same driver)... Let me know your thoughts if you dont mind


 

bowlingbeeg wrote:

If it's only the volume and mute that don't work then couldn't you just replace the command in the volume macro to use the specific driver id that does the volume correctly and use the other driver as the default driver for the power commands?

Looking at the volume macro, that would probably be very easy... I see that macro uses "avamp" as a source type... maybe I can point 1 source ID as the "TV" and another source ID as the "AVAMP" for that room?

RoyN wrote:

Hi, sure!

Yes I apologize as I didnt include all the "issues" as my post was more centered around tailoring a workaround for my own use...

I have 2 different Tizen TVs. One is a newer series (lets say TV1) , and one is a bit older (TV2).

What I have noticed:
Volume & Tizen Driver - Works correctly for both of my TVs.
Power & TIZEN Driver: TV1 (newer) OK! / TV2 (older) Discreet ON command toggles the power.  OFF command is correct.
Samsung Driver - Power discreet commands work OK for TV2, Volume doesnt work at all.

In summary my "issue" is only with 1 TV, with the Power... Thats why I thought about using the alternate driver for that one only... Maybe I can alter the macros for the Living room only (where the older TV2 is), as was suggested... I'm thinking what path is easiest and wont give more headache in the future... It seems to be only 1 TV giving me issues, so I also dont want you to waste time as I'm unsure there is a fix on the driver side... (at risk of breaking other TVs which now work on the same driver)... Let me know your thoughts if you dont mind





 

You can use both drivers.  Modify the room activation macro to set the TV_id variable to the tv that does power and the avamp_id variable to the TV id that controls volume. Then both drivers are in play.  Tizen OS doesn't support discrete On / Off commands...only Toggle.  And it also doesn't support status.  If the TV is on the network, we assume it's On.  But you could turn the TV off, and myServer still thinks it's on, until the NIC on the TV expires and falls off the network, then we know it's OFF.

Your TV apparently supports both protocols so with the above, you get the best of both.