Techman

I recently noticed that some devices located only within scenes would occasionally fail to either turn on or off. This problem was consistently inconsistent. When I did a compare link tables on the devices all looked normal. I even did a restore device(s) which didn't resolve the problem. However I noticed that when I ran a scene test on a problematic scene where all the link tables appeared correct I would always get at least one random device that would fail the scene test. The PLM was firmware v9E, Hardware version 2.0 and a date code of 1425, so the unit was about 3 years in service. I suspect that daughter board in the PLM which contains the RS232 circuit may be the culprit. I just replaced the PLM with one just obtained from Smarthome. The new PLM has a date code of 4616, v9E firmware and hardware revision 2.3. I didn't check to see what RS232 chip the new version has but was told last year that they were updating the RS232 components. After installing the new PLM the scene tests don't indicate any failures.

If you do a delete device then the ISY's links are deleted. A factory reset on a device only removes the links from the device itself, they still remain in the ISY and should be able to be restored to the device from the ISY using Restore Device as long as the device hasn't been physically deleted from the ISY. The ISY still retains the device address.

It's the 2342-222, 8 scene. I have several of them and am having the same problem with all of them. I tried doing a factory reset on one of them and am still unable to do a restore device. UPDATE: After the factory reset, and the failed restore device, I tried a write updates to device and that actually did a restore device even though there were no pending updates to be written to the device.

Firmware 4.5.4 Just tried to do a restore device to a remotelinc 2, 8 scene. After putting the device into linking mode and clicking on restore device nothing happened. I'm able to successfully see and compare the device's link tables which show a mismatch. Anyone else come across this issue?

The hidden door sensors have an option on how often you want it to send the heartbeat signal. change it to 12 or 24 hours. You'll need to put the device into linking mode in order to write the changes to the device

Check to see if there's an option on how often to send the heartbeat signal. If so, reduce it

Glad to hear it got resolved. The KPL's links can sometimes get corrupted. An easy way to check is to run a diagnostic | compare link tables, on a device. If a link mismatch shows up then do a restore device, that will correct the mismatch. Additionally, a power line surge or power fail can sometimes mess up the link tables in some devices.

Do your devices work locally, specifically Switchlincs and Lamplincs. Have you tried factory resetting the devices? You mentioned you tried different PLM's. Did you follow the correct PLM replacement procedure? Did you do a delete modem, if you didn't DON'T. Your PLM and/or Device link tables may be incorrect.

The "D" button on your keypad failed to respond. Try doing a scene test that involves one of the other KPL buttons to see if it succeeds. You can try doing a factory reset on the KPL then a restore device. It's possible that when it was converted from a 6 to 8 button the conversion got corrupted. After the factory reset you may have to convert it back to a 8 button device before you do the restore. I corrected the above line - You'll need to covert it back to a 8 button device not a 6 button.

If you right click on the scene, there's an option to run a scene test which will give you a diagnostic display of all the devices in the scene. Copy and paste the test results in a post.

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