Techman

It's also possible some of the links in the KPL are corrupted. Try doing a restore device on the KPL to see if that corrects the problem. You can also try doing a restore device on the devices in your scene(s).

Another option is to set a variable in the first program at the same time the MS is triggered, and then have the second program run when the variable is set. Once the 2nd program completes you can have it set the variable back to 0.

What type of device is "Front House Security-S", and once it's turned on does it stay on? Every time a parameter in the IF statement changes the THEN clause will start over.

The green light on the IOlinc should be on when t he door is open.

You want your contacts to be open (N/C) when the magnet and switch are in close proximity to each other When the garage door opens the contacts will then close and the sensor light on the IOLinc will light. This is the opposite of standard alarm wiring which triggers when the circuit is broken, i.e. a wire is cut or a door is opened. In short, the ISY works best with a N/C wired switch.

Just received a PLM directly from Smarthome. Date is 4616, version is 2.3

This is the program I use which runs when the ISY boots Create a custom email named "System Re-Start". which the attached program calls up. The 1 minute delay is to allow for the ISY to reboot. (The email will have the time and date it was sent). System Re-Boot Notify email If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Wait 1 minute Send Notification to 'ISY Message Home' content 'System Re-Start' Else - No Actions - (To add one, press 'Action')

It is supposed to work with the ISY 5.xx firmware which is still in alpha testing.

Yes, but if the connected load is connected to the dimmer and it's a device that's not/shouldn't be dimmed then it could be a problem

You're pairing a dimmer switch with a on/off switch which could be problematic depending on the type of load.. What switch is your load connected to? What type of load is it?

Glad to hear you got it all resolved.

Try removing power from both the ISY and the PLM, then power up the PLM, wait 10 seconds then power up the ISY About how many devices do you have? What's the date code and version of your PLM Do a PLM link count and let me know what the result is. Which ISY are you using, what is the firmware and UI versions?

The ISY configuration file with the font size is saved in the windows temporary file. When the temp file is cleared out you lose some of the ISY's configuration settings including the font size. If you open the admin console via the java app then there's no option to adjust the "browser font size" same if you open it via a direct call from a browser window.

The ISY doesn't know the status of the X10 devices as they don't report back to the ISY. If you manually turn a X10 switch on or off, or control them from another controller, then the ISY isn't aware of its current state.

run a "scene test" on the scene you're having a problem with by right clicking on the scene name. This will give you a diagnostic report that can help narrow down the issue. Copy and paste the report in a post

Seems there are a lot of users that have problems that could be easily resolved by doing a restore backup on the ISY yet they don't have a viable backup. Good programming practice is to back up your ISY configuration anytime you make changes. It only takes a few minutes to backup and will save you hours or days of having to start from scratch should something go awry.

When you restore wireless devices be sure to have only one wireless device in the linking mode at any one time otherwise the devices can get cross linked.. Once that device is out of linking you can then link the next wireless device. If you have the ISY pro be sure to uncheck the "automatic writes to wireless devices" before you do a restore PLM. The PLM link count can vary somewhat depending on the ISY's activity. A zero count is not normal. Either your previous restore failed, or the PLM is failing. Sounds like a good idea to have a spare close by.

If you're seeing the "Safe mode" message then that means that there's a communication problem between the ISY and the PLM. First Check your cable connection between the PLM and ISY. Remove power from both the ISY and the PLM, then power up the PLM and then the ISY (in that order) Do a PLM link count. If the count seems low then try doing a restore PLM If the above doesn't resolve the problems then you may have a defective PLM

Make sure only one battery operated device is in the linking mode at any one time. it's a bit of a pain but that's the only way to link those device to the new PLM

The 2844-222 is not supported in the ISY 4.5.x firmware. However it will be supported in the 5.x firmware which is still in alpha testing, so it will be sometime before you're able to use the sensor.

To uninstall the Admin Console go into your Java settings and delete your java cache including applications. This will delete the admin console. Then go to the admin console download page http://forum.universal-devices.com/topic/19961-release-454-is-now-official/ and reinstall the admin console app

What are you using for a firewall What (did you) changed since it last worked?

Is the First Alert model you have a "ONELINK" model? The smoke bridge works with the SC0501CN-3ST and the SA521CN-3ST

No, you have to update each one individually When you update the UI you first must delete both your Java cache and all java applications before downloading the UI. Be sure to do a ISY backup before any ISY firmware update

The ISY firmware and the UI should always be the same version. It's best to upgrade your firmware to 4.5.4