"Resending previous command..." error

[jay (support)]

Proximity can be a problem, though that's normally just circuit to circuit. Did it work when you just plugged the PowerLinc into a different outlet in the same room? That may have to be your solution. You could, of course, try a new FilterLinc to see if that makes any difference - it may perform better.

So just to clarify, physical proximity of the devices shouldn't matter, right? The PowerLinc is within two feet of the UPS and six devices (which are all plugged into the UPS). Circuit-wise, the PowerLinc and the UPS are plugged into the same outlet.

The nearest (and only other) outlet that the PowerLinc can reach with the 6-foot USB cable I'm using is a few feet above it, and is directly wired to that outlet. (I saw the wiring when my house was being built.) There was no noticeable improvement when I tried this outlet.

The outlet that does seem to work OK is the one across the room which is on a different circuit, but to reach it, I have a bright orange extension cord laying across the floor of my living room.

Aside from trying a new FilterLinc, what are your thoughts on these approaches (in case that doesn't work)?

1. Double up on FilterLincs, i.e. plug the UPS into one FilterLinc and then plug that FilterLinc into another FilterLinc
2. Using a USB extension cable like this one (http://www.amazon.com/dp/B004AGX4YO)

I've been on a relentless purge of all my daily errors that occur in my system. I removed all but the most minute of asynchronous events in order to make everything ordered and collision-free, yet I still have a couple of errors.
One of them is a random "resending previous command..." error once every 1 or days.
There is no activity to cause these except a request for analog status of my EZIO8SA.
I have delays all around it so I'm 100% confident nothing is going on except the issuing of the command to the EZIO8SA.

It does indeed always resend the status command and the EZIO8SA does always respond with data. I just don't know why it has this rare event occurring.

Any ideas of what this is?

[matt (support)]

Can you copy/paste into a post the error line(s) from the Event Log, along with several lines before and after the error?

Extract from one example below. The routine is sequentially running through sampling heating thermostats, water temp sensors and my EZIO8SA analog channels (that I use for water and solar temp sensing). There are multiple seconds between sequential samples and no scheduled activities during the sampling time.

2016-01-19 00:49:20.933 Action Collection Solar Status: false PoolTempTarget: 85
2016-01-19 00:49:20.931 Action Collection Ambient Temp: 0, Pool Temp: 70 Solar Temp: 70
2016-01-19 00:49:20.928 Script Nothing happened with Solar
2016-01-19 00:49:20.904 Script Processing Pool and Solar Temperature Readings
2016-01-19 00:49:20.903 Trigger Pool Temp Control Solar
2016-01-19 00:49:20.897 Schedule Pool Temp Measure (delayed action)
2016-01-19 00:49:19.966 Action Collection Solar Status: false PoolTempTarget: 85
2016-01-19 00:49:19.964 Action Collection Ambient Temp: 0, Pool Temp: 70 Solar Temp: 70
2016-01-19 00:49:19.933 Script Measuring Pool and Solar Temperature Readings
2016-01-19 00:49:19.932 Trigger Pool Temp Measure
2016-01-19 00:49:19.910 Trigger PoolSampleUntilValidDelay
2016-01-19 00:49:19.904 Schedule PoolSampleUntilValid (delayed action)
2016-01-19 00:49:11.725 Sent INSTEON Pool Control - New input analog value request (received: 1023, 1023)
2016-01-19 00:49:09.903 Schedule PoolSampleUntilValid (delayed action)
2016-01-19 00:48:59.905 Trigger PoolSampleUntilValid
2016-01-19 00:48:59.904 Schedule Get Temperature Sensor Data (delayed action)
2016-01-19 00:48:56.897 Schedule Get Temperature Sensor Data (delayed action)
2016-01-19 00:48:55.011 Sent INSTEON Pool Control - New input analog value request (received: 1023, 1023)
2016-01-19 00:48:52.716 Email Sent to "xxx@yyy.com"; subject "Indigo Error Detected"
2016-01-19 00:48:52.199 Trigger Error - In Log File
2016-01-19 00:48:52.198 Error resending previous command (reply mismatch)
2016-01-19 00:48:51.906 Action Collection Get Pool Temperatures
2016-01-19 00:48:51.902 Schedule Get Temperature Sensor Data (delayed action)
2016-01-19 00:48:51.897 Schedule Get Temperature Sensor Data (delayed action)
2016-01-19 00:48:42.905 Action Collection Garage Temperature: 70, Fish Temperature: 70
2016-01-19 00:48:42.898 Schedule Get Temperature Sensor Data (delayed action)
2016-01-19 00:48:41.907 Schedule Get Temperature Sensor Data (delayed action)
2016-01-19 00:48:31.934 Action Collection Get Fish Temperatures
2016-01-19 00:48:31.933 Action Collection Becky's Wing Temperature 68.0
2016-01-19 00:48:31.932 Action Collection Master Bedroom Temperature 68.0
2016-01-19 00:48:31.931 Action Collection Main House Temperature 71.0
2016-01-19 00:48:31.926 Schedule Get Temperature Sensor Data (delayed action)
2016-01-19 00:48:31.921 Schedule Get Temperature Sensor Data (delayed action)
2016-01-19 00:48:31.917 Schedule Get Temperature Sensor Data (delayed action)
2016-01-19 00:48:31.913 Schedule Get Temperature Sensor Data (delayed action)
2016-01-19 00:48:31.908 Schedule Get Temperature Sensor Data (delayed action)
2016-01-19 00:48:21.917 Schedule Get Temperature Sensor Data (delayed action)
2016-01-19 00:48:21.913 Schedule Get Temperature Sensor Data (delayed action)
2016-01-19 00:48:21.908 Schedule Get Temperature Sensor Data (delayed action)
2016-01-19 00:48:12.746 Sent INSTEON Heating - Main temperature request (received: 71.0)
2016-01-19 00:48:11.899 Schedule Get Temperature Sensor Data (delayed action)
2016-01-19 00:48:02.264 Sent INSTEON Heating - Becky's Wing temperature request (received: 68.0)
2016-01-19 00:48:01.911 Action Collection Get Thermostat Temperatures
2016-01-19 00:48:01.901 Action Group Get Sensor Data
2016-01-19 00:48:01.900 Schedule Get Temperature Sensor Data (delayed action)
2016-01-19 00:45:01.717 Action Collection Get Temperature Sensor Data
2016-01-19 00:45:01.715 Schedule Get Temperature Sensor Data

[matt (support)]

So I'm not sure exactly what is causing it in this situation, but that specific error occurs when Indigo is trying to send a command via the PowerLinc and the PowerLinc responds back with invalid data. Normally when the PowerLinc is busy it will refuse to accept commands, but sometimes the PowerLinc will accept the command but then return data that is obviously invalid. I think the likelihood of this occurring may increase if there is a lot of INSTEON traffic and/or power line noise (it could also be a USB level error, so try swapping the cable and plugging the PowerLinc into a different USB port). Basically, the PowerLinc gets confused. Indigo logs it as an error but then just re-sends the command.

I'm not sure there is going to be a way though for you to eliminate it from occurring 100%. Even though Indigo can normally recover from the situation, I still want Indigo to log it as an error since bad data is being received. In cases of malfunctioning PowerLinc or excessive noise those errors can be clues that something is really wrong. But not in your case of only seeing it so sporadically.

Thanks for the explanation.
In this case there is no other Insteon activity
I will check out the USB path though as I have not looked at that yet.

Just my 2 cents...

I had the same problem and realized my USB Link was plugged into a cheap power strip. Now it's been running that way for over 3 years with no issues, but today it wigged out. I plugged it into a 10' extension cord, and then into the wall and the errors vanished. Wahoo!

Thanks for the tips!