Originally posted by alexbk66
View Post
Announcement
Collapse
No announcement yet.
Easy Trigger plug-in - Feature Requests
Collapse
This is a sticky topic.
X
X
-
Originally posted by spud View PostYou can already do that by adding stuff in the Startup.vb script.
Moreover ET doesn't know when HS starts, it only knows when the ET plugin is started itself which is a bit different.
But I don't like using Startup.vb as it's a bit hidden from view, but using ET for this would be more convinient.
Regarding "it only knows when the ET plugin is started itself which is a bit different" - it's not really important, a few secods difference...
Comment
-
Originally posted by spud View PostI understand how it could be useful, I guess I could add a special variable (something like $ControlUse:On) to the "Set Group of Devices to Expression"
Or inside (+/-) combobox add "ControlUse" option, but this is less obvious.
Comment
-
Originally posted by alexbk66 View PostI know that (both points).
But I don't like using Startup.vb as it's a bit hidden from view, but using ET for this would be more convinient.
Regarding "it only knows when the ET plugin is started itself which is a bit different" - it's not really important, a few secods difference...
Comment
-
Originally posted by alexbk66 View PostI know that (both points).
But I don't like using Startup.vb as it's a bit hidden from view, but using ET for this would be more convinient.
HS 4.2.8.0: 2134 Devices 1252 Events
Z-Wave 3.0.10.0: 133 Nodes on one Z-Net
- Likes 1
Comment
-
Originally posted by alexbk66 View PostI know that (both points).
But I don't like using Startup.vb as it's a bit hidden from view, but using ET for this would be more convinient.
Regarding "it only knows when the ET plugin is started itself which is a bit different" - it's not really important, a few secods difference...HS4 Pro, 4.2.19.0 Windows 10 pro, Supermicro LP Xeon
Comment
-
Originally posted by rprade View PostJude a master startup Event called from startup.vb and a master shutdown Event called from shutdown.vb.Originally posted by sparkman View PostTrigger an event from the startup script, and then you can add actions to that event as needed and they are then no longer "hidden from view".
Comment
-
Here is an example of how I did mine a few years back. Though since that post it has evolved somewhat. I run one immediately and another on a 1 minute delay called from the first Event. The actions you see with "Never" in front of them are disabled. The Never vs Then lets me enable or disable actions as needed or desired.
The delayed event does most of the hard work after HS has been up for a minute. The double entries for Jon00's DBCharting are to make sure the executable starts. I have a gremlin that occasionally would keep the exe from starting with HomeSeer, so I delay it and hit it twice. Now it never fails.
HS4 Pro, 4.2.19.0 Windows 10 pro, Supermicro LP Xeon
Comment
-
"Set Group of Devices to Expression" Question / Feature Enhancement
(give this post a 'like" if you would also find this a useful function)
It appears that te Expression part of "Set Group of Devices to Expression" evaluated only once for all devices in the group. I propose two modifications:
1) Evaluate the expression individually for each device in the group, thus letting each device in the group be set differently depending on the expression's calculated value for each device. Perhaps adding a check box option to choose whether to evaluate once or individually (though given the low overhead of a typical expression evaluation, the check box may not be that important).
2) Add global variables that can be used in the expression evaluations as each device's expression is evaluated. This would be analogous to the Easy Trigger global variables ETDeviceLocation1, ETDeviceLocation2, ETDeviceName, ETDeviceRef, ETDeviceStatus, and ETDeviceValue.
Here's an example use case:
I'd like to set up a group that includes a large number of interior dimmers. When sunset occurs, I'd like to turn on each dimmer to 10% if the dimmers is currently off, but not do anything if it is on. I'd envision being able to use "Set Group of Devices to Expression" to do this, where I'd select the "evaluate expression for each device" option and have an expression along the following lines:
IF($ThisDeviceValue == 0, 10, $ThisDeviceValue)
Where $ThisDeviceValue is the global variable I proposed that is analogous to ETDeviceValue
This expression would then get evaluated individually for each device allowing a different value to be computed for each device in the group.
Comment
-
Feature Request:
I have a couple of lights on dimmer wall sockets that I would like to go from 0 to 60% over a period of time (30 minutes) in the morning and down again in the evening. Any thoughts to an event control to manage the ramp from a current status value to a new value over a period? I currently do it by script, but a managed Event would be great.
Cheers
Scott
Comment
-
Originally posted by ScottRennie View PostI have a couple of lights on dimmer wall sockets that I would like to go from 0 to 60% over a period of time (30 minutes) in the morning and down again in the evening. Any thoughts to an event control to manage the ramp from a current status value to a new value over a period? I currently do it by script, but a managed Event would be great.
Comment
-
Originally posted by ScottRennie View PostFeature Request:
I have a couple of lights on dimmer wall sockets that I would like to go from 0 to 60% over a period of time (30 minutes) in the morning and down again in the evening. Any thoughts to an event control to manage the ramp from a current status value to a new value over a period? I currently do it by script, but a managed Event would be great.
Cheers
Scott
-Setup a schedule in ET with the two 30 minute intervals when you would like the light to gradually increase and decrease.
-Create event for morning time
If time enters (xyzschedule) time range
And if the time is before 12:00pm
And If The Device was Set and is not greater than 62
Or If The device had its value set and is less than 62
And If EasyTrigger:Time is within (xyzschedule) time range
And If the time is before 12:00pm
Then EastTrigger:Set Device to Expression, choose your dimmer, set it to $$DVRinsert device ref#) + 2
**In the Options for the event, make sure you set the can not rerun for one minute.
-Create event for evening
If time enters (xyzschedule) time range
And if the time is after 12:00pm
And If The Device was Set and is not greater than 62
Or If The device had its value set and is less than 62
And If EasyTrigger:Time is within (xyzschedule) time range
And If the time is after 12:00pm
Then EastTrigger:Set Device to Expression, choose your dimmer, set it to $$DVR: insert device ref#) - 2
**In the Options for the event, make sure you set the can not rerun for one minute.
Let me know how this works for you, hope it helps!
Sent from my iPad using TapatalkHS4 4.2.6.0 &HSTouch Designer 3.0.80
Plugin's:
BLBackup, BLOccupied, BLShutdown, EasyTrigger, Ecobee, Nest, AK Bond
EnvisaLink DSC, PHLocation, Pushover, SONOS, Blue Iris, UltraRachio3,
weatherXML, Jon00 Alexa Helper, Network Monitor, MyQ, Z-Wave
Comment
-
Originally posted by The Profit View Post
You should be able to do this with the existing EasyTrigger plugin. Question first, once the light has reached the 60% do you want to leave it on until the time where you will start to decrease the light level or will it need to turn off after its reached 60%?
-Setup a schedule in ET with the two 30 minute intervals when you would like the light to gradually increase and decrease.
-Create event for morning time
If time enters (xyzschedule) time range
And if the time is before 12:00pm
And If The Device was Set and is not greater than 62
Or If The device had its value set and is less than 62
And If EasyTrigger:Time is within (xyzschedule) time range
And If the time is before 12:00pm
Then EastTrigger:Set Device to Expression, choose your dimmer, set it to $$DVRinsert device ref#) + 2
**In the Options for the event, make sure you set the can not rerun for one minute.
-Create event for evening
If time enters (xyzschedule) time range
And if the time is after 12:00pm
And If The Device was Set and is not greater than 62
Or If The device had its value set and is less than 62
And If EasyTrigger:Time is within (xyzschedule) time range
And If the time is after 12:00pm
Then EastTrigger:Set Device to Expression, choose your dimmer, set it to $$DVR: insert device ref#) - 2
**In the Options for the event, make sure you set the can not rerun for one minute.
Let me know how this works for you, hope it helps!
Sent from my iPad using Tapatalk
Looks like that would work. Still would be cool to have the functionality built in as an Action
Sent from my SM-G950U using Tapatalk
Comment
-
Originally posted by Ltek View Post... I think I follow. Your event would increment the dim level 2% every minute. Correct?
Looks like that would work. Still would be cool to have the functionality built in as an Action
Sent from my SM-G950U using Tapatalk
I’m not a plugin developer but it seems like it would be possible to set up an action to do this. With all the different possibilities that people could come up with however, it’s great that Spud has at least opened up a lot more options with ET.
Sent from my iPad using TapatalkHS4 4.2.6.0 &HSTouch Designer 3.0.80
Plugin's:
BLBackup, BLOccupied, BLShutdown, EasyTrigger, Ecobee, Nest, AK Bond
EnvisaLink DSC, PHLocation, Pushover, SONOS, Blue Iris, UltraRachio3,
weatherXML, Jon00 Alexa Helper, Network Monitor, MyQ, Z-Wave
- Likes 1
Comment
Comment