Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RM-bcu1: VD issues and enhancements #59

Open
dallmair opened this issue Dec 27, 2023 · 0 comments
Open

RM-bcu1: VD issues and enhancements #59

dallmair opened this issue Dec 27, 2023 · 0 comments

Comments

@dallmair
Copy link
Member

dallmair commented Dec 27, 2023

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

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.
  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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant