Generally no. If the hard drive takes longer than about 10s to start up recordings will fail. It also means a bad user experience waiting to be able to start playing back a recording.

I don’t even get why they’re telling us this. I’ve gotten to the point my Homerun is now sitting in my rack at home unplugged because at this point, it’s a brick and a waste of electricity. Even if some of your ATSC 3.0 channels are DRM encrypted your HDHomeRun 4K has all the features of the HDHome...

Notice from A3SA: We [A3SA] have scheduled system maintenance for Wednesday, May 29th from 4:30am to 5:30am EST. The maintenance activity involves updates to the A3SA content protection system. While we do not expect any technical issues to arise during this system maintenance window, during mainten...

We designed the HDHomeRun PRIME and newer boxes specifically avoiding any/all components that have a limited lifespan to ensure a long lasting high quality product. We back all our HDHomeRun models with a 2-year warranty. We still have users using our original model from 2006/2007 and will still mai...

I have split your post off to a new thread...

>It is impossible to navigate

Can you please elaborate on this.

gberchin wrote: ↑Tue May 21, 2024 2:40 pm V92.0 Build 20240517 still exhibits the problem.

Specifically "Discovering Devices" appears for a fraction of a second, and then the app returns to the Roku menu?

HDHomeRun App for Roku - 20240517
* Add crash report dialog.
* Fix possible crash on startup when no devices are found.
* Rollup of minor bugfixes and improvements.

"Val: ?" is a problem - you need to call your cable company and repeat the card paring before any DRM protected channels will work.

"hdhomerun_discover2_device_if_get_ip_addr" missing indicates that the libhdhomerun library version is out of date - you need to install a newer / latest version.

I understand the problem

The logs from the new ONN indicate AC4 passthrough and codec support. I will try to buy one to test in our lab.

Test - Can you please set the speaker configuration to "5.1 Surround Sound" then watch an ATSC 3.0 channel.

It should not be checking every 10 minutes... that suggests the record engine thinks the sync failed triggering a faster than normal retry.

The sync is required because the guide servers need to know what images to keep around for recordings to have images.

If you can please try a non Android/FireTV device such as Windows, Mac, iPhone/iPad, Apple TV, or XBox.

The HDHomeRun app waited 10s for data then timed out.
The stats from the HDHomeRun FLEX look fine.

Wondering if your WiFi might be having problems...

Open to feedback - what features/areas do you think there is room to improve on? I hope that you have this already on the to-do list? The record engine already supports playout only operation (ie disabling recording) by setting the RecordStreamsMax to 0 in the conf file. We can't disable internet A...