Problem with remote access through Apple TV #170

daddvok · 2019-10-26T23:20:26Z

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 · 2019-10-28T14:45:11Z

disconnected ipv6 on raspberry, no improvements

Shaquu · 2019-10-28T21:37:31Z

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 · 2019-10-28T21:42:56Z

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 · 2019-10-28T21:49:14Z

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 · 2019-10-28T21:56:46Z

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

daddvok · 2019-10-28T22:39:24Z

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 · 2019-10-29T14:26:19Z

Reported as well in KhaosT/HAP-NodeJS#727

NorthernMan54 · 2019-10-30T01:40:20Z

@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 · 2019-10-30T01:48:29Z

Please knock when it will be possible to update

alexsidorin · 2019-11-02T13:09:54Z

@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 · 2019-11-02T17:57:02Z

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

Fix for name issue raised in #170

radokristof · 2019-11-07T09:43:43Z

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 · 2019-11-07T09:45:21Z

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

radokristof · 2019-11-07T09:46:25Z

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

daddvok · 2019-11-07T09:52:45Z

when it will be possible to update?

radokristof · 2019-11-07T09:53:35Z

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

daddvok · 2019-11-07T09:57:42Z

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 · 2019-11-07T09:57:46Z

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

Shaquu · 2019-11-07T09:58:40Z

#163 look for changes here

daddvok · 2019-11-07T12:07:15Z

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

daddvok · 2019-11-15T17:04:15Z

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 · 2020-01-28T22:54:51Z

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

daddvok · 2020-01-28T22:59:34Z

@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 · 2020-01-28T23:16:45Z

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.

@radokristof

## [1.0.0] - 2020.02.23 Lost backward compatibility. In order to make it work read this [notice](#163 (comment)). ### Fixed - Node id macify algorithm changed [#170](#170) - Corrections regarding issue [#12](#12) so that changes can be deployed without restarting node-red - Automatically creating a new service and replacing the old one if the service type changed - Automatically replacing an accessory with a new one if the accessory information changes (e.g. Name, Manufacturer, ...) - Video Filter value in Camera Control is now optional [#194](#194) (can be empty, before it was generated if was empty) - Removed updateReachability as it is deprecated (and doesn't make a difference) ### Added - After Service selection in node configuration Category will be automatically set to default for Service - Interface Name for Camera Service configuration - Support for new TV Remote services - Now first output is for onChange, second for onSet and third for camera snapshot. [#200](#200) - Sponsor Button on repository page ### Changed - Accessory Category in node configuration moved under Service selection - Clarify NO_RESPONSE in README - Update node-red version in dependencies - Camera Service source code to match newest improvements in homebridge-camera-ffmpeg - Update to latest HAP-NodeJS - Removed unnecessary accessory category from service node - Removed fields Manufacturer, Serial Number and Model from linked service nodes - Moved eslint and prettier configuration to package.json - Added automatic linting on pre-commit Thanks to all contributors! @radokristof @NorthernMan54 @gotofoo And thanks to those who also helped in testing! @crxporter @sjorge

daddvok added the bug 🐛 There is at least high chance that it is a bug! label Oct 26, 2019

Shaquu mentioned this issue Oct 29, 2019

EventedHTTPServer HTTP server was closed homebridge/HAP-NodeJS#727

Closed

Shaquu added a commit that referenced this issue Nov 7, 2019

Merge pull request #172 from NorthernMan54/patch-1

d0563d4

Fix for name issue raised in #170

Shaquu mentioned this issue Dec 16, 2019

Corrections regarding issue #12 #184

Merged

Shaquu closed this as completed Jan 28, 2020

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Problem with remote access through Apple TV #170

Problem with remote access through Apple TV #170

daddvok commented Oct 26, 2019

daddvok commented Oct 28, 2019

Shaquu commented Oct 28, 2019

daddvok commented Oct 28, 2019

Shaquu commented Oct 28, 2019 •

edited

daddvok commented Oct 28, 2019

daddvok commented Oct 28, 2019 •

edited

Shaquu commented Oct 29, 2019

NorthernMan54 commented Oct 30, 2019 •

edited

daddvok commented Oct 30, 2019

alexsidorin commented Nov 2, 2019

Shaquu commented Nov 2, 2019

radokristof commented Nov 7, 2019

Shaquu commented Nov 7, 2019 •

edited

radokristof commented Nov 7, 2019

daddvok commented Nov 7, 2019

radokristof commented Nov 7, 2019

daddvok commented Nov 7, 2019

Shaquu commented Nov 7, 2019 •

edited

Shaquu commented Nov 7, 2019

daddvok commented Nov 7, 2019

daddvok commented Nov 15, 2019 •

edited

Shaquu commented Jan 28, 2020

daddvok commented Jan 28, 2020 •

edited

Shaquu commented Jan 28, 2020

Problem with remote access through Apple TV #170

Problem with remote access through Apple TV #170

Comments

daddvok commented Oct 26, 2019

daddvok commented Oct 28, 2019

Shaquu commented Oct 28, 2019

daddvok commented Oct 28, 2019

Shaquu commented Oct 28, 2019 • edited

daddvok commented Oct 28, 2019

daddvok commented Oct 28, 2019 • edited

Shaquu commented Oct 29, 2019

NorthernMan54 commented Oct 30, 2019 • edited

daddvok commented Oct 30, 2019

alexsidorin commented Nov 2, 2019

Shaquu commented Nov 2, 2019

radokristof commented Nov 7, 2019

Shaquu commented Nov 7, 2019 • edited

radokristof commented Nov 7, 2019

daddvok commented Nov 7, 2019

radokristof commented Nov 7, 2019

daddvok commented Nov 7, 2019

Shaquu commented Nov 7, 2019 • edited

Shaquu commented Nov 7, 2019

daddvok commented Nov 7, 2019

daddvok commented Nov 15, 2019 • edited

Shaquu commented Jan 28, 2020

daddvok commented Jan 28, 2020 • edited

Shaquu commented Jan 28, 2020

Shaquu commented Oct 28, 2019 •

edited

daddvok commented Oct 28, 2019 •

edited

NorthernMan54 commented Oct 30, 2019 •

edited

Shaquu commented Nov 7, 2019 •

edited

Shaquu commented Nov 7, 2019 •

edited

daddvok commented Nov 15, 2019 •

edited

daddvok commented Jan 28, 2020 •

edited