Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Sony Bravia TV Driver
Well, keep in mind I mean all or nothing for each individual device class. If you can support any, then do it. Those aspects of the device will benefit from that, even if others don't. But most V2 drivers are combinations of V2 and V1 fields.

That's why device classes don't typically cover a whole device, but just aspects of a device. So, for instance, if you can just support audio, then that still means that anywhere that an Audio interface is accepted, this driver could be used for that. Supporting Power is very useful if you can, even if that's the only thing you can support and so forth.
Dean Roddey
Explorans limites defectum
OK, That makes sense.

There should be a wider set of definitions for V1 as well. Lets take TV as this is what I am working on.

Power is usually always there
Source input is always there - (is it Source or Input - different authors will take different views)
Volume, Mute etc etc. If we all use the same field names it makes life a lot easier.

Even if the field is not available and thus not used, it should be defined for consistency across all drivers of that type.

Have you ever given thought to defining what fields should be used for drivers
Mykel Koblenz
Illawarra Smart Home
V1 is what it is. That's not going to change. Any formal definitions for V1 would never be that useful since there will always be existing drivers out there that don't follow them. So you could never count on them.

So really V2 is where any such formal definitions would happen. We can of course add more formal V2 device classes. It has to be done carefully though, since they have be such that the bulk of devices could hope to meet the requirements, and that's often tough.

There are semantic field types of course, which V1 drivers can use. They provide some basic indication of what a field is. But V2 device classes are the only way to define groups of fields that work together to achieve some particular goal.
Dean Roddey
Explorans limites defectum

Possibly Related Threads...
Thread Author Replies Views Last Post
  New Driver - How hard would this be? kblagron 4 550 05-20-2019, 11:28 AM
Last Post: zaccari
  Cytech Comfort Driver znelbok 6 507 04-10-2019, 05:39 PM
Last Post: znelbok
  OpenHAB Driver whozeawhat 6 2,364 01-16-2019, 06:45 AM
Last Post: greymatter
  LIFX Driver bobskie708 14 3,959 01-10-2019, 06:36 PM
Last Post: Dean Roddey
  XBMC Driver wuench 428 186,891 12-28-2018, 11:07 AM
Last Post: dogman
  Amazon Echo Hue Simulator Driver wuench 117 49,857 12-24-2018, 11:10 AM
Last Post: Dean Roddey
  RunTimer2 driver rbroders 15 5,628 12-14-2018, 05:28 PM
Last Post: rbroders
  Driver for Bigass Fan lleo 7 956 11-25-2018, 08:57 AM
Last Post: Dean Roddey
  Generic Modbus Driver - Serial & IP znelbok 25 14,652 10-09-2018, 08:59 AM
Last Post: Ron Haley
  Issues debugging IP based driver jnolting 5 1,293 09-24-2018, 11:52 AM
Last Post: Dean Roddey

Forum Jump:

Users browsing this thread: 1 Guest(s)