Thursday Shows still show as recording

In the Browser I see Thursday shows as still recording .... anyway to clear that up ?

Click the button and select Delete.

or Click the button and select Stop Recording.
I had that happen when my cable service went out a minute before a recording was supposed to end.

I discovered it because the morning after the recording I didn't have Internet access and had to restart my cable modem/gateway and found this the the Channels DVR log.

2019/10/06 22:00:00 [DVR] Starting job 1570424400-257 Mr. Robot on ch=[738]
2019/10/06 22:00:00 [TNR] Opened connection to 1323AADB for ch738 USAHDP
2019/10/06 22:00:00 [DVR] Recording for job 1570424400-257 from 1323AADB ch738 into "TV/Mr. Robot/Mr. Robot S04E01 2019-10-06 401 Unauthorized 2019-10-06-2200.mpg" for 1h3m29.990259398s
2019/10/06 22:00:00 [IDX] Generating video index for job 1570424400-257
2019/10/06 23:02:23 [TNR] Cancelling stream 1323AADB ch738 after 6s read timeout
2019/10/06 23:02:23 [TNR] Closed connection to 1323AADB for ch738 USAHDP
2019/10/06 23:02:23 [TNR] Closed connection to 1323AADB for ch738 USAHDP
2019/10/06 23:02:23 [DVR] Job 1570424400-257 Mr. Robot ended prematurely: 1m6.359863291s
2019/10/06 23:02:23 [DVR] Starting job 1570424400-257 Mr. Robot on ch=[738]
2019/10/06 23:02:28 [ERR] Failed to start stream on channel 738 via 1323AADB: HDHomeRun: 807 No Video Data
2019/10/06 23:02:28 [DVR] Error running job 1570424400-257 Mr. Robot: could not start stream on channels=[738]: HDHomeRun: 807 No Video Data
2019/10/06 23:02:58 [DVR] Starting job 1570424400-257 Mr. Robot on ch=[738]
2019/10/06 23:03:03 [ERR] Failed to start stream on channel 738 via 1323AADB: HDHomeRun: 807 No Video Data
2019/10/06 23:03:03 [DVR] Error running job 1570424400-257 Mr. Robot: could not start stream on channels=[738]: HDHomeRun: 807 No Video Data
2019/10/06 23:27:29 [SYS] Error checking for update: Get https://channels-dvr.s3.amazonaws.com/latest.json: dial tcp: lookup channels-dvr.s3.amazonaws.com on 192.168.1.1:53: read udp 192.168.1.4:58029->192.168.1.1:53: i/o timeout
2019/10/07 00:29:38 [SYS] Created database snapshot: backup-20191007.002938
2019/10/07 00:29:38 [SYS] Removing old backup backup-20190908.010608
2019/10/07 00:30:04 [ERR] Failed to refresh auth: Post https://community.getchannels.com/dvr/api: dial tcp: lookup community.getchannels.com on 192.168.1.1:53: server misbehaving
2019/10/07 01:27:29 [SYS] Error checking for update: Get https://channels-dvr.s3.amazonaws.com/latest.json: dial tcp: lookup channels-dvr.s3.amazonaws.com on 192.168.1.1:53: server misbehaving
2019/10/07 03:27:29 [SYS] Error checking for update: Get https://channels-dvr.s3.amazonaws.com/latest.json: dial tcp: lookup channels-dvr.s3.amazonaws.com on 192.168.1.1:53: server misbehaving
2019/10/07 03:30:04 [ERR] Failed to refresh auth: Post https://community.getchannels.com/dvr/api: dial tcp: lookup community.getchannels.com on 192.168.1.1:53: server misbehaving
2019/10/07 05:27:29 [SYS] Error checking for update: Get https://channels-dvr.s3.amazonaws.com/latest.json: dial tcp: lookup channels-dvr.s3.amazonaws.com on 192.168.1.1:53: server misbehaving
2019/10/07 06:30:04 [ERR] Failed to refresh auth: Post https://community.getchannels.com/dvr/api: dial tcp: lookup community.getchannels.com on 192.168.1.1:53: server misbehaving
2019/10/07 07:27:29 [SYS] Error checking for update: Get https://channels-dvr.s3.amazonaws.com/latest.json: dial tcp: lookup channels-dvr.s3.amazonaws.com on 192.168.1.1:53: server misbehaving

This happened to me yesterday when my Mac rebooted randomly while recording, and by the time it came back the program was over so it never got marked as finished. This bug is now fixed in the next prerelease.

3 Likes