Unlisted ED command from EZIO2x4

[Anonymous]

#40245

Hi everyone,

Has someone run into the following?
I am using a PLC to communicate to an EZIO2x4 device. There are no links between the 2 devices at this point.
I have a status polling loop that periodically sends a read input port command to the EZIO device (SD msg w/ cmd1=0x49). Works great, I get accurate input port status.
However once in a while (every few hundred iterations), I get an extended message from the EZIO. And the message type is not in the EZIO command set, nor is documented in the Insteon command tables (they are listed as “Reserved”).
Here are two examples I got (in hex):
02 51 01 7F 83 13 AC 0F 76 36 C9 02 0B 0F 7F 2C 44 02 CE AD 18 81
– 02 51 plm ED msg
– from my EZIO 017Fb3 to my plm 13AC0F
– flags of 76, which is an unused ED msg type (EC cleanup ack)
– cmd of 36 (unlisted in the EZio doc and reserved on the insteon docs)

Another example I got:
02 51 01 7F 83 13 AC 0F 30 B6 C3 3D CF 9F FC C8 92 24 85 93 AE A1 B2 AD B2
– flags of 30 which is an unused ED msg type (ED NACK)
– cmd of B6 (unlisted in the EZio doc and reserved on the insteon docs)

Any clues to what these messages can be?? What they mean and what I should do about them?
(yes I know I can link the 2 devices to not have to poll, but that is besides the point 🙂 ).
Thanks in advance for any insight!
Pierre

[Anonymous]

#43269

Can you clarify a few points, you initially said a PLC is being used, then described the modem as a PLM. Also in the description of the parts of the message you indicate “from my EZIO 017Fb3 to my plm 13AC0F” an EZIO2X4 address of 017Fb3 but the trace shows a FROM address of “01 7F 83”.

They look like garbage messages that my PLC sometimes generates unrelated to any specific device type (if you are using a PLC). If these are coming from a PLM they are very strange. The flag byte of 76 is a Group Cleanup Direct ACK of an Extended message. Since Group messages are not being used nor are Extended messages this is another indication of a garbage message. Also the command is garbage. A Flag byte of 30 in the second example is an ACK but of an Extended message which is not in play here. Also the command is garbage.

Please post the clarifications to the first two questions (PLC versus PLM and EZIO2X4 Insteon address).

[Anonymous]

#43270

My apologies, I typed too fast and made a few spelling mistakes.
No PLC involved, just a PLM (13AC0F)
Yes my EZIO is 017F83 as in the trace (the addresses in the messages are correct).

I would agree that the messages look like “garbage” since they don’t correspond to anything “documented”, but why would the EZIO generate them in the first place? 🙂
Just wondering if anyone saw this, or if anyone from simplehomenet might be able to shed some light.

Thanks for the help,
Pierre

[Anonymous]

#43271

What level is the firmware in the EZIO2X4? How often do you poll the EZIO2X4? Do you know the firmware level of the PLM? This information may be useful to SHN.

Until someone else has other suggestions or ideas, I would move the EZIO2X4 near the PLM plug point. You do not need to move the controlling circuitry. This should reduce the possibility of a truly garbage message. With the messages having inconsistent data (flags, cmd1, cmd2) they look like something on the powerlIne is trashing the message. Harder to happen with an Insteon message due to the CRC character but it does happen. I have 3 EZIO2X4s installed running v25 firmware for more than a year and have never seen those types of messages being generated by the EZIO2X4. Two of the EZIO2X4s are in a detached garage several hundred feet from the house. However, I do not poll the devices on a regular basis.

I’ll set up a test where I poll both EZIO2X4s in the garage and see if I can reproduce what you are seeing. Let me know how often you poll and I will use the same interval.

[Anonymous]

#43272

I have been able to recreate the symptom on both of my EZIO2X4s using the 0x49 (Read Input Port) command and two different ICON switches using the 0x19 (Ping) command. Looks like the PLM is passing out a garbage message every once in awhile.

2010-02-20 16:28:20.194 TX 02 62 09 FD 5D 05 49 00
2010-02-20 16:28:20.225 RX SENTINSTEON=0F 44 DC 09 FD 5D 05 49 00 06
2010-02-20 16:28:20.772 RX RECEIVEINSTEONRAW=09 FD 5D 0F 44 DC 22 49 00
2010-02-20 16:28:20.928 RX RECEIVEINSTEONEXT=09 FD 5D 0F 44 DC 12 49 00 66 F8 E5 9E 65 54 A3 6A BF F0 38 E5 9E 65

2010-02-20 16:36:32.210 TX 02 62 04 5A F1 05 19 00
2010-02-20 16:36:32.241 RX SENTINSTEON=0F 44 DC 04 5A F1 05 19 00 06
2010-02-20 16:36:32.444 RX RECEIVEINSTEONRAW=04 5A F1 0F 44 DC 21 00 00
2010-02-20 16:36:32.663 RX RECEIVEINSTEONEXT=04 5A F1 0F 44 DC 12 FF C0 B1 F0 3E 58 0C 7F 8F A1 E6 55 4D EE B7 FF

2010-02-20 16:41:35.366 TX 02 62 04 5A F1 05 19 00
2010-02-20 16:41:35.397 RX SENTINSTEON=0F 44 DC 04 5A F1 05 19 00 06
2010-02-20 16:41:35.991 RX RECEIVEINSTEONRAW=04 5A F1 0F 44 DC 22 00 00
2010-02-20 16:41:36.241 RX RECEIVEINSTEONEXT=04 5A F1 0F 44 DC 55 FF C0 DD 50 3E 58 0C 7F 8F A1 E6 55 4D EE B7 FF

2010-02-20 16:54:16.600 TX 02 62 04 5B 2E 05 19 00
2010-02-20 16:54:16.632 RX SENTINSTEON=0F 44 DC 04 5B 2E 05 19 00 06
2010-02-20 16:54:17.178 RX RECEIVEINSTEONRAW=04 5B 2E 0F 44 DC 22 00 00
2010-02-20 16:54:17.350 RX RECEIVEINSTEONEXT=04 5B 2E 0F 44 DC 12 00 00 BF 11 6B C4 28 64 00 6F 66 55 4D EE B7 FF

2010-02-20 16:55:20.757 TX 02 62 0C B0 AC 05 49 00
2010-02-20 16:55:20.788 RX SENTINSTEON=0F 44 DC 0C B0 AC 05 49 00 06
2010-02-20 16:55:21.038 RX RECEIVEINSTEONRAW=0C B0 AC 0F 44 DC 21 49 00
2010-02-20 16:55:21.210 RX RECEIVEINSTEONEXT=0C B0 AC 0F 44 DC 12 88 80 70 E1 6B C4 28 64 00 6F 66 55 4D EE B7 FF

[Anonymous]

#43273

Many thanks for trying it out, that’s very kind of you!
I’m somewhat glad to see I am not the only one seeing this behavior.
I hadn’t tried it with other devices, but I think your test does point to the PLM as being the culprit. A bit disappointing though.
I guess I’ll filter these garbage messages in software then.

By the way I am using the dual band USB PLM (2413u V1.0) w/ a firmware code of 0x85 (from an IM 02 60 inquiry), an EZIO2x4 V2.8, and was polling every 5 seconds.

Cheers,
Pierre

[Author]

Posts