LeeG

My security sirens are powered from 12V DC. They have a wail and solid tone function built in so all that necessary is to supply 12VDC. The Insteon 2450 I/O Linc relay has a 5A @ 30V capacity which is more than enough to switch 12V to a siren. To that list is a 12V DC power supply. There are wall warts that will handle that. I expect Radio Shack will have a small 12V DC power supply. The ISY would turn On the I/O Linc Relay (defined for latching mode) which will sound the siren until the I/O Linc relay is turned Off perhaps with an ISY Program so that the siren does not run for hours if no one is home.

I'm not familiar with a "Smartlinc 4 button keypad" (maybe a 4 Scene RemoteLinc2?). What is the device number (2444A2WH4 ?)? What are the specific KeypadLinc buttons that have been lost? (ON/OFF, A,B C,D)? When one of the lost buttons is pressed On/Off does the Admin Console show a state change in the Current State column for the KeypadLinc button node? It sounds like perhaps Set button links have been done outside of the ISY and were overlaid/erased when the ISY Scenes were defined. Have Set button links been created? What were the lost buttons controlling? Another Insteon device where the links were defined with an ISY Scene, another Insteon device where Set button links were used to link the other device, or perhaps ISY Programs are no longer being triggered. The solution could be a Restore Device for the KeypadLinc. Really need the detail of what is no longer happening and why before a specific solution can be identified.

dansmith The email problem is fixed in beta 3.2.0 which was released today. There are special URLs for accessing the Admin Console for 3.2.0 beyond the normal special URLs for accessing a beta Admin Console. There is a glitch in the area of Programs in the initial 3.2.0 Admin Console which UDI has fixed. The Admin Console containing the Program fix must be pulled from the UDI web site. There is a post in the 3.2.0 Available topic that lists the two URLs. This will be fixed in another beta drop Monday at the latest (also described in the same forum post from Michel). viewtopic.php?f=25&t=8320&start=15 about the 6th post on page 2 of this topic is the post from Michel containing the special URLs for accessing the 3.2.0 Admin Console fix.

A Motion On is always used as the event perhaps because a Motion Sensor can operate in On Only mode. When updates are pending and a Motion On is received a command is sent to the Motion Sensor to keep it from going to sleep. This must be done quickly to prevent the MS from going to sleep in the normal fashion. Don't remember the command code right off but I'm sure I've got that information somewhere. After that the pending updates are written just as though the MS was put into linking mode manually, When the updates are complete another command is issued to allow the MS to go back to sleep. Really pretty simple but the initial command to keep the MS awake has to be done quickly. Also if the ending command to allow the MS to sleep is missed the MS battery will drain quickly. I wrote a Powerhome macro that configures the Motion Sensor options when a Motion On triggers the macro. It takes two motion on messages, the first allows the current options to be retrieved and the second motion on is used to write any changes back. I did it initially as a proof of concept. The macro is not very sophisticated but it does allow the MS options to be retrieved and changed without pulling the MS off the wall. I'll look around for the two commands that are used for sleep management. They are not in my very old out dated Insteon command reference. EDIT: actually the sleep management commands are not necessary if the commands to the MS are done quickly. So long as the MS is receiving commands it will not sleep. The sleep management commands eliminates the problem if the system is held up sending commands for some reason.

Installed 3.2.0 successfully on house system. Have no Program issues here either but not many Programs here either. Cleared the Java cache and Help | About shows correct information. Access this system with 192.168.2.6 Have tested the Master Bathroom Motion Sensor Programs. They are working fine.

Installed 3.2.0 successfully. Have no Program issues but not many Programs on the test bed system. Cleared the Java cache and Help | About shows correct information. I use 192.168.2.2 to access test bed system. Successfully added an I2CS Motion Sensor using New INSTEON Device and specifying Device Type Motion Sensor. Successfully added an I2CS FanLinc using New INSTEON Device with Auto Discovery.

Have you looked at the Programs | Summary tab, Last Run Time, Status columns? What do they indiczte? Can you post the Program.

ELA I hope the "Update With Motion On" will eventually be implemented in the ISY but not today. It is such a well received function in HL. The original HL implementation was poor because it tried to do more than simply write updates. When HL withdrew the function because of the poor implementation lots of folks were unhappy. They put the function back with a good design this time.

Do a Tools | Diagnostics | Show PLM Links Table. It is very unlikely to have lost the link database in all the individual Insteon devices but it is possible to lose the links in the PLM. A File | Restore Modem (PLM) is the corrective action. If Insteon device to Insteon device is not working an Access Point could have been lost or locked up, Unplug the Access Points and then run the 4 tap Set button test to insure coupling is working.

