webOS <4.0 doesn't run startup.sh, hence no SSH or Telnet #124

kopiro · 2022-10-29T10:18:12Z

I had a working version of Homebrew until I decided to upgrade to 05.50 system software, now webOS 4.4.2 (from 05.40).

The initial symptoms after upgrading are that SSH server is not working, Telnet is not working and also PicCap doesn't auto-start - but I still have elevated privileges.

After some debugging, it looks like that the autostart service registered by Homebrew is not being called; hence no startup.sh called.

I built a companion app that tries to call the autostart service via LunaBus; once installed, you can see that the first call to the autostart services fails because of a LunaBus error - but trying again it works.

Our assumption is that probably the service doesn't get registered in time or there are some overloads of the LunaBus at startup.

The error we get from LunaBus is this: https://github.com/webosose/luna-service2/blob/master/src/libluna-service2/transport.c#L239

Most likely, this new method of using previewMetadata in the appinfo.json doesn't work on webOS 4+, and the startup method was working in the previous firmware because of the presence of /etc/wam/plugins/conf.sh that called our script in the $EXTRA_CONF path:

EXTRA_CONF=/mnt/lg/cmn_data/wam/extra_conf.sh

if test -f $EXTRA_CONF; then
    source $EXTRA_CONF;
fi

That has now been removed from the 4.4 firmware.

The text was updated successfully, but these errors were encountered:

* adding discovery endpoint * updated startup * changed autostart endpoint name * installs startup.sh if not present

kopiro · 2022-10-29T17:35:19Z

In my case, I've a running Homebrew + startup with the companion app I built myself and managed to manually run the startup.sh script and everything works correctly, but U guess we ned to find a new way to run services at startup.

mariotaku · 2022-10-30T06:25:32Z

Hi, I think the previewMetadata was working on webOS 4 and above. Did it stop working recently?

kopiro · 2022-10-30T09:54:16Z

It doesn't work for me on webOs 4.4 - and most likely not working before?

mariotaku · 2022-10-31T09:45:24Z

I was using webOS 4.9 and 5.3 and it worked. Could you install Netflix and see if there are suggestions when you focus the icon?

kopiro · 2022-10-31T10:08:52Z

Nope, no suggestions.

Also, the Netflix ipk I inspected installed on the TV doesn't have any previewMetadata attribute.

I did a grep search and none of the package appinfo.json have it.

This is a TV from 2018, LG B8 running latest software with webos 4.4

kopiro · 2022-10-31T10:14:12Z

It may be possible that with webOS4.4 we are stick in a limbo where none of the previous startup method works (extra_conf.sh or start_devmode.sh) as they patched this but the firmware is too old to support new features like the previewMetadata.

Also, what I've noticed after some usage is that Homebrew stops working and all INSTALL options are greyed-out.

After some digging I found out that's because the LunaBus stop being responsive, causing no luna-message to be dispatched (by looking at ls-monitor).

mariotaku · 2022-10-31T13:42:19Z

That's really unfortunate. I think in such case only crashd method is available (if they are still working).

kopiro · 2022-10-31T13:43:27Z

Isn't crashd method only to gain root?

mariotaku · 2022-11-01T01:17:15Z

IIRC if the file is there it will always work.

fryc88 · 2022-11-01T14:55:10Z

I'm on same boat with kopiro, with SK8500PLA, MY2018 tv, with webos 4.4 as well.
Looks like i have same issues with doing root, with help of hellobox on discord i've managed to get kopiros ipk working on my tv because even that didn't work for me at the beggining, it was just showing some weird output, but hellobox suggested to do some magic, and after that i've got it. However now, after starting up tv, few minutes later homebrew ipk stop working, root status becomes pending and i can't launch/install new apps. After power cycle it does work for few minutes and then back on that again.

CoreyD97 · 2022-11-08T14:35:42Z

Similar boat to @kopiro and @fryc88 here. Managed to crashd my way to root, but autostart isn't working for me. I tried installing https://github.com/kopiro/webosbrew-autostart, but that encounters errors when running the autostart service as luna-send -n 1 'luna://org.webosbrew.hbchannel.service/autostart' '{}' gives the error {"returnValue":false,"errorText":"undefined is not a function"}.

