You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Provide the ability to deploy a device discovery test or feature stack test to help collect data on new devices. E.g. someone could write a "zigbee light" feature stack test attached to the database, then use it (on systems that approve) to test hardware. Because you control the testing, you maintain a single point of truth on what features, commands, etc. the devices support.
This would solve a problem of having to guess what parts of different protocols are implemented. One could know definitively if, for example, a given [light * firmware] combination supported prestaging commands while off. And it could stay relatively up to date with firmware changes.
I understand there are MANY implications to think through on something like this but the usefulness of such a database could not be underestimated for maintainers, integration developers, etc.
I personally run into this problem a lot with zigbee stuff but I imagine the broader idea of deploying test stacks could solve a number of device questions beyond what I can think of.
Thanks for the work on the database and providing the ability to participate in the discussion!
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Provide the ability to deploy a device discovery test or feature stack test to help collect data on new devices. E.g. someone could write a "zigbee light" feature stack test attached to the database, then use it (on systems that approve) to test hardware. Because you control the testing, you maintain a single point of truth on what features, commands, etc. the devices support.
This would solve a problem of having to guess what parts of different protocols are implemented. One could know definitively if, for example, a given [light * firmware] combination supported prestaging commands while off. And it could stay relatively up to date with firmware changes.
I understand there are MANY implications to think through on something like this but the usefulness of such a database could not be underestimated for maintainers, integration developers, etc.
I personally run into this problem a lot with zigbee stuff but I imagine the broader idea of deploying test stacks could solve a number of device questions beyond what I can think of.
Thanks for the work on the database and providing the ability to participate in the discussion!
All reactions