search

AntonioMeireles / homebridge-vieramatic

Homebridge plugin for Panasonic™ Viera™ TVs (includes support for 2018 and later models)
Apache License 2.0
43 stars 9 forks source link

TV is not reachable #73

Closed rpvandoorn closed 2 years ago

rpvandoorn commented 3 years ago

Describe your issue

[19/03/2021, 13:15:42] Homebridge v1.3.4 (Homebridge) is running on port 51398.
[19/03/2021, 13:15:42] [PanasonicVieraTV] IGNORING '192.168.1.204' as it is not reachable, and we can't relay on cached data as it seems that it was never ever seen and setup before.

Please make sure that your TV is powered ON and connected to the network.

Issue Context

Please add the following items, when applicable:

  1. the contents of accessories/vieramatic.json (path is relative to homebridge's datadir)

    {
        "tvs": [
            {
                "friendlyName": "TV Woonkamer",
                "ipAddress": "192.168.1.204",
                "encKey": "XXXX",
                "appId": "XXXX",
                "hdmiInputs": [
                    {
                        "id": "2",
                        "name": "XXXX"
                    }
                ],
                "disabledAppSupport": false,
                "customVolumeSlider": true
            }
        ],
        "platform": "PanasonicVieraTV"
    }

  2. Details about your specific homebridge setup

    • hardware and arch Raspberry Pi model B (2012)
    • Operating System and its version Raspbian GNU/Linux Buster (10)
    • NodeJS version v14.15.1
    • Homebridge version 1.3.4
    • specific vieramatic version being used 3.1.7
    • Viera TV(s) model(s) being used (and connectivity type being used - wired or wireless) TX-65GZW954, wired

  3. anything else you may find relevant

Recently updated the TV to new software version 3.222, before that (in a previous setup) everything worked fine. https://av.jpn.support.panasonic.com/support/global/cs/tv/download/fw/eu_2019/down_eu_uk_cis_02.html

I discovered Panasonic TV Remote 3 is not working as well. Last time I checked that app working was also before the software was updated to 3.222. The app displays that the TV needs to be connected to the same wifi network. The TV is wired connected.

TV Remote 2 is working correct.

AntonioMeireles commented 3 years ago

humm...

can you physically turn off/unplug TV from power and plug it again (and check that IP address hasn't changed for some reason) ? Thanks in advance and a great weekend!

rpvandoorn commented 3 years ago

Nope, it’s fixed! I already did that, but it didn’t help. Is it possible this problem has something to do with the software update on the TV? Because everything worked before in a previous setup.

AntonioMeireles commented 3 years ago

dunno. the fact that Panasonic TV Remote 3 also not working a priori should exclude any issue in my side...

so, some debugging is needed ...

Thanks in advance and a great weekend!

wlee88 commented 3 years ago

~i have this issue too. All the tv remote app settings are on too (works with TV Remote 2 also - didn't try TV Remote 3).~

~I'll try deleting the pairing and repairing - i'll re-edit this comment if it works/doesn't work.~

Update: After screwing around for an hour in the morning- and then coming back in the afternoon/restarting homebridge to see the logs again - it's miraculously working again

AntonioMeireles commented 3 years ago

@rpvandoorn

(hi) any update on your side ?

rpvandoorn commented 3 years ago

is the TV pingable ? (check plz) Yes, average time of 3ms

is it connect to the network wirelessly or wired ? (if wirelessly could you try wired if possible ?) Wired. I tried wireless, but that also doesn't work. New IP, new config, but no changes

could it be that the update somehow reset some settings ?

on your TV go to Menu -> Network -> TV Remote App Settings and make sure that the following settings really are all turned ON:

TV Remote Powered On by Apps Networked Standby all settings in this menu are switched to on

AntonioMeireles commented 3 years ago

@rpvandoorn

could you please attach here full homebridge boot logs ?

thanks again for your patience!

wlee88 commented 3 years ago

@rpvandoorn sorry to ask the obvious but is it still an issue if you reboot homebridge? I get this error if I turn off the tv from the mains then turn it back on again.

If I restart homebridge it all works again.

rpvandoorn commented 3 years ago

@rpvandoorn sorry to ask the obvious but is it still an issue if you reboot homebridge? I get this error if I turn off the tv from the mains then turn it back on again.

If I restart homebridge it all works again.

No problem, I have restarted Homebridge many times, but the error message keeps coming back.

@AntonioMeireles Allright here it is...

[23/03/2021, 08:24:32] [HB Supervisor] Restarting Homebridge... [23/03/2021, 08:24:32] [HB Supervisor] Starting Homebridge with extra flags: -I [23/03/2021, 08:24:32] [HB Supervisor] Started Homebridge v1.3.4 with PID: 3613 [23/03/2021, 08:26:20] [HB Supervisor] OS: Linux 5.10.11-v7+ arm [23/03/2021, 08:26:20] [HB Supervisor] Node.js v14.15.1 /usr/local/bin/node [23/03/2021, 08:26:20] [HB Supervisor] Homebridge Path: /usr/local/lib/node_modules/homebridge/bin/homebridge [23/03/2021, 08:26:20] [HB Supervisor] UI Path: /usr/local/lib/node_modules/homebridge-config-ui-x/dist/bin/standalone.js [23/03/2021, 08:26:48] [Homebridge UI] Homebridge Config UI X v4.41.0 is listening on :: port 8581 [23/03/2021, 08:26:50] [HB Supervisor] Starting Homebridge with extra flags: -I [23/03/2021, 08:26:50] [HB Supervisor] Started Homebridge v1.3.4 with PID: 661 Initializing HAP-NodeJS v0.9.4... [23/03/2021, 08:26:54] Loaded config.json with 8 accessories and 4 platforms. [23/03/2021, 08:26:54] Loaded 2 cached accessories from cachedAccessories. [23/03/2021, 08:26:54] --- [23/03/2021, 08:26:57] Loaded plugin: homebridge-config-ui-x@4.41.0 [23/03/2021, 08:26:57] Registering platform 'homebridge-config-ui-x.config' [23/03/2021, 08:26:57] --- [23/03/2021, 08:26:57] Loaded plugin: homebridge-dummy@0.5.0 [23/03/2021, 08:26:57] Registering accessory 'homebridge-dummy.DummySwitch' [23/03/2021, 08:26:57] --- [23/03/2021, 08:26:58] Loaded plugin: homebridge-gsh@2.1.0 [23/03/2021, 08:26:58] Registering platform 'homebridge-gsh.google-smarthome' [23/03/2021, 08:26:58] --- [23/03/2021, 08:27:03] Loaded plugin: homebridge-ring@9.15.5 [23/03/2021, 08:27:03] Registering platform 'homebridge-ring.Ring' [23/03/2021, 08:27:03] --- [23/03/2021, 08:27:04] Loaded plugin: homebridge-vieramatic@3.1.8 [23/03/2021, 08:27:04] Registering platform 'homebridge-vieramatic.PanasonicVieraTV' [23/03/2021, 08:27:04] --- [23/03/2021, 08:27:04] Loading 4 platforms... [23/03/2021, 08:27:04] [Config] Initializing config platform... [23/03/2021, 08:27:04] [Config] Running in Service Mode [23/03/2021, 08:27:04] [Google Smart Home] Initializing google-smarthome platform... [23/03/2021, 08:27:04] [PanasonicVieraTV] Initializing PanasonicVieraTV platform... [23/03/2021, 08:27:04] [Ring] Initializing Ring platform... [23/03/2021, 08:27:04] Loading 8 accessories... [23/03/2021, 08:27:04] [1] Initializing DummySwitch accessory... [23/03/2021, 08:27:04] [2] Initializing DummySwitch accessory... [23/03/2021, 08:27:04] [3] Initializing DummySwitch accessory... [23/03/2021, 08:27:04] [4] Initializing DummySwitch accessory... [23/03/2021, 08:27:04] [5] Initializing DummySwitch accessory... [23/03/2021, 08:27:04] [6] Initializing DummySwitch accessory... [23/03/2021, 08:27:04] [7] Initializing DummySwitch accessory... [23/03/2021, 08:27:04] [8] Initializing DummySwitch accessory... [23/03/2021, 08:27:04] [Ring] Configuring cached accessory [23/03/2021, 08:27:04] [Ring] Configuring cached accessory [23/03/2021, 08:27:04] [PanasonicVieraTV] launching encryption helper endpoint on :8973 [23/03/2021, 08:27:04] [PanasonicVieraTV] handling '192.168.1.203' from config.json Preparing Advertiser for 'Homebridge E5CE' using bonjour-hap backend! Setup Payload: X-HM://0023TW7HWF3GM Enter this code with your HomeKit app on your iOS device to pair with Homebridge:

┌────────────┐     
│ ************* │     
└────────────┘

Starting to advertise 'Homebridge E5CE' using bonjour-hap backend! [23/03/2021, 08:27:09] Homebridge v1.3.4 (Homebridge) is running on port 51398. [23/03/2021, 08:27:09] [PanasonicVieraTV] IGNORING '192.168.1.203' as it is not reachable, and we can't relay on cached data as it seems that it was never ever seen and setup before.

Please make sure that your TV is powered ON and connected to the network. [23/03/2021, 08:27:09] [Google Smart Home] Connected (1) - wss://homebridge-gsh.iot.oz.nu [23/03/2021, 08:27:12] [Ring] Found the following locations: [23/03/2021, 08:27:12] [Ring] locationId: [23/03/2021, 08:27:12] [Ring] Configuring 1 cameras and 2 devices for location

Thanks for your help so far!

AntonioMeireles commented 3 years ago

@rpvandoorn

a) the TV is pingable ? i.e. ping 192.168.1.203 works (paste plz output ( around 10/20 lines) to check latency values) b) time curl -L 192.168.1.203:55000/nrc/ddd.xml returns what (paste please)?

AntonioMeireles commented 3 years ago

@rpvandoorn

btw the TV is in the same network segment / vlan / interface as the homebridge host ?

rpvandoorn commented 3 years ago

a)

