Indigo Domotics

Thinking back to my weekend problems I think it originally was a lost connection with interface that caused me to change the 2414U so this is actually #3 after upgrading my Mini to Leopard 10.5.6.

Could be just coincidence though and not 10.5.6. related at all.

Just me or are others experiencing similar problems, I.e. loosing the interface connection?

The current 2414U is a brand new one.
A simple unplug and plugging it back in lets Indigo continue without a reboot/restart.

Ideas?

No problems here, but I hope others chime in as well.

Do you have the PowerLinc plugged directly into a USB port on your Mac? USB hubs are known for power fluctuations that can cause problems with the PowerLinc.

Yup, straight in to the Mini. If it happens again I'll change USB cable, just in case.

I do have a hub running other stuff, I.e. keyspan usb but if problems crop up the hub is the first to go

Only changes in last few days has been the 10.5.6 upgrade. Since I had updated every other Mac I felt it was safe

Can you copy/paste what was logged in the Event Log for all of the failures? I'd like to see exactly what Indigo thinks is occurring.

I was wrong in my guess that the initial problem was "Error lost connection with interface" as I couldn't find one prior to changing the 2414U.

It may be Dakota related? or it could simply just look that way as most activity is from the Dakota as I use them as "room occupied" sensors in conjunction with the timer script.

I'll keep looking for that initial failure which caused me to think the 2414U had failed.

Code: Select all

2009-03-08 11:54:44   Received INSTEON   "Dakota" off (button 6)
2009-03-08 11:54:48   Received INSTEON   "Dakota" on (button 5)
2009-03-08 11:54:48   Trigger Action   MD House Garage Light On
2009-03-08 11:54:48   Trigger Action   Sensor Button 5 (Dakota) House Garage
2009-03-08 11:54:52   Error   resending previous command (timeout)
2009-03-08 11:54:53   Script   varname: OutsideTemperature set to: 3.11
2009-03-08 11:54:53   Script   varname: OATfh set to: 37.6
2009-03-08 11:54:53   Script   varname: WindSpeed set to: 0.4
2009-03-08 11:54:55   Error   resending previous command (timeout)
2009-03-08 11:54:56   Error   usb data write: timeout
2009-03-08 11:54:56   Error   usb data write: clearing pipes
2009-03-08 11:54:56   Error   usb data write: failed2 (0xE00002EB)
2009-03-08 11:54:56   Power Failure   possible power failure
2009-03-08 11:54:56   Error   usb data write: not open (closed during write)
2009-03-08 11:54:59   Error   lost connection with interface
2009-03-08 11:55:00   Trigger Action   Power Back Online daytime
2009-03-08 11:55:00   Trigger Action   Power off
2009-03-08 11:55:01   Email Sent   to "7782310722@txt.bellmobility.ca"; subject "Power dropped"
2009-03-08 11:55:01   Email Sent   to "heinz@bytedesigns.com, heinz@mac.com"; subject "Lakeside Power Failed"
2009-03-08 11:55:06   Time/Date Action   Sensor Button 5 (Dakota) House Garage (delayed action)
2009-03-08 11:55:53   Script   varname: OutsideTemperature set to: 3.17




