Update after I said I changed the zip code. I will wait to see how many stations I can pull in once i get my rooftop antenna installed to decide if it will send it back in the 30 days. There is so much “free” streaming content with commercials that i may not miss having any local digital channels.
Hi there,
Unfortunately, our guide data provider is currently unable to correct guide data for incorrect channels. Our team is investigating some solutions to resolve this issue to acquire the schedule data for channels like this in the future, but this is likely a few months away until we’re able to resolve these types of inquiries.
Trying a different zip code in the Location section of the Tablo Settings can sometimes help! However, we do not have any other work-arounds for this at this time.
We sincerely apologize for the inconvenience and appreciate your patience and understanding while our team works to resolve this.
I know this is an old thread - but it put me on a hunt for a zip code I could enter that would pass the limitation based on my phone’s location near Princeton Airport that would also get the WCBS info for 2.x virtual channels and WNBC info for 4.x channels. Edison wasn’t far north enough. Clifton was disallowed as too far out of range. Elizabeth, 07201, did the trick, though!
I also picked up some other stations that didn’t seem to register with the 08540 zip, like WABC 7.x and CW 11.1. Fox WNYW 5.x seems too weak to pull in reliably but I think it registered with either zip.
And on the plus side, I still got accurate data for 3.x WKYW-CBS, 6.x WPVI-ABC, 10.x WCAU-NBC, 33.1 Me-TV, and 57.x WPSG.
The only tweak I had to make was turning off 2.6 through 2.10. Those are WDPN subchannels. It was WDPN’s 2.1-2.5 that were hosing WCBS 2.x channels with my true zip code. The guide data is accurate for 2.6-2.10 but the signal is inadequate and they’re unwatchable.
I wonder if they reversed the order of the scan for the (central?) NJ area, if it would get find WCBS (RF 36) before WDPN (RF 2) and find WNBC (RF 35) before WACP (RF 4) and the correct guide data would get picked up.
When I do a channel scan, I scan the RF2 2.x channels come up with mid-level signal and all 480 resolution. As it scans further, I can watch the signal improve on the RF 36 channels and the resolution switches to 1080i. It wouldn’t surprise me if the first one detected take precedence.
It’s odd that they can overwrite the RF channel in the database row but not the station identifier… I’d love a peek into their code…
Yes, when I get just about all the Philadelphia stations quite well here, which is great.
But I also get WCBS and WNBC from New York quite strongly, too. But before the channel scan gets to RF 36 and 35, it picks up RF 2 and RF 4 with somewhat watchable level of signal so 2.x and 4.x end up with the WDPN and WACP guide data.
I’m pretty thrilled with my reception - but logistically I need to disable the WCBS and WNBC channels.
(I’ve worked out some of this since my previous post.)
When I used an Elizabeth zip code, I managed to get the NY guide associations for 2.x and 4.x but some of my Philadelphia channels got mismatched. Given I get a complete set of networks from Philadelphia but miss Fox NY and struggle with CW NY, I’ll stick with my Princeton zip and Philly-dominant lineup.
I have a similar problem. Where I live in eastern Connecticut, I can also pick up stations from Boston (MA), and Provfidence (RI). When I use my zip code, I get many program guide errors because the Tablo thinks that a lot of the stations are from different DMAs. It assigns some channels to Boston and even NY instead of CT, resulting in wrong program guide data.
I had to experiment with zip codes. There is no zip code that works for all of the channels that I get, but I found one that gets almost everything right. The wrong channels are duplicates, so I just unchecked them from the saved channels, and they do not show up in my program guide.