Yes, we know there is the bug. It does give me 'hints' though, as long as I remember that they are switched, very annoying.

I got an idea, if you look at df carefully, on the N810, the 1st row does trap the correct id! and it is different from the 2nd row. While on the N800, both rows reported the same correct id. What do you think?

So, one can kind of err trap df report of the 1st 2 rows, if same, must be an N800, will take the id as reported. If different, must be an N810, will switch id from reported and flag a statement before backup. Make sense? It does to me

bun