Unable to parse Insteon Address [OE.FE.CE] into parts.

[Osler]

Scott:

Just had a power outage to the HB computer and ended up with a corrupted DB (got "record deleted" at system start-up). The outage occured because I was installing some new insteon switches on the breaker the the server is on (stupid me).

Now when I go and attempt to add the new switch, HB gives me the above error code and continues to complain. I appear to still be able to control my other insteon equipment, although the time between the telling HB to dim the light and it actually dimming is quite long.

I actually restored from a backed up config file. Then also reinstalled HB 3.30. Then reinstalled by drivers for my USB to serial thingamajiggies. I am still getting this error though. When I try to delete the device I just get an hour glass with continued error beeps in the backgroun...HB won't let me get rid of the thing.

DUMP FILE:

Code: Select all

====== Begin Dump - Saturday, January 10, 2009 17:58:24 ======
Server Version = 3.30

==================================
======== House Server Thread =======
==================================
Thread Type    = Main UI Thread
Thread ID   = 68C
Exception code: E06D7363 
Fault address:  7C812A5B 01:00011A5B C:\WINDOWS\system32\kernel32.dll

Registers:
EAX:0012F2A4
EBX:086DAFF8
ECX:00000000
EDX:00000000
ESI:0012F32C
EDI:00000007
CS:EIP:001B:7C812A5B
SS:ESP:0023:0012F2A0  EBP:0012F2F4
DS:0023  ES:0023  FS:003B  GS:0000
Flags:00040206

Call stack:
Address   Frame
7C812A5B  0012F2F4  RaiseException+52
7857DBF9  0012F32C  CxxThrowException+48
7862E3D7  0012F340  Ordinal1252+1B


====== End Dump ======

====== Begin Dump - Saturday, January 10, 2009 17:59:07 ======
Server Version = 3.30

==================================
======== House Server Thread =======
==================================
Thread Type    = Main UI Thread
Thread ID   = 190
Exception code: E06D7363 
Fault address:  7C812A5B 01:00011A5B C:\WINDOWS\system32\kernel32.dll

Registers:
EAX:0012F2A4
EBX:086EB128
ECX:00000000
EDX:00000000
ESI:0012F32C
EDI:00000007
CS:EIP:001B:7C812A5B
SS:ESP:0023:0012F2A0  EBP:0012F2F4
DS:0023  ES:0023  FS:003B  GS:0000
Flags:00040206

Call stack:
Address   Frame
7C812A5B  0012F2F4  RaiseException+52
7857DBF9  0012F32C  CxxThrowException+48
7862E3D7  0012F340  Ordinal1252+1B


====== End Dump ======

====== Begin Dump - Saturday, January 10, 2009 17:59:47 ======
Server Version = 3.30

==================================
======== House Server Thread =======
==================================
Thread Type    = Main UI Thread
Thread ID   = FC
Exception code: E06D7363 
Fault address:  7C812A5B 01:00011A5B C:\WINDOWS\system32\kernel32.dll

Registers:
EAX:0012F2A4
EBX:086EB278
ECX:00000000
EDX:00000000
ESI:0012F32C
EDI:00000007
CS:EIP:001B:7C812A5B
SS:ESP:0023:0012F2A0  EBP:0012F2F4
DS:0023  ES:0023  FS:003B  GS:0000
Flags:00040206

Call stack:
Address   Frame
7C812A5B  0012F2F4  RaiseException+52
7857DBF9  0012F32C  CxxThrowException+48
7862E3D7  0012F340  Ordinal1252+1B


====== End Dump ======

====== Begin Dump - Saturday, January 10, 2009 18:00:32 ======
Server Version = 3.30

==================================
======== House Server Thread =======
==================================
Thread Type    = Main UI Thread
Thread ID   = 5B8
Exception code: E06D7363 
Fault address:  7C812A5B 01:00011A5B C:\WINDOWS\system32\kernel32.dll

Registers:
EAX:0012F2A4
EBX:086EAEF0
ECX:00000000
EDX:00000000
ESI:0012F32C
EDI:00000007
CS:EIP:001B:7C812A5B
SS:ESP:0023:0012F2A0  EBP:0012F2F4
DS:0023  ES:0023  FS:003B  GS:0000
Flags:00040206

