The Viera TV at 192.168.xxx.xxx could not be edited.

[nodecentral]

Describe your issue

Since upgrading it is not finding my TV, all the required setting on the TV are enabled, (FYI nothing has been changed from when it was working before), it just no longer finds the TV. If I remove it and try to add it again , i get the same error message

The Viera TV at 192.168.102.200 could not be edited.
Please, do make sure that it is turned on and connected to the network, and then try again.

Also, if you haven't done it already...

...on your TV go to Menu / Network / TV Remote App Settings and make sure that the following settings are all turned ON:
TV Remote
Powered On by Apps
Networked Standby

Issue Context

Timezone	GMT+0100
Alpine Linux (3.12.3)
NAS4DD1B5
192.168.102.134
v14.15.3
v6.14.9
root
/homebridge
/homebridge/config.json
/homebridge/node_modules
Yes
Yes

[AntonioMeireles]

@nodecentral

hi!

thanks for reporting! shouldn't happen afaict.

some open questions:
a) what was your previous version ?
b) are you using docker ?
c) can you try with node16 ?
d) can you attach the corresponding homebridge logs ? (if possible run it in debug mode)

thanks again for your patience!

[nodecentral]

Hi,

The homebridge logs are reporting that the ping failed.

[4/17/2022, 11:01:57 PM] [Homebridge UI] Running Command: npm install --save homebridge-vieramatic@latest
[4/17/2022, 11:02:23 PM] [Homebridge UI] [homebridge-vieramatic] Incoming Request: /ping
[4/17/2022, 11:02:25 PM] [Homebridge UI] [homebridge-vieramatic] ---> (ping) 192.168.102.200 false
[4/17/2022, 11:02:38 PM] [Homebridge UI] [homebridge-vieramatic] Terminating child process...
[4/17/2022, 11:02:38 PM] [Homebridge UI] [homebridge-vieramatic] Child process ended

However if i go to the terminal, and run the ping command, with the same IP ping -c 5 192.168.102.200 it works fine, all pings are successfull.

[AntonioMeireles]

@nodecentral

how long does each ping takes (in miliseconds) ? Also, how is homebridge talking to the TV ? same network - homebridge running in host , in a container ?

thanks in advance

[nodecentral]

Hi @AntonioMeireles

The pinging is as follows.

PING 192.168.102.200 (192.168.102.200) 56(84) bytes of data.
64 bytes from 192.168.102.200: icmp_seq=1 ttl=64 time=0.257 ms
64 bytes from 192.168.102.200: icmp_seq=2 ttl=64 time=0.286 ms
64 bytes from 192.168.102.200: icmp_seq=3 ttl=64 time=0.281 ms
64 bytes from 192.168.102.200: icmp_seq=4 ttl=64 time=0.271 ms
64 bytes from 192.168.102.200: icmp_seq=5 ttl=64 time=0.280 ms

--- 192.168.102.200 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4134ms
rtt min/avg/max/mdev = 0.257/0.275/0.286/0.010 ms

All are on the same network, Homebridge docker is running in host mode, the above ping was run from the terminal (top right drop down) ) option of the Homebridge UI.

[AntonioMeireles]

@nodecentral

at sight all signs point to the fact that it seems that you do not have host mode enabled in your docker container which is upstream an hard requirement by design (see here the upstream documentation on that front].

can you check that, retry again and report back please ?

and thanks again for your patience.

[nodecentral]

Hi, looking at the Docker compose it states host, plus I’m accessing it via the parent/host IP - so everything seems to confirm it’s set up as host.

It’s strange that if I simple use Homebridge’s own Terminal program, and run the ping command - I’m able to see it pings my TV fine, yet the Viera plugin log says it can’t ?

Is there anything else I can try ?

Update - I removed and recreated the Docker again, still in host mode - but I still get the same message in the logs / and on the plugin screen, after adding the IP, it still says it cannot be edited.

[AntonioMeireles]

@nodecentral

humm, this is odd, way odd. do you have any way to to setup homebridge nativelly (to remove docker from the equation) ?

[nodecentral]

It is odd isn’t it :) also I have other IP addressable devices set up via HomeBridge on the same subnet and they work, so it seems to be unique to the Pani plugin. Sadly I removed the previous version where it was working - so I’m scratching my head what might be wrong.

[nafrayu85]

Have exactly the same problem! Has it since been resolved?