LGTV2012 interfers with PLUGIN @Shelly

Ludelag commented 3 years ago

I have installed the plugin LGTV2012 to my homebridge, configured with the TV info, it has worked quiet well, but then I notice that the Shelly devices stop being recognized since I install the LGTV2012 Plugin, i decide to uninstall the plugin LGTV and erease from the Json the confirguration, all came to normal. How to fix this issue?

My LGTV2012 JSON configurations was:

{ "platform": [ { "platform": "lgtv-2012", "name": "MY LG KITCHEN", "ip": "192.00.00.00", "pairingKey": "123456", "min_volume": 2, "max_volume": 20, } ] } Any ideas how could I fix it?

markus7017 commented 3 years ago

hmm, the only thing I could imagine are

LG uses the same UDP port - seems to be unlikely, but who knows
LG causes some problems in the mDNS discovery

Does only the discovery stop to work, or are the Shellys not working anymore

Dis you checked a DEBUG log?

markus7017 commented 3 years ago

please add the tag [shelly] to the title, this is the usual convention and what I'm searching for, I found this one by mistake

Ludelag commented 3 years ago

hmm, the only thing I could imagine are

LG uses the same UDP port - seems to be unlikely, but who knows

LG causes some problems in the mDNS discovery

Does only the discovery stop to work, or are the Shellys not working anymore

Dis you checked a DEBUG log?

The discovery stops working, not found by home app and looks like get into a loop updating status and finding no answer from the rest of devices.

i0null commented 3 years ago

Hi @Ludelag, this plugin connects directly to IP in the config via TCP 8080 (no mDNS discovery). I've not used Shelly before but I believe that uses 8081. So not entirely sure what would cause the issue. The only explanation I can think off is the SetTimeout in the code to check the TV Status, it seems unlikely but I was hoping a better method would surface for checking the TV status.

Are you using Homebridge or Hoobs (and which version)?

Could you share any logs?

markus7017 commented 3 years ago

Shelly doesn't listen to http, it uses

REST calls to read status/set config
UDP for CoIoT discovery
IP Multicast for CoIoT status updates

please add the [shelly] tag to the title

Ludelag commented 3 years ago

Hi @Ludelag, this plugin connects directly to IP in the config via TCP 8080 (no mDNS discovery). I've not used Shelly before but I believe that uses 8081. So not entirely sure what would cause the issue. The only explanation I can think off is the SetTimeout in the code to check the TV Status, it seems unlikely but I was hoping a better method would surface for checking the TV status.

Are you using Homebridge or Hoobs (and which version)?

Could you share any logs?

Hi @i0null thank to answer my post, I am using Homebridge. the funny of this is that when I install the plugin LGTV2012 all works good, I have the Shelly Plugin and the WebOS plugin as well. So when I turn of the tv connected to the plugin LGTV2012 after 20 seconds HomeKit start to update the status of all the devices including shelly and WebOS. but Hue devices or other connected directly to its own firmware to HomeKit are ok, even one shelly devices which I updated with Homekit firmware.

Ludelag commented 3 years ago

@markus7017 Could you share any logs? what logs, the Homebridge?

markus7017 commented 3 years ago

Are we talking a out the Shelly binding or Shelly integration into Homebridge?

It’s you installation so you share the logs? Why do you think that I could share something to diagnose a problem on your system? Check openhab.log for indications

markus7017 commented 3 years ago

Are we talking a out the Shelly binding or Shelly integration into Homebridge?

It’s you installation so you share the logs? Why do you think that I could share something to diagnose a problem on your system? Check openhab.log for indications

Ludelag commented 3 years ago

Are we talking a out the Shelly binding or Shelly integration into Homebridge?

It’s you installation so you share the logs? Why do you think that I could share something to diagnose a problem on your system? Check openhab.log for indications

No, I just repeat your question, what logs do you need I share

markus7017 commented 3 years ago

Again: Are you using the Shelly binding or some other type of integration?

IF you are using the Shelly binding

