I'll start off by saying I don't subscribe to OTA and I don't see any OTA guide info displayed for the OTA channels.
I've lost a few recordings on my 622 due to OTA timers firing and running with no endpoint. The HD fills up and just starts to delete recordings. I thought the record button was getting pressed inadvertently. This morning it was recording its fifteenth hour, but I wasn't home to accidentally push the rec button. No timers show in the daily schedule. I have changed remote addresses and the timers keep firing.
So, on a whim, I looked up an OTA program on titantv and set the 622 for a Dishpass for the program's key words. Sure enough, the 622 started recording the OTA program using the inaccessible OTA guide information.
So to summarize, Dish blocks the OTA guide info unless you pay for it. Dishpass continues to use the blocked and inaccessible guide info to fire errant timers. These fired timers do not have an endpoint that correlates with the guide info that triggered the timer. The recording runs without bounds to fill and delete previous recordings.
This sux!
Please, just open up the guide info so this stops being an issue!
I've lost a few recordings on my 622 due to OTA timers firing and running with no endpoint. The HD fills up and just starts to delete recordings. I thought the record button was getting pressed inadvertently. This morning it was recording its fifteenth hour, but I wasn't home to accidentally push the rec button. No timers show in the daily schedule. I have changed remote addresses and the timers keep firing.
So, on a whim, I looked up an OTA program on titantv and set the 622 for a Dishpass for the program's key words. Sure enough, the 622 started recording the OTA program using the inaccessible OTA guide information.
So to summarize, Dish blocks the OTA guide info unless you pay for it. Dishpass continues to use the blocked and inaccessible guide info to fire errant timers. These fired timers do not have an endpoint that correlates with the guide info that triggered the timer. The recording runs without bounds to fill and delete previous recordings.
This sux!
Please, just open up the guide info so this stops being an issue!