Author Topic: Help with Insteon, please! (merkur2k and/or Aviator?)  (Read 3114 times)

mkbrown69

  • Guru
  • ****
  • Posts: 213
    • View Profile
Help with Insteon, please! (merkur2k and/or Aviator?)
« on: June 26, 2011, 04:45:52 am »
Hi Folks!

I'm hoping merkur2k and Aviator are monitoring... I've got a 10.04 install running, that I'm trying to migrate over my 2412S PLM from Misterhouse to LMCE for control.  I've looked through Trac tickets 1115 (Insteon PLM work) and 1112 (Insteon PnP detection), and tried implementing both.

I've set up an interface using Template 2103, and I put the PLM detection script from Trac#1112 in /usr/pluto/pnp (which I also symlinked from InsteonPLM.sh to 88_InsteonPLM.sh, to correspond with the Wiki instructions for Insteon).  So far, I'm not having any joy...

From the logs, I get this...

Code: [Select]
== ATTEMPT FRESH START ==
1 06/25/11 21:57:09 /usr/pluto/bin/Spawn_Device.sh 54 (spawning-device) 17376 Dev: 54; Already Running list: 15,16,18,19,29,30,37,21,22,23,26,32,27,51,49,53,
== FRESH START ==
1 06/25/11 21:57:09 /usr/pluto/bin/Spawn_Device.sh 54 (spawning-device) device: 54 ip: localhost cmd_line: Insteon_PLM_DCE
0 06/25/11 21:57:09 54 (spawning-device) Entering 54
========== NEW LOG SECTION ==========
1 06/25/11 21:57:09 54 (spawning-device) Starting... 1
1 06/25/11 21:57:09 54 (spawning-device) Found /usr/pluto/bin/Insteon_PLM_DCE
05 06/25/11 21:57:09.867 Connection for client socket reported NEED RELOAD IP=127.0.0.1, device 54 last error 2 <0xb77db6d0>
05 06/25/11 21:57:09.867 The router must be reloaded before this device is fully functional <0xb77db6d0>
05 06/25/11 21:57:09.870 void ClientSocket::Disconnect() on this socket: 0x807e0a0 (m_Socket: 5) <0xb77db6d0>
05 06/25/11 21:57:09.877 Connection for client socket reported NEED RELOAD IP=127.0.0.1, device 54 last error 2 <0xb77db6d0>
05 06/25/11 22:03:54.274 Got a reload command from 0  <0xb63d8b70>
05 06/25/11 22:03:54.535 void ClientSocket::Disconnect() on this socket: 0x807e310 (m_Socket: 7) <0xb77db6d0>
Return code: 2
2 06/25/11 22:03:55 54 (spawning-device) Device requests restart... count=1/50 dev=54
Sat Jun 25 22:03:55 EDT 2011 Restart
========== NEW LOG SECTION ==========
1 06/25/11 22:04:05 54 (spawning-device) Starting... 1
1 06/25/11 22:04:07 54 (spawning-device) Found /usr/pluto/bin/Insteon_PLM_DCE
05 06/25/11 22:04:09.027 Connect() failed, Error Code 111 (Connection refused)) <0xb77f36d0>
05 06/25/11 22:04:10.028 Connect() failed, Error Code 111 (Connection refused)) <0xb77f36d0>
05 06/25/11 22:04:11.029 Connect() failed, Error Code 111 (Connection refused)) <0xb77f36d0>
05 06/25/11 22:04:12.031 Connect() failed, Error Code 111 (Connection refused)) <0xb77f36d0>
05 06/25/11 22:04:13.033 Connect() failed, Error Code 111 (Connection refused)) <0xb77f36d0>
05 06/25/11 22:04:14.034 Connect() failed, Error Code 111 (Connection refused)) <0xb77f36d0>
05 06/25/11 22:04:15.039 Connect() failed, Error Code 111 (Connection refused)) <0xb77f36d0>
== ATTEMPT FRESH START ==
1 06/25/11 22:34:31 /usr/pluto/bin/Spawn_Device.sh 54 (spawning-device) 14314 Dev: 54; Already Running list: 15,16,18,19,29,30,49,
== FRESH START ==
1 06/25/11 22:34:31 /usr/pluto/bin/Spawn_Device.sh 54 (spawning-device) device: 54 ip: localhost cmd_line: Insteon_PLM_DCE
0 06/25/11 22:34:31 54 (spawning-device) Entering 54
========== NEW LOG SECTION ==========
1 06/25/11 22:34:31 54 (spawning-device) Starting... 1
1 06/25/11 22:34:31 54 (spawning-device) Found /usr/pluto/bin/Insteon_PLM_DCE
05 06/25/11 22:37:58.951 Got a reload command from 0  <0xb63c9b70>
05 06/25/11 22:37:59.632 void ClientSocket::Disconnect() on this socket: 0x99f5310 (m_Socket: 7) <0xb77cc6d0>
Return code: 2
2 06/25/11 22:38:00 54 (spawning-device) Device requests restart... count=1/50 dev=54
Sat Jun 25 22:38:00 EDT 2011 Restart
========== NEW LOG SECTION ==========
1 06/25/11 22:38:09 54 (spawning-device) Starting... 1
1 06/25/11 22:38:09 54 (spawning-device) Found /usr/pluto/bin/Insteon_PLM_DCE
05 06/25/11 22:38:11.036 Connect() failed, Error Code 111 (Connection refused)) <0xb77396d0>

I'm presuming merkur2k has only recently started working on the DCE device for the PLM, given the recent date on the trac ticket.  Could you help me out with this?  I can provide testing info for you...

Thanks!

/Mike

merkur2k

  • Addicted
  • *
  • Posts: 513
    • View Profile
Re: Help with Insteon, please! (merkur2k and/or Aviator?)
« Reply #1 on: June 26, 2011, 06:51:53 pm »
the DCE device 2103 is in VERY early development stages right now, it does not even do anything useful.
You may have more luck with the GSD device 1932 since it is more complete, but i have not worked with this one so i do not know how well it works.

mkbrown69

  • Guru
  • ****
  • Posts: 213
    • View Profile
Re: Help with Insteon, please! (merkur2k and/or Aviator?)
« Reply #2 on: June 27, 2011, 06:10:48 am »
Thanks for the quick response!

I'm having enough issues with 10.04 that I think I'll blow it away and re-install with 8.10, and then try again with template 1932.  I've tried it with 10.04, and all I get is mangled data.  I'm also having trouble getting 1-wire working, so I'm hoping both will work better on 8.10

Thanks for your help on this!

/Mike