Unlike @kopiro though, I do seem to get suggestions when hovering over home icons like Netflix as suggested earlier ( #124 (comment))

HagiaHaya · 2022-11-12T22:02:22Z

If you can't access the telnet via homebrew app, add this repo https://repo.webosapp.club -> install root.telnet and connect normally.

kopiro · 2022-12-14T19:18:22Z

@mariotaku yes, the file is there and you can get root - but no startup scripts.

soeren-a · 2023-01-20T08:07:17Z

I'm facing the exact same issue. Successfully rooted via crashd, PicCap and Hyperion are working as expected but only if I start the apps manually after TV start. Autostart is just not working, even though the option is enabled for both services.
Telnet and SSH are also not working.
Using webOS 5.50.10, and HomeBrew 0.5.1 on a OLED55B8LLA.
Any chance that the issue will be fixed?

throwaway96 · 2023-01-20T18:12:10Z

It's not something that can really be "fixed", since webOS 4.[0-4] is missing the feature we're currently using for autostart functionality. There are other ways of hooking into the boot process, but only for newer versions of webOS. The next version of Homebrew Channel will try to work around this to a limited extent by running startup.sh when the app is launched.

If anyone wants to look for new boot hooks, it would be greatly appreciated.

kopiro · 2023-01-20T19:13:04Z

Hello; I'll share the solution that works for me.

The main problem with not having autostart so far is only that PicCap and Hyperion/HDR don't start automatically, hence no LEDs.

What you only need is a device that is always on in your network - example: a raspberry Pi.

Generic solution

Install https://github.com/merdok/homebridge-webos-tv using npm -g install homebridge-webos-tv - I't s a plugin for homebridge that also has a nice CLI tool (/usr/bin/webostv) you can use.

I recently added support for sending raw luna-messages, we're going to use that.

Create a binary on your system with the following (example: /usr/local/bin/tv-autostart)

#!/bin/sh
TV_IP=192.168.0.40
TV_MAC=AA-BB-CC-DD-EE-FF
if ! ping $TV_IP; then 
  echo "TV is off"
  exit 1
fi
if curl -s "http://$TV_IP:8090/json-rpc?request=%7B%22command%22:%22serverinfo%22%7D"; then 
  echo "TV already rooted"
  exit 2
fi
echo "Calling autostart"
webostv luna-message $TV_IP $TV_MAC luna://org.webosbrew.hbchannel.service/autostart '{}'

And of course chmod +x /usr/local/bin/tv-autostart

Now, what you're going to do with this binary is really up to you.

Solution 0: Call this script in a CRON

Well, simply enough, setup a CRON that calls /usr/local/bin/tv-autostart every minute.

Solution 1: Use HomeBridge create a switch that you can use when you want to switch LEDs on/off

Since I don't always want the LEDs on (especially during daylight), I've setup a switch using in HomeKit so that I can just say "Hey Siri, switch on TV LEDs" or use the Homekit app in order to switch them on-off.

The script i'm using is a bit more complex than the one above, since it's also controlling HyperHDR status on/off - you can find it here and put it in /usr/local/bin/tv-hyperhdr

Then, install the plugin "homebridge-cmdswitch2" and add the following:

 {
    "platform": "cmdSwitch2",
    "name": "homebridge-cmdswitch2",
    "switches": [
        {
            "name": "TV LED",
            "on_cmd": "/usr/local/bin/tv-hyperhdr on",
            "off_cmd": "/usr/local/bin/tv-hyperhdr off",
            "state_cmd": "/usr/local/bin/tv-hyperhdr status",
            "polling": true,
            "interval": 30,
            "timeout": 15,
            "manufacturer": "HyperHDR"
        }
    ]
}

Now that you have this switch, you can leave it there to manually call it, or, for example, you can configure it to run when TV get switched on, if you also have the TV in HomeKit.

soeren-a · 2023-01-22T21:30:51Z

The luna://org.webosbrew.hbchannel.service/autostart '{}' call kills my Homebrew Channel app. After executing the command, I cannot install any apps from the Channel and the root status under"Settings" is shown as "pending".
It is "fixed" again after a restart if the TV was completely shut down.
But I can confirm that executing the command fixes the autostart and SSH issue for my TV.

kopiro · 2023-01-22T21:35:27Z

Hello - I can confirm you that this behaviour is "everything is locked" happened to me as well, but not because of the luna message you just sent.

It may be that the luna bus is a bit buggy with this webOS version, and messages don't get delivered - therefore, also the "install app" message is not delivered, or the "get root status" message is never delivered and is always shown as pending.

I'm not sure if this is a specific webOS issue or a problem with the homebrew service itself (with this version). - perhaps @Informatic knows more :)

soeren-a · 2023-01-22T21:36:50Z

As a workaround for anyone that uses the LG integration within Home Assistant:
I created a script that executes the command suggested by @kopiro, which can be used in an automation (e.g. on TV start):

alias: Enable app autostart on rooted LG TV
sequence:
  - service: webostv.command
    data:
      entity_id: media_player.lg_tv
      command: system.notifications/createAlert
      payload:
        message: Executing HB Channel autostart...
        modal: false
        buttons:
          - label: OK
            focus: true
            buttonType: ok
            onClick: luna://org.webosbrew.hbchannel.service/autostart
            params: {}
        type: confirm
        isSysReq: true
  - delay:
      hours: 0
      minutes: 0
      seconds: 2
      milliseconds: 0
    alias: Delay for Button click to close the alert toast
  - service: webostv.button
    data:
      entity_id: media_player.lg_tv
      button: ENTER
mode: single
icon: mdi:television-ambient-light

panic175 · 2023-01-22T22:14:23Z

My workaround also uses Home Assistant but with a custom component: https://github.com/panic175/webosbrew-autostart-helper

popy2k14 · 2023-03-21T19:58:57Z

@panic175 tried your custom integration, sadly it doesn't work. The first time the remote control Dialog was presented on the tv. I clicked yes and nothing happens. Also she i run the custom component service again.

When I'll open HBC autostart apps will be launched. So my setup works, except autostart .

Any hints i can debug this?

panic175 · 2023-03-22T13:58:46Z

@popy2k14 Do you see any errors from the custom component in your Home Assistant Logs?

popy2k14 · 2023-03-22T20:57:58Z

@panic175 sorry for hijacking your thread. I have webOS 6.3.1-411 (kisscurl-kinglake). In my case i had to uncheck all EULAs and retry (incl. reboot) until they are unchecked (two times in my case). Then enabled the TOP one and autostart is working again.

Just if anybody like me has this issue and needs this information.
I am in conact with the https://gist.github.com/throwaway96/e811b0f7cc2a705a5a476a8dfa45e09f owner, so maybe this info get's also added there.

thx again

kitsuned · 2023-07-17T22:32:12Z

hi there!

I think I found a way:

luna-send -f -n 1 -m org.webosbrew.hbchannel.service luna://com.webos.service.activitymanager/create '{
 "activity": {
  "name": "org.webosbrew.hbchannel.service.autostart",
  "description": "who cares",
  "type": {
   "foreground": true,
   "persist": true, 
   "continuous": true
  },
  "trigger": {
   "method": "luna://com.webos.bootManager/getBootStatus",
   "params": {
    "subscribe": true
   },
   "where": {
    "prop": [
     "signals",
     "core-boot-done"
    ],
    "op": "=",
    "val": true
   }
  },
  "callback": {
   "method": "luna://org.webosbrew.hbchannel.service/autostart",
   "params": {}
  }
 },
 "replace": true,
 "start": true
}'

