LG TV WebOs 3.0

Moderator: leecollings

mapsindustrial
Posts: 6
Joined: Tuesday 23 February 2021 23:05
Target OS: Raspberry Pi / ODroid
Domoticz version:
Contact:

Re: LG TV WebOs 3.0

Post by mapsindustrial »

waltervl wrote: Wednesday 24 February 2021 22:20
mapsindustrial wrote: Wednesday 24 February 2021 16:32 I want solve the ploblem with the plugin and use it. Domoticz isn't a problem because i can reinstall and work fine.
Could be many things beside the plugin. If nobody else complains about crashes it could be your Domoticz install.
Do you run Stable or Beta?
Stable
What does the log file say?
Impossible see, domoticz no start.
What does the crash log say?
Impossible see, domoticz no start.
Is your SD card functioning right?
Yes.
Is your power adapter functioning correctly?
Yes.
Will Stable domoticz 2020.2 run on your system for 2 days without this plugin? Yes,
2 years.
User avatar
waltervl
Posts: 5148
Joined: Monday 28 January 2019 18:48
Target OS: Linux
Domoticz version: 2024.7
Location: NL
Contact:

Re: LG TV WebOs 3.0

Post by waltervl »

From the troubleshooting wiki
Crash log
When Domoticz really crashes a domoticz_crash.log file is created in the domoticz install folder eg /home/<user>/domoticz.
In this crash log you can search for the phrase signal_handler that will show which thread caused the crash of Domoticz.
To open the crash log you normally need root (also called administrator) rights. Use for example sudo cat domoticz_crash.log

The normal log file (if activated) is in /tmp or /var/log it depends what is specified in /etc/init.d/domoticz.sh

Both files should give clues what happened and if the plugin is the problem.
You can (as stated in the troubleshooting wiki) rename the domticz/plugins folder to for example plugins_old and the the plugin will not be activated and domoticz can start again.

If the database (domoticz/domoticz.db) got corrupt you could set a backup back (if activated earlier in Setup-Settings) from the domoticz/backups folder.

If you cannot find all of these please reinstall domoticz, activate log file and automatic backup and install the plugin again so you can debug after a crash what the issue was.
Domoticz running on Udoo X86 (on Ubuntu)
Devices/plugins: ZigbeeforDomoticz (with Xiaomi, Ikea, Tuya devices), Nefit Easy, Midea Airco, Omnik Solar, Goodwe Solar
mapsindustrial
Posts: 6
Joined: Tuesday 23 February 2021 23:05
Target OS: Raspberry Pi / ODroid
Domoticz version:
Contact:

Re: LG TV WebOs 3.0

Post by mapsindustrial »

Thx very mucho !!! This wkd try It !!!
mapsindustrial
Posts: 6
Joined: Tuesday 23 February 2021 23:05
Target OS: Raspberry Pi / ODroid
Domoticz version:
Contact:

Re: LG TV WebOs 3.0

Post by mapsindustrial »

waltervl wrote: Thursday 25 February 2021 0:23 From the troubleshooting wiki
Crash log
When Domoticz really crashes a domoticz_crash.log file is created in the domoticz install folder eg /home/<user>/domoticz.
In this crash log you can search for the phrase signal_handler that will show which thread caused the crash of Domoticz.
To open the crash log you normally need root (also called administrator) rights. Use for example sudo cat domoticz_crash.log

The normal log file (if activated) is in /tmp or /var/log it depends what is specified in /etc/init.d/domoticz.sh

Both files should give clues what happened and if the plugin is the problem.
You can (as stated in the troubleshooting wiki) rename the domticz/plugins folder to for example plugins_old and the the plugin will not be activated and domoticz can start again.

If the database (domoticz/domoticz.db) got corrupt you could set a backup back (if activated earlier in Setup-Settings) from the domoticz/backups folder.

If you cannot find all of these please reinstall domoticz, activate log file and automatic backup and install the plugin again so you can debug after a crash what the issue was.
find it this:

#3 0x002dbeb8 in signal_handler(int, siginfo_t*, void*) ()
#4 <signal handler called>
#5 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#6 0x76995230 in __GI_abort () at abort.c:79
#7 0x0096d02c in __gnu_cxx::__verbose_terminate_handler() ()
#8 0x008d04cc in __cxxabiv1::__terminate(void (*)()) ()
#9 0x008d0540 in std::terminate() ()
#10 0x008daff0 in __cxa_throw ()
#11 0x006ecaec in Json::throwLogicError(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&) ()
#12 0x006f2b98 in Json::Value::resolveReference(char const*, char const*) ()
#13 0x0037bca0 in http::server::CWebServer::GetJSonDevices(Json::Value&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, bool, bool, bool, long, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&) ()
#14 0x2c274448 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
mapsindustrial
Posts: 6
Joined: Tuesday 23 February 2021 23:05
Target OS: Raspberry Pi / ODroid
Domoticz version:
Contact:

