Like many others I had HS Events using the Z-Wave actions for ALL ON /OFF commands to control devices based on their assigned Room or Floor. With this feature removed in V4 of the Z-Wave plugin I have been looking for alternatives. EasyTrigger is often mentioned for this use case. I love ET but found this less than ideal. It requires creating device groups for each room and each floor. Groups can be not only static, requiring devices to be manually added, but also dynamic. I found the options for creating dynamic groups to be limiting. I can't easily exclude devices I may not want. It gets very cumbersome to build and manage all of these groups regardless of the method. If you want to control these groups by voice or with the app you have to make events. One for On, and one for Off, for each room and floor. Unless I am approaching this wrong, it feels like a lot to manage.
I have found a method that is working for me, but would like to suggest that HST make it more of a defined feature (with easier access) rather than a workaround. After the Z-Wave ALL feature was removed, I noticed that my Alexa voice command "tell HomeSeer to turn off all <floor/room> lights" continued to work. I use these commands fairly often. Especially when I notice that a light is burning on another floor, but I don't necessarily know which light. I can call out these commands and it Just Works. I don't have to make ET groups or events. I can add a device to a brand new room and I can immediately issue voice commands. This is a testament to HomeSeer's built-in natural language processor. This engine predates Alexa and other assistants but can be very useful. It just figures out what you want. I have found that using this interface to turn all lights on or off for a given space is not reliant on the similar Z-Wave feature at all. It even works on Virtual devices.
My suggestion is that this be made accessible from Events. The functionality is there. I can trigger it with my voice from Alexa. I think it would be great to trigger from Events too. I think there should be an action with selectable commands (ON/OFF) and selectable room/floor.
Taking this idea a bit further: It's a bit of a black-box as to how HS determines which devices will be included in these commands. I have some Z-Wave smart-plugs that are also energy monitors. They have around 5 child devices and one of them is a Switch. This Switch child device is unaffected by the ALL ON/OFF commands. I have Z-Wave outlets that are a simple, single-child Switch that ARE controlled. I'm not sure why. Ultimately this works for my use-case as the smart-plugs are behind Kitchen appliances mainly for energy monitoring. I do not want them controlled by these commands. That said, it occurred to me that it would be useful to put control in the user's hands. The "Is Light" checkbox does not seem to impact this functionality but I feel like it should. If defined as a light then it should be included in these commands as they are specifically for turning on all the *lights* in a room or floor. If not this checkbox then perhaps another one could be added with this goal in mind.
Stretch goal: While a niche feature, I think it would be neat if text-based commands could be passed directly to the voice command engine as an event action. I am currently doing this albeit in a hacky way. I am using a immediate script statement to call hs.GetURL and hitting the JSON voicecommand interface and passing a string. This allows me to effectively issue "turn off all the downstairs lights" as part of an event, without the use of any plugins. I just think it would be cool if I could do this with a dedicated action instead of hs.GetURL.
I'm just brainstorming before I submit an official feature request in the support portal. I appreciate any feedback.
Thanks.
I have found a method that is working for me, but would like to suggest that HST make it more of a defined feature (with easier access) rather than a workaround. After the Z-Wave ALL feature was removed, I noticed that my Alexa voice command "tell HomeSeer to turn off all <floor/room> lights" continued to work. I use these commands fairly often. Especially when I notice that a light is burning on another floor, but I don't necessarily know which light. I can call out these commands and it Just Works. I don't have to make ET groups or events. I can add a device to a brand new room and I can immediately issue voice commands. This is a testament to HomeSeer's built-in natural language processor. This engine predates Alexa and other assistants but can be very useful. It just figures out what you want. I have found that using this interface to turn all lights on or off for a given space is not reliant on the similar Z-Wave feature at all. It even works on Virtual devices.
My suggestion is that this be made accessible from Events. The functionality is there. I can trigger it with my voice from Alexa. I think it would be great to trigger from Events too. I think there should be an action with selectable commands (ON/OFF) and selectable room/floor.
Taking this idea a bit further: It's a bit of a black-box as to how HS determines which devices will be included in these commands. I have some Z-Wave smart-plugs that are also energy monitors. They have around 5 child devices and one of them is a Switch. This Switch child device is unaffected by the ALL ON/OFF commands. I have Z-Wave outlets that are a simple, single-child Switch that ARE controlled. I'm not sure why. Ultimately this works for my use-case as the smart-plugs are behind Kitchen appliances mainly for energy monitoring. I do not want them controlled by these commands. That said, it occurred to me that it would be useful to put control in the user's hands. The "Is Light" checkbox does not seem to impact this functionality but I feel like it should. If defined as a light then it should be included in these commands as they are specifically for turning on all the *lights* in a room or floor. If not this checkbox then perhaps another one could be added with this goal in mind.
Stretch goal: While a niche feature, I think it would be neat if text-based commands could be passed directly to the voice command engine as an event action. I am currently doing this albeit in a hacky way. I am using a immediate script statement to call hs.GetURL and hitting the JSON voicecommand interface and passing a string. This allows me to effectively issue "turn off all the downstairs lights" as part of an event, without the use of any plugins. I just think it would be cool if I could do this with a dedicated action instead of hs.GetURL.
I'm just brainstorming before I submit an official feature request in the support portal. I appreciate any feedback.
Thanks.
Comment