vbsafire1 Check the ISY Admin Console for the same device. If the Lamp shows the wrong status in the Admin Console that indicates a powerline comm problem where the ISY did not receive a change in status message. If the Admin Console is correct and MobiLinc does not have the correct status perhaps MobiLinc lost connectivity to the ISY so it did not receive the status update message pushed out to all the clients.

As far as the RF devices are concerned just let the updates fail. Then put each into linking mode and select Write Updates to Device. Be sure to complete one before starting the next. Trying to put two RF devices into linking mode at the same time cancels out both.

How is the Motion Sensor being added? New INSTEON Device must be used and the Device Type pulldown must select Motion Sensor. Also the Motion Sensor must be put into linking mode using the Motion Sensor Set button. However, if this is a new Motion Sensor purchased in the last few weeks you will need to wait for the 3.2.0 Beta which has a tentative date of 3/16/2012. The newest Motion Sensors are I2CS devices which require 3.2.0. EDIT: the UDI Wiki has information on devices that are processed differently. RF devices tend to be a little different than wired devices. http://www.universal-devices.com/mwiki/ ... de#Devices

Yes. The 3.2.0 beta has a tentative availability of 3/16/2012. Once the Beta is installed the Motion Senosr must be Deleted and added back to the ISY under the Beta.

Xathros As with all Betas the announcement post that it is actually available (the above post says tentative 3/16/2012) will have a link to download the beta image.

From a programming perspective all PLMs look the same as far as the serial command set. USB PLMs are Serial PLMs with a USB to Serial converter built in. USB PLMs have a Comm Port number just like a Serial PLM. There is no difference in the application code whether talking to a Serial PLM or a USB PLM. The various PLMs support different numbers of link records but that should not matter here as links would not be in play. There is no issue with multiple PLMs on the powerline. I run with 4-6 external PLMs at any given time. Every wired Insteon device has a PLM internal to the device. There could be issues with the amount of Insteon traffic being generated. Insteon does allow multiple Scenes to run at the same time and Insteon traffic from other sources could have an adverse affect on what the ISY Programs are trying to accomplish. No difference then if someone is hitting the paddle on a SwitchLinc over and over. The ISY will not be aware of changes in status of the ApplianceLinc by the PC app but that should not be an issue with the ApplianceLinc being removed from the ISY device list.

Is the ApplianceLinc being managed by the ISY? There would be no difference between an Insteon switch sending commands to the ApplianceLinc and another PLM doing the same thing. The conflict will be if the ApplianceLinc is managed by the ISY and being manipulated without the ISY knowledge.

Yes.

I made no reference to any existing Scene. The question was how to get KeypadLinc button D On. To do that define a new ISY Scene, add KeypadLinc button D as a responder to the new ISY Scene. When KeypadLinc button D should be turned On turn On the new Scene. EDIT: " write a program that says if light1 or light2 or light3 is on, then illuminate button D on my keypadlinc?" to illumninate button D turn on the new ISY Scene that has button D as a responder.

Sure. The only trick is a Secondary KeypadLinc button LED cannot be controlled (On/Off) directly. KeypadLinc button D is assigned as a Responder in an ISY Scene. When any of the lights switches are On turn the Scene On which will turn button D On. Another Program can check that all the switches are Off and turn the Scene Off to turn button D Off.

An InLineLinc 2475SDB can be installed in the light fixture. I'm assuming there is no wall switch that controls power to the closet fixture. An RF TriggerLinc 2421 installed on the sliding closet door detects when the door is opened, turning On the InLineLinc, and turning Off the InLineLinc when the door is closed.

Every now and then the SD card becomes unseated during shipping and handling. Post again if needed. Thanks for the feedback.

bdw72 Remove the power from the ISY, pull and reseat the SD card. See if that changes the Status to Active.

vbsafire1 The Ramp Rate cannot be specified with the Insteon Direct device On command. The switch can be defined as a Responder in an ISY Scene. The responder Ramp Rate can be changed with an Adjust Scene Action statement. The Ramp Rate is stored in the responder device link database so it is not a value that should be changed on a whim but setting the Ramp Rate for day operation and a different value at night for example is fine. The next time the Scene is turned On/Off the new Ramp Rate will be in effect.

bclarke01 Try a Restore Modem (PLM) if all devices fail to show status changes. Sounds like the PLM link database was reset.

No. If the Sense line has been temporarily overridden with Fast On/Fast Off changes to the Sense line voltage have no affect on the SwitchLinc itself. The SwitchLinc will send On/Off commands from a manual paddle press.