2009-03-09 12:39:31   Trigger Action   MD Dining Motion Active Off (Hydro)
2009-03-09 12:39:31   Sent INSTEON   "PowerLinc Interface" off (instant) (group/scene 6)
2009-03-09 12:43:16   Received INSTEON   "Dakota" on (button 6)
2009-03-09 12:43:18   Received INSTEON   "Dakota" off (button 6)
2009-03-09 12:43:33   Received INSTEON   "Dakota" on (button 6)
2009-03-09 12:43:35   Received INSTEON   "Dakota" off (button 6)
2009-03-09 12:43:47   Received INSTEON   "IN02 Fam Room Floor lamp" on
2009-03-09 12:43:51   Received INSTEON   "Dakota" on (button 6)
2009-03-09 12:43:53   Received INSTEON   "Dakota" off (button 6)
2009-03-09 12:44:15   Received INSTEON   "Dakota" on (button 6)
2009-03-09 12:44:17   Received INSTEON   "Dakota" off (button 6)
2009-03-09 12:44:33   Received INSTEON   "Dakota" on (button 6)
2009-03-09 12:44:35   Received INSTEON   "Dakota" off (button 6)
2009-03-09 12:45:08   Received INSTEON   "Dakota" on (button 6)
2009-03-09 12:45:11   Received INSTEON   "Dakota" off (button 6)
2009-03-09 12:45:27   Received INSTEON   "Dakota" on (button 6)
2009-03-09 12:45:30   Received INSTEON   "Dakota" off (button 6)
2009-03-09 12:46:06   Received INSTEON   "Dakota" on (button 6)
2009-03-09 12:46:08   Received INSTEON   "Dakota" off (button 6)
2009-03-09 12:46:29   Received INSTEON   "Dakota" on (button 6)
2009-03-09 12:46:31   Received INSTEON   "Dakota" off (button 6)
2009-03-09 12:46:48   Received INSTEON   "Dakota" on (button 6)
2009-03-09 12:46:51   Received INSTEON   "Dakota" off (button 6)
2009-03-09 12:47:16   Received INSTEON   "Dakota" on (button 6)
2009-03-09 12:47:17   Received INSTEON   "Dakota" on (button 6)
2009-03-09 12:47:18   Received INSTEON   "Dakota" off (button 6)
2009-03-09 12:47:33   Received INSTEON   "Dakota" on (button 6)
2009-03-09 12:47:36   Received INSTEON   "Dakota" off (button 6)
2009-03-09 12:47:53   Received INSTEON   "Dakota" on (button 6)
2009-03-09 12:47:55   Received INSTEON   "Dakota" off (button 6)
2009-03-09 12:48:11   Received INSTEON   "Dakota" on (button 6)
2009-03-09 12:48:13   Received INSTEON   "Dakota" off (button 6)
2009-03-09 12:48:31   Received INSTEON   "Dakota" on (button 6)
2009-03-09 12:48:32   Error   resending previous command (timeout)
2009-03-09 12:48:35   Error   resending previous command (timeout)
2009-03-09 12:48:36   Error   usb data write: timeout
2009-03-09 12:48:36   Error   usb data write: clearing pipes
2009-03-09 12:48:36   Error   usb data write: failed2 (0xE00002EB)
2009-03-09 12:48:36   Power Failure   possible power failure
2009-03-09 12:48:36   Error   usb data write: not open (closed during write)
2009-03-09 12:48:39   Error   lost connection with interface
2009-03-09 12:48:40   Trigger Action   Power Back Online daytime
2009-03-09 12:48:40   Trigger Action   Power off
2009-03-09 12:48:40   Email Sent   to "7783849311@pcs.rogers.com"; subject "Power dropped"
2009-03-09 12:48:40   Email Sent   to "heinz@bytedesigns.com, heinz@mac.com"; subject "Lakeside Power Failed"


Looks like the illegal 4A started the ball rolling and then bad diagnostic procedures (by me) snowballed into grief.

Am I somewhat correct that a constant X10 stream would just simply raise havoc by delaying legit command, etc? And then I imagine I simply made it worse by resetting/rebooting without finding the real cause (and not watching the log as much as I should have as there were oodles of A01's )

The V752, which was the cause of the A01's was out of view and therefore out of mind as it's not used much. Something that won't happen again
It's still off-line.

Code: Select all

2009-03-07 12:24:11   Script   varname: WindSpeed set to: 9.6
2009-03-07 12:25:11   Script   varname: WindSpeed set to: 14.4
2009-03-07 12:25:11   Script   varname: WindGust set to: 18.5
2009-03-07 12:26:11   Script   varname: WindSpeed set to: 12.8
2009-03-07 12:27:11   Script   varname: WindSpeed set to: 12.4
2009-03-07 12:27:11   Script   varname: WindGust set to: 16.7
2009-03-07 12:28:11   Script   varname: WindSpeed set to: 12.8
2009-03-07 12:28:38   Error   illegal security code byte 4A
2009-03-07 12:28:38   Error   illegal security code byte 4A
2009-03-07 12:28:39   Error   illegal security code byte 4A
2009-03-07 12:28:39   Received X10   "A01 Front Porch" on
2009-03-07 12:28:39   Error   illegal security code byte 4A
2009-03-07 12:28:40   Received X10   "A01 Front Porch" on
2009-03-07 12:28:41   Received X10   "A01 Front Porch" on
2009-03-07 12:28:41   Received X10   "A01 Front Porch" on
2009-03-07 12:28:42   Received X10   "A01 Front Porch" on
2009-03-07 12:28:43   Received X10   "A01 Front Porch" on
2009-03-07 12:28:44   Received X10   "A01 Front Porch" on
2009-03-07 12:28:45   Received X10   "A01 Front Porch" on


Part of the resulting grief was that Indigo couldn't connect to postgreSQL on restart/reboot due to a remaining postgreSQL pid file. Then I changed the 2414U since I had a new one available (that's the one currently running). After all that I finally twigged onto the V752 as being the cause of the constant A01 stream.

Cheesh

All is well at the moment but as one gets real spoiled by Indigo it's almost disastrous to have to do without.

hwitten wrote:

Am I somewhat correct that a constant X10 stream would just simply raise havoc by delaying legit command, etc?

Yes, continuous X10 or INSTEON traffic, as well a severe continuous power line noise, will cause the interface to wait forever before it thinks it can send a command. I'm glad you pinpointed the problem!

Lost it again today. No abnormal activity in the log. Is there deeper debugging possible?

Here is a snap from the log. Just an unplug of the 2414U brought it back.

Code: Select all