pi@homebridge:/var/lib/homebridge $ ping 192.168.1.203
PING 192.168.1.203 (192.168.1.203) 56(84) bytes of data.
64 bytes from 192.168.1.203: icmp_seq=1 ttl=64 time=0.924 ms
64 bytes from 192.168.1.203: icmp_seq=2 ttl=64 time=0.726 ms
64 bytes from 192.168.1.203: icmp_seq=3 ttl=64 time=0.761 ms
64 bytes from 192.168.1.203: icmp_seq=4 ttl=64 time=0.740 ms
64 bytes from 192.168.1.203: icmp_seq=5 ttl=64 time=0.738 ms
64 bytes from 192.168.1.203: icmp_seq=6 ttl=64 time=0.748 ms
64 bytes from 192.168.1.203: icmp_seq=7 ttl=64 time=1.07 ms
64 bytes from 192.168.1.203: icmp_seq=8 ttl=64 time=0.785 ms
64 bytes from 192.168.1.203: icmp_seq=9 ttl=64 time=0.775 ms
64 bytes from 192.168.1.203: icmp_seq=10 ttl=64 time=0.795 ms
64 bytes from 192.168.1.203: icmp_seq=11 ttl=64 time=0.931 ms
64 bytes from 192.168.1.203: icmp_seq=12 ttl=64 time=0.728 ms
64 bytes from 192.168.1.203: icmp_seq=13 ttl=64 time=0.745 ms
64 bytes from 192.168.1.203: icmp_seq=14 ttl=64 time=0.744 ms
64 bytes from 192.168.1.203: icmp_seq=15 ttl=64 time=0.714 ms
64 bytes from 192.168.1.203: icmp_seq=16 ttl=64 time=0.689 ms
64 bytes from 192.168.1.203: icmp_seq=17 ttl=64 time=0.687 ms
64 bytes from 192.168.1.203: icmp_seq=18 ttl=64 time=0.827 ms
64 bytes from 192.168.1.203: icmp_seq=19 ttl=64 time=0.779 ms
64 bytes from 192.168.1.203: icmp_seq=20 ttl=64 time=0.774 ms

