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.
The Homey Community has been moved to https://community.athom.com.
This forum is now read-only for archive purposes.
Official CommunityApp
Comments
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?
2015 (J/K series) or newer
Not supported. Samsung TVs now run on Tizen which is for now outside the scope of this app.
You can find it in the network connection menu of your tv.
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 , lol.
I would like to test you app on both of these.
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?
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?
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?
The only action I use it for is to switch off the TV
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!
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 .
@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).
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.
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.
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
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