This discussion reminds me of this very long post dealing with a feature request... two of which are copied below, Mine and Spanky's.
Everyone has made some good points but I would zoom out to the macro view and take a different look. My disappointment relates to mis-set expectations. I've seen many, many responses from Elk whether they be by phone, email, private message or posts that have indicated that a requested feature / function has been "added to the list" or "its already on the list". We need to know the timeframe of "the list".
My expectation, especially for minor items is that these requests should be in the next major release. Is this latest release a "major" release from Elk's perspective? If so we have a problem. If its a minor release please say so then we can move on to a discussion about priorities. There is no doubt that some of the things they are adding are very complex on such a low level platform but its not fair to the users to spend all your time and energy on the complex additions and overlook a boatload of small one's.
Ok now back to the micro level... Example: How difficult is it to add the ability to control the backlighting of keypads via a rule. If your not a programmer or firmware expert please don't make up a long line of excuses as to why this is hard, needs more memory or could break ten other things. ITS SIMPLE, the basic control structure is already in place and the functionality exists in the keypad. It can already be set it just can't be changed programatically. Even the lowest level is too bright at night in a bedroom and if you turn it off after inactivity (to make it go dark) then you can't see it at all during the day.
Spanky's reply:
Being on the suggested feature addition list generally means that when enough people ask for the feature, it could be added. When one person asks for a feature and it is added to a consideration list, does not mean it will be in the next software release.
To understand the complexitity of adding a perceived simple feature like keypad backlight control from Rules involves these considerations:
1. ELKRP software changes, ELKRP protocol to M1 changes and documentation.
2. M1 software changes.
3. RS-485 data bus protocol changes and documentation.
4. Keypad software changes.
5. UL retesting evaluation. If UL retesting is involved, the answer is probably NO. Ask Digger!
6. Documentation and manual changes. Obsoleting printed manuals.
7. Training procedure changes.
8. Technical support training.
9. Evaluation of code space required. Some features just can't be added.
10. Perceived value of the feature against cost to add the feature.
11. Beta testing and field support.
...
Adding keypad backlighting control from Rules is a complex feature change. I would guesstimate this feature will cost $50K to add. You be the judge!
Some people have commented "Why updates are not more often". Other people complain that they are too often now. If a major issue is found, the update will come out very quickly. "It would be nice to have" updates are spaced out.
--------------------
Herd Leader
Elk Products, Inc.
