Good to know, I thought I was alone. I've filtered alot and added access point but probably need to do some more hunting (haven't hit the breakers yet). I have noticed the reliability goes down on the other phase, accross access points. I've noticed that with the 2412 on each phase. Not sure if it's my set up but I figured I'd mention it here again.

That being said, I may just permanently give up. I may just give the thing to a neighbor. But it would be for a part time house. Has the freezing issue been resolved?

Any news on this? I'm about to revert back to the 2414U I think.

This is an example of the failures I get several times a day and on different devices:

Code: Select all

 Received INSTEON   "MD01-dining" on (button 1)
  Trigger Action     MD Dining Motion On (Hydro) - Insteon
  Sent INSTEON       "IB13 Dining Room Light" on
  PowerLinc          Unexpected command 02 60 (flushing)


And of course the Dining Room light doesn't get turned on. On the next motion, a very short time later, same command except for the 02 60 and the light turns on.

MD01 is a Dakota Motion detector. IB13 is an Insteon Switch relay. Have re-synced and synced from scratch a few times but it doesn't seem to make it any better.

This is just an example. It's not always same device and sometimes never (per day).

hwitten wrote:Any news on this? I'm about to revert back to the 2414U I think.

This is an example of the failures I get several times a day and on different devices:

Code: Select all

 Received INSTEON   "MD01-dining" on (button 1)
  Trigger Action     MD Dining Motion On (Hydro) - Insteon
  Sent INSTEON       "IB13 Dining Room Light" on
  PowerLinc          Unexpected command 02 60 (flushing)


And of course the Dining Room light doesn't get turned on. On the next motion, a very short time later, same command except for the 02 60 and the light turns on.

MD01 is a Dakota Motion detector. IB13 is an Insteon Switch relay. Have re-synced and synced from scratch a few times but it doesn't seem to make it any better.

This is just an example. It's not always same device and sometimes never (per day).

Seems like I only see the "Unexpected command XX XX (flushing)" about once a week or so. Does it always occur when:

1) You receive a Motion Sensor event
2) You immediately send an INSTEON command

We may have a timing issue with the Motion Sensors. If that's what you're seeing, try this (just for testing): before you send the second command, delay a couple of seconds. This could help figure out if it's some strange timing issue that we're not replicating.

I've rarely seen the "Unexpected command 02 60" error, and so far I haven't noticed any commands being missed/skipped because of it.

Is anyone else: A) Seeing this error, B) noticing a reliability problem because of it?

First off,apologies, it was late The MD01 is an Insteon MD that replaced a Dakota in an effort to improve reliability. Made no diff.

This morning I have:

Code: Select all

 Received INSTEON   "MD01-dining" on (button 1)
  Trigger Action     MD Dining Motion On (Hydro) - Insteon
  Sent INSTEON       "IB13 Dining Room Light" on


No 02 60, but no light either.
Indigo shows status as On.
Status request results in:

Code: Select all

Error              "IB13 Dining Room Light" status request; send failed (no acknowledgment)

Frustrating because the performance is definitely better than the 2414U. If it is noise on the powerline than they have to build it better. Would another pair of access points help? I imagine not as the MD01's signal ends up in the event log and Indigo turns the light on. As I said, frustrating but reluctant to give up

hwitten wrote:First off,apologies, it was late The MD01 is an Insteon MD that replaced a Dakota in an effort to improve reliability. Made no diff.

This morning I have:

Code: Select all

 Received INSTEON   "MD01-dining" on (button 1)
  Trigger Action     MD Dining Motion On (Hydro) - Insteon
  Sent INSTEON       "IB13 Dining Room Light" on


No 02 60, but no light either.
Indigo shows status as On.
Status request results in:

Code: Select all

Error              "IB13 Dining Room Light" status request; send failed (no acknowledgment)

Frustrating because the performance is definitely better than the 2414U. If it is noise on the powerline than they have to build it better. Would another pair of access points help? I imagine not as the MD01's signal ends up in the event log and Indigo turns the light on. As I said, frustrating but reluctant to give up

Do you have the "Report error on all NAKs regardless of firmware version" checkbox checked in the Interface Options for your 2412? If not, turn that on, and I suspect you'll see the same error when Indigo tries to control the light. Certainly, that looks like some type of signal issue.

You didn't answer my question above - when you see the problem, is it always a combination of Motion Sensor/trigger/control Insteon device?

Now turned on.

Sorry about the senior moment
Not always with motion. But motions have the most activity during the day/night. Rest is basically turning on garden/yard lights at night etc.

I run a script every 30 minutes based on time of day that sets some lights to what they should be at that time, I.e. on or off. This goes back to when I was all X10 and lots of 'misses'. I have the occasional one now so I left the Time/Date actions in with adjustments to Insteon, etc.

I get errors on those actions occasionally but most times no impact as they are actually in the correct state already.

I have the Always send group/scene cleanup message unchecked. Should that be on too?

hwitten wrote:I have the Always send group/scene cleanup message unchecked. Should that be on too?

That can help, but only if you are sending a PowerLinc based Group/Scene command. Based on your Event Log snippets above, all your commands are direct to individual modules (not scenes/groups) in which case that preference isn't used.

1. no freezing
2. Mac OS X 10.4.11
3. B. A bit faster
4. I get this entry in my log a lot: PowerLinc Unexpected command 02 60 (flushing) It seems to come right after some X10 activity. I have an V572A installed on the powerline, so maybe there is some issues with that?

Matt wrote: I get this entry in my log a lot: PowerLinc Unexpected command 02 60 (flushing) It seems to come right after some X10 activity. I have an V572A installed on the powerline, so maybe there is some issues with that?

I believe I have this problem fixed in Indigo 4.1.1 (not yet available).

Indigo 4.1.1 is now available and should eliminate, or at least reduce, this problem.