Any reason M1XEP would go hinky?

[will40]

I've found that the XEP locks up whenever I attempt to access it directly. It is able to communicate with Homeseer via the UltraM1 Plugin just fine, but then when I try to access the Elk directly through it from a remote location, it initially displays the virtual keypad, but often without complete info (example: it doesn't show the armed status, or the thermostat status, although it does show the temperatures at the keypads). Then it loses its connection with Homeseer, and I can't log back into the Elk. The login screen comes up, then the blue screen that asks for my code (prior to virtual keypad, but when I enter my code I get a busy / unavailable message. Restarting homeseer, reloading the page, etc., etc. have no effect. The XEP has to be restarted, and at least yesterday, the Elk had to be shut down and restarted as well. Will check it again in a few hours when I return home, and report any findings that might be potentially useful.

Joe

And I was just going to post the question of why I cannot login to the XEP VK anymore. I can usually get by the password blue screen and then it just hangs. Once or twice I can see the virtual keypad but no active buttons or status display. Majority of the time an hour glass (no busy/retry message).

I have tried disconnecting UltraM1 plugin and that does not help.

This sounds like the same issue that is ailing you...?

 

[Madcodger]

I've found that the XEP locks up whenever I attempt to access it directly. It is able to communicate with Homeseer via the UltraM1 Plugin just fine, but then when I try to access the Elk directly through it from a remote location, it initially displays the virtual keypad, but often without complete info (example: it doesn't show the armed status, or the thermostat status, although it does show the temperatures at the keypads). Then it loses its connection with Homeseer, and I can't log back into the Elk. The login screen comes up, then the blue screen that asks for my code (prior to virtual keypad, but when I enter my code I get a busy / unavailable message. Restarting homeseer, reloading the page, etc., etc. have no effect. The XEP has to be restarted, and at least yesterday, the Elk had to be shut down and restarted as well. Will check it again in a few hours when I return home, and report any findings that might be potentially useful.

Joe

And I was just going to post the question of why I cannot login to the XEP VK anymore. I can usually get by the password blue screen and then it just hangs. Once or twice I can see the virtual keypad but no active buttons or status display. Majority of the time an hour glass (no busy/retry message).

I have tried disconnecting UltraM1 plugin and that does not help.

This sounds like the same issue that is ailing you...?

Yes, sounds very similar. Suggestion to try:

Unplug the XEP, then turn off the Elk main switch on the panel for about 30 seconds. While it's down, shut down the plugin on homeseer using the interface page (don't forget to hit "save"). Then, restart the elk and plug the XEP back in. Wait maybe 3 - 5 minutes (the XEP takes a while to reboot, I've found) and then see if you can log in to the elk via the XEP, directly.

If so, it seems like the same issue. You can then restart the plugin in homeseer.

 

[Madcodger]

FYI:
The future is VERY BRIGHT!!!


For now you could build an external watchdog with Rules:

WHENEVER EVERY 5 Minutes
AND ETHERNET TROUBLE EXISTS
THEN TURNON OUTPUT X FOR 5 Seconds

Break the power going to the XEP through the relay output X using the normally closed set of contacts on the relay.

Every 5 minutes the M1 will check for any problems in the M1XEP and cause a power cycle of the M1XEP if a problem is detected.

There is a watchdog built into the M1XEP that performs automatic power cycling if the watchdog circuit detects a problem.

I had a problem with my routers locking up during the day, so now I power cycle my routers also. I built a TASK for the power cycling and can access it through the telephone should my routers lock up.

Spanky,

Is there any way to automatically power down and then restart the M1 itself? Restarting the XEP alone doesn't fix it...

Joe

 

[RobWalker]

I've found that the XEP locks up whenever I attempt to access it directly. It is able to communicate with Homeseer via the UltraM1 Plugin just fine, but then when I try to access the Elk directly through it from a remote location, it initially displays the virtual keypad, but often without complete info (example: it doesn't show the armed status, or the thermostat status, although it does show the temperatures at the keypads). Then it loses its connection with Homeseer, and I can't log back into the Elk. The login screen comes up, then the blue screen that asks for my code (prior to virtual keypad, but when I enter my code I get a busy / unavailable message. Restarting homeseer, reloading the page, etc., etc. have no effect. The XEP has to be restarted, and at least yesterday, the Elk had to be shut down and restarted as well. Will check it again in a few hours when I return home, and report any findings that might be potentially useful.

