We have moved at community.getvera.com

Author Topic: [bug] Altsteon binaries dissapear, Insteon not working -- no errors logged?  (Read 1627 times)

Offline Aaron

  • Hero Member
  • *****
  • Posts: 1985
  • Karma: +61/-193
*Altsteon v0.5*

Bug found... Altseon "seems" to properly load/run when the binaries are missing from \overlay\sbin

HOW the binaries disappeared eludes me since I made no system changes. As you can see from the logs, during Vera's boot, Vera 'thinks' Altsteon is loading properly and checking in all the Insteon devices. But, of course, the devices do not respond when sent a command. Also, there is no error that is thrown when trying to send a command to a binary (Altsteon) that does not exist?

I have attached a log of the Vera boot/startup.
Here's the portion of a log when trying to turn on/off 2 separate devices...
Code: [Select]
08 02/16/13 10:46:41.303 JobHandler_LuaUPnP::HandleActionRequest device: 45 service: urn:upnp-org:serviceId:Dimming1 action: ctrl_chr[36;1mSetLoadLevelTargetctrl_chr[0m <0x2ffa5680>
08 02/16/13 10:46:41.304 JobHandler_LuaUPnP::HandleActionRequest argument DeviceNum=45 <0x2ffa5680>
08 02/16/13 10:46:41.304 JobHandler_LuaUPnP::HandleActionRequest argument serviceId=urn:upnp-org:serviceId:Dimming1 <0x2ffa5680>
08 02/16/13 10:46:41.304 JobHandler_LuaUPnP::HandleActionRequest argument action=SetLoadLevelTarget <0x2ffa5680>
08 02/16/13 10:46:41.304 JobHandler_LuaUPnP::HandleActionRequest argument newLoadlevelTarget=0 <0x2ffa5680>
08 02/16/13 10:46:41.304 JobHandler_LuaUPnP::HandleActionRequest argument rand=0.7225738289909723 <0x2ffa5680>
50 02/16/13 10:46:41.305 luup_log:29: Setting dimmer to 0 <0x2ffa5680>
50 02/16/13 10:46:41.306 luup_log:29: Sending (setloadleveltarget) : "17.3a.2c" instant_dim 0
<0x2ffa5680>
08 02/16/13 10:46:45.110 JobHandler_LuaUPnP::HandleActionRequest device: 44 service: urn:upnp-org:serviceId:Dimming1 action: ctrl_chr[36;1mSetLoadLevelTargetctrl_chr[0m <0x2eda5680>
08 02/16/13 10:46:45.110 JobHandler_LuaUPnP::HandleActionRequest argument DeviceNum=44 <0x2eda5680>
08 02/16/13 10:46:45.110 JobHandler_LuaUPnP::HandleActionRequest argument serviceId=urn:upnp-org:serviceId:Dimming1 <0x2eda5680>
08 02/16/13 10:46:45.110 JobHandler_LuaUPnP::HandleActionRequest argument action=SetLoadLevelTarget <0x2eda5680>
08 02/16/13 10:46:45.110 JobHandler_LuaUPnP::HandleActionRequest argument newLoadlevelTarget=100 <0x2eda5680>
08 02/16/13 10:46:45.111 JobHandler_LuaUPnP::HandleActionRequest argument rand=0.5258315995082126 <0x2eda5680>



« Last Edit: February 17, 2013, 01:03:05 pm by Aaron »

Offline garrettwp

  • Master Member
  • *******
  • Posts: 6371
  • Karma: +227/-128
  • Vera 3, Lite, ISY994
Re: Insteon devices no longer working - PLM seems fine
« Reply #1 on: February 16, 2013, 12:56:58 pm »
Are you using Altsteon or Vera's built in insteon support? If altsteon, have you loaded up the command line and try to interact with the plm?

- Garrett

Offline Aaron

  • Hero Member
  • *****
  • Posts: 1985
  • Karma: +61/-193
Re: Insteon devices no longer working - PLM seems fine
« Reply #2 on: February 16, 2013, 12:58:38 pm »
Are you using Altsteon or Vera's built in insteon support? If altsteon, have you loaded up the command line and try to interact with the plm?

- Garrett

Sorry I should have noted... Altsteon

Offline Aaron

  • Hero Member
  • *****
  • Posts: 1985
  • Karma: +61/-193
Re: Insteon devices no longer working - PLM seems fine
« Reply #3 on: February 17, 2013, 12:55:39 pm »
SOLVED - kinda - I updated post #1

To me the log looked fine so I decided to go troubleshoot using CLI... much to my surprise both the binaries were gone, not in \overlay\sbin

I had made no modifications to the system so why they were gone eludes me.

But what is more mysterious is why there were no errors in the log and Altsteon "seemed" to be running and identifying my Insteon devices?

FBA -- please look into this. I suggest removing your binaries from \overlay\sbin and testing the results.

« Last Edit: February 17, 2013, 01:03:30 pm by Aaron »