Call stack:
Address   Frame
7C812A5B  0012F2F4  RaiseException+52
7857DBF9  0012F32C  CxxThrowException+48
7862E3D7  0012F340  Ordinal1252+1B


====== End Dump ======

====== Begin Dump - Saturday, January 10, 2009 18:17:31 ======
Server Version = 3.30

==================================
======== House Server Thread =======
==================================
Thread Type    = Device Thread [X10 Security Sensor] - [Pool Level]
Thread ID   = 96C
Exception code: C0000005 ACCESS_VIOLATION
Fault address:  0164998F 00:00000000 

Registers:
EAX:787F06C8
EBX:00000004
ECX:01652D90
EDX:08C44748
ESI:00E8DC68
EDI:05351008
CS:EIP:001B:0164998F
SS:ESP:0023:0A38F7AC  EBP:0A38F7AC
DS:0023  ES:0023  FS:003B  GS:0000
Flags:00010202

Call stack:
Address   Frame
0164998F  0A38F7AC  0000:00000000 
00453C0A  08C43690  CxIOFile::~CxIOFile+50C8A


====== End Dump ======

====== Begin Dump - Saturday, January 10, 2009 18:35:18 ======
Server Version = 3.30
Exception code: C0000005 ACCESS_VIOLATION
Fault address:  0048CDB6 01:0008BDB6 C:\Program Files\HouseBot\HouseBotServer.exe

Registers:
EAX:030404FF
EBX:08772700
ECX:08D19008
EDX:78841288
ESI:08D19008
EDI:0167C848
CS:EIP:001B:0048CDB6
SS:ESP:0023:0143EF9C  EBP:0167C848
DS:0023  ES:0023  FS:003B  GS:0000
Flags:00010202

Call stack:
Address   Frame
0048CDB6  0167C848  CxIOFile::~CxIOFile+89E36
08771FF8  005AA7E4  0000:00000000 
00422DE0  00425A30  CxIOFile::~CxIOFile+1FE60
FFFFD348  E8F18B56  0000:00000000 


====== End Dump ======

====== Begin Dump - Saturday, January 10, 2009 18:41:07 ======
Server Version = 3.30

==================================
======== House Server Thread =======
==================================
Thread Type    = Device Thread [X10 Security Sensor] - [Pool Level]
Thread ID   = 654
Exception code: C0000005 ACCESS_VIOLATION
Fault address:  08C13680 00:00000000 

Registers:
EAX:08C5ED38
EBX:00000004
ECX:01682E38
EDX:0166D440
ESI:0132DC70
EDI:01682E38
CS:EIP:001B:08C13680
SS:ESP:0023:0A39F7A8  EBP:0A39F7AC
DS:0023  ES:0023  FS:003B  GS:0000
Flags:00010202

Call stack:
Address   Frame
08C13680  0A39F7AC  0000:00000000 
00453C0A  08C5EB98  CxIOFile::~CxIOFile+50C8A


====== End Dump ======

====== Begin Dump - Saturday, January 10, 2009 18:44:43 ======
Server Version = 3.30

==================================
======== House Server Thread =======
==================================
Thread Type    = Device Thread [X10 Security Sensor] - [Pool Level]
Thread ID   = 938
Exception code: C0000005 ACCESS_VIOLATION
Fault address:  787F06C6 01:0020F6C6 C:\WINDOWS\WinSxS\x86_Microsoft.VC90.MFC_1fc8b3b9a1e18e3b_9.0.30729.1_x-ww_405b0943\mfc90.dll

Registers:
EAX:08DD6308
EBX:00000004
ECX:08D041B8
EDX:08A6FD68
ESI:00E8DC18
EDI:08D041B8
CS:EIP:001B:787F06C6
SS:ESP:0023:0A38F7AC  EBP:0A38F7AC
DS:0023  ES:0023  FS:003B  GS:0000
Flags:00010206

Call stack:
Address   Frame
787F06C6  0A38F7AC  Ordinal4337+10
00453C0A  08D498B8  CxIOFile::~CxIOFile+50C8A


====== End Dump ======

====== Begin Dump - Saturday, January 10, 2009 18:47:54 ======
Server Version = 3.30

