I am new to Homeseer and I have only added a couple of zwave devices to test things out. I have added a zooz ZSE18 motion sensor and a zooz wall switch. I am trying to create an event to turn the light on when motion is detected and then turn off the light after 1 minute if no other motion is detected. However, it doesn't turn the light on. I can run the event and it will turn the light on and then off again but when I walk in the room, nothing. What am I doing wrong? I have also noticed that when creating the event, I have to select the sensory binary motion child part, right?
Announcement
Collapse
No announcement yet.
Newbie question about an Event I have created not working
Collapse
X
-
I recommend looking through the items in the Event Clinic table of contents post and especially the Navigating the Event Management page thread. While there is still more that I would like to make the time to add, it covers much Information. I also recommend reading the Virtual Device Creation and Modification thread which will give insight to how HomeSeer’s devices work. All HomeSeer’s Devices are based on the same template.HS4 Pro, 4.2.19.16 Windows 10 pro, Supermicro LP Xeon
- Likes 1
Comment
-
I do this the first way you did it with a small change. The light would turn off in one minute after the initial motion was detected in where you could still be in the room moving around. To mitigate that, add another action as the first "then" to remove a delayed device action choosing the appropriate light switch.
Len
HomeSeer Version: HS3 Pro Edition 3.0.0.435
Linux version: Linux homeseer Ubuntu 16.04 x86_64
Number of Devices: 633
Number of Events: 773
Enabled Plug-Ins
2.0.54.0: BLBackup
2.0.40.0: BLLAN
3.0.0.48: EasyTrigger
30.0.0.36: RFXCOM
3.0.6.2: SDJ-Health
3.0.0.87: weatherXML
3.0.1.190: Z-Wave
Comment
-
Originally posted by lveatch View PostI do this the first way you did it with a small change. The light would turn off in one minute after the initial motion was detected in where you could still be in the room moving around. To mitigate that, add another action as the first "then" to remove a delayed device action choosing the appropriate light switch.
Comment
-
Originally posted by pcgirl65 View Post
Wouldn't the second Event that I posted do this as well?Len
HomeSeer Version: HS3 Pro Edition 3.0.0.435
Linux version: Linux homeseer Ubuntu 16.04 x86_64
Number of Devices: 633
Number of Events: 773
Enabled Plug-Ins
2.0.54.0: BLBackup
2.0.40.0: BLLAN
3.0.0.48: EasyTrigger
30.0.0.36: RFXCOM
3.0.6.2: SDJ-Health
3.0.0.87: weatherXML
3.0.1.190: Z-Wave
Comment
-
For me, HomeSeer has been extremely stable and it is quite powerful. The key is to understand the way the Event Engine works and to learn the language. It is not a standard programming language. It is capable of IF, THEN, ELSE execution, but not in a conventional programmatic way. Instead it is based on a Triggered (or multiple Triggered) Event structure using Actions that are common to all Triggers. Perhaps this thread illustrates it best.
My system is quite busy with over 1500 Events and thousands of devices, yet it has never crashed due to problems with HomeSeer’s software. It just works. We rarely interact directly with HomeSeer, it just percolates day in and day out in the background - since 2014.HS4 Pro, 4.2.19.16 Windows 10 pro, Supermicro LP Xeon
Comment
-
Originally posted by rprade View PostMy system is quite busy with over 1500 Events and thousands of devices, yet it has never crashed due to problems with HomeSeer’s software. It just works. We rarely interact directly with HomeSeer, it just percolates day in and day out in the background - since 2014.
Comment
-
You can always send an on command and if the unit is on already it will stay on. I do not check the status of I want to force a device on (or off).Karl S
HS4Pro on Windows 10
1070 Devices
56 Z-Wave Nodes
104 Events
HSTouch Clients: 3 Android, 1 iOS
Google Home: 3 Mini units, 1 Pair Audios, 2 Displays
Comment
-
As you state you are new to homeseer, a little bit more education / exposing homeseer magic. Delayed actions and delayed events are homeseer generated events which are placed in either the "delayed actions" or "delayed events" event groups which are both dynamically created and removed.Len
HomeSeer Version: HS3 Pro Edition 3.0.0.435
Linux version: Linux homeseer Ubuntu 16.04 x86_64
Number of Devices: 633
Number of Events: 773
Enabled Plug-Ins
2.0.54.0: BLBackup
2.0.40.0: BLLAN
3.0.0.48: EasyTrigger
30.0.0.36: RFXCOM
3.0.6.2: SDJ-Health
3.0.0.87: weatherXML
3.0.1.190: Z-Wave
Comment
-
Originally posted by lveatch View PostDelayed actions and delayed events are homeseer generated events which are placed in either the "delayed actions" or "delayed events" event groups which are both dynamically created and removed.
Comment
Comment