Joe

And I was just going to post the question of why I cannot login to the XEP VK anymore. I can usually get by the password blue screen and then it just hangs. Once or twice I can see the virtual keypad but no active buttons or status display. Majority of the time an hour glass (no busy/retry message).

I have tried disconnecting UltraM1 plugin and that does not help.

This sounds like the same issue that is ailing you...?

I have the same issue -- I have never been able to get the VK to work. Sometimes it will accept the code, sometimes it gets hung up at that point.

I find the ElkRP software keeps dropping the connection too. Today was particularly bad -- the connection would last about 30 seconds until I get an error message. I have the XEP plugged into a netgear wireless router and am connecting to it from a laptop over a wireless connection. However, I don't have any other networking problems either accessing machines local to the network, or going out onto the internet.

The XEP is running the latest firmware. If there is a simple fix then I'd love to hear it -- or even some way of getting more diagnosis of the error.

 

[lugnut]

I have some problem with the Virtual Keypad also.

From the same laptop, I can access the VK and it works fine when I'm on the local network, but when I try from an external address, I get the username/password login and it accepts, then it goes to the Sun Java screen, then it shows the blue "Establishing Secure Connection" screen, but then it always craps out and comes up with the message:
"Cannot connect. Another device may be connected already." But I do not have ElkRP connected to the control.

It never gets to the "Enter user code" screen.

Also, on the internal network when I use the VK, I get the warning about the invalid digital signature, but I don't get that pop up when I try to access externally. Not sure if that gives any clues.

I assume if you get the login screen and it accepts the password, all the necessary ports are open ?
I'm at a loss for what else to try.

 

[ultrajones]

I also experienced issues with the Java based vitual keypad application. This application caused my Elk M1EXP to lock up on a fairly regular basis. I don't use it any more and have not experienced a lockup in over a year with heavy usage from HomeSeer and the UltraM1G plug-in.

Regards,
Ultrajones

 

[Madcodger]

I think I'll access through HS only until they get this resolved. Only problem is that if HS goes down, I'm stuck. Was hoping to use the Elk as a way to reboot things (my back door).

 

[Photon]

Lugnut described what I see when I try to access the demo on the Elk site from my office. I assumed there was always someone else accessing the demo, but perhaps not.

Is this the result of a firmware "upgrade?" I don't recall reading about this issue until recently. I hope it is resolved soon since I plan to place my Elk Phase One order in just a few weeks. If I do that, y'all can look forward to Elk releasing the M1-Platinum in mid-February.

 

[Spanky]

From the M1XEP Guru:

If you can connect with a web browser from one PC and not another, chances are it's an issue with either Java or SSL on the one PC - especially if you can't connect to the elk demo at http://m1demo.elkproducts.com

To get to the bottom of this issue, it would be helpful if anyone experiencing this problem could do the following:
1) Use ElkRP to make sure the non-secure port (2101) is enabled. Receive or Send M1XEP setup to verify.
2) Start HyperTerminal and connect to the M1XEP on port 2101. Enable HyperTerminal to log to a disk file. Leave it running (24/7) until the lockup occurs. Send the log file to Elk Technical Support, and indicate the date/time the lock up appeared to occur. If the log file is over 2 Mbytes, you may ZIP it or break it into smaller chunks.
3) After accessing the Virtual Keypad, try again every 15 minutes or so a few more times to see if it seems to happen after a VK session ends. Do the same after disconnecting with ElkRP.
4) Although some have said an M1 reboot is necessary, first try rebooting the M1XEP alone. Then reboot both if still needed. Let Elk Tech Support know which was needed.
5) As all installations are unique (some using HomeSeer, CQC, HomeLobby, etc, others none of the above, some with Elk-TS07s, some without), any experiment you can try by disabling any of these is helpful.
6) Finally, try to remember what you last did before the lockup occurred - whether seconds or days before.

Your feedback regarding the above will be very helpful and will be treated confidentially.