I haven't tested this on 4.4.
I would be glad to receive any feedback!

Doridian · 2023-07-17T22:56:11Z

hi there!

I think I found a way:
luna-send -f -n 1 -a org.webosbrew.hbchannel.service luna://com.webos.service.activitymanager/create '{
......
}'
I haven't tested this on 4.4. I would be glad to receive any feedback!

On my webOS TV (version 4.4.2), this above worked perfectly, I could finally disable my HomeAssistant automation :D

kitsuned · 2023-07-17T23:07:51Z

On my webOS TV (version 4.4.2), this above worked perfectly, I could finally disable my HomeAssistant automation :D

that was quick! thank you for the feedback.

follow #143 👀

Chaoscontrol · 2023-10-11T16:32:13Z

As a workaround for anyone that uses the LG integration within Home Assistant: I created a script that executes the command suggested by @kopiro, which can be used in an automation (e.g. on TV start):

alias: Enable app autostart on rooted LG TV
sequence:
  - service: webostv.command
    data:
      entity_id: media_player.lg_tv
      command: system.notifications/createAlert
      payload:
        message: Executing HB Channel autostart...
        modal: false
        buttons:
          - label: OK
            focus: true
            buttonType: ok
            onClick: luna://org.webosbrew.hbchannel.service/autostart
            params: {}
        type: confirm
        isSysReq: true
  - delay:
      hours: 0
      minutes: 0
      seconds: 2
      milliseconds: 0
    alias: Delay for Button click to close the alert toast
  - service: webostv.button
    data:
      entity_id: media_player.lg_tv
      button: ENTER
