I've had two odd problems occur, not related I don't think.  Last night I created a new state variable for use in a new program.  Everything proceeded as normal, program worked fine.

This morning I find that when I created the new state variable it actually overwrote an existing variable(21).  The new program still works correctly but programs that used variable 21 are of course now messed up.

I have an i3 4 button that works but the leds are always off.  I was going to do a restore but when I attempted this I got this error:

 

Unrelated of course but now I'm wondering if there is some kind of file corruption happening in my eisy.  Any thoughts on this?  Is there a way to check file integrity, like 'chkdisk'.

Thank you.

The thought I have is minor tear down and rebuild:

1. I'm guessing that 60:7A:97 is the Insteon id of the 4 button keypad? 
   • Delete it and re-add it
2. For the variable, I would create an additional new variable and update the programs to use it, save and retry. 

Thanks for the response,

I should have mentioned that I already fixed it doing exactly what you suggested before I posted.  My concern in reaching out to the group, is whether this might be an indication that there is some corruption going on in the file system.  I've been using UD products a long time and I've never had a variable overwrite another one when being created.  That's also my first restore failure due to a bad file.  Is there a way to check file system integrity on eisy?

I agree with you it's odd. They'll likely want logs from the time you perform recreates to the extent that's possible. 

If possible, do that, download the log files and submit a ticket with them and a link back here