The confirmed bug reported in this post is still present in 2.11 and still not listed as “known issue”.
It’s just a year…
A&H isn’t going to list every single reported “bug” in the “know issues” section of the firmware update page. They are only going to post the “biggest” bugs (ie the bugs that affect the largest number of people). The fact that a bug is “missing” from the update page doesn’t mean that A&H has failed to catalog it in the official bug tracking system they use.
While this is a bug that needs to be fixed, it is on a very specific use case that doesn’t affect the majority of people. As such, it is understandable why A&H doesn’t list it as a “know bug” in the update guide.
1 Like