[email protected]

 

[will40]

Yes, sounds very similar. Suggestion to try:

Unplug the XEP, then turn off the Elk main switch on the panel for about 30 seconds. While it's down, shut down the plugin on homeseer using the interface page (don't forget to hit "save"). Then, restart the elk and plug the XEP back in. Wait maybe 3 - 5 minutes (the XEP takes a while to reboot, I've found) and then see if you can log in to the elk via the XEP, directly.

If so, it seems like the same issue. You can then restart the plugin in homeseer.

Ok...just tried it in that order. Waited 10 minutes or so after powering up XEP before I tried to log in. Same issue as before.

I get by the code screen two out of three times I can see the keypad, but no active buttons, just my hourglass and just hangs for 10 minutes.

Spanky - I captured hyperterminal session the three times I tried it. You want it emailed to you?

Thanks.

 

[Madcodger]

From the M1XEP Guru:

If you can connect with a web browser from one PC and not another, chances are it's an issue with either Java or SSL on the one PC - especially if you can't connect to the elk demo at http://m1demo.elkproducts.com

[email protected]

Spanky, et al -

Sorry, have been sick the last week with something like the flu, so couldn't pay much attention to this. I can access the Elk demo on the site above just fine, but is there a code we can enter to see if we can go forward? I can get to that point just fine...

As for trying an XEP reboot alone, sorry - I tried several times before falling ill, and in each case had to reboot the Elk itself to get back up and running. Does anyone know of a way to automate that?

Will try the steps Spanky suggested, with hyperterminal, etc., later this week. Beginning to suspect this is only going to happen when I have the UltraM1 plugin (and perhaps the ElkM1 plugin) also connected to the XEP. They may be jealous plugins that will not allow simultaneous access of the XEP, but we'll soon see.

Joe

 

[Spanky]

From the M1XEP Guru:

A fellow Cocooner discovered that blank zone names can cause the Java Application to “hang” after entering the user code. Until this can be fixed in the M1XEP, a work-around is to use ElkRP to make sure all zone names – even those that are disabled – have a non-blank name with no leading or trailing spaces. As a precaution, you should similarly check all area and keypad names as well.

 

[lugnut]

From the M1XEP Guru:

A fellow Cocooner discovered that blank zone names can cause the Java Application to “hang” after entering the user code. Until this can be fixed in the M1XEP, a work-around is to use ElkRP to make sure all zone names – even those that are disabled – have a non-blank name with no leading or trailing spaces. As a precaution, you should similarly check all area and keypad names as well.

Are you referring to only the case of accessing from outside the local network?

In any case, I still am not able to get past the dark blue secure screen in the virtual keypad (when accessing from outside the local network) and I got this same result on 2 different computers.
Inside the local network it works OK though.
(I don't have any blank zone, area, or keypad names)

 

[Spanky]

From the M1XEP Guru:

A fellow Cocooner discovered that blank zone names can cause the Java Application to “hang” after entering the user code. Until this can be fixed in the M1XEP, a work-around is to use ElkRP to make sure all zone names – even those that are disabled – have a non-blank name with no leading or trailing spaces. As a precaution, you should similarly check all area and keypad names as well.

Are you referring to only the case of accessing from outside the local network?

In any case, I still am not able to get past the dark blue secure screen in the virtual keypad (when accessing from outside the local network) and I got this same result on 2 different computers.
Inside the local network it works OK though.
(I don't have any blank zone, area, or keypad names)

Lugnut (Love the name)

You need port 2601 open through your router and modems for outside access. Port 2601 is used by the Virtual Keypad to establish a secure connection.

Have you tried accessing the M1 with ELKRP from the outside world using the secure port 2601?

 

[lugnut]

You need port 2601 open through your router and modems for outside access. Port 2601 is used by the Virtual Keypad to establish a secure connection.

Have you tried accessing the M1 with ELKRP from the outside world using the secure port 2601?

Yes (or I think so anyway). From the "Forwarding" tab of my Linksys router setup screen I set it to forward 2601 to the XEP's 192.168.1.x address.
Would I still be able to login remotely if that part wasn't working (I assume the password is not transmitted in the clear)?