This may sound a little convoluted but it should work. The problem is I don’t know how to relate the Dakota Alert frequency/zone value to the “code” that would have to be entered using the Utility. I follow the Set button linking technique described in the EZSnsRF doc which you must have already done for the motion sensor to turn on the Togglelinc. Use the Utility to display the link record(s) in the EZSnsRF to determine the Group number being used by the “Controller of” link record pointing to the Togglelinc. The relationship of the Dakota Alert frequency/zone to Group number was established during the Set button linking process.
Add the EZSnsRF device to EZSrve, selecting NO link be established when the device is added. Use EZSrve Scenes Management and define a Scene where the EZSnsRF device is the Controller and the Unit number is the Group number determined above by looking at the existing link between the EZSnsRF and the Togglelinc. Add the EZSrve as the responder for the new Scene.
Now define an EZSrve Macro….
Then device: the EZSnsRF device name
Unlabeled Input Field to the Right of Does ON: enter the Unit number
of the Scene you created with EZSnsRF as the controller.
When: Between Sunset and Sunrise
Then device: the device name of the Togglelinc
When the Dakota Alert motion sensor sends its code to EZSnsRF, EZSnsRF will send an ON command to EZSrve using the Unit number as the Group number. The EZSrve Macro should trigger as a result of this and turn on the Togglelinc, only between sunset and sunrise.
The Dakota Alert motion sensor will send its OFF message to EZSnsRF soon after motion is no longer detected. You need another EZSrve macro which triggers with a Does: OFF from EZSnsRF to turn off the Togglelinc. You can use the After Delaying: option to establish how long the Togglelinc will stay on after receiving the off message from the motion sensor.
When all that is working, use the Utility to delete the link that was originally established with the EZSnsRF Set button.