b)

pi@homebridge:/var/lib/homebridge $ time curl -L 192.168.1.203:55000/nrc/ddd.xml
<?xml version="1.0"?>
<root xmlns="urn:schemas-upnp-org:device-1-0" xmlns:vli="urn:schemas-panasonic-com:vli" xmlns:viera="urn:schemas-panasonic-com:viera" xmlns:pxn="urn:schemas-panasonic-com:pxn">
  <specVersion><major>1</major><minor>0</minor></specVersion>
  <device>
    <deviceType>urn:panasonic-com:device:p00RemoteController:1</deviceType>
    <friendlyName>TV-Woonkamer</friendlyName>
    <manufacturer>Panasonic</manufacturer>
    <modelName>Panasonic VIErA</modelName>
    <modelNumber>TX-65GZ950W</modelNumber>
    <UDN>uuid:4D454930-0200-1000-8001-80C755F65E90</UDN>
    <viera:X_DMSUDN>uuid:4D454930-0000-1000-8001-80C755F65E90</viera:X_DMSUDN>
    <viera:X_DMRUDN>uuid:4D454930-0100-1000-8001-80C755F65E90</viera:X_DMRUDN>
    <viera:X_NRCUDN>uuid:4D454930-0200-1000-8001-80C755F65E90</viera:X_NRCUDN>
    <viera:X_PACUDN>uuid:4D454930-0300-1000-8001-80C755F65E90</viera:X_PACUDN>
    <vli:X_MHC_DEVICE_ID>7853739518797849</vli:X_MHC_DEVICE_ID>
    <viera:X_VERSION>NRC-4.00</viera:X_VERSION>
    <viera:X_DEVICE_TYPE>DTV</viera:X_DEVICE_TYPE>
    <viera:X_KEY_TYPE>PAL-41,PAL-21,PAL-1</viera:X_KEY_TYPE>
    <viera:X_PAD_TYPE>15-1</viera:X_PAD_TYPE>
    <viera:X_NRC_ID>80C755F65E90</viera:X_NRC_ID>
    <viera:X_NRCCAP>VR_POWER,VR_DMR,VR_DMS,VR_PAC,VR_VECTOR,VR_BROWSER,VR_LAUNCH,VR_RECDMS,VR_TUNERDMS,VR_MEDIADMS,VR_LVDMS,VR_VGADMS,VR_UPDMS,VR_TUNER2,VR_WOL,VR_OWNPLAY,VR_XRC,VR_MES,VR_UPBROWSER,VR_MC,VR_AREKORE</viera:X_NRCCAP>
    <iconList>
      <icon>
        <mimetype>image/png</mimetype>
        <width>48</width>
        <height>48</height>
        <depth>24</depth>
        <url>/nrc/dlna_icon_48.png</url>
      </icon>
      <icon>
        <mimetype>image/png</mimetype>
        <width>120</width>
        <height>120</height>
        <depth>24</depth>
        <url>/nrc/dlna_icon_120.png</url>
      </icon>
      <icon>
        <mimetype>image/jpeg</mimetype>
        <width>48</width>
        <height>48</height>
        <depth>24</depth>
        <url>/nrc/dlna_icon_48.jpg</url>
      </icon>
      <icon>
        <mimetype>image/jpeg</mimetype>
        <width>120</width>
        <height>120</height>
        <depth>24</depth>
        <url>/nrc/dlna_icon_120.jpg</url>
      </icon>
    </iconList>
    <serviceList>
      <service>
        <serviceType>urn:panasonic-com:service:p00NetworkControl:1</serviceType>
        <serviceId>urn:upnp-org:serviceId:p00NetworkControl</serviceId>
        <SCPDURL>/nrc/sdd_0.xml</SCPDURL>
        <controlURL>/nrc/control_0</controlURL>
        <eventSubURL>/nrc/event_0</eventSubURL>
      </service>
    </serviceList>
  </device>
</root>
real    0m0.096s
user    0m0.061s
sys     0m0.030s

c) Yes, it is! IP from Homebridge is 192.168.1.140