mode: single
icon: mdi:television-ambient-light

Massive thanks for this. It helped me find the syntax needed to run the PicCap service directly from Home Assistant, as it doesn't autorun in my webOS 3.4.0. Might be that the createAlert method doesn't exist in that version?

However, your script doesn't work for me. The button step works, but the toast alert doesn't appear at any time. Any idea why?

[21:14:25.594][INFO] com.webos.service.secondscreen.gateway SSG_PERM Failed to find permissions for ssap://system.notifications/createAlert: Error: method /createAlert not found in interface system.notifications {}

soeren-a · 2023-10-11T20:54:52Z

Hmm, yes, it seems that the method is not found on your OS. But the error message also indicates, that you do not have the right permissions to execute? Not sure what's the issue here. All available methods are listed here, but without OS version support information: https://github.com/bendavid/aiopylgtv/blob/master/aiopylgtv/endpoints.py

Chaoscontrol · 2023-10-11T20:58:00Z

@soeren-a Yeah, I have been checking that and testing all I can think of. But can't make it work. createToast works fine, but createAlert doesn't.

Isn't there any other way to send the command to start SSH from HA?

soeren-a · 2023-10-11T21:03:14Z

@soeren-a Yeah, I have been checking that and testing all I can think of. But can't make it work. createToast works fine, but createAlert doesn't.

Isn't there any other way to send the command to start SSH from HA?

Not that I'm aware of. As far as I know, a user interaction like a button click is needed to execute the call. Showing a toast with a button and click it was the easiest way to achieve that.

TulipVang · 2023-11-14T05:37:48Z

In my case, I've a running Homebrew + startup with the companion app I built myself and managed to manually run the startup.sh script and everything works correctly, but U guess we ned to find a new way to run services at startup.

I face same issue.
Can you help me to manually run the startup.sh script please.

throwaway96 · 2023-11-15T03:55:22Z

@TulipVang

Opening recent versions of Homebrew Channel will execute startup.sh.

swiss6th · 2024-01-06T21:40:56Z

I haven't tested this on 4.4. I would be glad to receive any feedback!

@kitsuned, I have a C8 on 4.4.2, and this solved the issue for me as well. startup.sh is now running, and the autostart of PicCap and HyperHDR are both working now.

Dahman97 · 2024-01-17T06:22:29Z

I haven't tested this on 4.4. I would be glad to receive any feedback!

I would like to thank you for your solution as it worked like a charm, after reboot everything that is supposed to auto start runs as it should, including hyperhdr and picap.... WebOS V-4.4-x. thanks a lot dude! TV model from 2019 updated to last webOS available for its gen :)

dancingmadkefka · 2024-02-17T17:24:59Z

@TulipVang

Opening recent versions of Homebrew Channel will execute startup.sh.

Hey thanks a lot, I was struggling all day to try to ssh into my B8 running 4.4.2 and this advice helped. I ran the homebrew updater and when I rebooted it popped up with a message saying that "autostart.sh has been updated" or something. Once that happened, I was able to ssh into it. Also handy that the updater allows you to open an emergency telnet session".

rmp63526 · 2024-03-04T21:42:11Z

@kitsuned
It also worked for my Oled TV, WebOs 4.4.2-11 Goldilocks - Gorongosa/ Softwareversion 05.50.15
I have only noticed that when I switch off the TV, wait 1 minute and then unplug it and switch it on again, it goes into failsafe mode the first time it starts. When I restart it, it works again.

