ISY-994i: Cannot determine Insteon Engine

[autopro]

The rest of my house linked up fine (25 devices).

I'm trying to add an EZIO2x4. It's plugged into the same outlet as the ISY Modem.

I've tried: Start Linking, Auto Discover and Type [07.03].

It fails with the following log:

 

Sat 12/21/2013 08:39:19 AM : [1 dc 32 ] Added to list of devices to link to ISY

Sat 12/21/2013 08:39:19 AM : [iNST-TX-I1 ] 02 62 01 DC 32 0F 0D 00

Sat 12/21/2013 08:39:19 AM : [iNST-ACK ] 02 62 01.DC.32 0F 0D 00 06 (00)

Sat 12/21/2013 08:39:28 AM : [iNST-TX-I1 ] 02 62 01 DC 32 0F 0D 00

Sat 12/21/2013 08:39:28 AM : [iNST-ACK ] 02 62 01.DC.32 0F 0D 00 06 (00)

Sat 12/21/2013 08:39:37 AM : [iNST-TX-I1 ] 02 62 01 DC 32 0F 0D 00

Sat 12/21/2013 08:39:37 AM : [iNST-ACK ] 02 62 01.DC.32 0F 0D 00 06 (00)

Sat 12/21/2013 08:39:41 AM : [1 DC 32 0 ] Failed to add device, reason 3

Sat 12/21/2013 08:39:41 AM : ---- Start: Generate Scenes from links ----

Sat 12/21/2013 08:39:43 AM : ---- End: Generate Scenes from links ----

Sat 12/21/2013 08:39:43 AM : [All ] Writing 0 bytes to devices

 

The Users Guide says "Reason 3" is 'DEVICE RETURNED INVALID NODE'.

Any idea what is going on?

And better yet, what I can do to fix it?

[LeeG]

Check the Insteon address being used. The device did not respond to the three attempts made to communicate with that address. Should see an 02 50 response from the device.

[autopro]

Thanks for the quick reply!

 

I'm sure the address is right. I can talk to it with the SimpleHomeNet Utility Suite running through a different PLM.

Any chance the EZIO is simply not recognizing the requested command?

 

Separately: Is there a reference guide to decoding these Log Files somewhere?

[LeeG]

The 0x0D command is asking the device what type Insteon Engine does it support. This command has been available in all Insteon devices.

 

This link may provide helpful information about the event viewer log entries.

 

http://wiki.universal-devices.com/index ... ent_Viewer

 

The actual Insteon messages can be found in the PLM Developers Guide and the insteondetails.pdf document on insteon.com web site.

 

This is a trace from an EZIO2X4 asking for the Insteon Engine information

 

Sat 12/21/2013 01:08:15 PM : [iNST-TX-I1 ] 02 62 16 B0 CC 0F 0D 00

Sat 12/21/2013 01:08:15 PM : [iNST-ACK ] 02 62 16.B0.CC 0F 0D 00 06 (00)

Sat 12/21/2013 01:08:15 PM : [iNST-SRX ] 02 50 16.B0.CC 22.80.0B 2B 0D 01 (01)

 

Make sure analog inputs 3 & 4 are connected to GND. These are floating inputs and can produce unwanted Insteon messages.

 

Try a factory reset of the EZIO2X4

[autopro]

Well the EZIO problem seems resolved.

 

In trying to fix my communications problems with Programs and Scenes (only about 75% of the devices actually get switched) I moved the ISY and PLM to an outlet down near the breaker box. But left the EZIO module where it was upstairs here.

 

Communications problems did not resolve, but coincidentally the Add Device worked for EZIO.

Weird that the PLM could not communicate with the EZIO in the same outlet, but it worked over about 100 feet away.

 

Oh well, I'll be starting a new thread about all the problems I'm having with this new PLM (2413S v1..

My old PLM (2412UH v2.9) worked flawlessly, but this 2413 is pretty bad.

[LeeG]

What does Tools | Diagnostics | PLM Info/Status show for the PLM firmware level?

[autopro]

It shows v9B.

[LeeG]

That is the same one I am running. Is the 2413 plugged into the same outlet as the 2412UH?

[autopro]

No. They were on separate branches.

 

I'll run more diagnostics over the next couple days. Maybe I can nail it down to 1 or 2 devices. Or maybe one ac phase.

 

Speaking of which. I have two RF branch couplers in the basement near the breaker panel. However, all my basement circuits are on GFCIs. How good do Insteon signals pass through GFCIs?

[LeeG]

I have not heard of issues with GFCI not passing Insteon signals.