Easy Trigger plug-in - Feature Requests

[pseudocode]

also Super groups are super, thanks!

[pseudocode]

Would be great to have a plugin function that checks whether a specific time is in a schedule, rather than always assuming NOW.

Could be a simple addition of an optional second parameter of type DateTime in the call to IsTimeInScheduleTimeRange.

Scenario I want to handle - I have scripts which use schedules to decide when actions are allowed (e.g. managing blinds for direct sunlight), but in some cases I want to not take a specific action during the last X minutes of a schedule - so I'd like to be able to use IsTimeInScheduleTimeRange("Schedule", Now.AddMinutes(X)) to check that.

[randy]

All good now!

[spud]

randy, please test version 3.0.0.78, it should solve your problem.

[Ltek]

In version 3.0.0.77 released as a Beta, I have added the "Super" group type. A super group can contain any other group type including other super groups, but if a super group contains another super group be careful to not create circular references which would lead to a group containing itself.

Any plans to add other feature soon?
A natural extension to groups (which as immense value) is being able to place them in a virtual device to see the status. I made this request a few years ago I think. Super Groups make this even more useful... a device that we can set to show the status like: Doors/Windows currently Open, Motion Sensors currently triggered, etc

[randy]

randy could tou send me your EasyTrigger.ini so that I can try to replicate. Thanks

Here you go

[spud]

randy could tou send me your EasyTrigger.ini so that I can try to replicate. Thanks

[randy]

Back to .76 and all is well. It’s time to quit for the evening. I’ll try again tomorrow when I can look for log errors.

[randy]

Installed beta .77. The Easy Trigger Settings page simply says “ERROR”. I cannot get the plug-ins menu to open to roll back. Will restore from a backup.

[spud]

In version 3.0.0.77 released as a Beta, I have added the "Super" group type. A super group can contain any other group type including other super groups, but if a super group contains another super group be careful to not create circular references which would lead to a group containing itself.

[andyf]

As a natural extension to Enable/Disable Event can you add a condition for "Event is Enabled" / "Event is Disabled"? That would help me a lot since I do some actions based on whether a Motion Event is enabled or disabled.

Really appreciate the plug-in, thanks.

[spud]

I would like to have functionality that can

1) Create new schedules
2) Delete existing schedules

Both of those basically allow to modify schedules but also with the option to create new schedules that didn't exist yet. I am not sure what the best way is to get the schedule information. Maybe through global variables. It should be some mechanism that can be used via HSTouch so schedules can be created via HSTouch.

You can update or create a schedule using the SetSchedule scripting function:
https://forums.homeseer.com/forum/ul...15#post1281015

[mulu]

I would like to have functionality that can

1) Create new schedules
2) Delete existing schedules

Both of those basically allow to modify schedules but also with the option to create new schedules that didn't exist yet. I am not sure what the best way is to get the schedule information. Maybe through global variables. It should be some mechanism that can be used via HSTouch so schedules can be created via HSTouch.

[bebaldin]

I would like to request some new features in EasyTrigger:

1. A method for easily sorting all of the schedules and device groups either manually (or even automatically, if possible). I have more than 150 entries now in ET, and I periodically go into the INI file and manually sort everything back out alphabetically, to make it easy to find what I need.
2. A new ET condition that works to find Invalid or Error Conditions, especially for those objects that do not use the 254 value definition, and rely on the internal invalid flag. This would be similar to the HS built in condition This Device Has Been For At Least...(Device Name has been Invalid or Error State). This would allow devices to be grouped together, and then an scripting action that would clear the invalid flag or turn the device on or off employed to remove the Invalid State. I have several problem devices that will go invalid from time to time (locks are a good example), and I have written events for each to deal with them when they do. That is a lot of events that could be consolidated by using ET global variables and this new condition. Another annoying issue this would address is the Root Device on some devices going invalid and displaying Unknown. I currently use &hs.DeviceInvalidValue(dvRef) = False to clear those when I see them. Adding them to an ET group would allow me to automate this process.
3. A new ET action that would set the current device defined by ETDeviceRef global variable to an Expression. It could be named something like EasyTrigger: Set Current Device by Reference to Expression. The logic here would be that If an ET condition or trigger occurs, this could immediately trigger some action to happen to the single device from the group that triggered the event. I would use something like this to take a device in an invalid state from #2, and send a command to turn it on or off, lock or unlock, etc. The flag used in Set A Group of Devices to Expression that only runs the command if it would result in a change would also be useful here to prevent excessive commands.

Thank you for your consideration!

[bebaldin]

Not sure why, but mine has never operated in this manner. If the light is on, for example, and I press the button, it will only go to off if Off is at the top of the order in the list. If On is at the top of the order, I have to press twice to get the device to turn off.

I have verified this on every toggle trigger I have. The order of execution absolutely determines what happens when you push the button each time. If the order is Off, On, then the event will always first try to turn the device off regardless of its actual state.