Tizen Samsung TV works only when ON. (Wifi connected)

Hi,

I'm wondering if I'm the only one that has this issue.  I have 2 tizen TVs configured in myServer, however whenever they power off, myServer loses communication with the and the only way to wake them up again is with their remote (I think its a BT remote iirc, regardless, the factory remote)...

Unfortunately these TVs are connected through wifi only, now other option right now...  Has anyone gotten them to stay awake on the wifi and not drop off of myServer?  Another possibility would be to use the smartremote's IR emitter to send power on to the TVs... not ideal, but it would wake them and from then myServer can communicate with them via IP.

Wondering what other Samsung TV users are experiencing?

I will post here from now on rather than in the other thread since that's not really the appropriate place for this discussion. I'm using the Samsung tv driver for older tv's because the Tizen driver doesn't work well for my sets but I've played with both drivers and the concept is the same.

Once my set powers down it kills the wifi and ethernet connections after about 30 seconds and will no longer respond to an IP power on command. I got thrown off in thinking this works while testing at first because occasionally my set doesn't fully power down for about ten minutes while it's doing some maintenance stuff in the background.

What I have been doing to get around this is exactly what you have suggested with setting the remote itself to send the power on command via IR and then using the IP driver for everything else. This has worked for the time being.

It's not ideal. It creates the issue of having to be in the room pointing the remote at the tv when first powering everything up but I have another IP2IR coming tomorrow (weather permitting) to address just this. After I'm sure everything is where I want it to be I need to order two more for another two Samsung's that are in other rooms. It's ridiculous that I need to spend ~$300 just to address this but that's not Allonis's fault. Samsung should really fix this crappy behavior via a firmware update but this is unlikely to happen. C'est la vie.

 

Samsung TVs most all use Wake On Lan to turn on.
If your network isn't supporting a WOL, then the TV won't turn on.
WOL doesn't traverse subnets.
Ensure the TV external controls are enabled.
And, WOL will only work once the TV is really OFF (off the network).  so you can't toggle TV on / off / on / off..you have to wait multiple minutes for the TV network card to time out.

My network supports WOL (I use it every day with an LG OLED that I use as a monitor in my office) and all of my devices are on the same subnet. External controls are enabled on my set as well as they are required to control the set remotely when I am doing a picture calibration.

My experience with my set is the opposite of what you say about on/off/on/off. I can happily turn the set on and off from myServer all day long provided I do it quickly (I haven't timed it but it's probably less than a 30 second window. The exception to this is if I turn my set off and it's running a compensation cycle in the background. Then I have about a 10 minute window where I can turn the set back on via IP. Any longer than that and it's game over.

I'm not sweating it anymore. I'll have a viable solution up and running shortly.

Thanks for the replies and info!  I thought WOL was a much hackier thing than it seems to be (I sometimes forget that we arent in the early 2000's anymore)...

Anyways, I've successfully implemented the IR control from the SmartRemote, which was a good exercise!  I'll try and understand later what is going on with WOL and why it doesnt seem to be waking either of our TVs (even from a "deep sleep").

For now this will do!

I believe I've cracked the case, so to say... at least on my setup...

Once I added the TV's MAC address to myDesigner its waking up the TV correctly... This makes sense as the tv wont have an IP when its off the network...

I just added the TV's MAC address to the Tizen driver and that solved it... It was good that this forced me to learn the IR driver

It would be best if the driver discovery already got the MAC address, but at least we know how to fix it...