So for the motion sensor, it should be updating the HomeSeer device status correctly. Many of the ISY plug-in triggers are triggered when the plug-in receives a message from the ISY instead of being based on the HomeSeer device status.įor devices where the status aligns with the status definitions in HomeSeer, On/Off/Dim/unknown are the only real standard status values in HomeSeer, the plug-in devices should be conforming. The dimmer/relay devices are a close match to a "standard" HomeSeer device model so any custom triggers are also very close to the standard one. Probably just because no one has asked before now. Even if the motion sensor shows status ON in Homeseer (and on the ISY of course), the event will not trigger.įor example, instead of using ISY Dimmer Condition, can I just use "device" condition and select the ISY dimmer device? Are there rules for when to use one type of condition over the other?There's no particular reason why the motion sensors don't have custom trigger conditions. There no ISY conditions applicable to motion sensors, so I used the standard device condition. ![]() Perhaps you just need to define it as an ON/OFF device within Homeseer. 99%, ON which seems to be what you would expect for a dimmer. but should I need one?Īlso, when I select a motion sensor as a device, the options come up as OFF, 1%, 2%, 3%. I have created a program that is true when the motion sensor is ON, and changed the event condition to include the program status "true" rather than the motion sensor ON. I could create a program in the ISY to be true when a motion sensor is on, but that seems like a band-aid.Ĭoudl you create a device condition type for motion sensors so that I can use their status in conditions? Is there some way to make the regular device condition work - I don't understand why you have special ISY conditions for everything else? Is there a problem making Homeseer recognize the states of the ISY devices?įor example, instead of using ISY Dimmer Condition, can I just use "device" condition and select the ISY dimmer device? Are there rules for when to use one type of condition over the other? Even if the motion sensor shows status ON in Homeseer (and on the ISY of course), the event will not trigger. There are no predefined ISY condition groups applicable to motion sensors, so I used the standard device condition. (they are set to remain on for a few minutes, so that by the time a kid would get into the hallway, they are still on) So I wanted to add a condition that required the 2420 motion sensors in each of the kids' rooms to be ON before the event trigger would be valid. The event was triggering often because our very fat cat would set off the hallway motion sensor causing the security device to trigger. In one path group, if neither IP address is reachable, then that path group fails, and triggers a failover.Hello, I have an event that triggers on a hallway security device from my JDS Stargate system. ![]() we have two path groups, each path group has two IP addresses to track, and the failure condition is all. If we have more then one Path group, and the Path monitoring has a failure condition of any, if any of the path group fails, then a failover is triggered.įor example. Suppose we have only one entry in the Path group. If the path monitoring has a failure condition of any, and the path group has a group failure condition of all, then all is preferred, because whatever's configured in the path group is preferred. If both interface 1/1 and 1/2 fail, then the link group fails and triggers a failover. If we have more then one link group and the link monitoring has a failure condition of any, if any of the link group fails, then a failover is triggered.įor example, say you have two link groups, each link group has two interfaces, and the failure condition of the link group is all. Suppose we have only one entry in the Link group. If the link monitoring has a failure condition of any and Link group has a group failure condition of all, then all is preferred, because whatever's configured in the Link group takes precedence. ![]() ![]() This document provides information about link and path monitoring behaviour.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |