TWC Today Forums
Present - The Weather Channel 2000 => Local Forecast => IntelliStar 2 Discussion => Topic started by: Eric on May 04, 2012, 09:26:08 AM
-
About a week ago the Intellistar 2 stopped working in my area. I contacted TWC through their website, and they said they'll get in touch with the cable company to see what the matter is. Nothing happened.
I contacted the cable company myself, and they said there was an "issue" with it, but in three separate emails they insisted it was working and that I should be seeing its output. Nothing doing - only the national LDL and local forecast segments.
The cable company just sent me an email saying there's nothing more they can do about it and that if I want to pursue the matter I have to get in touch with The Weather Channel.
I was so happy when the HD feed got added to my cable company, and downright ecstatic that it had the IS 2, and it's killing me to have to go back to the SD feed to watch the local forecasts. :cry3:
-
You could have posted a tech support thread here, right? :unsure:
-
You could have posted a tech support thread here, right? :unsure:
He did, and there was no reply. ;)
https://twctodayforums.com/forums/weatherstar-tech-support/daytona-beach-fl-is2-outage/ (https://twctodayforums.com/forums/weatherstar-tech-support/daytona-beach-fl-is2-outage/)
-
The emails have been going back and forth for a week between TWC, Bright House, and me. Bright House insists it's working, when it clearly isn't, TWC is deferring to Bright House, and I'm just begging for someone to do something.
And, alas, my original post to the Star team in this forum has still gone unanswered. :(
It's just so annoying having to not watch the long-awaited HD feed because of the lack of local weather. :(
-
I just think it's Bright House's Customer Service that is reporting the wrong information,
if this was happening on an Xfinity Headend i bet the same thing would occur.
-
It's been about a week since you started the thread in STAR support, you probably should bump it just to let them know the issue still hasn't been resolved. The thread may have been accidently overlooked.