Please update to the latest DVR pre-release v2020.03.22.0232 and then run the following command to send me the DVR logs and other data from the DVR:
curl -X POST http://[DVR-IP]:8089/diagnostics
It may take a minute or two to complete. When it's done let me know and I'll see if there's anything useful I can find.
Here are the results in the log
2020/03/22 06:44:28.239935 http: TLS handshake error from 73.54.202.57:58820: EOF
2020/03/22 06:45:15.846127 [TRS] DNS: OK: Resolved host via system DNS
2020/03/22 06:45:15.913784 [TRS] Cloudflare DNS: OK: Resolved host via 1.1.1.1
2020/03/22 06:45:16.388073 [TRS] Cloud Reachable: OK: Connected to community.getchannels.com
2020/03/22 06:45:16.494243 [TRS] Local Time: OK: Local clock is accurate
2020/03/22 06:45:16.882965 [TRS] Remote Access: OK: Successfully established external connection
2020/03/22 06:45:16.896768 [TRS] Disk Permissions: OK
2020/03/22 06:45:16.896888 [TRS] System Firewall: OK
2020/03/22 06:45:16.993749 [TRS] Third Party Firewall: OK
2020/03/22 06:45:17.089428 [TRS] Little Snitch: OK
2020/03/22 06:45:17.089549 [TRS] Sleep: OK
2020/03/22 06:45:33.040955 New diagnostic log submitted under 3a0d32e3-48ea-4bd1-a19a-1e18d0cb02ceI don’t see anything obviously unusual in the diagnostics. I think we’re at the point where you start posting photos of all of your network devices and describe your setup in detail and give us screenshots of the configuration of all of your network equipment.
Who do you get your internet from? Do they provide a box? Do you have a switch? Do you have anything other than your Eero? What cables are plugged into what?
Internet ---- Cable Modem ---- Erro Pro ---- Switch --- DVR Server
| |
| - HD Homeruns
|
- WIFI to DVR Clients and other Eero Pros.There have been issues in the past with some Wifi routers defaulting to a private/separate network/subnet for wireless clients; this partitioning can cause issues, especially with tuners. Furthermore, mesh routers (Eero, Google Home, Plume) seem to introduce additional network traffic that has been known to introduce problems, too.
You may want to double-check your router's network settings, and make sure they match your expected behavior.
I am only having problems with TVE. My OTA tuners work just fine.
The problem would happen on OTA too if you enabled Tuner Sharing. It's streaming through the DVR that's broken, since it isn't connecting to the DVR via the internal network.
I'd say you should try rebooting all the networking equipment since the routing table somewhere is out of whack.
I did a network reboot yesterday. I do have turner sharing enabled.
Local Network
DVR records TVE just fine. Can watch TVE on DVR machine from Web Interface. Can watch TVE on mobile safari. Can watch OTA from iOS/tvOS client or web ui.
Cellular Network
Can watch TVE on mobile safari. Can watch from iOS client. Can watch OTA from client or web ui.
Local Network
cannot watch TVE from iOS or tvOS clients. I submitted additional logs from today for tvOS.
This seems weird to me. I only have the ethernet port active. WiFi is turned off but I see this under the bonjour section. Is this normal?
'*Advertising Mac-mini.local via 4 networks: [192.168.7.219, 169.254.158.106, 169.254.204.146]*
You can check http://x:8089/system/network to see where the other IPs are coming from. But that's generally normal since the bonjour service on macOS is network-aware and only responds with the correct IP depending on the interface used.
I've noticed some problems in the past with extra interfaces not being properly addressed, and clients were unable to connect. However, since you can see the DVR server from that Apple TV, it seems there's a weird disconnect here.
I submitted diagnostics from this morning. I was able to view from iPhone on prod app, but not beta app.
It seems to work when I use the connect channels DVR Server and use away from home. I guess that's why you see the external IP.
Still not working on local network for TVE. OTA is still working.
Sent the System Network info via private message.
Here's what the log had for prod app. Took a couple of tries before the stream worked.
2020/03/24 08:33:34.545617 [TVE] stream timestamps: espn1: start_at=2020-03-24T08:33:34-04:00 current_at=2020-03-24T08:33:34-04:00 end_at=2020-03-24T08:34:02-04:00
2020/03/24 08:33:34.547499 [TNR] Opened connection to TVE-ATTOTT for ch6140 ESPN1
2020/03/24 08:33:34.559308 [HLS] Starting transcoder for channel 6140 from 73.54.xxx.xxx (encoder=remux, resolution=, deinterlacer=, bitrate=0)
2020/03/24 08:33:37.684405 [HLS] Probe failed for live stream after 3.123273772s and 0 bytes
2020/03/24 08:33:40.904794 [HLS] Session ch6140-dANY-23278ccdc69d started in 7.976190692s
2020/03/24 08:33:40.905736 [HLS] Couldn't generate master playlist for ch6140-dANY-23278ccdc69d: Could not determine video format
2020/03/24 08:33:40.906119 [HLS] Stopping transcoder session ch6140-dANY-23278ccdc69d (out: 0s, finished: false)
2020/03/24 08:33:40.969788 [TNR] Closed connection to TVE-ATTOTT for ch6140 ESPN1
2020/03/24 08:33:55.245460 [TVE] stream timestamps: espn1: start_at=2020-03-24T08:33:55-04:00 current_at=2020-03-24T08:33:55-04:00 end_at=2020-03-24T08:34:23-04:00
2020/03/24 08:33:55.245567 [TNR] Opened connection to TVE-ATTOTT for ch6140 ESPN1
2020/03/24 08:33:55.262973 [HLS] Starting transcoder for channel 6140 from 73.54.xxx.xxx (encoder=remux, resolution=, deinterlacer=, bitrate=0)
2020/03/24 08:33:58.306398 [HLS] Probe failed for live stream after 3.043003453s and 0 bytes
2020/03/24 08:34:00.948643 [HLS] Session ch6140-dANY-23278ccdc69d started in 5.90254389s
2020/03/24 08:34:00.949137 [HLS] Couldn't generate master playlist for ch6140-dANY-23278ccdc69d: Could not determine video format
2020/03/24 08:34:00.949165 [HLS] Stopping transcoder session ch6140-dANY-23278ccdc69d (out: 0s, finished: false)
2020/03/24 08:34:00.984615 [TNR] Closed connection to TVE-ATTOTT for ch6140 ESPN1
2020/03/24 08:34:17.911296 [TVE] stream timestamps: espn1: start_at=2020-03-24T08:34:17-04:00 current_at=2020-03-24T08:34:17-04:00 end_at=2020-03-24T08:34:46-04:00
2020/03/24 08:34:17.912459 [TNR] Opened connection to TVE-ATTOTT for ch6140 ESPN1
2020/03/24 08:34:17.922333 [HLS] Starting transcoder for channel 6140 from 73.54.xxx.xxx (encoder=remux, resolution=, deinterlacer=, bitrate=0)
2020/03/24 08:34:18.263181 [HLS] Probed live stream in 340.185624ms: h264 1280x720 progressive 6078393bps
2020/03/24 08:34:18.353760 [HLS] Session ch6140-dANY-23278ccdc69d started in 642.088266ms
2020/03/24 08:34:18.372180 [ENC] Starting encoder for ch6140 in /Volumes/ChannelsDVR/recordings/Streaming/ch6140-dANY-23278ccdc69d-510655158/encoder-1-651571274 at 1 (0.013667) (encoder=h264_videotoolbox, resolution=720, deinterlacer=linear, bitrate=3000 segment_size=0.01)
2020/03/24 08:34:28.453305 [HLS] Stopping transcoder session ch6140-dANY-23278ccdc69d (out: 32.746367s, finished: false)
2020/03/24 08:34:28.465727 [ENC] Stopped encoder for ch6140 in /Volumes/ChannelsDVR/recordings/Streaming/ch6140-dANY-23278ccdc69d-510655158/encoder-1-651571274 after encoding 1 to 15
2020/03/24 08:34:28.491304 [TNR] Closed connection to TVE-ATTOTT for ch6140 ESPN1
2020/03/24 08:34:29.128438 [TVE] stream timestamps: espn1: start_at=2020-03-24T08:34:29-04:00 current_at=2020-03-24T08:34:29-04:00 end_at=2020-03-24T08:34:57-04:00
2020/03/24 08:34:29.128578 [TNR] Opened connection to TVE-ATTOTT for ch6140 ESPN1
2020/03/24 08:34:29.140984 [HLS] Starting transcoder for channel 6140 from 73.54.xxx.xxx (encoder=remux, resolution=, deinterlacer=, bitrate=0)
2020/03/24 08:34:32.274371 [HLS] Probe failed for live stream after 3.132900214s and 0 bytes
2020/03/24 08:34:40.086817 [HLS] Session ch6140-dANY-23278ccdc69d started in 11.52331896s
2020/03/24 08:35:00.146995 [HLS] Stopping inactive session ch6140-dANY-23278ccdc69d
2020/03/24 08:35:00.149117 [HLS] Stopping transcoder session ch6140-dANY-23278ccdc69d (out: 57.344s, finished: false)
2020/03/24 08:35:00.182198 [TNR] Closed connection to TVE-ATTOTT for ch6140 ESPN1After further digging and testing. It appears that it is an Eero router issue related to enabling Secure HomeKit. After I disabled. All seems to be working. Sorry for all of this back en forth and I appreciate the efforts. Sorry to put on a wild goose chase.
For reference here is the reddit topic, Loopback and Hairpin NAT
Sorry to revive this old thread, but do you still use eero and have you tried turning HomeKit secure router back on since?
I remember running into similar problems 1-2 years ago and would like to use the HomeKit security features on my eeros, but also don’t want to mess with Channels.
I have not turned it back on.
Thanks for the reply. I want to try turning it on again but I'd rather not have to re-configure my entire HomeKit setup if I have to turn it off due to Channels.