Node-red-contrib-homekit-bridged: Problem with remote access through Apple TV

[daddvok]

I use your node, everything is great on the local network, but from the outside sometimes everything works well, but basically I always see the update status on all devices in homekit, waiting a few minutes and then no response. After some time, access appears again and so cyclically.
There are no problems on the apple's side, I did a complete reset apple tv, home app, in and out in icloud on all devices, check few different internet providers. I think that trouble is with connection with HAP server, maybe I forgot to install something, but I don’t know what. Still my router does not support ipv6, maybe this has an effect.
I have already homebridge 0.4.50 and see the same problem(
Tell me please what could be the problem

node v10.17.0
npm 6.12.0
apple tv 4k with tvOs 13
iphone 8 with iOs 13.2

by installing was the following

DEBUG=HAPServer,EventedHTTPServer node-red ->

thanks

[daddvok]

disconnected ipv6 on raspberry, no improvements

[Shaquu]

All right then.
Have you tried fiddling with MDNS Configuration?
Are required ports open?
Is you Apple TV connected via cable or wireless connection?
Is your Apple TV and node-red server ip's reserved on the router so will not be changed over time? (maybe it could help)

I guess ipv6 should not be a problem.

[daddvok]

Hi, thank for your answer
no, I do not know what mdns is, explain for dumb how to configure please
ATV and raspberry connected via cable, dhcp on router reserved ip’s for all devises in network

[Shaquu]

Shortly. Hap (and I believe devices made by Apple) is based on and is using mdns/bonjour.
It allows zero configuration services.
So this is plug and play and devices should discover other devices automatically in the network.

Look here for example explanation: https://www.youtube.com/watch?v=w3OK2A1uOE0

So my question is if you tried to use any configuration and it looks like you didn't.
So you could really just try to enable custom MDNS configuration and try to go with default values.

Custom MDNS Configuration: Check if you would like to use custom MDNS configuration.

• Multicast: Use udp multicasting. Optional. Default true.
• Multicast Interface IP: Explicitly specify a network interface. Optional. Defaults to all.
• Port: Set the udp port. Optional. Default 5353.
• Multicast Address IP: Set the udp ip. Optional.
• TTL: Set the multicast ttl. Optional.
• Loopback: Receive your own packets. Optional. Default true.
• Reuse Address: Set the reuseAddr option when creating the socket. Optional. Default true.

[daddvok]

Do I just need to try putting a daw here? without additional settings? Do I need to re-add the bridge?

[daddvok]

HAPServer [00:0e:d5:7d:6c:84:e0:05] HAP Request: PUT /characteristics +0ms

"[00:0e:d5:7d:6c:84:e0:05]" is valid? It must be shortly, no?

[Shaquu]

Reported as well in KhaosT/HAP-NodeJS#727

[NorthernMan54]

@Shaquu I pulled together a quick fix for the name issue, #172 but it is a breaking change for existing users. They will need to unpair and repair, as part of implementing this.

[daddvok]

Please knock when it will be possible to update

[alexsidorin]

@Shaquu I pulled together a quick fix for the name issue, #172 but it is a breaking change for existing users. They will need to unpair and repair, as part of implementing this.

Hello, thanks for that fix. I am experiencing something similar. But instead on No response, there are just wrong states of devices and controlling them have no effect in node-red. Does this fix help for that? Do I need just change the file, that you pulled in the fix.

[Shaquu]

@alexsidorin I would advice to wait until it's on master branch or at least on the dev.

[radokristof]

It is possible thats why I had to always reopen the Home app multiple times from outside my network for everyone to catch up its state? Otherwise it will only show 'NO RESPONSE'.

[Shaquu]

You ask if fix will fix your problem? Who knows until we test it properly :) you should try and tell us.

[radokristof]

I will try :) I just tried to understand what it is error exactly and what change I should see...

[daddvok]

when it will be possible to update?

[radokristof]

You can change the branch to develop, that way you can test it now.

[daddvok]

You can change the branch to develop, that way you can test it now.

Current version in dev also 0.8.0 as well in master, so I thought there are no changes. I will try

[Shaquu]

But please remember that dev branch requires to unpair and pair again devices to use.

[Shaquu]

163 look for changes here

[daddvok]

added everything, everything works, if there are errors - I will write. Thank you!

[daddvok]

I’ve been using it for 8 days, the ATV is no longer “not responding”, but it often takes a long time to update devices, both in the local and outside the local network, on homebridge bridge in local network this does not happen.

still noticed “No response” all devices after reboot rpi, there is no answer on all devices, but when you go inside the device, this device normalizes, but once you go out and go into the "home" there is no answer again on all devices, homebridge bridge works normally without no response. I can send a video with a problem if you say where

[Shaquu]

@daddvok does the problem still exist for you? Can you send a video?

[daddvok]

@daddvok does the problem still exist for you? Can you send a video?

apple tv is no longer "no response", remote access works well, there are a maximum delay of 10-15 seconds for updating devices

[Shaquu]

Let's close it. Many things got improved in latest dev so next official release should make it better and faster.
If you need then comment or open new Issue.