IPv4 (eth0) 192.168.1.140
AntonioMeireles commented 3 years ago

@rpvandoorn

thanks for the quick reply .. could you plz try to revert locally to homebridge-vieramatic@3.1.6 (npm i -g homebridge-vieramatic@3.1.6, restart homebridge and check if issue persists ?

rpvandoorn commented 3 years ago

Well, thanks for your quick responses too!

I did, but still the same problem... 

[23/03/2021, 12:01:12] ---
[23/03/2021, 12:01:13] Loaded plugin: homebridge-vieramatic@3.1.6
[23/03/2021, 12:01:13] Registering platform 'homebridge-vieramatic.PanasonicVieraTV'
[23/03/2021, 12:01:13] ---
[23/03/2021, 12:01:18] [PanasonicVieraTV] IGNORING '192.168.1.203' as it is not reachable, and we can't relay on cached data as it seems that it was never ever seen and setup before.

 Please make sure that your TV is powered ON and connected to the network.
rpvandoorn commented 3 years ago

Allright...... so after 3.1.6 I installed 3.0.0, just to try. I had to request and fill in the security codes again and now succesfully added the TV!

[23/03/2021, 12:05:54] [PanasonicVieraTV] found a 'Panasonic VIErA' TV (TX-65GZ950W) at '192.168.1.203' (requires crypto for communication).
[23/03/2021, 12:05:54] [PanasonicVieraTV] adding HDMI input '2' - 'Apple TV' as it was appended to config.json
[23/03/2021, 12:05:54] [PanasonicVieraTV] unsetting HDMI input '1' ['Apple TV'] since it was dropped from the config.json
[23/03/2021, 12:05:55] [PanasonicVieraTV] successfully loaded TV Woonkamer
AntonioMeireles commented 3 years ago

ok, progress... could you plz try incrementing revisions from that (full list here - https://www.npmjs.com/package/homebridge-vieramatic) one by one to check which specific one broke on your setup ?

&& thanks again for your patience!!!

rpvandoorn commented 3 years ago

3.1.2 is working perfect, but 3.1.3 gives me the same error message.

AntonioMeireles commented 3 years ago

@rpvandoorn

many, many! thanks!!!! looking at it on my side now.

AntonioMeireles commented 3 years ago

@rpvandoorn

attach plz the contents of accessories/vieramatic.json (the parent path is relative to the dir where the homebridge's config.json is stored)

rpvandoorn commented 3 years ago

Do you mean this config?

{
    "tvs": [
        {
            "friendlyName": "TV Woonkamer",
            "ipAddress": "192.168.1.203",
            "encKey": "****",
            "appId": "****",
            "hdmiInputs": [
                {
                    "id": "2",
                    "name": "Apple TV"
                }
            ],
            "disabledAppSupport": false,
            "customVolumeSlider": true
        }
    ],
    "platform": "PanasonicVieraTV"
}
AntonioMeireles commented 3 years ago

no. not that one. that is homebridge's config.json. the one i want is located (as accessories/vieramatic.json) inside the directory where the config you pasted is located.

AWeidenbacher commented 3 years ago

3.1.2 is working perfect, but 3.1.3 gives me the same error message.

The same on my Homebridge installation - after reverting back to 3.1.2 I have the controls back in HomeKit. Hopefully the issue can be solved with the next update...

THX AWeiden

AntonioMeireles commented 3 years ago

@AWeidenbacher

thanks to let me know! which tv model? could you attach here a copy of your vieramatic.json (see above) please ? and also of your homebridge boot logs (of a failing version)

thanks!!!!

AWeidenbacher commented 3 years ago

I have a PANASONIC OLED 835 (German Model 2019). Hope you will find the problem...

THX AWeiden

Startup with V3.1.2:

[25.3.2021, 20:23:26] [PanasonicVieraTV] found a 'Panasonic VIErA' TV (TX-55FZ830W) at '172.20.20.85' (requires crypto for communication).

[25.3.2021, 20:23:27] [PanasonicVieraTV] successfully loaded OLED
Preparing Advertiser for 'OLED 0766' using bonjour-hap backend!
Starting to advertise 'OLED 0766' using bonjour-hap backend!
[25.3.2021, 20:23:27] OLED 0766 is running on port 35959.
[25.3.2021, 20:23:27] Please add [OLED 0766] manually in Home app. Setup Code: 448-01-670

Startup with V3.1.9:

[25.3.2021, 20:28:07] [PanasonicVieraTV] launching encryption helper endpoint on :8973
[25.3.2021, 20:28:07] [PanasonicVieraTV] handling '172.20.20.85' from config.json
Preparing Advertiser for 'Google Maps Traffic 72AD' using bonjour-hap backend!
[25.3.2021, 20:28:07] [PanasonicVieraTV] IGNORING '172.20.20.85' as it has an invalid MAC address: '80-C7-55-64-F1-55'
{
  "friendlyName": "OLED",
  "ipAddress": "172.20.20.85",
  "mac": "80-C7-55-64-F1-55",
  "encKey": "secret",
  "appId": "secret",
  "hdmiInputs": [
    {
      "id": "4",
      "name": "FIRE TV"
    },
    {
      "id": "2",
      "name": "MARANTZ"
    },
    {
      "id": "1",
      "name": "OPPO"
    }
  ],
  "disabledAppSupport": false,
  "customVolumeSlider": true
}

VIERAMATIC.JSON: more vieramatic.json

{"4D454930-0200-1000-8001-80C75564F155":{"data":{"inputs":{"applications":{"0":{"id":"0387878700000102","name":"Apps Market"},"1":{"id":"0010000200000001","name":"Netflix"},"2":{"id":"007
0000200180001","name":"YouTube"},"3":{"id":"0020002400180001","name":"Cinema"},"4":{"id":"0387878700000016","name":"VIERA Link"},"5":{"id":"0387878700000003","name":"TV Guide"},"6":{"id":
"0077777700160002","name":"Browser"},"7":{"id":"0010000100180001","name":"Amazon Prime Video"},"8":{"id":"0020003F00000001","name":"Joyn | deine Streaming App"},"9":{"id":"002000710000000
1","name":"Meteonews TV"},"10":{"id":"0020000600000001","name":"ARTE"},"11":{"id":"0076010807000001","name":"ARD Mediathek"},"12":{"id":"0020005400000001","name":"videociety"},"13":{"id":
"0020004700000001","name":"CHILI"},"14":{"id":"0010001800000001","name":"TuneIn"},"15":{"id":"0076011807000001","name":"ZDFmediathek"},"16":{"id":"0076002307170001","name":"Digital Concer
t Hall"},"17":{"id":"0387878700000141","name":"Audio Link"},"18":{"id":"0387878700000013","name":"TV-Aufnahmen"},"19":{"id":"0387878700000050","name":"Multi Window"},"20":{"id":"002000190
0000001","name":"Viewster - Finest Movies On Demand"},"21":{"id":"0020000300000001","name":"tagesschau"},"22":{"id":"0387878700000140","name":"Mitteilungszentrale"},"23":{"id":"0387878700
150020","name":"Kalender"},"24":{"id":"0387878700000146","name":"Smart Speaker Settings"},"25":{"id":"0020013100000001","name":"Zattoo - TV Streaming"},"26":{"id":"0020010800000001","name
":"DAZN"},"27":{"id":"0020013500000001","name":"ProSieben"},"28":{"id":"0020013600000001","name":"SAT.1"},"29":{"id":"0310006000000001","name":"XUMO: FREE Movies&amp;TV"}},"hdmi":[{"id":"
4","name":"FIRE TV"},{"id":"2","name":"MARANTZ"},{"id":"1","name":"OPPO"}],"TUNER":{"hidden":0}},"ipAddress":"172.20.20.85","specs":{"friendlyName":"OLED","manufacturer":"Panasonic","mode
lName":"Panasonic VIErA","modelNumber":"TX-55FZ830W","requiresEncryption":true,"serialNumber":"4D454930-0200-1000-8001-80C75564F155"}}}}
stijndevries commented 3 years ago

Hi Antonio,

I'm also having issues adding my TV back after I changed my router. All of the debug questions you asked @rpvandoorn are successful, I can ping it, it gives the correct info back and it's on the same IP level.

Reverting back to version 3.0.0 doesn't work for me though, I still get an “unable to finish initial setup please make sure the TV is powered on and not in standby.” This while's definitely on and I'm able to ping it.

I will send the results of the ping logs when I'm on my laptop.

Stijn

AntonioMeireles commented 3 years ago

@AWeidenbacher

(sorry lag - was mostly offline until now) At sight your issue is (should be) mostly due to this...

[PanasonicVieraTV] IGNORING '172.20.20.85' as it has an invalid MAC address: '80-C7-55-64-F1-55'

MAC address is in wrong format. the separator should be :. in the past the regexp to mac addresses was a bit more relaxed.
So, changing '80-C7-55-64-F1-55' to '80:C7:55:64:F1:55' should allow things to move forward.

On the other hand, as far as i know, Wake on Lan (which is what MAC addressed are for) is only needed in very old models. you should have everything working 100% without having to set it at all. (please correct me if i'm wrong because if i'm not i should probably add code to make sure that they aren't used on recent models (i.e. al the ones that require crypto) as those are reachable via network all the time - on standby or not).

thanks again, for your patience, and waiting for your feedback!

Have also a great weekend!

António

AntonioMeireles commented 3 years ago

@stijndevries

please attach here contents of accessories/vieramatic.json, homebridge's config.json and homebridge's boot logs please.

thanks!

AntonioMeireles commented 3 years ago

@stijndevries

also, at the time you changed your router, did your TV also changed IP address ?

if so, you'd need either to just delete accessories/vieramatic.json and restart homebridge or (better) edit accessories/vieramatic.json and update there ipAddress value to present one, and after also restart homebridge. either approach should get you back on track!

All the best,

António

AWeidenbacher commented 3 years ago

@AntonioMeireles - after changing the format of the MAC adress (using ":" instead of "-" it is working 👍 !!! THX for your help AWeiden

AntonioMeireles commented 3 years ago

@AntonioMeireles - after changing the format of the MAC adress (using ":" instead of "-" it is working 👍 !!! THX for your help AWeiden

great! anyway - please ponder stop using MAC address at all - for your set it does more harm than good. it should just work (and wake faster :-) ) without it.

all the best, António

AntonioMeireles commented 3 years ago

@rpvandoorn

hi again. please update to homebridge-vieramatic@3.1.10 that i've just published, restart homebridge and then just attach here just the full homebridge boot logs. they should now make obvious what is causing your issue (or i hope).

All the best,

António

AntonioMeireles commented 3 years ago

hi again. please update to homebridge-vieramatic@3.1.10 that i've just published, restart homebridge and then just attach here just the full homebridge boot logs. they should now make obvious what is causing your issue (or i hope).

@stijndevries, @rpvandoorn

could you both try the above and report back please when with some spare time... thanks in advance!

stijndevries commented 3 years ago

I installed the update, this is what I got:

Boot log

[29/03/2021, 11:17:28] [HB Supervisor] Starting Homebridge with extra flags: -I
[29/03/2021, 11:17:28] [HB Supervisor] Started Homebridge v1.3.3 with PID: 6933
Initializing HAP-NodeJS v0.9.3...
[29/03/2021, 11:17:37] Loaded config.json with 2 accessories and 6 platforms.
[29/03/2021, 11:17:38] Loaded 7 cached accessories from cachedAccessories.
[29/03/2021, 11:17:38] ---
[29/03/2021, 11:17:45] Loaded plugin: homebridge-airrohr@1.1.9
[29/03/2021, 11:18:00] Registering accessory 'homebridge-airrohr.airrohr'
[29/03/2021, 11:18:00] ---
[29/03/2021, 11:18:05] Loaded plugin: homebridge-blink-for-home@3.7.2
[29/03/2021, 11:18:05] Registering platform 'homebridge-blink-for-home.Blink'
[29/03/2021, 11:18:05] ---
[29/03/2021, 11:18:06] Loaded plugin: homebridge-config-ui-x@4.41.0
[29/03/2021, 11:18:06] Registering platform 'homebridge-config-ui-x.config'
[29/03/2021, 11:18:06] ---
[29/03/2021, 11:18:06] Loaded plugin: homebridge-http-tv@1.0.0
[29/03/2021, 11:18:06] Registering platform 'homebridge-http-tv.http-tv'
[29/03/2021, 11:18:06] ---
[29/03/2021, 11:18:10] Loaded plugin: homebridge-miot@0.5.2
[29/03/2021, 11:18:10] Registering platform 'homebridge-miot.miot'
[29/03/2021, 11:18:10] ---
[29/03/2021, 11:18:10] Loaded plugin: homebridge-printer@1.1.0
[29/03/2021, 11:18:11] Registering platform 'homebridge-printer.PrinterPlatform'
[29/03/2021, 11:18:11] ---
[29/03/2021, 11:18:11] Loaded plugin: homebridge-sonytvon@0.1.2
[29/03/2021, 11:18:11] Registering accessory 'homebridge-sonytvon.Sony'
[29/03/2021, 11:18:11] ---
[29/03/2021, 11:18:14] Loaded plugin: homebridge-vieramatic@3.1.10
[29/03/2021, 11:18:14] Registering platform 'homebridge-vieramatic.PanasonicVieraTV'
[29/03/2021, 11:18:14] ---
[29/03/2021, 11:18:17] Loaded plugin: homebridge-xiaomi-fan@1.3.1
[29/03/2021, 11:18:17] Registering accessory 'homebridge-xiaomi-fan.xiaomifan'
[29/03/2021, 11:18:17] Registering platform 'homebridge-xiaomi-fan.xiaomifan'
[29/03/2021, 11:18:17] ---
[29/03/2021, 11:18:17] The plugin "homebridge-zp" requires Node.js version of ^14.16.0 which does not satisfy the current Node.js version of v14.15.4. You may need to upgrade your installation of Node.js - see https://git.io/JTKEF
[29/03/2021, 11:18:19] Loaded plugin: homebridge-zp@1.2.0
[29/03/2021, 11:18:19] Registering platform 'homebridge-zp.Lib'
[29/03/2021, 11:18:19] Registering platform 'homebridge-zp.ZP'
[29/03/2021, 11:18:19] Registering platform 'homebridge-zp.ZPS1'
[29/03/2021, 11:18:19] ---
[29/03/2021, 11:18:19] Loading 6 platforms...
[29/03/2021, 11:18:19] [Config] Initializing config platform...
[29/03/2021, 11:18:19] [Config] Running in Service Mode
[29/03/2021, 11:18:19] [xiaomifan] Initializing xiaomifan platform...
[29/03/2021, 11:18:19] [PanasonicVieraTV] Initializing PanasonicVieraTV platform...
[29/03/2021, 11:18:19] [Sonos] Initializing ZP platform...
[29/03/2021, 11:18:19] [Sonos] homebridge-zp v1.2.0, node v14.15.4, homebridge v1.3.3, homebridge-lib v5.1.0
[29/03/2021, 11:18:19] [Sonos] warning: not using recommended node v14.16.0 LTS
[29/03/2021, 11:18:20] [Blink] Initializing Blink platform...
[29/03/2021, 11:18:20] [PrinterPlatform] Initializing PrinterPlatform platform...
[29/03/2021, 11:18:36] Loading 2 accessories...
[29/03/2021, 11:18:36] [Living Room TV] Initializing Sony accessory...
[29/03/2021, 11:18:36] [AirRohr] Initializing airrohr accessory...
[29/03/2021, 11:18:36] [AirRohr] AirRohr: Update interval 200 s
[29/03/2021, 11:18:37] [PrinterPlatform] HP Officejet Sensor: Configuring accessory...
[29/03/2021, 11:18:37] [PrinterPlatform] HP Officejet Switch: Configuring accessory...
[29/03/2021, 11:18:37] [xiaomifan] Init - initializing devices
[29/03/2021, 11:18:37] [xiaomifan] Init - initializing device with name: Mi Fan
[29/03/2021, 11:18:37] [PanasonicVieraTV] launching encryption helper endpoint on :8973
[29/03/2021, 11:18:37] [PanasonicVieraTV] handling '192.168.0.130' from config.json
[29/03/2021, 11:18:37] [Sonos] restored 1 accessories from cache
[29/03/2021, 11:18:37] [Blink] Init Blink
Preparing Advertiser for 'Mi Fan 4B7F' using ciao backend!
Preparing Advertiser for 'Homebridge EDCD BB0C' using ciao backend!
Setup Payload:
X-HM://xxx
Enter this code with your HomeKit app on your iOS device to pair with Homebridge:

    ┌────────────┐     
    │ XXXXXXX │     
    └────────────┘     

Starting to advertise 'Mi Fan 4B7F' using ciao backend!
[29/03/2021, 11:18:38] Mi Fan 4B7F is running on port 40647.
[29/03/2021, 11:18:38] Please add [Mi Fan 4B7F] manually in Home app. Setup Code: xxx
Starting to advertise 'Homebridge EDCD BB0C' using ciao backend!
[29/03/2021, 11:18:38] Homebridge v1.3.3 (Homebridge EDCD) is running on port 51017.
[29/03/2021, 11:18:39] [PanasonicVieraTV] cached: {} 
reachable: false 
all Known:
 {}
[29/03/2021, 11:18:39] [PanasonicVieraTV] IGNORING '192.168.0.130' as it is not reachable, and we can't relay on cached data as it seems that it was never ever seen and setup before.

 Please make sure that your TV is powered ON and connected to the network.

(It is turned on and the IP address is the same as is shown on the TV)

Ping

ping 192.168.0.130
PING 192.168.0.130 (192.168.0.130) 56(84) bytes of data.
64 bytes from 192.168.0.130: icmp_seq=1 ttl=64 time=10.4 ms
64 bytes from 192.168.0.130: icmp_seq=2 ttl=64 time=7.50 ms
64 bytes from 192.168.0.130: icmp_seq=3 ttl=64 time=12.8 ms
64 bytes from 192.168.0.130: icmp_seq=4 ttl=64 time=5.96 ms
64 bytes from 192.168.0.130: icmp_seq=5 ttl=64 time=19.8 ms
64 bytes from 192.168.0.130: icmp_seq=6 ttl=64 time=11.0 ms
64 bytes from 192.168.0.130: icmp_seq=7 ttl=64 time=15.1 ms
64 bytes from 192.168.0.130: icmp_seq=8 ttl=64 time=4.84 ms
64 bytes from 192.168.0.130: icmp_seq=9 ttl=64 time=15.2 ms

time curl

time curl -L 192.168.0.130:55000/nrc/ddd.xml
<?xml version="1.0"?>
<root xmlns="urn:schemas-upnp-org:device-1-0" xmlns:vli="urn:schemas-panasonic-com:vli" xmlns:viera="urn:schemas-panasonic-com:viera" xmlns:pxn="urn:schemas-panasonic-com:pxn">
  <specVersion><major>1</major><minor>0</minor></specVersion>
  <device>
    <deviceType>urn:panasonic-com:device:p00RemoteController:1</deviceType>
    <friendlyName>Viera</friendlyName>
    <manufacturer>Panasonic</manufacturer>
    <modelName>Panasonic VIErA</modelName>
    <modelNumber>TX-42AS650E</modelNumber>
    <UDN>uuid:4D454930-0200-1000-8001-20C6EBA2563B</UDN>
    <viera:X_DMSUDN>uuid:4D454930-0000-1000-8001-20C6EBA2563B</viera:X_DMSUDN>
    <viera:X_DMRUDN>uuid:4D454930-0100-1000-8001-20C6EBA2563B</viera:X_DMRUDN>
    <viera:X_NRCUDN>uuid:4D454930-0200-1000-8001-20C6EBA2563B</viera:X_NRCUDN>
    <vli:X_MHC_DEVICE_ID>8440522203947199</vli:X_MHC_DEVICE_ID>
    <viera:X_VERSION>NRC-3.00</viera:X_VERSION>
    <viera:X_DEVICE_TYPE>DTV</viera:X_DEVICE_TYPE>
    <viera:X_KEY_TYPE>PAL-16,PAL-6,PAL-1</viera:X_KEY_TYPE>
    <viera:X_PAD_TYPE>14-2</viera:X_PAD_TYPE>
    <viera:X_NRC_ID>BC307D1B69A2</viera:X_NRC_ID>
    <viera:X_NRCCAP>VR_POWER,VR_DMR,VR_DMS,VR_VECTOR,VR_BROWSER,VR_VCTRL,VR_LAUNCH,VR_RECDMS,VR_TUNERDMS,VR_MEDIADMS,VR_LVDMS,VR_VGADMS,VR_UPDMS,VR_TUNER1,VR_WOL,VR_OWNPLAY,VR_XRC,VR_MES,VR_UPBROWSER,VR_MHC,VR_OUTSTREAM,VR_OUTEPG,VR_TVANYWHERE</viera:X_NRCCAP>
    <iconList>
      <icon>
        <mimetype>image/png</mimetype>
        <width>48</width>
        <height>48</height>
        <depth>24</depth>
        <url>/nrc/dlna_icon_48.png</url>
      </icon>
      <icon>
        <mimetype>image/png</mimetype>
        <width>120</width>
        <height>120</height>
        <depth>24</depth>
        <url>/nrc/dlna_icon_120.png</url>
      </icon>
      <icon>
        <mimetype>image/jpeg</mimetype>
        <width>48</width>
        <height>48</height>
        <depth>24</depth>
        <url>/nrc/dlna_icon_48.jpg</url>
      </icon>
      <icon>
        <mimetype>image/jpeg</mimetype>
        <width>120</width>
        <height>120</height>
        <depth>24</depth>
        <url>/nrc/dlna_icon_120.jpg</url>
      </icon>
    </iconList>
    <serviceList>
      <service>
        <serviceType>urn:panasonic-com:service:p00NetworkControl:1</serviceType>
        <serviceId>urn:upnp-org:serviceId:p00NetworkControl</serviceId>
        <SCPDURL>/nrc/sdd_0.xml</SCPDURL>
        <controlURL>/nrc/control_0</controlURL>
        <eventSubURL>/nrc/event_0</eventSubURL>
      </service>
    </serviceList>
  </device>
</root>
real    0m0.452s
user    0m0.067s
sys     0m0.088s

Config.json

{
            "tvs": [
                {
                    "friendlyName": "Viera",
                    "ipAddress": "192.168.0.130",
                    "hdmiInputs": [
                        {
                            "id": "2",
                            "name": "Apple TV"
                        }
                    ],
                    "disabledAppSupport": false,
                    "customVolumeSlider": false
                }
            ],
            "platform": "PanasonicVieraTV"
        },

I'm not to sure how to get to the accessories/vieramatic.json file though the terminal.

AntonioMeireles commented 3 years ago

@stijndevries thanks! just running sudo find / | grep "accessories/vieramatic.json" on the homebridge host should get you the full path of accessories/vieramatic.json.

stijndevries commented 3 years ago

Hmm, I'm not able to find that file, that command finds nothing. I would expect it to be in /var/lib/homebridge/accessories/vieramatic.json, but that doesn't exist. I will try reinstalling the plugin.

AntonioMeireles commented 3 years ago

Hmm, I'm not able to find that file, that command finds nothing. I would expect it to be in /var/lib/homebridge/accessories/vieramatic.json, but that doesn't exist. I will try reinstalling the plugin.

OK. BTW you're restarting the plugin with the TV on or in standby ? (if in standby plz try with it ON)

stijndevries commented 3 years ago

I'm doing it while its on. I reinstalle, so now it goes like this:

[29/03/2021, 12:00:52] [PanasonicVieraTV] Initializing PanasonicVieraTV platform...
[29/03/2021, 12:00:53] [PanasonicVieraTV] launching encryption helper endpoint on :8973
[29/03/2021, 12:00:53] [PanasonicVieraTV] handling '192.168.0.130' from config.jso
[29/03/2021, 12:00:57] [PanasonicVieraTV] found a 'Panasonic VIErA' TV (TX-42AS650E) at '192.168.0.130' .
[29/03/2021, 12:00:57] [PanasonicVieraTV] Initializing 'Viera' first time ever.

And then it just stops, nothing happens.

AntonioMeireles commented 3 years ago

@stijndevries

humm, at sight that is very good as you should now have an accessories/vieramatic.json created. You just need to add now your TV to Home.app afaict, and that's it. doesn't that work ?

stijndevries commented 3 years ago

No. I just restarted again and got an additional

[29/03/2021, 12:07:27] [PanasonicVieraTV] Unable to finish initial setup of Viera.

 Please make sure that this TV is powered ON and NOT in stand-by.

I am able to ping it tough and the time curl command also works.

AntonioMeireles commented 3 years ago

this is getting interesting :/ . and still no accessories/vieramatic.json on disk ?

stijndevries commented 3 years ago

Nope. I now get:

[29/03/2021, 12:14:00] [PanasonicVieraTV] cached: {} 
reachable: false 
all Known:
 {}
[29/03/2021, 12:14:00] [PanasonicVieraTV] IGNORING '192.168.0.130' as it is not reachable, and we can't relay on cached data as it seems that it was never ever seen and setup before.

 Please make sure that your TV is powered ON and connected to the network.

I will try removing and then installing version 1.3.0 to see if that works.

AntonioMeireles commented 3 years ago

@stijndevries

your TV set is way old... can you try again with "disabledAppSupport": true in your config please ...

can you ping me, referencing this issue, by email for offline debugging ? (address is in git commit logs) . Thanks

AntonioMeireles commented 3 years ago

@rpvandoorn

could you also ping me, referencing this issue, by email for offline debugging ? (the address is the one in git commit logs).

Thanks

rpvandoorn commented 3 years ago

@AntonioMeireles Sorry, I was a little busy with work, so no time to check.

I just installed version 3.1.11, and everything is still working. So thanks for that!

rpvandoorn commented 3 years ago

@rpvandoorn

could you also ping me, referencing this issue, by email for offline debugging ? (the address is the one in git commit logs).

Thanks

I really don't know how to do that... Can you explain?

AntonioMeireles commented 3 years ago

@rpvandoorn

great to hear that issue went away in latest iteration! so no need to additional offline debugging.

thanks for your patience and have a great extended weekend!

AntonioMeireles commented 3 years ago

@stijndevries

ping!, wondering if still having issues with latest revs as not hearing from you for a while ...

Thanks in advance

AntonioMeireles commented 2 years ago

closing; afaict this should be behaving in recent versions of the plugin. please reopen if that isn't the case.