kopiro · 2024-06-16T09:29:30Z

It looks like that 804f947 fixed this - we can close this issue!

throwaway96 · 2024-06-16T14:02:28Z

It's not fixed on webOS <4.0.

kopiro · 2024-06-16T19:47:32Z

Sorry! :)

angyp · 2024-07-01T10:31:51Z

I would like to get this going on
OLED65C7T-T
Firmware version 06.10.30
webOS version 3.9.0
Used DejaVuln
The only way I can get it to run is to open the homebrew app.

angyp · 2024-07-03T11:08:27Z

hi there!

I think I found a way:

luna-send -f -n 1 -m org.webosbrew.hbchannel.service luna://com.webos.service.activitymanager/create '{
 "activity": {
  "name": "org.webosbrew.hbchannel.service.autostart",
  "description": "who cares",
  "type": {
   "foreground": true,
   "persist": true, 
   "continuous": true
  },
  "trigger": {
   "method": "luna://com.webos.bootManager/getBootStatus",
   "params": {
    "subscribe": true
   },
   "where": {
    "prop": [
     "signals",
     "core-boot-done"
    ],
    "op": "=",
    "val": true
   }
  },
  "callback": {
   "method": "luna://org.webosbrew.hbchannel.service/autostart",
   "params": {}
  }
 },
 "replace": true,
 "start": true
}'

I haven't tested this on 4.4. I would be glad to receive any feedback!

How do I use this? Auto start doesn't work on my TV

lsahnicne · 2024-08-24T15:37:03Z

hi there!

I think I found a way:

luna-send -f -n 1 -m org.webosbrew.hbchannel.service luna://com.webos.service.activitymanager/create '{
 "activity": {
  "name": "org.webosbrew.hbchannel.service.autostart",
  "description": "who cares",
  "type": {
   "foreground": true,
   "persist": true, 
   "continuous": true
  },
  "trigger": {
   "method": "luna://com.webos.bootManager/getBootStatus",
   "params": {
    "subscribe": true
   },
   "where": {
    "prop": [
     "signals",
     "core-boot-done"
    ],
    "op": "=",
    "val": true
   }
  },
  "callback": {
   "method": "luna://org.webosbrew.hbchannel.service/autostart",
   "params": {}
  }
 },
 "replace": true,
 "start": true
}'

I haven't tested this on 4.4. I would be glad to receive any feedback!

It seems to take a few moments after turning the TV on to initialize (judging by lginputhook key binds activation), but ultimately works. Thanks!
LG OLED C2
webOS 7.2.0-47 (mullet-marine) 03.21.45
Homebrew channel 0.6.3

How do I use this? Auto start doesn't work on my TV

SSH into TV and execute the code

angyp · 2024-08-24T22:48:33Z

I tried that and it didn't work on my OLED C7 so I thought I was doing it wrong. Seems no way to get autostart working on my TV. Everything starts working correctly after I open the Homebrew channel.

xenouch · 2024-10-25T13:39:39Z

Not work for me.
I need to open hbchannel after TV start if i want lginputhook to work.
But ssh work without starting hbchannel

Device Model
LG 43UR73006LA

Device OS
WebOS 8.3.0-2306

Software version
03.31.16

Hbchannel version
0.7.1

kopiro referenced this issue Oct 29, 2022

