I still don’t get why this is happening. What is really motivating Athom to piss off not only developers but even the end users at the end ? Obviously they don’t have capacity to do everything on their own but why they are even pushing away developers and community ? Simply I don’t get it, maybe nobody from us.
@MaxvandeLaar I’m so far testing your app few days only but for sure I found very reliable replacement compared to original and many missing functionalities LG Web OS app from Athom. Thank you for it !
I understand that they need a base level of high quality apps (I know that’s a relative thing ) to ensure people will buy the product. But if the community app surpasses the homey team they should rejoice and declare their own app as deprecated as long as the dev is willing to keep it open source.
If that community dies over time they can always adopt it back into the self managed apps. I also do not see the big problem for them here. Just save dev time from them.
btw I am going to do a throw on getting LG Music Flow implemented. If we merge that then we call the app a LG smart devices app with both music flow speakers and web os tv’s. Maybe it can get it since it is a more clear other type of app than their own.
But dont get your hopes up yet, discovery is working now but still need to send messages, no api but more classic network messages with encryption etc.
Sounds interesting. Before I decided to obfuscate my code I was actually looking into LG smart ThinQ since I also have an lg airco unit. When you are a bit further let’s definitely discuss merging
While we’re at it. are you working on an update by any chance? The tv turns on by itself since the last update. I’ve just turned it off with the remote and within some seconds or minutes it magically turns on again. Of course not the tv itself but virtually in the app, which also makes my lights go on again. Turning it off in the app just doesn’t help. It will revert back to on status.
@Martijn_C, yes that is a problem in the v2.0.0-rcX. Should be resolved in RC4, however, I need to get my development environment setup correctly. I hope to finish this today. I also know how to fix it, with thanks to @Kaoh for helping me debug it with his TV. So to shortly give you an idea what happens… I am now using the API to check the state of the TV instead dumb polling its ip address. However, it appears that LG tv’s don’t have the same progress they are going through when powering on or off. This is kinda frustrating as it could work for me, but not for you… So @Kaoh suggested to check certain types of progress instead of the state of the TV. Which will work fine, but there are a few different states I need to check for. In other words, easy fix, will be released ASAP.
UPDATE (edit) setting up my new dev flow is a great success, the app is now much smaller actually Anyway I will make a new release tomorrow.
I hate to be the bearer of bad news, but no luck. Controlling the tv from the app goes well, but the status does not change when the tv is controlled with the remote. When off in the app and turned on with the remote, it stays off in the app. The other way around the same. I’ve tried changing (upping) the timeout tv uit check but no luck.
Status change in RC4 does work for me: if I turn on the tv with the remote, within seconds it’s on in the app.
And when I switch it off again with the remote it switches off in the app again too within seconds.
@Martijn_C, I will go well out my way to prevent people from removing their devices so you don’t have to do that. As I stated before, LG appears to have implement a different on/off process for their tv’s. I just need to figure out what the possible processes are. Each process has a state and a progress indicator. For example, my living room tv nicely shutdown by sending a state that does not equal ‘active’, however, my upstairs tv doesn’t do this and keeps the active state however, ends with the progress indicator set to ‘prepare suspend’. Since there is no documentation available for the entire WebOS api I am currently using, it can get a bit frustrating. I’ll send you a guide on how to send me the logs so I can get the on/off process.
@MaxvandeLaar I’m able to run the app with '“homey app run” so if you need any debug info please let me know
@Martijn_C: I just recall I did do one more thing before installing/running the app.
I did run the “npm install -g npm” command which did execute some dependency update:
Release candidate 5 arrived today: Added support for more tv’s. The release candidates are actually full releases however, I still need to figure out if all your tv’s are supported by the new on/off listener. Please don’t let this stop you from trying out v2.0.0. If this version isn’t responding on your remote on/off buttons I will most likely have a fix for you within a day provided you can get me your logs
So why upgrade from version 1.x.x to version 2.x.x-rcx? Much (and I mean it!) faster on/off detection! For me personally it went from 2 minutes to less than 1 second(!)
Thank you for it !
) to ensure people will buy the product. But if the community app surpasses the homey team they should rejoice and declare their own app as deprecated as long as the dev is willing to keep it open source.
Anyway I will make a new release tomorrow.
