Elk M1XSP behavior - misses first command from M1

[DDomnick]

Hello I was wondering if anyone has experienced the following behavior before when running multiple M1XSP:

Setup is new, all latest firmware.

M1XSP @ Address 1 is Insteon interface 2413s v1.5
M1XSP @ Address 2 is AprilAire 8811 with 6 Thermostats
M1XSP @ Address 3 is Lutron GRX-PRG interface to 7 Graphic Eye panels. This one functions simply as a pure serial interface to send TEXT commands to the GRX-PRG. For example, sending A613456^M to Port 3 selects Scene 6 on Graphic Eye panels 1,3,4,5,6.

All work fine EXCEPT - When issuing a command via rule or task to the Insteon, for example turning a Switchlink On or Off, the very next command to port 3 is dropped / ignored. The second or repeated command works fine. All subsequent commands to port 3 work fine. Only when issuing another lighting command to the Insteon(s) via the Elk lighting interface does the next command get dropped on port 3. Also, it does not happen in reverse - After sending text out port 3, the first Insteon command works fine. I also believe everything being sent to Port 2 via TStat control is fine, but am still gathering data. I have tried swapping the addresses of M1XSP 1 & 3 with same issue. This is repeatable and consistant problem.

Any advise appreciated.

Dan

 

[DDomnick]

I have some additional info on this issue. The thermostat XSP does not miss commands after a command is sent to port 1. Also, I just noticed that the amber heartbeat LED on ALL of the M1XSP's flash normally @ 1 beat per second for 30 seconds, then all of them stop for 5 seconds, then resume for another 30 seconds. Is this normal? The input expansion board and supervised power supply heartbeat LED's do not pause.

Dan

 

[Spanky]

I think you found an issue in the M1XSP. We have fixed the software and it will be available in the next release. In the mean time you can code around the issue by breaking the Rules down into separate Rules and putting a few seconds between the Rules.

Thanks for the heads up.

 

[DDomnick]

Thanks for the reply. I tried re-coding several ways, adding delays, etc. Nothing worked. Then I reformated the Graphic Eye text strings to add a CR BEFORE each string, and now it works perfectly (I.E. example changed A613456^M to ^MA613456^M). I assume that somewhere the XSP is adding garbage into the buffer and my first text strings WITHOUT the leading ^M are being appended to that garbage, making for an invalid text string.