I wanted to start a new thread here to try and narrow down the reason for the "Unable To Locate Hub" nag that I and many others are getting frome the MR DVR when watching a program. The Unable to Locate Hub nag happens only to people who are streaming a recorded program to a Hd receiver (not a Standard Receiver). My questions are simple....
1) Are you getting the nag?
2) What model is your Hd receiver?
3) Do you have new wiring? or did the installer use the coax that already exsisted in your house?
4) Do you have a direct connection to the splitter that Verizon installed?
5) When the nag comes up, does it also come up at the same time in another room?
6) Has anyone received the nag when watching a program on a Std receiver?
Answering any of these questions would be helpful. If you have anything to add that would be helpful also.
I am getting the nag now and again. It could happen in 15 mins or an hour. But it almost always happens in the course of an hours time.
The model HD receiver that verizon sent me is HDQ1P-6200-2.
I have new wiring up until the splitter...to each room the installer used the pre-exsisting wiring that was inside the house already.
I have direct connections to each box from the splitter.
I am testing to see if the nag comes up the same time in another room.
When I had a Std receiver I never received the nag.
I have no idea if answering these questions will help at all. But if we could narrow down the problem or when the nag comes up, maybe it will help fix the problem.
If you MR-Dvr is working and streaming to a HD receiver without getting the nag, please post and provide info about your set-up.
Let me start off by saying that I am glad this is getting some response. I would like to say that I love the Verizon service so far. I expected some glitches along the way because this is a new service that is providing new technology. The unable to locate hub message is a bug that happens now and again. It just happened to me as I was watching South Park which is a recording was not in HD. 10 mins into the program the nag comes up. So it is all playback Hd and Std recordings.
I would like to thank The Sanchez for posting in this forum and giving us some of his time. The only way this problem will be fixed is if people complain about it. I can't deal with this nag for another month or two so I am ordering std receivers to replace my HD receivers in my room. When Verizon fixes the problem, I will bother them again for the HD receivers. But for sure I am a Verizon customer for life because I feel they give the customer so much more than cable or Directv.
To TS, all: Has anyone had this drop-out problem while trying to play NON-HD recordings at a remote site? HD is all I've recorded so far.
I have the same symptoms as everyone. I also noticed that on fast forwarding through a commmercial, that when I would return to "Play", the counter would momentarily indictate that it had gone back to the begining of the recording, but then would quickly indicate (and play) the correct location. However, after abt 20-30 min, it would begin to screw up, often with no 'lost hub' error that we've all been experiencing. My 4 mos old Verizon/Fios setup is:
1-DVR main (the hub)
1-STB slave (upstairs BR) Verizon tech has replaced this once, trying to fix the 'lost hub' prob
The Fios back-up entry box is in the walk-up attic. No temp extremes up there, though
The verizon phone techs have taken me all through all the various resets, including the router (that was fun). The house cabling/fiber is all new Fios, up to the back-up entry box. The rest of the TV wiring from the 'back-up entry box' is largely 2-3yr old COX co-ax.. The main DVR has never screwed up. However, this week, the Verizon guy is bringing out a new DVR to try next. Based on what I've read so far, it's probably a software/firmware prob and the new DVR will have no effect. more as it develops. Bill
@gdi wrote:To TS, all: Has anyone had this drop-out problem while trying to play NON-HD recordings at a remote site? HD is all I've recorded so far.
...
Yes, I've had the Unable to Locate Hub error with both SD & HD recordings. It has occurred when DVR was recording something else, or recording nothing. Doesn't seem to matter what DVR is doing; have tried leaving DVR "off" with both tuners set to SD channels (like 49 & 119) but that doesn't help either.
It's not wiring. All my wiring is new &/or recently checked by Vz techs in person. It's very unlikely replacing the box(es) will fix it either; all my boxes are relatively new (less than 2 months). It's a software bug. I hope they fix it soon.
It's only with the HD STB (QIP-6200), my SD box (QIP-2500) never had this error. Until they fix it I wouldn't recommend anyone pay for a MR-DVR to stream to a QIP-6200 STB, it's very frustrating.
I would love to test the CoAx throughput at the time of failure. The original post’s question: “5) When the nag comes up, does it also come up at the same time in another room?” speaks to this nicely, but only if throughput on individual cable runs is the issue. If throughput rates are poor at a splitter or some other CoAx issue upstream, the issue grows a little more complex to troubleshoot. If the MoCa rates fall low enough though this certainly could trigger it. We can sure try to help you guys escalate this issue, but we need to try to determine if the thing causing the loss of communication (or a loss of smart-recovery really it sounds like), is due to a throughput/buffering type of issue, or a MAC/IP address one (while less likely, address issues should not be completely ruled out in my opinion). Knowing the exact nature of the event that causes the failure will help us in repair to help the developers if we can.
Does the event last long enough to test another IP address dependent feature like VOD?
I’ll also ask question 6-b: Does this happen to anyone on any other box besides the 6200-2?
@G-Pon wrote:...I’ll also ask question 6-b: Does this happen to anyone on any other box besides the 6200-2?
Not for me. My 6200 replaced a 2500 in same location (exact same wiring), and it never happened. I still have a 2500 in another room, & it never has the problem. I've had a 6416-1 & 6416-2 DVR, and this problem has never occurred while replaying on either DVR directly. Never had a 6200-1 or any 7xxx box so can't say anything about those.
It's not wiring, & it's not a router issue. The problem does not coincide with IP renewals, by inspection of router logs. I recently had my old DLink replaced with a new ActionTec, & still have the problem. All my wiring & connections have been tested by Vz techs, in person, & are good.
It's a software problem, & I really hope they're working on it & fix it soon. As an engineer I know Intermittent problems are the hardest to troubleshoot; but this issue occurs when I'm viewing something with my non-engineer wife who has far less patience with technical glitches. Vz needs to setup a testbed somewhere & experience the problem for themselves, troubleshoot it, & fix it.
It wouldn't be nearly as bad if Resume worked. When it kicks you out, you have to start over from the beginning. "Resume" rarely works right on MRDVR playbacks anyway, even when not having this issue. I hope they fix that too.
"It wouldn't be nearly as bad if Resume worked. When it kicks you out, you have to start over from the beginning. "Resume" rarely works right on MRDVR playbacks anyway, even when not having this issue. I hope they fix that too."
That really is a huge part of why this nag is so annoying. It wouldn't be anywhere close to as annoying as it is now if you were able to start the program from where it cuts off. Problem is when trying to watch a two hour or three hour football game and it sends you back to the beginning.... well lets say you don't even want to watch tv anymore.
Is there any update on the fix to this issue. This is simply unusable especially with very long shows like movies and of course today NFL playoff games. Running FF is Not acceptable Not to mention it doesn't work. Few min passing the first snag, am running into another one this time the playback just switch to a random place on the recording.
BTW: I read this is HD recording being played on SD box .... Not sure. In my configuration its an HD recording with playback is on an HD STB on a second room.
The issue is set to be fixed with the next build that was scheduled for the beginning of Jan or something like that. I still get the nag and when it does happen, it happens in every room at the same time. It does not happen when I am watching on demand. I am just waiting for this issue to be fixed. Before I upgraded to HD receivers in my rooms the nag never came up.
I too have experienced the "Unable to Locate Hub" nag, and I think I found a possible cause.
Bandwidth.
When it happened I was watching a show in HD. My fiance was uploading something over the wifi at a pretty decent clip, and thats when I got the nag...
So could the bandwidth (or lack thereof) be the issue?
Zac
I'm not sure it's bandwith. I say that because I've gotten the nag while watching a SD recording on the HD STB, and nobody else is on the computer. Also, we watch recordings in the basement (a SD STB) and have never received the error. I think it has to be a software problem with the HD STB.
Now I'm seeing a post on dslreports from somebody who received the 1.6.1 update, and they are saying they are still getting the "unable to locate HUB" error, especially when FF or skipping. What the hell, VZ?? It's been stated that 1.6.1 will fix this problem, yet it persists? I'm beginning to regret my decision to leave Comcast.
I think that was I. Just to reiterate here, I have a 6416 HD DVR and then an HD STB in the master bedroom. We usally will pick up HD programming in the bedroom off the MR DVR. Since the 1.6.1 update last Tuesday morning, we still occasionally encounter the Hub error message. This AFTER I had told my wife that it was "fixed." HA! I didn't get a chance to use it last night but will try again tonight to see if any errors pop up. I did reboot the HD STB and will do the same for the DVR just in case although both have shown the new IMG since last Tuesday.
Stay tuned...
Please update, squatch. Very interested to see how this turns out.
Techman (or another VZ rep.) - what is the procedure now? 1.6.1 was meant to fix the HUB error message, and we are now learning it does not? Does this mean roll-out to the other VHOs will be delayed? Does this mean another IMG is needed (1.6.2) to fix this problem? Why would 1.6.1 be released if it doesn't address what is was supposed to?
Don't mean to be a pain, but these answers will help me decide if I should just go with 2 separate DVRs, or if I should dump VZ entirely. Much like squatch, my wife is getting upset with the VZ quality - and one thing I don't need is an upset wife.
Start a new topic or ask questions in the open forum.
