Teken

In case you the OEM power supply can't be found any DC transformer that outputs from 5 ~ 30 VDC is fine.

I believe most places indicate the command and control must reside in the hardware. So Stu may be correct the ISY Series Controller may not be considered native in command and control. Then again, I highly doubt any building inspector would know the difference if they walked into a room. Most of them would see the MS and call it good and I have never seen a inspector follow up and check to see if the lights actually operated on-off.

The API & Firmware are not the same when speaking about this topic. The firmware UDI states in that specific thread pertains to the ISY which contains the API commands to include the Alert Module. As you correctly noted there has been no mention in any forum thread that UDI has obtained the API for the newly released Insteon siren to include it the ISY firmware. Clear as mud?

Hello Jay, The following programs are examples I use in my home for various lighting fixtures and use case. Some of them do not have motion sensors attached / linked to them for obvious reasons. My reply is to simply offer you a general sense of how the code is crafted and the logic that follows. You may take any portion and use them to your use case. This program is to monitor a large LED tube ceiling light. Pressing the button will invoke 30 minute timer. If the switch is double tapped (Fast On) it will over ride the 30 minute timer and the light will remain on indefinitely until the user presses the off button. Ceiling 30 Min Timer - [iD 0024][Parent 00C0] If Control 'Ceiling Lights' is switched On And Control 'Ceiling Lights' is not switched Fast On Then Wait 30 minutes Set 'Ceiling Lights' Off Set Scene 'Ceiling Light' Off Else - No Actions - (To add one, press 'Action') This program monitors the laundry room and for obvious reasons I didn't want the lights to turn off while anyone was moving around. But the system is programmed to turn off the lights after 10 minutes of no motion. It should be noted the use of the *Control* function instead of the *Status* function as this determines how the MS will react when it senses motion. Laundry 10 Min Timer - [iD 002F][Parent 00C0] If Control 'Laundry Motion-Sensor' is switched On Then Set Scene 'Laundry Room' On Wait 10 minutes Set Scene 'Laundry Room' Off Else - No Actions - (To add one, press 'Action') This program is a variation of the same (laundry 10 min timer & reset countdown based on movement). This program basically says if the MS senses movement turn the lights on for 2 minutes than turn it off. If I happen to be in the office I don't want the blasted thing to keep turning off and leaving me in the dark. So all I need to do and (Any lay person) would expect is to tap the on paddle position. This will over ride the 2 minute timer and leave the lights on indefinitely until someone presses the off paddle. Office Over Ride Timer - [iD 02C7][Parent 00C0] If Control 'Office Motion Sensor-Sensor' is switched On And Program 'Office Manual' is False Then Set Scene 'Office Light' On Wait 2 minutes Set Scene 'Office Light' Off Else - No Actions - (To add one, press 'Action') This is the over ride program to the above office program. Office Manual - [iD 02D3][Parent 00C0] If Control 'Office Lights' is switched On And Control 'Office Lights' is not switched Off Then - No Actions - (To add one, press 'Action') Else - No Actions - (To add one, press 'Action') As you can see there is more than one way to skin a cat and based on your use case. Any of the above can be modified to suite your needs. But since your intention is the reverse of most peoples use its going to be easier.

Post 13 & 16 from both Michel and Chris allude to the fact they do have the API. But will not incorporate the Alert Module into the 4.XX branch. Regarding the Insteon Siren I don't pretend to know if the API is completely different or the same. No mention from the UDI team has indicated when this new module will be supported or where. If I was to guess it too will be included into the 5.XX branch as 4.XX will be deprecated moving forward.

B.S.G: So say we all . . .

OBerkc, Your like a freaking poet in dumbing things down to the masses . . .

Also keep in mind if its programmed correctly any movement will simply add more time. So if you define a safe interval of say three hours. Anytime movement is detected in that room it will simply reset the clock and start another 3 hour (ON) time. No movement from 7:00 AM to 5:00 PM turn the lights off. As a watch dog timer you can create another program that queries the conference room lights. Say you know for a fact no one is ever going to be there from 10:00 PM to 5:00 AM. The system will check and then turn the lights off to ensure no wasted energy etc. One important consideration is to create a program that allows a person to double / triple tap a designated remote or switch to turn off the program.

Larry, I'm going to steal that one from you!

Hello Jay, There are several things that can be done but before we even go there you need to define the real world use case of this room. 1. How long will people be in this room? 2. Will everyone be sitting and not moving? 3. Have you considered simply making a program that says turn on the lights for XX hours from X time to X time? Doing so will ensure the highest customer satisfaction. 4. One of the easiest approaches is to program the motion sensor to turn on the lights when ever it detects motion. But have a program to govern what happens from X - X time periods.

This is the most recent thread from both Michel and Chris: http://forum.universal-devices.com/topic/18440-help-is-required-insteon-alert-module-error/?hl=%2Balert+%2Bmodule

I don't recall which thread it was but Michel noted they will not include support for Alert Module in the 4.XX branch. As I understand it they believe there is only two more Alpha trials to go before 5.XX goes into Beta. It was stated 4.XX branch has come to the end and they really wanted to move forward with all the extra features of 5.XX. As always what that means in human (time) terms could be anyone's guess. As 5.XX has been going on for more than two years . . .

Some basic questions if you will: 1. What is the brand and model of this GDO? 2. What sort of sensor is in place for this GDO kit? 3. Have you completed the annual safety checks for the GDO? 4. Remove the I/O Linc and simulate a power failure - what happens to the GDO?

I've read this entire thread and I just have to shake my head . . .

Make sure you leave the remote in its default *toggle* mode and not OFF vs ON only modes. LOL . . .

LOL - I'm going back to my project now! [emoji38][emoji5][emoji851]

As I noted up above those are all great pros of the tag system. LOL - I thought your comment was directed toward me! Use the quote feature damn it! [emoji35][emoji13]

I'm not sure that would be the apt phrase I would use vs short term gain. Over long term investment with almost zero out of pocket expense using a 1 wire system after a properly executed install. [emoji851]

First as a proof of concept - next to reduce cooling costs due to thermal heat soaking. It had nothing to do with electronics in the attic this is all driven by my goal of reaching a NET Zero Passive Hause state. [emoji4] Regardless of how much active / passive cooling is in a attic you can't fight thermal dynamics and Mother Nature.

Oh I follow kind of like jack of all trades master of none. [emoji12] ultimately the choice is the OP's and anyone who understands no one uses these tags in any serious industry vs 1 wire. That is a fact . . . [emoji15]

I don't follow what you mean about the use of a attic fan. [emoji848]

You're just grasping at straws here . . . [emoji58] In your mind what exactly are the basic differences if not to measure environmentals?!? [emoji53]

Are you saying monitoring the temperature isn't the same function?!? [emoji37]

LOL . . . Oh Scotty . . .

Dallas 1 Wire DS18B20 sensors . . . Where do you get $1200 from?!?!