This behavior looks like it has been addressed in the newest version, 2.7.2
See firmware details here: