"Resending previous command..." error

Over the past week, I've been getting the following error constantly.

resending previous command (busy or unexpected command)

I've tried multiple things to troubleshoot the problem but all with no luck. To the best of my recollection, here's what I've tried so far (not in this order).

Plugging the PowerLinc 2412U into a different USB port (I'm not using a hub)
Unplugging the PowerLinc and then plugging it back in
Swapping USB cables
Plugging the PowerLinc into another outlet (with an extension cord)
Updating Indigo server to 6.1.4
Replacing the PowerLinc 2412U with a new PowerLinc 2413U (I'll return it if I can definitely rule this one out.)
Adding FilterLincs to my unfiltered UPSs (I had added my third unfiltered UPS to my home in December and have been fine until now.)

And here is an excerpt from my log file.

2015-09-25 16:49:07.918 Application Enabling interface "INSTEON Commands 2.0.5"
2015-09-25 16:49:07.921 Application Starting interface "INSTEON Commands 2.0.5" (pid 61103)
2015-09-25 16:49:08.478 Application Connected to PowerLinc 2412U interface on port usbserial-A6004tyD
2015-09-25 16:49:08.480 Application PowerLinc address 0F.DF.0B, firmware version 8.5
2015-09-25 16:49:08.555 Application Started interface "INSTEON Commands 2.0.5"
2015-09-25 17:00:07.539 Error resending previous command (busy or unexpected command)
2015-09-25 17:00:07.894 Error resending previous command (busy or unexpected command)
2015-09-25 17:00:08.253 Error resending previous command (busy or unexpected command)
2015-09-25 17:00:08.615 Error resending previous command (busy or unexpected command)
2015-09-25 17:00:08.975 Error resending previous command (busy or unexpected command)
2015-09-25 17:00:09.336 Error resending previous command (busy or unexpected command)
2015-09-25 17:00:09.692 Error resending previous command (busy or unexpected command)
2015-09-25 17:00:10.048 Error resending previous command (busy or unexpected command)
2015-09-25 17:00:10.406 Error resending previous command (busy or unexpected command)
2015-09-25 17:00:10.767 Error resending previous command (busy or unexpected command)
2015-09-25 17:00:11.126 Error resending previous command (busy or unexpected command)
2015-09-25 17:00:11.482 Error resending previous command (busy or unexpected command)
2015-09-25 17:00:11.842 Error resending previous command (busy or unexpected command)
2015-09-25 17:00:12.196 Error resending previous command (busy or unexpected command)
2015-09-25 17:00:12.549 Error resending previous command (busy or unexpected command)
2015-09-25 17:00:12.901 Error SendInsteonMessage failed
2015-09-25 17:00:19.764 Error resending previous command (busy or unexpected command)
2015-09-25 17:00:20.132 Error resending previous command (busy or unexpected command)
2015-09-25 17:00:20.486 Error resending previous command (busy or unexpected command)
2015-09-25 17:00:20.842 Error resending previous command (busy or unexpected command)
2015-09-25 17:00:21.203 Error resending previous command (busy or unexpected command)
2015-09-25 17:00:21.555 Error resending previous command (busy or unexpected command)
2015-09-25 17:00:21.915 Error resending previous command (busy or unexpected command)
2015-09-25 17:00:22.274 Error resending previous command (busy or unexpected command)
2015-09-25 17:00:22.635 Error resending previous command (busy or unexpected command)
2015-09-25 17:00:22.996 Error resending previous command (busy or unexpected command)
2015-09-25 17:00:23.354 Error resending previous command (busy or unexpected command)
2015-09-25 17:00:23.715 Error resending previous command (busy or unexpected command)
2015-09-25 17:00:24.067 Error resending previous command (busy or unexpected command)
2015-09-25 17:00:24.428 Error resending previous command (busy or unexpected command)
2015-09-25 17:00:24.787 Error resending previous command (busy or unexpected command)
2015-09-25 17:00:25.148 Error SendInsteonMessage failed
2015-09-25 17:00:32.003 Error resending previous command (busy or unexpected command)
2015-09-25 17:00:32.369 Error resending previous command (busy or unexpected command)
2015-09-25 17:00:32.737 Error resending previous command (busy or unexpected command)
2015-09-25 17:00:33.121 Error resending previous command (busy or unexpected command)
2015-09-25 17:00:33.489 Error resending previous command (busy or unexpected command)
2015-09-25 17:00:33.857 Error resending previous command (busy or unexpected command)
2015-09-25 17:00:34.225 Error resending previous command (busy or unexpected command)
2015-09-25 17:00:34.593 Error resending previous command (busy or unexpected command)
2015-09-25 17:00:34.961 Error resending previous command (busy or unexpected command)
2015-09-25 17:00:35.329 Error resending previous command (busy or unexpected command)
2015-09-25 17:00:35.688 Error resending previous command (busy or unexpected command)
2015-09-25 17:00:36.048 Error resending previous command (busy or unexpected command)
2015-09-25 17:00:36.409 Error resending previous command (busy or unexpected command)
2015-09-25 17:00:36.768 Error resending previous command (busy or unexpected command)
2015-09-25 17:00:37.120 Error resending previous command (busy or unexpected command)
2015-09-25 17:00:37.472 Error PowerLinc not responding -- attempting reset
2015-09-25 17:00:37.734 Power Failure possible power failure
2015-09-25 17:00:41.006 Error resending previous command (busy or unexpected command)
2015-09-25 17:00:41.374 Error resending previous command (busy or unexpected command)
2015-09-25 17:00:41.673 Interface Failure lost connection with interface
2015-09-25 17:00:41.752 Error resending previous command (busy or unexpected command)
2015-09-25 17:00:42.127 Error resending previous command (busy or unexpected command)
2015-09-25 17:00:42.494 Error resending previous command (busy or unexpected command)
2015-09-25 17:00:42.862 Error resending previous command (busy or unexpected command)

At this point, the "resending previous command" error would just repeat until my window was full of that message. I'd also get a dialog box that read

Failed to establish connection or open serial port to interface. Make sure the correct interface type and port are chosen in the Preferences dialog and that the serial device or adapter are plugged in correctly.

Note that there were no errors for about 10 minutes before they started flooding my log file. I made sure not to touch any switches during the time captured above.

It seems like there's a breakdown in communication between Indigo and the PowerLinc (rather than a problem with the INSTEON devices/network), but I'm not sure what else to try. Any input is appreciated.


Thanks in advance,
Paul

[jay (support)]

Those errors indicate that Indigo isn't getting reliable communication with the PowerLinc. The most common problem is signal noise that's severe enough that the PowerLinc gets confused and isn't servicing the USB port because there's so much stuff on the power line that it's attempting to decipher. Use a long outdoor extension cord and run it from a completely different room to the PowerLinc and see if that makes any difference. If so, then it's likely something on the same circuit as the PowerLinc that's causing noise.

If that doesn't change anything, then you'll want to try shutting off all the circuits in your house except the one with the Mac and PowerLinc and see if the errors stop. If so, then then the noise maker is on another circuit but is bad enough to effect several circuits. Turn them back on one at a time until you notice the problems and that will lead you to the right circuit. Also check out the signal troubleshooting page for some other things to help with diagnosis.

One other thing to try: unplug all USB devices except keyboard, mouse, and PowerLinc from your Mac. We've seen some USB devices cause issues with the PowerLinc.

Thanks, Jay. This confirms what I was thinking. Your post came through as I was setting up my laptop as a temporary Indigo server. I figure I'll focus on the interface part of the network.

I copied the Indigo 6 data folder from my Mac mini to my MacBook Pro and started up the Indigo server on my MacBook Pro with my PowerLinc plugged into an outlet on a circuit that's different from the one I use in my original setup. I didn't get the "Resending previous command..." error after running on the MacBook Pro for a few hours. Instead I'm getting a constant stream of this.

2015-09-26 14:42:10.599 Received X10 J10 status request
2015-09-26 14:42:11.431 Received X10 J10 status request
2015-09-26 14:42:14.617 Received X10 J10 status request
2015-09-26 14:42:15.673 Received X10 M13 preset dim val of 31
2015-09-26 14:42:16.505 Received X10 J10 status request
2015-09-26 14:42:17.034 Received X10 J10 status request
2015-09-26 14:42:17.450 Received X10 J10 status request
2015-09-26 14:42:19.275 Received X10 J10 status request
2015-09-26 14:42:19.819 Received X10 J10 status request

I read on the forums (I think it was one of your posts actually) that these signals could be coming from a failing device. I'm wondering if I have another problem, but before you answer, read on.

I moved my laptop and PowerLinc to the outlet of my original set up, and still running the Indigo server off my laptop, I soon got the "Resending previous command..." error. I then took a 50 foot extension cord and plugged the PowerLinc into an outlet two rooms away but instead of using my laptop as my server, I switched back to my Mac mini. (So now I'm back to the original setup with the PowerLinc plugged in with a long extension cord as you suggested.)

It's been almost three hours, and there's no "Resending previous command..." error or "Received X10..." message. I'll keep my eye on it, but if it continues to function normally, do you have any suggestions on what could be the source of the noise? Could my FilterLinc on that circuit have gone bad? Do you think I need to worry about a failing device if the "Received X10..." message doesn't come back?

Thanks,
Paul

[jay (support)]

I'm pretty sure you have a failing device somewhere, probably on one of the circuits that showed the errors (either the resending one or the stream of fake X10 traffic). You're likely to continue to have periodic issues, and they may get worse as the failing device fails in even more odd ways.

Unfortunately, it could be anything, but I'd start with disabling Insteon devices one at a time. Put your PowerLinc back on the circuit(s) where it was showing errors while testing to help speed the diagnostic process.

Thanks, Jay. Both circuits are outlet-only circuits, and the only INSTEON device besides the PowerLinc (on either circuit) is the FilterLinc on the outlet that's giving the "resending..." error. The outlet that where I was getting the X10 error is on the kitchen island (GFCI), but now that I think about it, my laptop was plugged into the same outlet (unfiltered) at the time.

When I plugged the PowerLinc into the kitchen island (using the same 50-foot extension cord), I didn't get the X10 messages, but I did get the "resending..." error. At this point, I'm not sure how to reproduce the X10 error with my Mac mini. Could the GFCI circuit be contributing to this?

I've got another question about testing for a failing device, but first to clarify, X10 errors are likely gibberish from the failing device and the "resending..." error is noise on the circuit, right? Can a failing device also cause the "resending..." error? If so, what's the better way to test (or does it matter)?

1 . Turn all circuits with INSTEON devices off, verify the "resending..." error stops, and then turn them on one by one until the the error returns? (How long should I wait for the error to return?)
2. Turn off circuits with INSTEON devices a few at a time until the error stops and then turn those circuits back on one at a time until the error returns.

Will the presence or absence of signals from the non-failing INSTEON devices affect the test?

[jay (support)]

I've got another question about testing for a failing device, but first to clarify, X10 errors are likely gibberish from the failing device and the "resending..." error is noise on the circuit, right? Can a failing device also cause the "resending..." error? If so, what's the better way to test (or does it matter)?

My suspicion is that both errors reflect the same issue. Noise on the power line is ultimately the problem. In one instance, it manifested as lots of resending commands, but at a different location it represented as random X10 commands.

1 . Turn all circuits with INSTEON devices off, verify the "resending..." error stops, and then turn them on one by one until the the error returns? (How long should I wait for the error to return?)

Right - I don't know how long you'll have to wait. How long does it currently take for your system to get those errors now (I assumed it was relatively predictable).

2. Turn off circuits with INSTEON devices a few at a time until the error stops and then turn those circuits back on one at a time until the error returns.

Will the presence or absence of signals from the non-failing INSTEON devices affect the test?

That's another option in terms of order, your choice. It is possible the results could be skewed by the absence of correctly functioning devices, but that's pretty unlikely. But in any event, these first diagnostic steps will be the same.

Thanks, Jay. Here's an update.

Messing with my circuit breakers proved tedious, so I pulled the set button on all my INSTEON switches (a little over 30) to cut power to them. At this point, the only things that still received power were an ApplianceLinc, a couple of Access Points (I don't have any dual band devices--at least that I can recall), a Thermostat Adapter, an I/O-Linc Controller, a few motion sensors, a few FilterLincs, and the PowerLinc Modem. (I had pulled a few set buttons at a time prior to pulling them all, but the "resending..." error would only pause and then resume.)

With all the set buttons pulled, it took a while, but the "resending..." error returned. I unplugged the Access Points, and it stopped, and now I'm watching it again.

1. Can my RF devices cause the problems I'm seeing? I’m thinking that unplugging my Access Points takes them all out of the picture, and if RF devices can't cause my errors, one of my Access Points could be the problem.
2. Is the INSTEON Range Extender the "new Access Point"? If so, is it backward compatible? (Can I put a Range Extender on one phase and an Access Point on another?)
3. Based on your experience, what's the likelihood that I could have two failing devices? (I thought I was having a problem with other switches, but it may have been the delayed appearance of the "resending..." error. That's what led me to pulling all the set buttons.)
4. Would the Item Detail panel on the Home Window tell me if a switch is dual-band? If so, then I don't have any dual-band devices.
5. If INSTEON devices have built-in diagnostics, can this be received by Indigo and used to notify users of a failing device? (This is more of a suggestion if it's even possible.)

Another update...

I'm fairly certain of one of my switches failing, so I'll replace that with a dual-band switch. (I'm still not sure if one of my Access Points is a suspect.)

Right now, I only have a few switches powered on, and I’m getting intermittent errors and X10 messages as below. Given the nature of these messages, could they be coming from something other than a failing INSTEON device? Does the fact that my system worked fine with the PowerLinc on a long extension cord help explain any of this (despite the FilterLincs throughout my house)?

Sep 30, 2015, 9:35:26 PM
Received INSTEON "Foyer" start dim

Sep 30, 2015, 9:36:37 PM
Received INSTEON "Living Room (KeypadLinc)" off (button 1)
Received INSTEON "Breakfast Room" off
Received INSTEON "Living Room (KeypadLinc)" on (button 7)

Sep 30, 2015, 9:36:58 PM
Received INSTEON "Stairs (remote - no load)" off

Sep 30, 2015, 9:45:07 PM
Error resending previous command (busy or unexpected command)
Error resending previous command (busy or unexpected command)
Error resending previous command (busy or unexpected command)
Error resending previous command (busy or unexpected command)
Error resending previous command (busy or unexpected command)
Error resending previous command (busy or unexpected command)
Error resending previous command (busy or unexpected command)
Error resending previous command (busy or unexpected command)
Error resending previous command (busy or unexpected command)
Error resending previous command (busy or unexpected command)
Error resending previous command (busy or unexpected command)
Error resending previous command (busy or unexpected command)

Sep 30, 2015, 9:47:25 PM
Received INSTEON "Stairs (remote - no load)" on
Received INSTEON "Stairs" off
Received INSTEON "Living Room (KeypadLinc)" on (button 1)

Sep 30, 2015, 9:56:07 PM
Indigo Cocoa client authenticated (10.0.1.169)

Sep 30, 2015, 10:39:20 PM
Received X10 J10 status request
Received X10 J10 status request
Received X10 J10 status request

Sep 30, 2015, 10:59:35 PM
Received INSTEON "Stairs (remote - no load)" on

Sep 30, 2015, 11:00:13 PM
Error resending previous command (busy or unexpected command)
Error resending previous command (busy or unexpected command)
Error resending previous command (busy or unexpected command)
Error resending previous command (busy or unexpected command)
Error resending previous command (busy or unexpected command)
Error resending previous command (busy or unexpected command)

Sep 30, 2015, 11:02:40 PM
Received INSTEON "Stairs (remote - no load)" off

Sep 30, 2015, 11:14:13 PM
Received X10 J10 status request

Sep 30, 2015, 11:14:44 PM
Received X10 J10 status request
Received X10 J10 extended data of 0 command of 0

Sep 30, 2015, 11:15:47 PM
Received X10 J10 status request

Sep 30, 2015, 11:16:24 PM
Received X10 J10 status request

Yet another update...

Now that I can work in daylight, I've shut down the power on all the INSTEON devices except the Thermostat Adapter, motion sensors, FilterLincs, and the PowerLinc Modem. (I figure the Thermostat Adapter and motion sensors are irrelevant without an Access Point, and I'm pretty sure I don't have any dual-band devices because my thermostat status isn't updating in Indigo.) I'm now getting a stream of X10 messages ("J10 status request") to the point that at times my communication queue starts filling up. (The X10 messages come and go, so the queue has a chance to clear.) Any thoughts?

[jay (support)]

It's something that's still powered somewhere that's generating all the noise that looks like X10 signals and is causing the PowerLinc confusion. Did you look at the usual suspects outlined in the signal troubleshooting page? It's just a matter of trial and error until you find the problem thing. And, no, it doesn't have to be an Insteon device - it really could be anything.

Thanks, I did look at that page initially. Unfortunately my home is probably one big noise generator. I'm assuming that although not listed, some of my suspects would include my whole home surge suppressor, solar inverter, and EV charging station. Since there isn't much more I can filter (even if I isolate the cause), is there any harm in ignoring the X10 signals? I'm hoping that when I replace the faulty INSTEON device that it's possible that INSTEON network signal strength will be strong enough to overcome the noise. Is this wishful thinking?

[jay (support)]

LOL - unfortunately, the first two things are all very likely signal noise makers, particularly the solar inverter which has been reported several times as problematic.

I'm skeptical but hopeful that the switch is the problem. The periodic bursts of fake X10 traffic will always be somewhat problematic because the PowerLinc will be busy trying to interpret those signals and waiting for them to clear before it can get to real work. They'll also cause signal collisions which are problematic for Insteon.

I think I have a lead. After cutting power to more circuits (bathrooms with non-INSTEON electronic dimmers, EV charging station, and refrigerator) and unplugging various electronics, I was still getting the X10 message. I tried unplugging the UPS of the original setup from the FilterLinc. The X10 signals stopped. I turned on some of the circuits and plugged in the gadgets I had just unplugged--still quiet. I plugged the UPS back into the FilterLinc, and almost immediately the X10 signals resumed. I suppose this is why the long extension cord helped.

I'm going to go out on a limb and say it looks like my headache was caused by a faulty INSTEON switch and FilterLinc. Let's hope there are no surprises after I get the replacement units up and running. Thanks for all your help, Jay.

Another update and new suspect...

After my last post, I replaced one of my INSTEON switches and my system worked fine until the past week or so when I started getting the "Resending previous command..." error again. This still seems to be a noise problem, so instead of starting a new thread, I thought I'd just add on to the one I started before.

After a lot of trial and error, I replaced what I suspected to be three additional failing switches. While testing though, I turned off/unplugged each (non-RF) INSTEON device and was still getting the "Resending" error. It wasn't until I unplugged the server's UPS (with FilterLinc) that the error messages stopped, and when I plugged it back in, the error started again. Can a FilterLinc go bad? Thinking it was the FilterLinc, I swapped the server's unit with two other ones I have in the house, but there was no improvement with either until I unplugged the server altogether and let it run on the UPS battery. It ran until the battery was just about depleted but I never got the error.

Now my PowerLinc is plugged into the same outlet as the server's UPS/FilterLinc when I get the error. When I use an extension cord and plug the PowerLinc into an outlet on another circuit, I can't reproduce the error. This leads me to conclude that the PowerLinc is fine, but there's something about the outlet/circuit that I normally have it plugged into that subjects the PowerLinc to enough noise to exceed the "error threshold" resulting in the "Resending" error. In addition, these conditions don't exist on the other circuit. It's my understanding that line noise is additive, but does proximity make a difference?

Are today's FilterLincs better in any way than the ones sold a few years ago? If the problem is the UPS's FilterLinc, are the other ones I swapped it out with faulty too? (I have them on other UPSs in the house.)