==================================
======== House Server Thread =======
==================================
Thread Type    = Device Thread [X10 Security Sensor] - [Pool Level]
Thread ID   = 748
Exception code: C0000005 ACCESS_VIOLATION
Fault address:  00453BEB 01:00052BEB C:\Program Files\HouseBot\HouseBotServer.exe

Registers:
EAX:08D13FF8
EBX:00000004
ECX:08D5ADE0
EDX:08A80DB8
ESI:0132DC70
EDI:08D5C7F0
CS:EIP:001B:00453BEB
SS:ESP:0023:0A39F7B8  EBP:08D5C7F0
DS:0023  ES:0023  FS:003B  GS:0000
Flags:00010217

Call stack:
Address   Frame
00453BEB  08D5C7F0  CxIOFile::~CxIOFile+50C6B


====== End Dump ======

====== Begin Dump - Saturday, January 10, 2009 19:03:09 ======
Server Version = 3.30

==================================
======== House Server Thread =======
==================================
Thread Type    = Device Thread [X10 Security Sensor] - [Pool Level]
Thread ID   = B4C
Exception code: C0000005 ACCESS_VIOLATION
Fault address:  787F06C6 01:0020F6C6 C:\WINDOWS\WinSxS\x86_Microsoft.VC90.MFC_1fc8b3b9a1e18e3b_9.0.30729.1_x-ww_405b0943\mfc90.dll

Registers:
EAX:089CF308
EBX:00000004
ECX:089041B8
EDX:07285C78
ESI:00E8DC18
EDI:089041B8
CS:EIP:001B:787F06C6
SS:ESP:0023:09F8F7AC  EBP:09F8F7AC
DS:0023  ES:0023  FS:003B  GS:0000
Flags:00010206

Call stack:
Address   Frame
787F06C6  09F8F7AC  Ordinal4337+10
00453C0A  08908008  CxIOFile::~CxIOFile+50C8A


====== End Dump ======

====== Begin Dump - Saturday, January 10, 2009 19:10:02 ======
Server Version = 3.30

==================================
======== House Server Thread =======
==================================
Thread Type    = Device Thread [X10 Security Sensor] - [Pool Level]
Thread ID   = 41C
Exception code: C0000005 ACCESS_VIOLATION
Fault address:  01676A9C 00:00000000 

Registers:
EAX:0890F478
EBX:00000004
ECX:016824C8
EDX:01673348
ESI:0132DC18
EDI:016824C8
CS:EIP:001B:01676A9C
SS:ESP:0023:0A09F7A8  EBP:0A09F7AC
DS:0023  ES:0023  FS:003B  GS:0000
Flags:00010286

Call stack:
Address   Frame
01676A9C  0A09F7AC  0000:00000000 
00453C0A  089161B8  CxIOFile::~CxIOFile+50C8A


====== End Dump ======

Osler

[Osler]

Ok...this is my fault for putting an O ("Oh") instead of a 0 (zero) in the device address. Still, HB could have handle an invalid insteon address a bit better.

Osler

[ScottBot]

So the problem was that because you used an 'oh' instead of a zero it was crashing? And it's working for you now?

[Osler]

Yes, after I put in the wrong address and tried to get the status, it just kept trying the address over and over, giving the error each time. I couldn't get it to stop by aborting the status update. Finally, I tried to delete the device, got the hour glass and waited...finally had to force HB to quit via Task Manager. At the next restart the device appeared to be deleted as it no longer showed up in my device list.

And yes, changing the Oh to a zero fixed this.

Osler

[ScottBot]

What type of Insteon Hardware Interface are you using?

[Osler]

PLM

[ScottBot]

When I try and send a command via the PLM with an invalid address (with O's), I get an error message about an invalid address format.

Do you see this when you try and send a power state change to an invalid address, or is something else happening (like receiving a command or something in the PLM configuration).

[Osler]

This is the sequence of events that got me to the error message:

1. Create a new switch device and at the end, populate the id with Oh instead of zero.

2. Open new device and change get status to yes.

It was when I went directly to the hardware interface and put in the device id to make sure it was linked (with Oh instead of zero) that I got some type of message about the device id being invalid. This is what led me to the id as the underlying problem.

Prior to all of this, the new switch had just been installed and manually linked to the PLM.

Osler