EZSrve 2.06 has lost communication with its PLM 2011-01-26T23:01:24+00:00

HOME Forums Gateways EZSrve EZSrve 2.06 has lost communication with its PLM

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • Anonymous
    Post count: 31
    #40295 |

    In an effort to fight some suspected powerline noise today, I brought my EZSrve with me to my home office. I have plenty of Insteon devices here which communicate just fine with the rest of the property. I plugged it in down here after hooking it to an Ethernet switch I have here, and promptly went to start testing it. All commands result in a ‘Device XX.XX.XX did not respond’ error. I took the EZSrve back up to where it originally was plugged in, same exact issue. I’ve gone through many resets, power cycles, even a fresh firmware update to no avail. It can’t even communicate with its own PLM — the ‘SimpleHomeNet Debug Mode’ shows the following messages after trying to ‘SYNC DEVICE’ on the EZServe itself (to make sure and clear its links):


    01/26/2011 14.51.36: In device submit function operation flag is 9 and my dev rec 0
    01/26/2011 14.51.48: In device submit function operation flag is 7 and my dev rec 202
    01/26/2011 14.51.48: In synchronising device 06.4C.E4
    01/26/2011 14.51.48: In synchronize device: cleared dev 06.4C.E4 mem
    01/26/2011 14.51.48: In synchronize dev: sending cmd to write to device -- 06.4C.E4 id,F8 lsb, LD1 0, LD2 0, LD3 0
    01/26/2011 14.51.48: In synchronize dev: mark as end of dev memory
    01/26/2011 14.52.05: File: ezbridge_socket - Fn: send_response - Device 06.4C.E4.28 did not respond
    01/26/2011 14.52.05: In synch dev err handler: resend 1
    01/26/2011 14.52.05: In synchronize dev: synch_dev_flag 2
    01/26/2011 14.52.05: In synchronize dev: sending cmd to write to device -- 06.4C.E4 id,0 lsb, LD1 0, LD2 0, LD3 0
    01/26/2011 14.52.05: In synchronize dev: mark as end of dev memory
    01/26/2011 14.52.22: File: ezbridge_socket - Fn: send_response - Device 06.4C.E4.28 did not respond
    01/26/2011 14.52.22: In synch dev err handler: resend 2
    01/26/2011 14.52.22: In synchronize dev: synch_dev_flag 2
    01/26/2011 14.52.22: In synchronize dev: sending cmd to write to device -- 06.4C.E4 id,0 lsb, LD1 0, LD2 0, LD3 0
    01/26/2011 14.52.22: In synchronize dev: mark as end of dev memory
    01/26/2011 14.52.39: File: ezbridge_socket - Fn: send_response - Device 06.4C.E4.28 did not respond
    01/26/2011 14.52.39: In synch dev err handler: resend 3

    What the heck happened? More importantly, what do I need to do to get it back online? This is ridiculous. I’m really considering scrapping this thing and going direct with a PLM, I’ve wasted SO much time on this unstable device.

    Anonymous
    Post count: 1001

    Use the SYNC EZSERVE function to rewrite the EZSrve PLM records, assuming you have some after doing a Reset. The SYNC DEVICE function assumes it is working with other than the actual EZSERVE device and uses the device Insteon address for communication. The EZSERVE cannot communicate with itself using its own Insteon address. THE SYNC EZSERVE function will use the serial interface to the internal PLM to restore the link records, again assuming there are link records listed after the Reset.

Viewing 2 posts - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.