Thanks for reporting this! It is a known change with the v1.2.0 of the Aranet4 firmware and I’ve created an issue on GitHub to address it.