This is the forum archive of Homey. For more information about Homey, visit the Official Homey website.

The Homey Community has been moved to https://community.athom.com.

This forum is now read-only for archive purposes.
Official CommunityApp

[App] Samsung Smart TV by Casper Boone - main discussion topic

1356

Comments

  • D Series dont work. :'(
  • UE48JU7500 does not work 
  • Nice work @casper !! 

    My UE40F6400 is controlled like a charm!

    I made a flow that mutes the TV when homey starts talking and unmutes it again after. Seems to work in 70% of the times. I might change that one to an IR command when it is stable. 

    I would really like some cards for in the IF and AND column, like:

    IF Samsung TV comes online (turns on) / IF Samsung TV goes offline (turns off)

    AND Samsung TV is on / AND samsung TV is off

    It would create a lot of extra cool possibilities! Would that be possible?

    And can we buy you a beer?  ;)
  • JeroenvanoJeroenvano Member
    edited September 2016
    UE48JU7500 does not work 
    Oh, reading backwards in this trail

    2015 (J/K series) or newer

    Not supported. Samsung TVs now run on Tizen which is for now outside the scope of this app.

  • posthokposthok Member
    edited September 2016
    olive said:
    D Series dont work.
    D8000 not recognized
  • posthok said:
    olive said:
    D Series dont work.
    D8000 not recognized
    Have you tried entering the tv IP manualy? It didnt find mine automatically as well. 
    You can find it in the network connection menu of your tv.
  • posthokposthok Member
    edited September 2016
    Qx5 said:
    posthok said:
    olive said:
    D Series dont work.
    D8000 not recognized
    Have you tried entering the tv IP manualy? It didnt find mine automatically as well. 
    You can find it in the network connection menu of your tv.
    There is no other way to add your tv then adding you tv ipadress.

  • Oops I was under the impression it was supposed to find a tv on the network and when it failed you could enter the ip manually. 
  • Qx5 said:
    Nice work @casper !! 

    My UE40F6400 is controlled like a charm!

    I made a flow that mutes the TV when homey starts talking and unmutes it again after. Seems to work in 70% of the times. I might change that one to an IR command when it is stable. 

    I would really like some cards for in the IF and AND column, like:

    IF Samsung TV comes online (turns on) / IF Samsung TV goes offline (turns off)

    AND Samsung TV is on / AND samsung TV is off

    It would create a lot of extra cool possibilities! Would that be possible?

    And can we buy you a beer?  ;)
    Cool :smile:.

    Hm.. 70% is not good enough ;). I used in the past in exactly for exactly the same flow, will re-enable that one to monitor it.

    Those cards would be nice, but I'm not sure if I can make them reliable. My TV cannot be reached until about 60s after I powered it on. But will try it soon.

    Although I usually don't say no to a beer, this is all just community lovings  <3, lol.
  • Could you add the UE40C5100 and UE37C6000.
    I would like to test you app on both of these.
  • I am no programmer but would like to see the newer 2015+ J/K Tizen series supported.

    Not sure if this is easy done but found some online doc: https://www.samsungdforum.com/TizenGuide/tizen231/index.html 

    Maybe someone can indicate if it is doable or hard to build an app for Homey?
  • casper said:
    Qx5 said:
    ...
    Cool :smile:.

    Hm.. 70% is not good enough ;). I used in the past in exactly for exactly the same flow, will re-enable that one to monitor it.

    Those cards would be nice, but I'm not sure if I can make them reliable. My TV cannot be reached until about 60s after I powered it on. But will try it soon.

    Although I usually don't say no to a beer, this is all just community lovings  <3, lol.
    No complaints anymore about that flow. Seems to run smooth now!

    I understand that the cards will have a large delay but it can avoid sending commands while the tv's not yet fully reachable. These cards would enable "queueing" of commands and sending them asap. Also it doesn't feels right to send commands to the tv without knowing if it's on  ;)

    A few days ago I saw that the app was chrashed and I restarted it. What can we do to give you more insight about what made it crash?

    <3
  • btwvincebtwvince Member
    edited September 2016
    @casper ; Everything worked once but now i see this message:

  • I am no programmer but would like to see the newer 2015+ J/K Tizen series supported.

    Not sure if this is easy done but found some online doc: https://www.samsungdforum.com/TizenGuide/tizen231/index.html 

    Maybe someone can indicate if it is doable or hard to build an app for Homey?
    Keen to know this as I have a Tizen 2015 model as well
  • I am no programmer but would like to see the newer 2015+ J/K Tizen series supported.

    Not sure if this is easy done but found some online doc: https://www.samsungdforum.com/TizenGuide/tizen231/index.html 

    Maybe someone can indicate if it is doable or hard to build an app for Homey?
    Keen to know this as I have a Tizen 2015 model as well
    That link is only about an on screen remote that can be used in apps that you install on your TV. Since I've no idea how these TV's work, I cannot indicate if it will easy to write an app for it. But you could always send me one of course, then I would be more than happy to take a look  :p.
  • @Qx5 ;
    You can see 'the reason' (a stack trace) why it crashed when you go to Settings > Apps. In case it happens again please let me know, try to remember if there was a specific action you (or Homey) did to let it crash, and provide me some details on your TV.

    @btwvince
    Do you see this constantly, or only some times?

  • btwvincebtwvince Member
    edited September 2016
    @casper When I restart the app it goes away but when it does it's first action then i get the same message. So yes every time :(
    The only action I use it for is to switch off the TV
  • @casper  I have a F6400 2013 model. 

    Dont know when it crashed, only that the app didnt work when it was suppositie to turn of the tv. Would be Nice if homey announced the crash of an app!

  • Qx5 said:
    @casper  I have a F6400 2013 model. 

    Dont know when it crashed, only that the app didnt work when it was suppositie to turn of the tv. Would be Nice if homey announced the crash of an app!

    Still same crash here :(
  • Same here. 
  • For some reason the number of crashes increased hugely somewhere around 0.9.3 / 0.10.0. Could also be a coincidental increased number of installs of course. Seeing some stack traces similar to the ones in your images.

    Also getting a "missing_listener" warning since 0.10.0 when trying to edit source/channel flows. Will have to look into this.

    Btw, I have very little time to put into this app, please don't expect things to be fixed within a few days/weeks. If anyone likes to help, I'm very open to PRs on the app :smile:.

    @btwvince Bit confused by this "When I restart the app it goes away but when it does it's first action then i get the same message.", since it only retrieves sources (the point where it fails according to the screenshots) when editing flows (for as far I remember).
  • Missing listener is fixed for 0.10.1:
    https://github.com/WeeJeWel/net.weejewel.hyperion/issues/4
    no code change so probably a bug in 0.10.0
    I would definitely wait for 0.10.1 before putting time in the stack-trace... Will probably be fixed too.

  • HomealoneHomealone Member
    edited October 2016
    I tried the App today for the first time (0.10.1), paired with UE46F6510, but when using the cards "set TV to source" or "set TV to channel" an error message "select a tv" shows up. Am I doing something wrong? I also wonder why there is card for "power off" but none for "power on".
  • Homealone said:
    I tried the App today for the first time (0.10.1), paired with UE46F6510, but when using the cards "set TV to source" or "set TV to channel" an error message "select a tv" shows up. Am I doing something wrong? I also wonder why there is card for "power off" but none for "power on".
    This is either a bug in 0.10.1 or an API change. I had noticed it already, but haven't had time to look into it yet.

    The reason there's no power on is because the TV is not reachable before it's turned on. Therefore it's not possible to send that command. The option to turn your tv on is also not available in the official Samsung smartphone apps.
  • Update that fixes the 'Select a TV' issue has been submitted for review. Should be available later this week.
  • casper said:
    For some reason the number of crashes increased hugely somewhere around 0.9.3 / 0.10.0. Could also be a coincidental increased number of installs of course. Seeing some stack traces similar to the ones in your images.

    Also getting a "missing_listener" warning since 0.10.0 when trying to edit source/channel flows. Will have to look into this.

    Btw, I have very little time to put into this app, please don't expect things to be fixed within a few days/weeks. If anyone likes to help, I'm very open to PRs on the app :smile:.

    @btwvince Bit confused by this "When I restart the app it goes away but when it does it's first action then i get the same message.", since it only retrieves sources (the point where it fails according to the screenshots) when editing flows (for as far I remember).
    @casper i'm sorry for my bad English but I mean the following: 
    I add the Samsung TV and after that my flow can switch the tv off.
    When I try to use the same flow the next day to turn the tv off, it doesn't work. I get the following message:


    When I press disable and enable, it works again one time and then again the error
  • 2bad that the app is not working right.

    Stack trace:

    TypeError: Cannot read property '0' of undefined
    at /samsung-tv-sources.js:74:108
    at /samsung-tv-soap-api.js:72:51
    at Parser.<anonymous> (/node_modules/xml2js/lib/xml2js.js:484:18)
    at emitOne (events.js:77:13)
    at Parser.emit (events.js:169:7)
    at Object.onclosetag (/node_modules/xml2js/lib/xml2js.js:445:26)
    at emit (/node_modules/xml2js/node_modules/sax/lib/sax.js:640:35)
    at emitNode (/node_modules/xml2js/node_modules/sax/lib/sax.js:645:5)
    at closeTag (/node_modules/xml2js/node_modules/sax/lib/sax.js:905:7)
    at Object.write (/node_modules/xml2js/node_modules/sax/lib/sax.js:1449:13)

    Exit code: 1
  • caspercasper Member
    edited October 2016
    An (probably successful) attempt to fix that has been submitted for review last Thursday, so will be available soon :smile: .
  • Oops, at least now it is, forget to press the actual submit button.
  • casper said:
    Oops, at least now it is, forget to press the actual submit button.
     :D hehe, thnx for the fix 
Sign In or Register to comment.