Channel Freezes on TVs and error log

#1

Noticed TVs were freezing (multiple TVs). I finally got around to checking the log and noticed this strange pattern in the logs. Basically my log is filled with these types of entries.

I can get back to an unfrozen channel by mearly backing out and going back into the same channel.
Any idea what this means?

2021/06/02 17:31:25.109612 [HTTP] | 200 | 33.949966ms | 192.168.0.52 | GET "/devices/1076456B/status/0/debug"
2021/06/02 17:31:26.045920 [HTTP] | 200 | 20.148459ms | 192.168.0.51 | GET "/devices/13149111/status/0/debug"
2021/06/02 17:31:27.145174 [HTTP] | 200 | 34.308739ms | 192.168.0.52 | GET "/devices/1076456B/status/0/debug"
2021/06/02 17:31:28.066768 [HTTP] | 200 | 19.607883ms | 192.168.0.51 | GET "/devices/13149111/status/0/debug"
2021/06/02 17:31:29.180155 [HTTP] | 200 | 33.446361ms | 192.168.0.52 | GET "/devices/1076456B/status/0/debug"
2021/06/02 17:31:30.087891 [HTTP] | 200 | 19.603501ms | 192.168.0.51 | GET "/devices/13149111/status/0/debug"
2021/06/02 17:31:31.215191 [HTTP] | 200 | 33.467438ms | 192.168.0.52 | GET "/devices/1076456B/status/0/debug"
2021/06/02 17:31:32.108800 [HTTP] | 200 | 19.633756ms | 192.168.0.51 | GET "/devices/13149111/status/0/debug"
2021/06/02 17:31:33.250205 [HTTP] | 200 | 33.412175ms | 192.168.0.52 | GET "/devices/1076456B/status/0/debug"
2021/06/02 17:31:34.130992 [HTTP] | 200 | 19.588829ms | 192.168.0.51 | GET "/devices/13149111/status/0/debug"
2021/06/02 17:31:35.284494 [HTTP] | 200 | 32.843327ms | 192.168.0.52 | GET "/devices/1076456B/status/0/debug"
2021/06/02 17:31:36.151852 [HTTP] | 200 | 19.5478ms | 192.168.0.51 | GET "/devices/13149111/status/0/debug"
2021/06/02 17:31:37.319706 [HTTP] | 200 | 33.800391ms | 192.168.0.52 | GET "/devices/1076456B/status/0/debug"
2021/06/02 17:31:38.172910 [HTTP] | 200 | 19.540676ms | 192.168.0.51 | GET "/devices/13149111/status/0/debug"
2021/06/02 17:31:39.354518 [HTTP] | 200 | 33.488918ms | 192.168.0.52 | GET "/devices/1076456B/status/0/debug"
2021/06/02 17:31:40.193738 [HTTP] | 200 | 19.538826ms | 192.168.0.51 | GET "/devices/13149111/status/0/debug"
2021/06/02 17:31:41.389564 [HTTP] | 200 | 33.570055ms | 192.168.0.52 | GET "/devices/1076456B/status/0/debug"
2021/06/02 17:31:42.214561 [HTTP] | 200 | 19.497922ms | 192.168.0.51 | GET "/devices/13149111/status/0/debug"
2021/06/02 17:31:43.425263 [HTTP] | 200 | 33.221188ms | 192.168.0.52 | GET "/devices/1076456B/status/0/debug"
2021/06/02 17:31:44.235233 [HTTP] | 200 | 19.499227ms | 192.168.0.51 | GET "/devices/13149111/status/0/debug"
2021/06/02 17:31:45.460295 [HTTP] | 200 | 33.44827ms | 192.168.0.52 | GET "/devices/1076456B/status/0/debug"
2021/06/02 17:31:46.256164 [HTTP] | 200 | 19.505524ms | 192.168.0.51 | GET "/devices/13149111/status/0/debug"
2021/06/02 17:31:47.497004 [HTTP] | 200 | 33.428787ms | 192.168.0.52 | GET "/devices/1076456B/status/0/debug"
2021/06/02 17:31:48.277298 [HTTP] | 200 | 19.522196ms | 192.168.0.51 | GET "/devices/13149111/status/0/debug"
2021/06/02 17:31:49.531783 [HTTP] | 200 | 32.736687ms | 192.168.0.52 | GET "/devices/1076456B/status/0/debug"

#2

I haven't looked at the error log, but I'm having the same freezing. Backing out and reselecting the channel restores playback.

I have upgraded the firmware on my HdHomeRun Connect Quatro a few minutes ago, for now the freezing appears to be fixed. For what it's worth, the firmware upgrade did restart the HdHomeRun tuner when the upgrade was complete. Who knows if a simple tuner power cycle would have fixed the issue also.

#3

Please submit diagnostics from the android app after this happens.

The DVR log looks normal. The client is asking the server to check on the signal from the HDHR.

#4

Same things been happening to me for months. Windows/FireStick. I have submitted DVR logs, but not Android logs. I'll try to capture an Android log next time.