@Daniel_Fille, I’m sorry, but please update once more before beginning tomorrow’s test. The same Test link now installs v1.0.48:
After publishing v1.0.47, I continued testing rather than leaving it with users. That deeper testing found that the intended reconnection repair was incomplete: after a previously authorised connection closed, stale registration state—or a late event from the old socket—could still prevent or disturb the replacement connection.
Version 1.0.48 corrects that specific lifecycle fault while retaining the three-attempt limit. It does not add continuous polling, permanent retries or command replay.
Before releasing it, I tested v1.0.48 on my webOS 25 television with normal controls, two standby periods longer than the previous retry-exhaustion period, a five-second off/on cycle, and a Homey app restart. Direct commands continued to work after each recovery. It still requires testing on your affected televisions, and it does not claim to solve the separate webOS 26 pairing issue.
Your observation that both TVs go offline after every app update is also useful. Some interruption is unavoidable because updating restarts the app and closes both TV connections, but needing another app to wake one TV before both reconnect is not behaviour I will dismiss as normal. Please install v1.0.48 over the existing app—do not uninstall it or delete either TV—and confirm that Homey shows v1.0.48 Test.
I apologise for the rapid succession of versions. v1.0.48 is a corrective replacement for the incomplete v1.0.47 repair, not another speculative feature change.
No problem! I fell asleep, so I didn’t have a chance to update to the latest test version yesterday. I have now updated to 1.0.48; both TVs lost the connection again, but I restored it by launching one TV from another app. This time I didn’t need to restart your app, as the TVs returned automatically as online in yours.
I have now started the TV and turned it off again.. now just have to wait till tomorrow and see if it works.
Hi @John_Kevin, I stumbled upon your app by chance and installed it.
However, I’ve run into a problem. My LG TV isn’t being recognized at all.
Modell: OLED55B19LA
webOS: 6.5.3-47 (kisscurl-koli)
Is the device or the webOS version not supported by your app?
With the official LG ThinQ app (Ver. 1.1.1 experimental), my LG TV is recognized without any issues, and everything works perfectly.
Just want to thank you for this app! It adresses plenty of issues I had with the old “Max-app”. Worked pretty flawlessly on an “old” LG B9 thus far. Hope you keep on maintaining it
@John_Kevin It looks like the standby issue might finally be resolved. Everything seems to be working smoothly now, although I don’t want to celebrate just yet! I’ll keep testing for a while longer.
There’s just one small issue remaining. When I run a Homey Flow, for example:
Turn on the TV
Wait 5 minutes
Change input to a selected HDMI source
The last step fails because the TV app hasn’t established a connection yet. I need to wait around 45–60 seconds after the TV turns on before it can successfully communicate with it.
This used to work perfectly when I was using the original app from Max, so I’m wondering if there’s a way to handle this differently?
Perhaps the app could detect when the TV is actually connected and ready to receive commands, rather than just reporting that it’s turned on?
