Yeah, early on when I started maintaining the add-on, I noticed that behavior too but since that code doesn't cause (and AFAIK, hasn't caused) any errors or issues with ntpMerlin itself, I just decided to leave that code alone, especially since I didn't (and I still don't) know all the reason(s)...