ConnectToMyHub() Succeeds but get unknown command errors and ListDevices() returns nothing

[James Beldock]

InsteonTerminal (git commit 030fb16) claims to connect successfully to my Hub 2 (2245-555, 0x03, 0x33).  The terminal reads:

>>> connectToMyHub()
Connecting
Connected

Within seconds I get these errors:

>>> 01:20:22.979 [Thread-2] WARN  us.pfrommer.insteon.msg.MsgReader - got unknown command code 50
01:20:30.008 [Thread-2] WARN  us.pfrommer.insteon.msg.MsgReader - got unknown command code 50
01:20:34.441 [Thread-2] WARN  us.pfrommer.insteon.msg.MsgReader - got unknown command code 51

I've seen unknown command codes 50, 51, 53, and 4C.  When I attempt to ListDevices(), I get nothing:

listDevices()

And if I try modem.getdb(), I get this error:

>>>modem.getdb()
Traceback (most recent call last):
  File "<string>", line 1, in <module>
NameError: name 'modem' is not defined

Please share advice!

Thank you,

-James

[James Beldock]

In case it's helpful, I turned on debug logging and see the following when unknown commands are being received:

01:30:44.859 [Thread-2] DEBUG us.pfrommer.insteon.msg.IOPort - Msg received: IN:Cmd:0x62|toAddress:53.C2.78|messageFlags:0x00=DIRECT:0:0|command1:0x0F|command2:0x00|ACK/NACK:0x06|
01:30:44.915 [Thread-2] TRACE us.pfrommer.insteon.msg.MsgReader - processing data: len 11 data: 025C53C2784E8C1C230F00
01:30:44.915 [Thread-2] TRACE us.pfrommer.insteon.msg.MsgReader - header length expected: -1 extended: false
01:30:44.919 [Thread-2] WARN  us.pfrommer.insteon.msg.MsgReader - got unknown command code 53
01:30:45.854 [Thread-2] TRACE us.pfrommer.insteon.msg.MsgReader - read buffer: len 9 data: 02624CDB3D000F0006
01:30:45.855 [Thread-2] TRACE us.pfrommer.insteon.msg.MsgReader - processing data: len 9 data: 02624CDB3D000F0006
01:30:45.855 [Thread-2] TRACE us.pfrommer.insteon.msg.MsgReader - header length expected: 6 extended: false
01:30:45.855 [Thread-2] TRACE us.pfrommer.insteon.msg.MsgReader - msgLen expected: 9
01:30:45.856 [Thread-2] TRACE us.pfrommer.insteon.msg.MsgReader - keeping buffer len 0 data:
01:30:45.856 [Thread-2] DEBUG us.pfrommer.insteon.msg.IOPort - Msg received: IN:Cmd:0x62|toAddress:4C.DB.3D|messageFlags:0x00=DIRECT:0:0|command1:0x0F|command2:0x00|ACK/NACK:0x06|
01:30:45.856 [Thread-2] TRACE us.pfrommer.insteon.msg.MsgReader - processing data: len 0 data:
01:30:45.856 [Thread-2] TRACE us.pfrommer.insteon.msg.MsgReader - msgLen expected: -1
01:30:45.857 [Thread-2] TRACE us.pfrommer.insteon.msg.MsgReader - keeping buffer len 0 data:
01:30:46.859 [Thread-2] TRACE us.pfrommer.insteon.msg.MsgReader - read buffer: len 11 data: 025C4CDB3D4E8C1C230F00
01:30:46.860 [Thread-2] TRACE us.pfrommer.insteon.msg.MsgReader - processing data: len 11 data: 025C4CDB3D4E8C1C230F00
01:30:46.860 [Thread-2] TRACE us.pfrommer.insteon.msg.MsgReader - header length expected: -1 extended: false
01:30:46.860 [Thread-2] WARN  us.pfrommer.insteon.msg.MsgReader - got unknown command code 4C
01:30:49.873 [Thread-2] TRACE us.pfrommer.insteon.msg.MsgReader - read buffer: len 4 data: 027F0206
01:30:49.874 [Thread-2] TRACE us.pfrommer.insteon.msg.MsgReader - processing data: len 4 data: 027F0206
01:30:49.874 [Thread-2] TRACE us.pfrommer.insteon.msg.MsgReader - header length expected: 2 extended: false
01:30:49.874 [Thread-2] TRACE us.pfrommer.insteon.msg.MsgReader - msgLen expected: 4
01:30:49.874 [Thread-2] TRACE us.pfrommer.insteon.msg.MsgReader - keeping buffer len 0 data:
01:30:49.874 [Thread-2] DEBUG us.pfrommer.insteon.msg.IOPort - Msg received: IN:Cmd:0x7F|Command2:0x02|ACK/NACK:0x06|
01:30:49.875 [Thread-2] TRACE us.pfrommer.insteon.msg.MsgReader - processing data: len 0 data:
01:30:49.875 [Thread-2] TRACE us.pfrommer.insteon.msg.MsgReader - msgLen expected: -1
01:30:49.875 [Thread-2] TRACE us.pfrommer.insteon.msg.MsgReader - keeping buffer len 0 data:

Cheers,

-James

[nhoe...@sinet.ca]

I am not sure what a 2245-555 is - I could find very few Internet hits. Although insteon-terminal claims it connected to the hub, it looks like the modem was not set up properly.  In addition to Connecting/Connected responses, I also get "Terminal ready!".  

Have you double-checked the hub configuration in init.py?   You need to update the last line below with the IP address of the hub and the username/password from the underside of the hub.

def connectToMyHub():
    """connects to my insteon hub modem at pre-defined address""" 

    connectToHub("insteonhub", 25105, 1000, "MyHubLogin", "MyHubPassword")

On Saturday, May 14, 2022 at 6:25:01 PM UTC-7 James Beldock wrote:

InsteonTerminal (git commit 030fb16) claims to connect successfully to my Hub 2 (2245-555, 0x03, 0x33).  The terminal reads:

>>> connectToMyHub()
Connecting
Connected

[Terry Wells]

Got bit by the same problem.

You have to read all the way to the end of init.py.  There is a list of commented devices at the bottom.

If all you want is the modem, then uncomment that one and update its address to match your Hub.  The address is printed on the back of the Hub above the username and password.