sorry for being silly, wouldn't be the first time i'm afraid.
i guess it's a matter of UX. when i add a camera i will also probably re-allocate a few cameras in the system for better optimization. i've been using BI for like 15 years or when ever it got started and while i'm always buying cameras for about the same amount of dollar value they just get so much better.
by experience i've found that i usually move one or two other cameras when adding a new one. i'll improve one camera location with a new camera, then move that old one to another position and give that location an upgrade. or recently we added a whole new location. that's happened rather regularly.
also the short name is a different variable than the full name so doesn't really fit in the count. it serves a special purpose also not always needed.
no worries, was wondering if there are any more codes for time and date and camera performance than are listed in the help.
sometimes people discover things....
i would never use the cameras for OSD stuff. at the least, the fonts wouldn't match and the opaqueness, size etc. placements would all be different and i would have to remember all their IPs and UI. don't need a dozen cameras pinging for the time, maybe failing for unknown reasons. i would have to place my BIT weather macros in different places to compensate...
that's one the best aspects of BI, is that it ties all this together for a professional looking result and doesn't make me dependent on firmware programmers in china.
really impressive software, and i obviously have strong positions about these things. since the beginning, i would add, and the improvements never stop.