virtual Device - Variable / action group optional
Posted: Fri May 12, 2017 1:59 amHi,
just when fiddeling with my network speakers I made a virtual device for every speaker. Doing that, I realized 2 things that might be enhanced:
1. Why do I have to define a toggle action group, if I want to be able to toggle the device? Homebridge/Homekit can do it without that. I think, this action group should be otional. I only need it, if I have to do something different from switching On/Off. Otherwise Indigo could use the state to determin how to toggle.
2. When I want to have status, why do I have to define a variable for that. In my case it is enough to be able to fire an action group - which in turn sets the status of the device. I think the variable for the status field should be optional as well. In my case it is simply redundant information which complicates things.
It seems to me, that might be a small enough change to see it realized?
Thanks
Wilhelm
just when fiddeling with my network speakers I made a virtual device for every speaker. Doing that, I realized 2 things that might be enhanced:
1. Why do I have to define a toggle action group, if I want to be able to toggle the device? Homebridge/Homekit can do it without that. I think, this action group should be otional. I only need it, if I have to do something different from switching On/Off. Otherwise Indigo could use the state to determin how to toggle.
2. When I want to have status, why do I have to define a variable for that. In my case it is enough to be able to fire an action group - which in turn sets the status of the device. I think the variable for the status field should be optional as well. In my case it is simply redundant information which complicates things.
It seems to me, that might be a small enough change to see it realized?
Thanks
Wilhelm