You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Per the code and my understanding(?) The powerOnAndConnect() function should, if passed to it, adjust maximum retries and timeout per retry right? Well I set retries to 90, and timeout to 1 second, i.e. 1000, and get connection refused? TV does power up, (not WOL in state) because it is only off for a few seconds. So do I understand the code wrong? As I recall this was an old issue previously reported, so is it just not fixed yet, or something not working right now?
Code example below... should way for up to 90 seconds for TV to be FULLY online... meaning more than just a ping, but all functions working, say getCurrentApp returns valid results for example, per my understanding. But I get connection refused almost immediately, and I know the TV powers up but is not fully responding.
When TV is powered on, or has only been offline for less than about 2 minutes, everything works as expected. However, if TV has been offline, for more than about 2 minutes... it has dropped off the network and WOL is required.
But there are 2 issues....
No matter how I pass the 90 retries, and the 1000 timeout, it is ignored apparently. I have tried as above, also as just raw numbers, nothing seems to be accepted. Yet I recall this was the expected behavior from past discussion.
From the time WOL happens, and TV powers up, the above code continues on, attempt to return getCurrentApp() but because the TV is not 'fully' on the wired so to speak, error is generated. when getCurrentApp() called. It is pingable, but not functional. Literally the lights-are-on-but-no-one-is-home type of issue.
Here is where the retries and timeout are ignored... Does not seem to await even 10 seconds which seems to be hard coded default? TV has been offline, powered off for at least 3 minutes. Note the 10 retries, but should be 90 per the code example, right?
# node lgtv-ip-control.mjs
MaxRetriesError: maximum retries of 10 reached
at Socket.connect (file:///root/node_modules/lgtv-ip-control/dist/classes/TinySocket.js:82:37)
at Socket.emit (node:events:517:28)
at Socket._onTimeout (node:net:598:8)
at listOnTimeout (node:internal/timers:569:17)
at process.processTimers (node:internal/timers:512:7) {
cause: undefined
The text was updated successfully, but these errors were encountered:
Per the code and my understanding(?) The powerOnAndConnect() function should, if passed to it, adjust maximum retries and timeout per retry right? Well I set retries to 90, and timeout to 1 second, i.e. 1000, and get connection refused? TV does power up, (not WOL in state) because it is only off for a few seconds. So do I understand the code wrong? As I recall this was an old issue previously reported, so is it just not fixed yet, or something not working right now?
Code example below... should way for up to 90 seconds for TV to be FULLY online... meaning more than just a ping, but all functions working, say getCurrentApp returns valid results for example, per my understanding. But I get connection refused almost immediately, and I know the TV powers up but is not fully responding.
Test Code...
When TV is powered on, or has only been offline for less than about 2 minutes, everything works as expected. However, if TV has been offline, for more than about 2 minutes... it has dropped off the network and WOL is required.
But there are 2 issues....
No matter how I pass the 90 retries, and the 1000 timeout, it is ignored apparently. I have tried as above, also as just raw numbers, nothing seems to be accepted. Yet I recall this was the expected behavior from past discussion.
From the time WOL happens, and TV powers up, the above code continues on, attempt to return getCurrentApp() but because the TV is not 'fully' on the wired so to speak, error is generated. when getCurrentApp() called. It is pingable, but not functional. Literally the lights-are-on-but-no-one-is-home type of issue.
Here is where the retries and timeout are ignored... Does not seem to await even 10 seconds which seems to be hard coded default? TV has been offline, powered off for at least 3 minutes. Note the 10 retries, but should be 90 per the code example, right?
The text was updated successfully, but these errors were encountered: