123
Senior Member
Yes, you can use the Class Wizard to quickly create a skeleton of a driver for whatever device you need. The resulting driver will bind to the appropriate Home object (thermostat, TV, etc).
You'll find that the Thermostat object will not be rendered by MiniBrowser unless it is bound to a driver. If you check the code you'll see it confirms that BoundObject exists before rendering the UI. I suspect one of Premise's developers thought that it was pointless to display a UI for something if it wasn't bound to a driver. It the object is not bound to a driver, the UI simply displays a message to that effect. It's a sound design decision but, with the notable exception of Thermostat and MediaZone, it was not implemented for most objects
You'll find that the Thermostat object will not be rendered by MiniBrowser unless it is bound to a driver. If you check the code you'll see it confirms that BoundObject exists before rendering the UI. I suspect one of Premise's developers thought that it was pointless to display a UI for something if it wasn't bound to a driver. It the object is not bound to a driver, the UI simply displays a message to that effect. It's a sound design decision but, with the notable exception of Thermostat and MediaZone, it was not implemented for most objects