Your Control is Busy or Unavailable. So, WHY?

[Madcodger]

Well, this has happened before, but I can't find out how we solved it via a search, so I'll post again...

My M1G is able to communicate with Homeseer just fine via port 2101 using the UltraM1G plugin for Homeseer, but I can't access it directly, even with ports 21, 26, 2101 and 2601 all forwarded to the M1XEP's IP address. Port 80 is also forwarded there. This is true both inside and outside the network. I am a able to get to the login screen for the Virtual keypad, but when I enter my user code and click "connect", I get " Your control is busy or unavailable. Try again?". Trying again does nothing, of course...

Any idea what's going on here? I need to be able to see my Elk log to resolve a transmitter low battery issue, but can't get to it.

BTW, doesn't help to shut down HS and try, either.

Thanks,

Joe

 

[ultrajones]

Is this the thread you are looking for?

http://www.cocoontech.com/forums/index.php?showtopic=9232

 

[Madcodger]

Is this the thread you are looking for?

http://www.cocoontech.com/forums/index.php?showtopic=9232

Ultra,

Hello, and thanks.

I did find that thread (I was a contributor on it with a similar problem) but the fix isn't working. I thought we had arrived at some other "magic fix", but I may be wrong. I'm going to try powering down everything again and restarting to see if that helps. In the interim, I was able to track down my sensor issue manually (without the logs) so it's less of an immediate problem. Thanks for the help,

Joe

 

[icellama21]

Just out of curiosity, are you using a Mac? There is still an issue with the java interface when logging in from a Mac. Only solution I found is to turn off the username/pw so it goes right to the usercode screen. Solved the problem for me, no more "busy" errors. Must be something to do with the authentication mechanism.

 

[Madcodger]

Just out of curiosity, are you using a Mac? There is still an issue with the java interface when logging in from a Mac. Only solution I found is to turn off the username/pw so it goes right to the usercode screen. Solved the problem for me, no more "busy" errors. Must be something to do with the authentication mechanism.

Hmmm... Come to think of it, I think I have been trying to log in only from my Mac... Will try from another computer tomorrow and see if that helps. Thanks for letting me know about the Java interface with Mac problem. Is Elk working on it?

 

[icellama21]

Is Elk working on it?

I had an email thread going with brad(customer support) in Jan or Feb of 2008 and I passed on what I discovered. So far it is still an issue with the latest XEP firmware. Never heard much back.

The workaround is to turn off the username/password for login(set them blank in elkRP) and it works great. Still have the usercode entry for some security.

There is also another Mac issue with the XEP java server not displaying the outputs table correct on firefox or safari. It was mentioned in the release notes for the last revision as fixed, but still is an issue for me.