Jump to content

ELK / ISY not talking


bigDvette

Recommended Posts

Ok,

 

I can talk to the elk using ElkRP2 and I can use the web based keyboard.

 

When I go to the ISY and put in the IP address and 2101 for port, I never see any of the arming buttons along the top.

 

If I put in port 2601, I see the buttons flash on for a second and go away. This happens whether I put in the password or not under the port field.

 

IN all cases I save the changes and I am running :

 

Elk - boot version 3.3.6

- firmware version 5.2.2

ISY - firmware 2.8.10

 

I'm not sure how else to debug.

 

I have exported and imported the lights successfully and I can see them in the web keyboard for the Elk.

Link to comment
Share on other sites

It does continue to crash and I believe it is related to when I go in to any other utility, the XEP web interface or my Home Automation controller which also utilize the non-secure port. I don't think the ISY should crash as a result, but I'm kind of guessing that does it. I'm doing a lot of programming right now of the ELK and maybe that is causing it to crash.

 

I can force it to crash by going in and out of ElkRP2 a few times. If you have an Elk maybe you can test that configuration. I'm considering removing the ELk from ISY since I don't plan to control the lights from ELK and you can't get any elk arming status info to use in rules.

Link to comment
Share on other sites

Michael, try taking over the ELK using RP. You will need to connect and disconnect a few times using the connection button in RP. it may be a timeing issue with a query from ISY going to the ELK while it isn't accepting requests.

 

I'll see if I can reproduce reliably on my side.

Link to comment
Share on other sites

  • 2 weeks later...

I observed a similar issue where the ISY would crash if it lost connection to the XEP. In my case, I can connect/disconnect without any problem, but if I reconfigure the XEP (which forces it to reboot) almost every time the ISY is locked up. Here is my sequence:

 

1. Launch Elk RP2

2. Connect to the M1 through the XEP

3. Click on XEP Setup

4. Click Reboot (acknowledge that M1 will be disconnected)

5. Close the XEP Setup Window

6. After a couple of minutes when the XEP finishes rebooting, connect again in RP2.

7. Disconnect in RP2 and exit the RP2 app.

8. Browse to the IP of the ISY. In my case, whenever I do this I will find that the ISY has crashed and I have to reboot.

 

ISY Version 2.7.15

 

M1G Boot Version - 3.3.6

M1G Firmware - 4.6.2

M1XEP Boot Version - 1.2.0

M1XEP Firmware - 1.3.24

ElkRP2 2.0.8

Link to comment
Share on other sites

I've just added an ELK M1G / M1XEP and can confirm the same situation.

 

My ISY has not "locked up" until adding the above equipment; now I've had it happen many times in just a few days.

 

Please advise on a possible time frame to fix this issue!

 

Thanks!

Link to comment
Share on other sites

Hello telljcl,

 

I want to make sure we are talking about the same issue: currently when you connect via ELK RP, AND IF, your ISY is connected, then it MIGHT crash. This should not happen if you are NOT using ELK RP of you disconnect ISY from ELK before connecting ELK RP.

 

With kind regards,

Michel

Link to comment
Share on other sites

Hello telljcl,

 

I want to make sure we are talking about the same issue: currently when you connect via ELK RP, AND IF, your ISY is connected, then it MIGHT crash. This should not happen if you are NOT using ELK RP of you disconnect ISY from ELK before connecting ELK RP.

 

With kind regards,

Michel

 

I have confirmed exactly that. All works fine until EXP reboots then isy crashes. So I have an alternative, unplug power to isy anytime you need to send or reboot your EXP. Wait a couple of minutes and all is well. Not a big deal here, seems like it might have to do with the EXP and not the isy? But Im just a novice.

 

Hope this helps

Mike Bell

Link to comment
Share on other sites

  • 1 month later...
Hi John,

 

Thanks so very much. We can reproduce it as well ... hopefully we'll fix it in the next beta cycle.

 

With kind regards,

Michel

 

Hi Michel,

 

Is this issue addressed in the Beta 3.1.0 that was just released? I had planned on updating this weekend, but thought that I would check with you first.

 

Thanks...

Link to comment
Share on other sites

Michel,

 

I submitted a support ticket and your response was to disable Elk integration. I did that and it seems to stay up. After reading this thread, I re-enabled the integration and will continue to watch.

 

Is this is issue you are working on with Elk the reason you asked me to remove my configuration or is it something else?

 

Thanks, Morris

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.


×
×
  • Create New...