[quote=“tgauchat, post:5, topic:22726”]
hen the detail screen for the Device shows up with a highlighted button that suggests alternative available Device Handlers for user selection (if any), giving the detailed brand and model number and other information to help the user choose. A “reset to default” button should also be available
[/quote]This could work… Actually, based on MSR (that most devices provide) it could auto-select the best device type. However, do all the device types for every possible device have to be pre-loaded on your v2hub?
By having conditionals in the property pages, it should be doable. Either based on the device type “description”, or the MSR (if supported.) As an obvious example, if a z-wave switch doesn’t advertise the configuration command, don’t show the tile for “indicator light” on the device page.
On the other hand, some of the “special features” of an otherwise generic device type can be quite extensive. There are 5-6 “special features” of the schlage z-wave lock that are either unique or uniquely implemented. If the same holds true for other z-wave locks, then a single generic type that intelligently exposes the proper features might become overwhelming. However, the alternative of a generic type that exposes nothing for any of them is also not great.
So, I actually do have an idea on this…
What if a device type could be generic, but also load type-specific modules? So, the z-wave lock device would be the catchall. After getting the MSR from the device, it would call a ST function passing the raw z-wave description and MSR as parameters. Then, something on the server side would recognize the description and/or MSR and send back a specific “add-on” to the device type which implemented the extra features?
So, for example, the generic “z-wave switch” would ONLY provide on/off capability for a GE z-wave switch. After detection, it would send the raw description (0 0 0x1001 0 0 0 7 0x25 0x27 0x73 0x70 0x86 0x72 0x77) and MSR (not sure if this switch supports it or what it is) to the server. The ST server would recognize that as a GE branded switch that, in addition to on/off, also supports an indicator light with 4 possible states. A linear switch would support an indicator light with 3 possible states. The z-wave socket adapter I have doesn’t even support the configuration class, so would ONLY be an on/off switch.
This differs from what Terry suggested in that it wouldn’t CHANGE device types… it would still use the “basic generic” device type, but would add on special modules for specific devices. So, the BASIC functionality is always 100% the same no matter what else changes. Even if the device specific module breaks, the basic type still works.
I realize the idea isn’t complete here. I’m only brushing the edges of the concept… Of course, none of us have a clue if ST is capable of doing anything like this with their infrastructure and the v2hub. Even if all the technical aspects aren’t hurdles, it would still take at least “a few weeks” before they could even consider the idea…