Feature request: add missing capabilities for action device

[hubitrep]

I am looking to run a Custom Action on a device. Ideally would like to see battery and carbon dioxide sensor in the capabilities list for action device selection:

I did notice that those capabilities are in the list for selecting a trigger event :

In the trigger event list, pressure is missing, but I can get to it by selecting "custom attribute". Perhaps the action device situation can be handled in a similar situation if the goal is to avoid really long combo box lists ?

Not a blocker at the moment as the devices I'm looking to automate have other capabilities I can use to get to them, but would be nice to have.

[aaiyar]

@hubitrep

Ideally would like to see battery and carbon dioxide sensor in the capabilities list for action device selection:

I'm kind of confused by this request. Are you trying to set the battery level of some device? Instead of whatever its reported battery level is?

[JasonJoel]

@hubitrep

action device selection

"Actuator" will allow you to select any command, custom or otherwise, on a device.

[aaiyar]

@JasonJoel

"Actuator" will allow you to select any command

As long as the device driver also supports the capability "Actuator". I don't know if sensor drivers (like a CO2 sensor) support that?

[JasonJoel]

Ah, well that's true. Details, details.

[hubitrep]

@aaiyar

I'm kind of confused by this request. Are you trying to set the battery level of some device? Instead of whatever its reported battery level is?

Yup. A virtual device.

I suppose that's an edge case and the reason why it's not already in the list.

[bravenel]

@hubitrep

Ideally would like to see battery and carbon dioxide sensor in the capabilities list for action device selection

Those capabilities do not have commands available, so even if they were on the list you couldn't do anything with them. If you have some virtual device, it has (or should have) capability Actuator.

[hubitrep]

@bravenel

Those capabilities do not have commands available, so even if they were on the list you couldn't do anything with them. If you have some virtual device, it has (or should have) capability Actuator.

Thanks. This is to run a custom command. I was assuming the capabilities list in "Run Custom Action" was just a means to filter the device list. Then the full list of commands for the selected device is offered, irrespective of the selected capability.

The VirtualOmniSensor, for example, doesn't appear to expose capability Actuator so instead I used "Temperature" to make it appear in the device selection list.

So, again. not a blocker, but a nice-to-have.

[csteele]

"Actuator" and "Sensor" are more like ocean and sea... you can't do anything. You can't change an ocean to a sea or a sea to an ocean. They just are.