Techman

MFBra Take a look at this thread. This should resolve your backup problem http://forum.universal-devices.com/topic/19368-unable-to-backup-isy/

Do you have any ZWave devices? What version of the ISY firmware and UI are you running?

Are you backing up to your local harddrive? Try rebooting the ISY and your Computer then give it another fry.

The current official firmware release is 4.5.4 Click on HELP | ABOUT in your admin console and double check your firmware and UI version

Is your ISY firmware and UI the same version (4.5.4)? If not then delete your java cache, including all applications, and then download version 4.5.4 of the admin console.

The subject and body of the email notification must be populated otherwise the ISY won't send it out. That might be your problem.

Try rebooting the ISY by removing power then wait a few seconds and power it up. If the ISY does a query after the power up be sure to wait until it's completed before you try another backup When you backup does it show the backup location before you start the actual backup?

Hi Michel, I just tried a restore device on the 8 scene Remotelinc 2, the restore device completed and it now works as it should. I also experienced problems with several of my wireless thermostats and had to factory reset them. All this happened after a replace PLM. At the time of the PLM replacement I put each wireless device, one at a time, into linking mode and wrote the updates to the devices without any error messages Apparently there was some anomaly that came and went. Guess I'll just attribute it to Murphy's law. One possibility is that Norton Security erased my temp files, as it does on a regular basis, during the restore process and messed up the admin settings

No, but it's possible that there could have been a pending write and for some reason the icon didn't show.

Not sure if 2.3 is the final fix. We all hope so. It was a hardware revision so something got updated. As far as RMA on the PLM's, Smarthome has taken a responsible position when it comes to replacing defective PLMs. Give their customer service line a call.

The current hardware version for the PLM is 2.3 If there's no entries in your log for any of the devices that turned on then there's a good possibility that the ON signal originated in the PLM. I'm not sure what changed in the PLM between versions 2.2 and 2.3, but I know there was an issue with the RS232 daughter board interface in the PLM which has recently been updated along with some capacitors in the PLM power supply that were known to fail.

There's a good chance your ON event is due to a failing PLM How many motion sensors do you have? What ISY firmware are you running? What's the date code and version of your PLM?

This happened with the new PLM installed. The only issue was with the remotelinc 2. This was more an ISY issue as the restore device window wouldn't open for this device. I did several restore devices on swithclincs with no problems.

Just got off the phone with Smarthome. They're replacing the PLM under warranty even though its 3 years old. The new PLMs, hardware version 2.3, have beefed up capacitors and a new RS232 interface. They believe that these enhancements should rectify the PLM issues. They're open to suggestions as to new products and / or product enhancements. Just send them an email to CustomerService@Smarthome.com. I'm optimistic that the new management will take the company forward, however it could be awhile before we start to see results

So the question remains, why didn't the restore device work. The restore device window wouldn't even open

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.