Re: LG TV WebOs 3.0

Post by mapsindustrial »

Up
Sarcas
Posts: 86
Joined: Wednesday 11 October 2017 8:50
Target OS: Raspberry Pi / ODroid
Domoticz version: 2022.1ß
Location: Friesland
Contact:

Re: LG TV WebOs 3.0

Post by Sarcas »

I migrated to a rPi4 but this plugin refuses to work like it did on the old rPi3.

Code: Select all

2021-05-21 14:41:43.054 (LGTV) Processing 'onHeartbeatCallback' message
2021-05-21 14:41:43.054 LGTV: (LGTV) Calling message handler 'onHeartbeat'.
2021-05-21 14:41:43.197 LGTV: (LGTV) Status TV: active
2021-05-21 14:41:43.621 LGTV: (LGTV) App: Traceback (most recent call last):
2021-05-21 14:41:43.621 File "/home/pi/domoticz/plugins/LGTV/lg.py", line 1, in <module>
2021-05-21 14:41:43.621 from pylgtv import WebOsClient
2021-05-21 14:41:43.621 ModuleNotFoundError: No module named 'pylgtv'
2021-05-21 14:41:43.621 LGTV: (LGTV) Input: Traceback (most recent call last):
It is installed though:

Code: Select all

pi@raspberrypi4:~ $ pip3 install pylgtv
Defaulting to user installation because normal site-packages is not writeable
Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
Requirement already satisfied: pylgtv in ./.local/lib/python3.7/site-packages (0.1.9)
Requirement already satisfied: asyncio in ./.local/lib/python3.7/site-packages (from pylgtv) (3.4.3)
Requirement already satisfied: websockets in ./.local/lib/python3.7/site-packages (from pylgtv) (9.0.2)
I am using this fork : https://github.com/bramvreugd/Domoticz- ... bOS-Plugin
--

Domoticz on rPi4 - RFXCOM RFXtrx433 USB - ZW090 Z-Stick Gen5 EU - IKEA Tradfri - Philips HUE - YouLess meter - SolarEdge
User avatar
Dnpwwo
Posts: 819
Joined: Sunday 23 March 2014 9:00
Target OS: Raspberry Pi / ODroid
Domoticz version: Beta
Location: Melbourne, Australia
Contact:

Re: LG TV WebOs 3.0

Post by Dnpwwo »

@Sarcas,

Use 'sudo pip3 install pylgtv'.
The reasonable man adapts himself to the world; the unreasonable one persists to adapt the world to himself. Therefore all progress depends on the unreasonable man. George Bernard Shaw
Sarcas
Posts: 86
Joined: Wednesday 11 October 2017 8:50
Target OS: Raspberry Pi / ODroid
Domoticz version: 2022.1ß
Location: Friesland
Contact:

Re: LG TV WebOs 3.0

Post by Sarcas »

Dnpwwo wrote: Saturday 22 May 2021 0:10 Use 'sudo pip3 install pylgtv'.
Doh…

I should have thought of that.

Thanks!

S.
--

Domoticz on rPi4 - RFXCOM RFXtrx433 USB - ZW090 Z-Stick Gen5 EU - IKEA Tradfri - Philips HUE - YouLess meter - SolarEdge
woempiej
Posts: 9
Joined: Saturday 19 October 2019 18:47
Target OS: Raspberry Pi / ODroid
Domoticz version: 2021.1
Location: Netherlands
Contact:

Re: LG TV WebOs 3.0

Post by woempiej »

Hello,

I have the new LG OLED 2021
The plugin works great, thanks for all the effort!

I have only 1 problem with the device status when the TV is off
1. The status device shows "TimeoutError() occurred, is the TV off?({})"
2. The Source device then sets the source to "TV"

Can someone help ?

The below screenshots is the behaviour of the devices at night, when the TV is off
Attachments
TV Source.JPG
TV Source.JPG (103.1 KiB) Viewed 3043 times
TV Status.JPG
TV Status.JPG (105.02 KiB) Viewed 3043 times
drwurn
Posts: 68
Joined: Sunday 10 June 2018 16:59
Target OS: Raspberry Pi / ODroid
Domoticz version:
Contact:

Re: LG TV WebOs 3.0

Post by drwurn »

I get this in my logg, how to fix this?

Code: Select all

