Good or Bad Idea?

I have a Samsung Tizen TV and a few other devices that don't work reliably or at all thru a network connection. So been using global cache ip2ir I got from Allonis. In my configuration to keep track of stuff current input source, power, ect I been setting varibles with something like
SetVariable|av_{{livingroom_display_id}}_input~hdmi3!
adding the input key to the list under av_46_input=hdmi3
this becomes part of the system created varibles and will show under drivers>tizen>device drop down.
What would be better saving these user created varibles the way I'm doing now or should I sepperate them the system created ones with some like this instead
SetVariable|uservar_{{livingroom_display_id}}_input~hdmi3!

Thanks

So, lets start with: Why is a Samsung Tizen TV not working well via IP?
We have used these thousands of times.
The issues are: They use Wake On Lan - which is fine, but you can't rapid fire the TV on / off / on again.
Some of the Samsung TVs (like Frame ones) you can't do discrete HDMI input control (how silly).
Sure you can use IR.

it's a qn65qn90bafxza not sure if that's considered a frame TV or not but hdmi switching doesn't work it ends up on some where on one of the apps in there smart hub.
But thats really not what I was worried about the ip2ir is reliable and the tizen driver only gives limited feed back and it's current input isn't one of them. 
My basic question is adding varibles into "av_<device ID>_varible~value" a bad idea?
or even adding my own device ID
SetVariable|{{activeroom_{{clientname}}}}_Xbox-One_id~72!
or adding
SetVariable|{{activeroom_{{clientname}}}}_Xbox-One_ir~5!
so I can reference IR blaster like
control|{{livingroom_xbox-one_ir}}~SendIR~Microsoft-Xbox One~POWER ON!
Everthing is working but I'm thinking this will comeback to bite me in the ass later
BTW adding the varibles into activate.room macro
thanks

Sat32 wrote:

it's a qn65qn90bafxza not sure if that's considered a frame TV or not but hdmi switching doesn't work it ends up on some where on one of the apps in there smart hub.
But thats really not what I was worried about the ip2ir is reliable and the tizen driver only gives limited feed back and it's current input isn't one of them. 
My basic question is adding varibles into "av_<device ID>_varible~value" a bad idea?
or even adding my own device ID
SetVariable|{{activeroom_{{clientname}}}}_Xbox-One_id~72!
or adding
SetVariable|{{activeroom_{{clientname}}}}_Xbox-One_ir~5!
so I can reference IR blaster like
control|{{livingroom_xbox-one_ir}}~SendIR~Microsoft-Xbox One~POWER ON!
Everthing is working but I'm thinking this will comeback to bite me in the ass later
BTW adding the varibles into activate.room macro
thanks
 

Sounds like your QN90B behaves like my S95C's. I know you said it's not a big deal but I thought I'd point out that you can use the other Samsung Smart TV driver and it works fine. That driver has discrete commands for sources so it doesn't try to faff around with macros in order to land on the correct input and you can accurately track the current state of your tv.

Sounds like your QN90B behaves like my S95C's. I know you said it's not a big deal but I thought I'd point out that you can use the other Samsung Smart TV driver and it works fine. That driver has discrete commands for sources so it doesn't try to faff around with macros in order to land on the correct input and you can accurately track the current state of your tv.

Thanks for the suggestion but didn't work
and I think my answered intial question myself when adding the TV to the samsung driver it tried to use the same device ID I assigned to my Xbox One

Thanks

Sat32 wrote:

Sounds like your QN90B behaves like my S95C's. I know you said it's not a big deal but I thought I'd point out that you can use the other Samsung Smart TV driver and it works fine. That driver has discrete commands for sources so it doesn't try to faff around with macros in order to land on the correct input and you can accurately track the current state of your tv.

Thanks for the suggestion but didn't work
and I think my answered intial question myself when adding the TV to the samsung driver it tried to use the same device ID I assigned to my Xbox One

Thanks
 

Sorry it didn't work out. I'm guessing you would probably have to redo a lot of stuff in order to get this running correctly and it would probably be a fair amount of work.

For the life of me I don't understand why Samsung started doing things this way over IP. It's a pain in the ass and totally unnecessary since their sets have functional support for direct source switching and have for quite a long time now.