Eloy and Dave,

I updated master to prevent this error from occurring.  You should be able to hold down a remotelinc button without crashing now.

Kevin


On Tue, Mar 19, 2013 at 7:49 PM, Dave Stenhouse <dave@stenhouse.us> wrote:
On 03/19/2013 07:25 PM, Eloy Paris wrote:
> Hi Kevin,
>
> On 03/19/2013 06:00 PM, Kevin Robert Keegan wrote:
>
>> Yup, that looks like an error.
>>
>> I don't own a remotelinc, but it looks like the error is as follows:
>> 1. You press and hold a remote link button (which acts like a dimmer
>> apparently)
> Ahhh, this was it! This explains why I could not reproduce -- I never
> keep pressed buttons in the RemoteLinc. But, my son definitely has in
> the past, and last night a book fell on top of the RemoteLinc and
> pressed some buttons, which caused the crash (I thought it could have
> been a combination of multiple button presses and never thought it was a
> single button kept pressed).
>
> But you are right -- I just tried keeping a button pressed and sure
> enough MisterHouse crashed again with the same message :-)
>
>> 2. This sends a start_manual_change command to MH
>> 3. You release the remote link button
>> 4. This sends a stop_manual_change command to MH
>> 5. B/c of how MH is designed, MH now sends a status request to the
>> remote link asking it to identify its "on-level" basically asking the
>> remote link "ok, I see you started dimming something, how far did you
>> dim it?"
>> 6. The remote link responds back with an on-level (the fact that it
>> responds I did not expect)
>> 7. MH tries to call the level sub to set the device state in MH to the
>> proper level, but level is not a sub in the remote link module so we crash.
> Wow, great analysis without having access to one of these devices.
> Impressive!
>
>> Simple solution, add the level sub to the remote.  This can either be
>> copied from the lighting module, or we can possibly cross reference to
>> cut down on duplicate code, depending on what it does.  (I think it just
>> verifies that a level is valid)
>>
>> More complicated, are all remotes level capable? Do we need some
>> distinction like we have for RELAY devices?  Does it even matter?
> Hhhmmm, no idea. I didn't even know that the RemoteLinc can be used to
> dim devices. That's nice to know although out of a dozen or so INSTEON
> light switches that I have in my house, only one is a dimmer.
>
>>    AFAIK, we don't ever set the state of the remote link, so having a
>> level command for a device that doesn't support dimming shouldn't be an
>> issue since no set command is sent to the device? Is that true?  I see
>> that the remote link responds to a status_request, a bit surprising for
>> a battery device.  Does it stay awake for some period of time after
>> sending a command and then sleep?
>>
>> All questions I can't answer without a device.  I am willing to make
>> code changes if you are willing to be a guinea pig as well as to provide
>> some technical details for me.
> Sure, I am more than happy to be a lab rat for you; just let me know
> what you'd like me to test.
>
> Cheers!
>
> Eloy Paris.-
>
>>
>> On Tue, Mar 19, 2013 at 1:56 PM, Eloy Paris <peloy@chapus.net
>> <mailto:peloy@chapus.net>> wrote:
>>
>>      Every now and then my MisterHouse crashes after pressing some button
>>      in a RemoteLinc. The message generated by Perl is:
>>
>>      Can't locate object method "level" via package "Insteon::RemoteLinc"
>>      at /opt/misterhouse/bin/../lib/__Insteon/BaseInsteon.pm line 443.
>>
>>      Unfortunately, I'd have to do some testing to figure out the exact
>>      sequence of events because, while I've seen the crash before, I
>>      cannot recreate by pressing all the buttons of the RemoteLinc.
>>
>>      Note that my RemoteLinc is configured probably in a "strange" way --
>>      instead of using INSTEON scenes linked to the RemoteLinc buttons
>>      directly, I just linked the buttons to my PLM and then configured
>>      button press actions in MH user code. I figured it was easier to do
>>      it this way than doing it the "proper" way with INSTEON scenes. I
>>      doubt this has anything to do with the crash, though.
>>
>>      Full log attached, if anyone is interested in taking a look.
>>
>>      Cheers,
>>
>>      Eloy Paris.-
>>
>>      P.S. Running git master updated a couple of weeks ago, but this
>>      problem has been in the code for a long time (since the old
>>      "insteon" branch in SVN).
>>
>
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_d2d_mar
> ________________________________________________________
> To unsubscribe from this list, go to: http://sourceforge.net/mail/?group_id=1365
>
I also have a remote linc, and can do some guinea pigging if that would
be helpful.


------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar
________________________________________________________
To unsubscribe from this list, go to: http://sourceforge.net/mail/?group_id=1365