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

RoyN wrote:

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...
 

This is a good find! I have some other issues that I need to get squared away first but once they're dealt with I will test this on my set as well.

From the Samsung Tizen driver documentation
"You can also use the manual AddTV command to add an Samsung TV to the network.  Enter the TV's IP address, MAC address including colons between value pairs (for Wake On Lan), and the friendly name of the TV (your choice)."

David Li post=853 userid=549From the Samsung Tizen driver documentation
"You can also use the manual AddTV command to add an Samsung TV to the network.  Enter the TV's IP address, MAC address including colons between value pairs (for Wake On Lan), and the friendly name of the TV (your choice)."
 

Hi David, I'm pretty sure this sort of thing is kind of obvious to you since you've been around it for ages, but even reading this snipet I kind of glanced through the "for Wake on Lan" parenthesis...  Anyways, my suggestion to read it from the auto-Discovery still stands (technically it should be feasible), as does putting a big fat warning that Wake on Lan isnt available because the MAC wasnt specified, something like that... 

As more and more users start using myServer, the things that are "obvious" will prevent support issues...

RoyN wrote:

David Li post=853 userid=549From the Samsung Tizen driver documentation
"You can also use the manual AddTV command to add an Samsung TV to the network.  Enter the TV's IP address, MAC address including colons between value pairs (for Wake On Lan), and the friendly name of the TV (your choice)."
 

Hi David, I'm pretty sure this sort of thing is kind of obvious to you since you've been around it for ages, but even reading this snipet I kind of glanced through the "for Wake on Lan" parenthesis...  Anyways, my suggestion to read it from the auto-Discovery still stands (technically it should be feasible), as does putting a big fat warning that Wake on Lan isnt available because the MAC wasnt specified, something like that... 

As more and more users start using myServer, the things that are "obvious" will prevent support issues...

The Samsung Tizen driver (and others) sends an NMAP command during discovery which is how the MAC is derived from the TURNED ON Samsung.  If NMAP does not return the MAC, then no MAC is available to autopopulate the device driver.  If NMAP behaves, then that is auto populated.
I suspect that some are not turning the TV on and clicking Discovery.
NMAP has some timing issues that are hard to determine. But, certainly for any WOL to work, the MAC is needed.

Yep, I understand that now... but hadn't stopped to think about it... My suggestion to make it obvious still stands, it will surely prevent future users from stumbling on this...

As an aside my Android boxes also seem to be waking up now that I put their MACs...

David Li wrote:

RoyN wrote:

David Li post=853 userid=549From the Samsung Tizen driver documentation
"You can also use the manual AddTV command to add an Samsung TV to the network.  Enter the TV's IP address, MAC address including colons between value pairs (for Wake On Lan), and the friendly name of the TV (your choice)."
 

Hi David, I'm pretty sure this sort of thing is kind of obvious to you since you've been around it for ages, but even reading this snipet I kind of glanced through the "for Wake on Lan" parenthesis...  Anyways, my suggestion to read it from the auto-Discovery still stands (technically it should be feasible), as does putting a big fat warning that Wake on Lan isnt available because the MAC wasnt specified, something like that... 

As more and more users start using myServer, the things that are "obvious" will prevent support issues...

The Samsung Tizen driver (and others) sends an NMAP command during discovery which is how the MAC is derived from the TURNED ON Samsung.  If NMAP does not return the MAC, then no MAC is available to autopopulate the device driver.  If NMAP behaves, then that is auto populated.
I suspect that some are not turning the TV on and clicking Discovery.
NMAP has some timing issues that are hard to determine. But, certainly for any WOL to work, the MAC is needed.

there *might* be a bug around this, since we did the discovery together, and the TV was on for sure (as I was waiting for the popup), so might be worth a look to make sure