mouse does not work and clicking inspect give error message

[danielfarley]

mouse does not work and clicking inspect give error message: ares-inspect ERR! uncaughtException Error: spawn cmd ENOENT

TV is: LG webOS TV UF770V S/W version 04.06.25

using MagicRemoteService_1.2.2.8

TV in developer mode and install app works

[Cathwyler]

You have a webOS 2.0 TV. I'm trying recently to get it working in this issue

About inspector, this is a webOS CLI error (node.js).

Some thread suggest to check if you have "C:\Windows\System32" missing in your system environement PATH variable.

• https://stackoverflow.com/questions/57054403/problem-with-npm-start-error-spawn-cmd-enoent
• https://stackoverflow.com/questions/28624686/get-spawn-cmd-enoent-when-try-to-build-cordova-application-event-js85
  
  

You can try directly with CLI. https://webostv.developer.lge.com/develop/tools/cli-dev-guide#ares-inspect

• Device is the TV Name.
• Package is com.cathwyler.magicremoteservice.hdmi1 depending the input you selected.

Ex: ares-inspect --device TVNAME --app com.cathwyler.magicremoteservice.hdmi1

One last other possibility is that you don't have defaut web browser configured.

If you are able to get inspector working the console log from this build would help me a lot MagicRemoteService_1.2.2.7_AppVisibleLog.zip

[Cathwyler]

Duplicate of #11

[danielfarley]

Hi, with out changing the version im running from the command line i managed to get the debug up, here is a screenshot from that.

[danielfarley]

Ok, i installed MagicRemoteService_1.2.2.7_AppVisibleLog.zip

This time the Inspector worked (i had updated the path as your post suggested)

Ouput from console after install

Then i moved the tv remote, and the console log filled up and and kept scrolling with this.

Note this time i ran the app as an admin as i had noticed this is what the guy you linked to with the same old version of webos was doing. the time from my first screen shot was not run as admin.

I don't know if any of this will help but thanks for trying to get it running on old TV's :)

[Cathwyler]

Thanks for your help.

I anticipated and already fixed the bug i see in this screenshot in 1.2.2.8 version. But the 1.2.2.8 version did not work either.

This is another build with new log to help me to undertsand. MagicRemoteService_1.2.2.9DebugForceConnectApiLog.zip Can you send me the console log again ?

There is a possibility that the 1.2.2.8 version worked but you met a whole other problem (config, firwall, etc...)

[danielfarley]

This time i ran it as administrator also, it kind of works. The only thing is it will not move the mouse but double clicking on where i left the mouse with a normal mouse will open folder etc.. Same as the other guy with the older lg tv.

[Cathwyler]

And with this one ? MagicRemoteService_1.2.2.9AppVisibleLog.zip

You will probably need to redo your bind i'm working on an other issue in same time.

[danielfarley]

"redo you bind"??

[danielfarley]

Im not sure i understand 'redo you bind' but when i run this version this is what i get. Also no mouse operations seem to work.

[Cathwyler]

Just saw another problem MagicRemoteService_1.2.2.9APILog.zip

if you configured some bind in the remote tab you will need to reconfigure them. I changed the way the keyboard code are stored. But for the test its not really important.

[danielfarley]

This version still no mouse movement or clicking working.

[Cathwyler]

One last try for me this evening. MagicRemoteService_1.2.2.9APILogForceConnect.zip

Be sure to delete the old executable file before running the new one. And each time you need to install again on the TV..

[danielfarley]

Now mouse click and scroll work, but not position on screen. with above version

sleep well :-)

[Cathwyler]

Thanks again.Can you send me beginning logs ? And only with moving mouse ? It seems that there is another new probleme with this webOS sdk version. The app think the HDMI is unplugged AND running in background. I need to confirm if the input API is working on your webOS version. In the other thread issue this API was working and the app was only thinking she is in background.