Error Importing ISY file to Elk

[upstatemike]

When I try to import my ISY file to my Elk M1 I get an error with no information. (It just says "Perhaps this is not a valid ISY export file?") So how do I troubleshoot this? Is there something I can check in the file to make sure it is valid? Is there a troubleshooting guide someplace?

 

Elk firmware is 5.1.8

ISY firmware is 2.6.4

[Michel Kohanim]

Hello upstatemike,

 

Please try using http://www.universal-devices.com/99i to generate/export your ELK file. For your reference, this is a known bug which has been fixed in 2.6.6.

 

With kind regards,

Michel

 

When I try to import my ISY file to my Elk M1 I get an error with no information. (It just says "Perhaps this is not a valid ISY export file?") So how do I troubleshoot this? Is there something I can check in the file to make sure it is valid? Is there a troubleshooting guide someplace?

 

Elk firmware is 5.1.8

ISY firmware is 2.6.4

[upstatemike]

I tried it but I get the same error when I try to generate the file. Elk console works fine and I can arm and disarm with no problem.

 

Just to confirm when I create the file.... I am using the non-secure port 2101 and in the "Security Code" field I am entering the "user code" NOT the "programmer code" or "RP Access Code". (Maybe "Security Code" shoud be changed to match the Elk terminology?)

 

What else can I try?

[Michel Kohanim]

Hello upstatemike,

 

I apologize for the inconvenience. I am not certain if 2.6.4 had this bug but before suggesting upgrade to 2.6.6 (which is going to break your IES touchpanel), may I humbly suggest clearing your Java cache and retrying?

 

With kind regards,

Michel

I tried it but I get the same error when I try to generate the file. Elk console works fine and I can arm and disarm with no problem.

 

Just to confirm when I create the file.... I am using the non-secure port 2101 and in the "Security Code" field I am entering the "user code" NOT the "programmer code" or "RP Access Code". (Maybe "Security Code" shoud be changed to match the Elk terminology?)

 

What else can I try?

[upstatemike]

No, clearing the cache didn't help. Could it be that I am using the wrong security code? Should it maybe be the RP Access code?

 

Or is it something simple like some names that are too long?

 

Or maybe just a bad XML tag? Is there something I could look for and just edit the file manually?

[Michel Kohanim]

Hello again upstatemike,

 

Do you have any &, in your names? If so, that might be the cause but I am afraid it's the bug in 2.6.4.

 

With kind regards,

Michel

No, clearing the cache didn't help. Could it be that I am using the wrong security code? Should it maybe be the RP Access code?

 

Or is it something simple like some names that are too long?

 

Or maybe just a bad XML tag? Is there something I could look for and just edit the file manually?

[upstatemike]

No, no funny characters in the names. I guess I am stuck until IES is ready and I can move up to 2.6.6

[Michel Kohanim]

Hello upstatemike,

 

I do apologize for the inconvenience ... of course, there's one more option: you could send your exported file to ELK as they are pretty good at telling you where the problem is. When you find the problem, you can forward the file to support@univesal-devices.com and will fix it and send it back to you.

 

 

With kind regards,

Michel

 

No, no funny characters in the names. I guess I am stuck until IES is ready and I can move up to 2.6.6

[upstatemike]

I will look at doing that if I get some more time but I pretty much burned up my window for this project. I'll probably just wait until Labor Day when I will have 3 full days to configure the Elk connectivity, IES touchscreen upgrade, NK8, and ISY firmware 2.6.6 upgrade all at once.

 

Hello upstatemike,

 

I do apologize for the inconvenience ... of course, there's one more option: you could send your exported file to ELK as they are pretty good at telling you where the problem is. When you find the problem, you can forward the file to support@univesal-devices.com and will fix it and send it back to you.

 

 

With kind regards,

Michel

[Michel Kohanim]

Hi upstatemike,

 

I am so very sorry for the inconvenience ...

 

With kind regards,

Michel

 

I will look at doing that if I get some more time but I pretty much burned up my window for this project. I'll probably just wait until Labor Day when I will have 3 full days to configure the Elk connectivity, IES touchscreen upgrade, NK8, and ISY firmware 2.6.6 upgrade all at once.

 

Hello upstatemike,

 

I do apologize for the inconvenience ... of course, there's one more option: you could send your exported file to ELK as they are pretty good at telling you where the problem is. When you find the problem, you can forward the file to support@univesal-devices.com and will fix it and send it back to you.

 

 

With kind regards,

Michel