| Author |
|
nerdboytodd
Newbie
Joined: January 19 2011
Location: United States
Online Status: Offline
Posts: 11
|
| Posted: January 06 2012 at 17:43 | IP Logged
|
|
|
Just today I started noticing that my PH box wasn't responding to events from my Elk M1 Gold, so I took a look at the log and found this message:
"System Message The Elk M1 ELKM1GOLD Zone Status Request did not return properly. Commands will not be transmitted."
I have had this setup working (with the Elk M1 Gold connecting via Ethernet to the PH over the unsecure port (2101)) for around a year now with no issues. I've rebooted the PH system, I rebooted the Elk XEP, I rebooted the M1 Gold itself. To no avail. I didn't change anything today, so no reason why it should stop communicating now.
Any thoughts? A few forum searches have turned up very little (I've checked to ensure the unsecure port on the M1Gold is turned on.
TIA,
NerdboyTodd
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: January 07 2012 at 15:44 | IP Logged
|
|
|
Todd,
I took a look at the source code and the Zone Status
Request is the first function PowerHome performs during
its connect phase after the socket is successfully
connecting. So it looks as if the connection to port
2101 is happening ok, PowerHome sends the zone status
request, and the data is either not being returned within
the time allowed or the returned data is not properly
formatted.
Have you tried connecting to the Elk via the Elk RP
program and verified the system has no problems?
Assuming nothing has changed on the PC side and there
isnt any firewall or similar software blocking 2101, it
would appear to be something hardware wise with the Elk.
Once you with ElkRP, can you give me the firmware version
loaded in both your Elk-M1 and the XEP? I can try to
load the same version in my system and see if perhaps
something is different there.
Let me know,
Dave.
|
| Back to Top |
|
| |
nerdboytodd
Newbie
Joined: January 19 2011
Location: United States
Online Status: Offline
Posts: 11
|
| Posted: January 09 2012 at 11:18 | IP Logged
|
|
|
Thanks for the reply back, Dave. I have checked both from the PH side and the Elk side. I have accessed the Elk M1 Gold with my ElkRP software (v2.0.6) with no issues. I also used my ElkRMS remote access software to access the M1 via the XEP and had no problem accessing those resources, so it looks like the XEP is at least mostly functional. Again it's strange as there were no changes made to firmware/software on either side of this equation.
The Elk M1 Gold Boot Ver is 3.3.6 and Firmware Ver is 5.2.2.
The M1XEP Boot Ver is 1.2.0 and Firmware Ver is 1.3.10.
Thanks for your efforts in helping troubleshoot this! Love your work!
NerdboyTodd
Edited by nerdboytodd - January 09 2012 at 11:18
|
| Back to Top |
|
| |
nerdboytodd
Newbie
Joined: January 19 2011
Location: United States
Online Status: Offline
Posts: 11
|
| Posted: January 09 2012 at 15:46 | IP Logged
|
|
|
Update:
After posting the current revs of code I was running on the Elk M1 Gold. I went out to their site to see what the latest and greatest was. So in an effort to make sure I was at the latest and greatest I updated the M1 Gold to Firmware Ver 5.2.8 and the M1XEP to Firmware Ver 1.3.28.
The net result was no change on the error message I was getting from the PH system.
On a lark, I was in the PH setup screen and listed my two controllers...the Insteon controller and the Elk controller. The Insteon being listed first (10) and the Elk 2nd (20). I decided to change the order by reducing the Elk to (5). Reinitialized and damn if that didn't work. Any idea why this would stop working and then why making this change would fix it?
Thanks,
NerdboyTodd
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: January 09 2012 at 21:37 | IP Logged
|
|
|
Todd,
Actually does make sense. I remember this happening to
someone else (may not have been Elk and Insteon but
another case where controller load order was an issue)
either on the board or through email.
What I suspect is happening is that the Elk is getting
timed out by an operation taking to long during Insteon
initialization. Insteon launches first, starts a timed
process, gives up control, the Elk launches, starts a
timed process, gives up control back to Insteon which
then starts a process that takes longer than it used to
and doesnt return control back to the Elk in a timely
fashion. After control is returned, the Elk process has
timed out and you get the error message. Changing the
order just switches the order of the processes and its
not an issue any more.
Probably some slight change in your Insteon network (new
devices, etc.) or possibly some communication issues (a
new computer power supply causing noise, etc.) and the
Insteon init process is taking a little longer than it
used to and the error started showing up.
Glad you happened upon this because I doubt I would have
thought to try that  .
Dave.
|
| Back to Top |
|
| |
Active Topics 
Memberlist 
Search 
Help
Register 
Login
PowerHome Messageboard : PowerHome General
Topic: Error message on PH2.1.4 regarding Elk M1
