DeviceButtonsAdd

[mnsandler]

Thanks Dirk,
can you post a small screen shot of how this device renders?

[Rick Tinker]

so then how do i create a status only device with control buttons?

Did you really just ask how to create a STATUS ONLY device with CONTROL buttons?

[dcorsus]

Thanks Dirk,
can you post a small screen shot of how this device renders?

See http://board.homeseer.com/showthread...41#post1058141

[mnsandler]

Yes I did Rick. I'm not really trying to control the physical device, just the hs device status/value in the scenario I mentioned in post #14

this is possible in HS2 and I don't want to give up/loss this capability in hs3

[rmasonjr]

Rick - I am doing the same thing as Mark. Status only devices with a "Reset" button so the user can clear the value as needed.

Is there a better way to do this?

[wetlip]

another reason to use status only device is to get rid of the radiobuttonlike status graphic, because that doesnt appear in status only devices.

[jon00]

Add me to the list. I normally use status only for buttons as it gives the control area a clean sheet.

[Rick Tinker]

Guys - if you have a single control option, then it is not "status only". There is no issue with having a control option on a device that is used MOSTLY as a status device.

Define your control option - button, drop-list, whatever - as a CONTROL pair, and then add your status options (individual VSPairs, range VSPair) as STATUS pairs.

When the control option is pressed/selected, it calls SetIOMulti in your plug-in, and it is your decision whether or not to change the value of the device which would update the status.

The status only MISC bit prevents the control options from displaying even if they are set on a device, so it is a way to turn control on/off without having to remove and re-add individual VSPairs.

[rmasonjr]

So is the code in posts 12 and 15 correct?