My guess is the guide provider gives Scripps/Nuvyyo all the programming data for the many subchannels of the 1700+ U.S. TV stations. It’s up to Scripps/Nuvyyo to get the right data to each Tablo.
I personally have heard the same story on my legacy device guide. They eventually had to get gracenotes to fix their end. And more then once.
With the legacy device you could tell where the fix was going by checking zap2it since it also used gracenotes. I used hdhomerun since it uses gracenotes. gen 2 guide who knows. The guide is rather mickey mouse.
I am not 100% sure about this, but I think part of the issue is they seem to simply map to the virtual channel instead of the combo of RF channel and virtual channel. So when there are two different RF channels that have a 2.1 virtual channel, they just seem to take the first one instead of looking at the RF channel and using that to resolve a conflict.
Guide data is organized by zip code and DMA. What ever they fix for your zip code may not have any affect on nearby zip codes. usually only when new channels or sub-channels are added to a DMA. Things get very messy when there are not only overlapping virtual channel numbers but translator broadcasting.
I think you’re right. Here is Gracenote’s developer documentation. Gracenote Developer Video + Sports APIs - Lineups
Looking up guide data starts with a postal code. We would need to see which stations Gracenote returns for those New Jersey zip codes to know where the problem is.