Autostart Fallback for webOS 4+ (#102)

3e970df

* adding discovery endpoint * updated startup * changed autostart endpoint name * installs startup.sh if not present

kopiro changed the title ~~After upgrade to 05.50, Autostart doesn't work~~ webOS 4.4 doesn't run startup.sh, hence no SSH or Telnet Oct 29, 2022

Informatic mentioned this issue Dec 13, 2022

ssh connection not possible [webos 4.9.5-10] #120

Closed

panic175 mentioned this issue Jan 17, 2023

[working] root OLED C9 (possibly others too) with newest Firmware (05.30.10 - 9/28/2022) RootMyTV/RootMyTV.github.io#85

Open

throwaway96 closed this as completed Nov 15, 2023

throwaway96 reopened this Nov 15, 2023

throwaway96 changed the title ~~webOS 4.4 doesn't run startup.sh, hence no SSH or Telnet~~ webOS <4.5 doesn't run startup.sh, hence no SSH or Telnet Feb 2, 2024

throwaway96 added enhancement New feature or request help wanted Extra attention is needed bug Something isn't working labels Feb 2, 2024

kitsuned added this to the 0.6.4 milestone Jun 11, 2024

kopiro closed this as completed Jun 16, 2024

throwaway96 reopened this Jun 16, 2024

throwaway96 changed the title ~~webOS <4.5 doesn't run startup.sh, hence no SSH or Telnet~~ webOS <4.0 doesn't run startup.sh, hence no SSH or Telnet Jun 16, 2024

lsahnicne mentioned this issue Aug 24, 2024

hooks do not persist on "true" reboot (eg Quick Start+ is off or power is lost) Simon34545/lginputhook#13

Open

webOS <4.0 doesn't run startup.sh, hence no SSH or Telnet #124

webOS <4.0 doesn't run startup.sh, hence no SSH or Telnet #124

Comments

kopiro commented Oct 29, 2022 • edited Loading

kopiro commented Oct 29, 2022

mariotaku commented Oct 30, 2022

kopiro commented Oct 30, 2022

mariotaku commented Oct 31, 2022

kopiro commented Oct 31, 2022

kopiro commented Oct 31, 2022

mariotaku commented Oct 31, 2022

kopiro commented Oct 31, 2022 • edited Loading

mariotaku commented Nov 1, 2022

fryc88 commented Nov 1, 2022

CoreyD97 commented Nov 8, 2022

HagiaHaya commented Nov 12, 2022

kopiro commented Dec 14, 2022

soeren-a commented Jan 20, 2023

throwaway96 commented Jan 20, 2023

kopiro commented Jan 20, 2023 • edited Loading

Generic solution

Solution 0: Call this script in a CRON

Solution 1: Use HomeBridge create a switch that you can use when you want to switch LEDs on/off

soeren-a commented Jan 22, 2023 • edited Loading

kopiro commented Jan 22, 2023 • edited Loading

soeren-a commented Jan 22, 2023 • edited Loading

panic175 commented Jan 22, 2023

popy2k14 commented Mar 21, 2023

panic175 commented Mar 22, 2023

popy2k14 commented Mar 22, 2023

kitsuned commented Jul 17, 2023 • edited Loading

Doridian commented Jul 17, 2023 • edited Loading

kitsuned commented Jul 17, 2023

Chaoscontrol commented Oct 11, 2023 • edited Loading

soeren-a commented Oct 11, 2023

Chaoscontrol commented Oct 11, 2023 • edited Loading

soeren-a commented Oct 11, 2023

TulipVang commented Nov 14, 2023 • edited Loading

throwaway96 commented Nov 15, 2023

swiss6th commented Jan 6, 2024

Dahman97 commented Jan 17, 2024

dancingmadkefka commented Feb 17, 2024

rmp63526 commented Mar 4, 2024 • edited Loading

kopiro commented Jun 16, 2024

throwaway96 commented Jun 16, 2024

kopiro commented Jun 16, 2024

angyp commented Jul 1, 2024

angyp commented Jul 3, 2024

lsahnicne commented Aug 24, 2024 • edited Loading

angyp commented Aug 24, 2024

xenouch commented Oct 25, 2024

kopiro commented Oct 29, 2022 •

edited

Loading

kopiro commented Oct 31, 2022 •

edited

Loading

kopiro commented Jan 20, 2023 •

edited

Loading

soeren-a commented Jan 22, 2023 •

edited

Loading

kopiro commented Jan 22, 2023 •

edited

Loading

soeren-a commented Jan 22, 2023 •

edited

Loading

kitsuned commented Jul 17, 2023 •

edited

Loading

Doridian commented Jul 17, 2023 •

edited

Loading

Chaoscontrol commented Oct 11, 2023 •

edited

Loading

Chaoscontrol commented Oct 11, 2023 •

edited

Loading

TulipVang commented Nov 14, 2023 •

edited

Loading

rmp63526 commented Mar 4, 2024 •

edited

Loading

lsahnicne commented Aug 24, 2024 •

edited

Loading