2021-09-25 19:30:46.037 LG TV: (LG TV) Info: TimeoutError() occurred, is the TV off?
2021-09-25 19:30:46.037
2021-09-25 19:30:46.038 (LGTV) Updating device from 0:'Off' to have values 1:'TimeoutError() occurred, is the TV off?
2021-09-25 19:30:46.038 (TimeoutError() occurred, is the TV off?
2021-09-25 19:30:46.038 )'.
2021-09-25 19:30:46.067 LG TV: (LG TV) Update 1:'TimeoutError() occurred, is the TV off?
2021-09-25 19:30:46.067 (TimeoutError() occurred, is the TV off?
2021-09-25 19:30:46.067 )' (LGTV)
2021-09-25 19:30:46.067 (LG TV - Source) Updating device from 0:'0' to have values 1:'10'.
2021-09-25 19:30:46.080 LG TV: (LG TV) Update 1:'10' (LG TV - Source)
2021-09-25 19:30:52.041 LG TV: (LG TV) Pushing 'onHeartbeatCallback' on to queue
2021-09-25 19:30:52.091 (LG TV) Processing 'onHeartbeatCallback' message
2021-09-25 19:30:52.091 LG TV: (LG TV) Calling message handler 'onHeartbeat'.
2021-09-25 19:30:54.856 LG TV: (LG TV) Status TV: off
2021-09-25 19:30:54.857 (LGTV) Updating device from 1:'TimeoutError() occurred, is the TV off?
2021-09-25 19:30:54.857 (TimeoutError() occurred, is the TV off?
2021-09-25 19:30:54.857 )' to have values 0:'Off'.
2021-09-25 19:30:54.878 LG TV: (LG TV) Update 0:'Off' (LGTV)
2021-09-25 19:30:54.878 (LG TV - Source) Updating device from 1:'10' to have values 0:'0'.
2021-09-25 19:30:54.892 LG TV: (LG TV) Update 0:'0' (LG TV - Source)
2021-09-25 19:31:12.025 LG TV: (LG TV) Pushing 'onHeartbeatCallback' on to queue
2021-09-25 19:31:12.075 (LG TV) Processing 'onHeartbeatCallback' message
2021-09-25 19:31:12.075 LG TV: (LG TV) Calling message handler 'onHeartbeat'.
2021-09-25 19:31:14.776 LG TV: (LG TV) Status TV: off
Maciek90
Posts: 19
Joined: Friday 05 March 2021 23:01
Target OS: NAS (Synology & others)
Domoticz version:
Contact:

Post by Maciek90 »

After installing the plugin and pylgtv, I receive the following errors in the logs:

Code: Select all

2023-11-06 19:28:57 LG TV Salon: Update 1:'(<class 'TypeError'>, TypeError("wait_for() got an unexpected keyword argument 'loop'"), <traceback object at 0x7f02136fd040>)
2023-11-06 19:28:57 )' (LG TV Salon - Status) 
Would someone be kind enough to tell me what the problem is?
rfvdboom
Posts: 38
Joined: Tuesday 20 September 2016 8:32
Target OS: Raspberry Pi / ODroid
Domoticz version: 2023.2
Location: Netherlands
Contact:

Re: LG TV WebOs 3.0

Post by rfvdboom »

I had the problem that i could start the TV with the plugin. When the tv is on, the plugin is working fine. I found out on the internet that more people had issues with switching the tv ON, even with the LG app. Apparently the LG switches off the wifi module in the Tv (after a while) when its off. Even when Quick start+ en Mobile tv is ON.

When i connected the TV with a LAN cable, it wasnt working either. Till i noticed that the TV uses an other MAC and IP-adres for the LAN connection. So here is the reminder to edit the plugin with the correct MAC and IP when you switch over to a LAN connection.

You can also use WOL (also present in Domoticz) to switch on the TV. I made a scene to switch on my LG and Denon and put in an extra step with de WOL the make sure my TV goes ON. My set-up is working fine now.
Odroid N2+ | Raspberry P 3 ModelB | RFXcom | AEOTEC Zwave | Honeywell Lyric T6| Milight | Milighthub (NodeMCU) | SolarEdge | P1 Smart meter USB | KAKU | Wemos D1 (esphome) | Denon | Logitech Harmony
VintageLogicJason
Posts: 4
Joined: Wednesday 31 January 2024 12:16
Target OS: Windows
Domoticz version:
Contact:

Re: LG TV WebOs 3.0

Post by VintageLogicJason »

rfvdboom wrote: Thursday 08 February 2024 11:32 I had the problem that i could start the TV with the plugin. When the tv is on, the plugin is working fine. I found out on the internet that more people had issues with switching the tv ON, even with the LG app. Apparently the LG switches off the wifi module in the Tv (after a while) when its off. Even when Quick start+ en Mobile tv is ON.

When i connected the TV with a LAN cable, it wasnt working either. Till i noticed that the TV uses an other MAC and IP-adres for the LAN connection. So here is the reminder to edit the plugin with the correct MAC and IP when you switch over to a LAN connection.

You can also use WOL (also present in Domoticz) to switch on the TV. I made a scene to switch on my LG and Denon and put in an extra step with de WOL the make sure my TV goes ON. My set-up is working fine now.
It seems like you've tackled the issue smartly by switching to a LAN connection and updating the MAC and IP accordingly. The WOL inclusion in your scene for powering on LG and Denon is a clever workaround.
Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest