RM-bcu1: VD issues and enhancements

[dallmair]

Issues with the current VD

1. Object functions "Network", "Reset", and "Status" are not entirely clear to newcomers, so it would be great if we could find more descriptive texts for these
2. DPT of Communication Object 7, Operating time: When "hours" is selected, DPT 7.007 overflows after roughly 7.4 years -- it seems DPT 12.102 (32-bit unsigned integer) would be better
3. Typo in "Betiebszeit senden als"
4. For operating time, instead of DPT 13.100 it should probably be 12.100
   • This is purely for metadata correctness, but does not have any practical effect, because even DPT 13.100 can represent 68 years

For number 2, please note that

1. Operating time is off by as much as +/-5% on many devices we've seen (i.e. some smoke detectors count only 57 seconds per minute, others count 63 seconds per minute)
2. Operating time gets reset whenever the device resets, and we've seen numerous spurious resets of these smoke detector devices

Thus, the informative value of the Operating Time communication object is in general relatively low from our point of view.

Potential enhancements

1. New writable communication object "Reset smoke alarm device": When any value is written into this communication object, we send a 00TEST command to the device which causes a device restart.
2. Allow to choose whether communication object 2 "Alarm Reset" just resets the wireless (KNX) alarm triggered by the module itself, or alternatively resets any local alarm. This would be helpful when the smoke alarm device is mounted on a high ceiling, where it's not easily reachable for pressing the button in case of a false alarm. Was already on the list, and then later also requested in knx-user-forum.
3. Add a new communication object "Local Alarm Status". This allows identification of the smoke alarm device that has local alarm even when several devices have both a KNX module and are connected via the green networking terminal. Requested in knx-user-forum.