open OH console
enter "log:set DEBUG org.openhab.binding.shelly"
the same for the LGTV binding
restart OH
and copy the log extract showing the initialization of both bindings/things (Shelly+LG)
include all lines from the beginng of the initialization, full initialization and first interaction with the device

Ludelag commented 3 years ago

Ok, I will

markus7017 commented 3 years ago

?

Ludelag commented 3 years ago

Today I will, sorry wasn't at home, I was in a business travel

Ludelag commented 3 years ago

[2020-10-11 23:54:03] Homebridge is running on port 51826. [2020-10-11 23:54:03] [HB Supervisor] Sending SIGKILL to Homebridge [2020-10-11 23:54:03] [HB Supervisor] Homebridge Process Ended. Code: null, Signal: SIGKILL [2020-10-11 23:54:08] [HB Supervisor] Restarting Homebridge... [2020-10-11 23:54:08] [HB Supervisor] Starting Homebridge with extra flags: -I [2020-10-11 23:54:08] [HB Supervisor] Started Homebridge v1.1.6 with PID: 3948 [2020-10-11 23:54:09] Loaded config.json with 1 accessories and 3 platforms. [2020-10-11 23:54:09] --- [2020-10-11 23:54:09] Loaded plugin: homebridge-config-ui-x@4.28.1 [2020-10-11 23:54:09] Registering platform 'homebridge-config-ui-x.config' [2020-10-11 23:54:09] --- [2020-10-11 23:54:09] Loaded plugin: homebridge-lgtv-2012@0.2.0 [2020-10-11 23:54:09] Registering accessory 'homebridge-lgtv-2012.lgtv-2012' [2020-10-11 23:54:09] --- [2020-10-11 23:54:09] Loaded plugin: homebridge-shelly@0.15.5 [2020-10-11 23:54:10] Registering platform 'homebridge-shelly.Shelly' [2020-10-11 23:54:10] --- [2020-10-11 23:54:10] Loaded plugin: homebridge-webos-tv@2.0.5 [2020-10-11 23:54:10] Registering platform 'homebridge-webos-tv.webostv' [2020-10-11 23:54:10] --- [2020-10-11 23:54:10] Loading 3 platforms... [2020-10-11 23:54:10] [Config] Initializing config platform... [2020-10-11 23:54:10] [Config] Running in Service Mode [2020-10-11 23:54:10] [Shelly] Initializing Shelly platform... [2020-10-11 23:54:10] [webostv] Initializing webostv platform... [2020-10-11 23:54:10] Loading 1 accessories... [2020-10-11 23:54:10] [MY LG KITCHEN] Initializing lgtv-2012 accessory... [2020-10-11 23:54:10] [Shelly] 10 accessories loaded from cache [2020-10-11 23:54:10] [webostv] Init - initializing devices [2020-10-11 23:54:10] [webostv] [LG TXOCO] Init - got TV configuration, initializing device with name: LG TXOCO [2020-10-11 23:54:10] LG TXOCO is running on port 56603. [2020-10-11 23:54:10] Please add [LG TXOCO] manually in Home app. Setup Code: 031-45-154 [2020-10-11 23:54:10] [Shelly] Admin server is running on port 8181 Setup Payload: X-HM://0023ISYWYHLMA Enter this code with your HomeKit app on your iOS device to pair with Homebridge:

┌────────────┐     
│ 031-45-154 │     
└────────────┘

[2020-10-11 23:54:10] Homebridge is running on port 51826.

[2020-10-11 23:54:18] [MY LG KITCHEN] TV [192.168.1.17]: On Channel: #0

[xmldom error] invalid doc source @#[line:0,col:undefined]

[xmldom error] invalid doc source @#[line:0,col:undefined] [2020-10-12 0:02:05] [MY LG KITCHEN] TV [192.168.1.17]: On Channel: #undefined undefined

[2020-10-12 0:02:33] [MY LG KITCHEN] TV [192.168.1.17]: On Channel: #NaN

here is it.

file 16

markus7017 commented 3 years ago

Hi, just noticed that we are not talking about the openHAB Shelly binding, sorry then I cN’t help

i0null / homebridge-lgtv-2012

LGTV2012 interfers with PLUGIN @Shelly #8