Installed 3.0.1 this morning. Works great on hp23!
I have the app new installed and it looks like it is allright, only homey “feels” a little slower.
After a reboot of homey the app doesn’t work anymore.
In the app-list on the homey i see no symbol in the red cirkel from the Web-OS app.
My tv is a oled65cx6la.
Seems the integration is working for newest models but is broken for older ones…
Today I tried to add the TV again and it always failed. Every-time I added TV via LG WebOS from Athom , it works. For now I’m switching to this version then ;-(
I might have figured out what the problem was. I found two bugs since the SDK3 version. TV’s were registered as unavailable when they could not be reached; as in turned off. A bit weird this was causing issues all of the sudden but okay. So whenever a TV is no longer reachable I now will force it to ‘available’. Furthermore, I found an issue with some flows using special web sockets. They would reject the secured connection and needed some extra love 
Anyway fix is incoming today.
PS: I was also working on something else you all might find interesting.
2 Likes
New version 3.0.2 is available in the store and via Github
2 Likes
New version 3.1.0 is available in the store and Github. New version includes an action card to create an alert instead of a toast. Alerts have buttons! You can do stuff with buttons, crazy right. Do you want to watch a series each evening at 19h and don’t feel like looking through all the apps? Create an alert with buttons to launch those apps.
Buttons should be defined as a valid JSON array. See com.webos.notification | webOS Open Source Edition for the button definition.
[
{
"label": "Netflix",
"onclick": "luna://com.webos.applicationManager/launch",
"params": {"id": "netflix"},
"buttonType": "confirm",
"focus": true
}, {
"label": "Got to website",
"onclick": "luna://com.webos.applicationManager/launch",
"params": {"id": "com.webos.app.browser", "target": "https://example.org"},
"buttonType": "confirm"
}
]
Per default, there will always be a Close button that does nothing but cancelling the alert.
Each app has a different ID and parameters. I don’t know all ID’s, I don’t know all possible parameters 
. Maybe we should create a list somewhere so we can share them.
4 Likes
@MaxvandeLaar Really cool! Unfortunately I can’t make the buttons work.
When I copy-paste your example, I get error:
Unexpected token } in JSON at position 202
When I leave the field empty, the default message (with only the close button) works perfectly fine.
Also tried just one button:
[
{
"label":"Got to website",
"onclick":"luna://com.webos.applicationManager/launch",
"params":{
"id":"com.webos.app.browser",
"target":"https://example.org"
},
"buttonType":"confirm"
}
]
But that gives me this error:
Message is not parsed
Support might be really flaky in this. Maybe the browser or your tv has a different ID? Or different params. Try adding a button with just a label and nothing else. See if that works.
I mean I have 2 lg tvs and one doesn’t support create alert at all. For the one that does work, the timeout does not work 
so it’s a very tricky thing to implement and get it working
Fiddled around for a bit. This works for me. Also, the timeout works without any problems.
My alert doesn’t show a title tho, but that’s not that big of an issue.
[
{
"label":"Netflix Test",
"onclick":"luna://com.webos.service.applicationmanager/launch",
"params":{
"id":"netflix"
}
},
{
"label":"Live TV",
"onclick":"luna://com.webos.service.applicationmanager/launch",
"params":{
"id":"com.webos.app.livetv"
}
}
]
1 Like
Very neat, it works here with your example JSON, Max.
LG webOS UJ630V (4 to 5 yrs old)
The last JSON of @basvanderploeg show the messagebox, but the buttons act like ‘cancel’. Bas has a newer model I guess?
Yeah, I’ve got a C2 OLED from last year.
1 Like
