I found a Denon AVR driver. When I go into device, I see all the commands/buttons that I need, but when I go to create a button in dashboard I don't see any of them. I look under attributes in templates of that device in the dashboard and I see maybe 1/4 of the available commands, and they don't even work...but they did work when clicking on the button command in devices. So how do I map the commands to the dashboard?
It sounds like there is some confusion with terminology, so I'll start there:
- "buttons" on the device page in the admin UI represent commands that the device supports
- the "Button" template on Dashboard allows you to simulate a "pushed" event (command) on a virtual or, if supported, real button device
- "attributes" are the names of things you see under "Current States," like "switch" or "level"
- The "Attribute" template on Dashboard lets you display the value of any attribute, though in most cases a template geared towards that specific type of device would be better (e.g., for a switch, the "Switch" template would be a better choice than choosing an "Attribute" tile with the "switch" attribute, which would only let you see the current value and not manipulate anything that might change it)
I'm not sure what you mean with the "attributes" not working on Dashboard, but I'm guessing it's related to that last point. Some Dashboard tiles are capable of sending commands to devices. Commands generally result in an attribute/state being changed, but if a stock Dashboard template doesn't do what you want, there's no way to create a Dashboard tile that sends a specific command to a device. If you're looking for a specific command, someone may know a template that does what you want. (If these are custom commands, there probably won't be anything you can do here; Dashboard templates are geared for "standard" commands you see on most devices.) Otherwise, you'll have to use a workaround.
One workaround people sometimes do: create a virtual button, expose that button to Dashboard, then create a Dashboard tile that pushes a certain button number on that virtual button. Then create a simple rule that triggers on that button event and runs the (stock or custom) command on your device.
The question is how to make simple rule to run command that exists in the device
but not on the available actions inside rule creation?
That sounds like a different question than what the OP was asking, and this thread is old.
Can you create a new thread to ask a question with a little more detail about what you’re trying to do?
2 Likes