13-Mar-09 4:01:50 PM
  Received INSTEON   "Dakota" on (button 6)
  Received INSTEON   "Dakota" off (button 6)

13-Mar-09 4:02:10 PM
  Received INSTEON   "Dakota" on (button 6)
  Received INSTEON   "Dakota" off (button 6)
  Script             varname: WindSpeed set to: 3.3
  Script             varname: WindGust set to: 5.6
  Received INSTEON   "Dakota" on (button 6)
  Received INSTEON   "Dakota" off (button 6)

13-Mar-09 4:02:44 PM
  Received INSTEON   "Dakota" on (button 6)
  Error              resending previous command (timeout)
  Error              resending previous command (timeout)
  Error              usb data write: timeout
  Error              usb data write: clearing pipes
  Error              usb data write: failed2 (0xE00002EB)
  Power Failure      possible power failure
  Error              usb data write: not open (closed during write)
  Error              lost connection with interface
  Trigger Action     Power Back Online daytime
  Trigger Action     Power off
  Email Sent         to "7783849311@pcs.rogers.com"; subject "Power dropped"
  Email Sent         to "heinz@bytedesigns.com, heinz@mac.com"; subject "Lakeside Power Failed"
  Indigo Cocoa client authenticated (192.168.2.244)
  Script             varname: WindSpeed set to: 3.5

13-Mar-09 4:03:43 PM
  Received RF        security command sensor alert (min delay) (ID 113)
  Script             (HouseSideDoor DS10A device ID 113)
  Action Group       HouseGarageCycle
  Trigger Action     GarageLight Trigger House WestDoor (113)
  Received RF        security command sensor alert (min delay) (ID 113)
  Script             (HouseSideDoor DS10A device ID 113)
  Action Group       HouseGarageCycle
  Received RF        security command sensor normal (min delay) (ID 113)
  Script             (HouseSideDoor DS10A device ID 113)
  Received RF        security command sensor alert (min delay) (ID 65)
  Script             (GarageSideDoor DS10A device ID 65)
  Received RF        security command sensor alert (min delay) (ID 65)
  Script             (GarageSideDoor DS10A device ID 65)
  Received RF        security command sensor normal (min delay) (ID 65)
  Script             (GarageSideDoor DS10A device ID 65)



BTW, the Dakota has been moved and unplugged several times since this mess started, thinking that it might need a reboot as well.

Does the problem always occur when the Dakota fires a command (via the EZSnsRF)? It sure looks like the EZSnsRF is putting something on the power line that is confusing the PowerLinc so badly that its ability to do USB communication with Indigo fails.

Next time it happens, try leaving the PowerLinc plugged in and unplugging the EZSnsRF.

Will do.

If that doesn't tell us anything I'll try and go "manual" lights for a few days

I can run multiple EZSnsRF's?
Have a spare coming so could try a Dakota setup from scratch and split a motion sensor off to the new one.

hwitten wrote:

I can run multiple EZSnsRF's?

I would think so. Just don't have them both responding the same hardware or you'll have collisions.

It dropped off on me again today, just as I was thinking all ok since it's been a while

Disconnected USB Cable and replaced it with a different one. Took a power off, I.e. unplug to bring the Interface back though.

A bit disheartening. While HA convenience is nice, a lot of my HA plans are security and house safeguards related. Makes me want to come up with a backup plan against Interface failure when not at home. Any ideas?

Heinz

Did you try unplugging the EZSnsRF first to see if that would unfreeze the PowerLinc? I'm wondering if it is putting a ton of commands on the power line and confusing the PowerLinc.

I knew there was something I had forgotten as next try

I did move it to another outlet but didn't do it as a first. Will do it next time. Adding it to my power off email.

It's been a while since last failure but today it went. Tried everything software-wise but could only get the 2414 back via an unplug.

Code: Select all

2009-04-26 20:36:47   Received INSTEON   "Dakota" on (button 5)
2009-04-26 20:36:47   Trigger Action   MD House Garage Light On
2009-04-26 20:36:51   Error   resending previous command (timeout)
2009-04-26 20:36:54   Error   resending previous command (timeout)
2009-04-26 20:36:54   Error   usb data write: timeout
2009-04-26 20:36:54   Error   usb data write: clearing pipes
2009-04-26 20:36:54   Error   usb data write: failed2 (0xE00002EB)
2009-04-26 20:36:54   Power Failure   possible power failure
2009-04-26 20:36:54   Error   usb data write: not open (closed during write)
2009-04-26 20:36:58   Error   lost connection with interface
2009-04-26 20:36:58   Trigger Action   Power off

Was unable to unplug the Dakota this time but it looks like it was involved again. Took this long due to low usage of that motion sensor. The one that got lots of traffic I had replaced with the crummy Insteon MD, which does work better with latest Indigo

I'm going to replace the Dakota tomorrow. Not looking forward to relinking Dakota stuff though.