Jump to content

Mobilinc and Keypadlinc issues


binaryman

Recommended Posts

Posted

So I have an 8 button keypad, and shows up in mobilinc fine. All the buttons work fine, except for 2...

 

One button is setup as a controller in my ISY for a Morninglinc deadbolt. When you push the button locally it locks and light turns off, push again and it unlocks and light goes on. In the ISY, this is a scene where the KPL is the controller, and the morninglinc as the responder (actually the morninglinc shows up as two devices, one for off command one for on. both are added as responders one locking one unlocking). However, when I trigger this button in Mobilinc, all it does is lock. Hit it again and it locks again (and icon stays the same in mobilinc). Is there a reason this isn't working right? I tried triggering the scene instead thinking this may work better but same thing, won't turn the scene off (when just tapping the icon) just on (in fact weirder yet, if you tell the scene to go on it goes off, and vice versa)

 

Second button I'm having issues with is setup for my garage door with an iolinc. When you push the button locally, it tells the garage to open, or shut depending on if it's already open or shut. The light is triggered by the sensor, when the garage door is open the light is on, closed the light is off. This takes place in two scenes in the ISY, one where the keypadlinc button is the controller, the other the responder. When I hit this button in mobilinc, it just turns the light on and mobilinc shows that the door is open (even though the door didn't really open\close and may in fact be closed). When I hit this button locally, it works as expected. Any reason this isn't working right?

Posted

One must activate the scenes in mobilinc, rather than a controller of the scene. Devices act as controllers only when activated physically.

Posted

Ug. Wonder if its be possible for mobilinc to emulate the links/commands the button would send or if that's even possible..

 

Between limitations of mobilinc, and isy hard to keep my device status, kpl button status, and programs in sync.

Posted

I have mobilinc controlling my "garage" relay scene and the KPL lights up appropriately with the door being open or closed.

 

I followed the wiki to set it up for the garage door and have 3 keypads display the status, and 2 that control the door. Mobilinc shows the correct status based on the IO scene state for me.

 

I cannot get the attachment to open to see what you have there.

 

Alan

Posted

Per the wiki-

 

Devices in my garage relay scene:

kpl button as controller in toggle mode(for you I'd assume multiple kpl buttons)

iolinc as responder (responding to on or off)

 

devices in my garage door sensor scene:

kpl as responder (for you I'd assume multiple kpl buttons)

iolinc sensor as controller

 

When I tap or turn on\off the garage relay scene in mobilinc, it just makes the kpl button light go on or off, but garage door doesn't open\close. If I use the iolinc device it does make the garage door open close. Right now I have the iolinc as the open\close button in mobilinc, and the iolinc sensor to show the status. I'd just like to be able to have one favorite that shows the status, that I can tap to open\close (like how the kpl button works). Is this possible? Is this what you did somehow arw01 or am I mistaken.

Posted

I don't control the SCENE from mobilinc, I control the IO relay device. Since the scene is linked to the IO lincs state, they come on and off on their own. Try controlling the device directly and observing your keypad lights and garage door.

 

Alan

 

So I have mine in mobilinc as Garage_door_IO-Relay (that I control and that causes the garage to open or close just like hitting the button in the garage)

 

and the Garage_door_IO_Sensor is the controller for the scene that the keypads respond too. They button on the keypads is also a controller for the IO Relay I suppose on two of the three.

 

Alan

Posted

Yep that's exactly how I have mine and how it works. But this means in mobilinc I need two devices as favorites in order to show status as well as control. I just like simplicity :)

Posted
When I tap or turn on\off the garage relay scene in mobilinc, it just makes the kpl button light go on or off, but garage door doesn't open\close.

 

That is interesting. Tapping the scene works for me.

 

Using the relay device directly in mobilinc...I recall a discussion that such an approach (direct commands) may result in leaving the relay permanently (until next command) in that state (ON or OFF). I believe the theory was that the IOLinc settings (momentary) were effective only if triggered by a scene command. Perhaps I am remembering incorrectly. Perhaps it does not matter. Certainly, I have never tested this personally.

 

I'd just like to be able to have one favorite that shows the status, that I can tap to open\close (like how the kpl button works). Is this possible?
But this means in mobilinc I need two devices as favorites in order to show status as well as control. I just like simplicity

In an earlier, but recent, post, someone (Xathros, I believe) came up with a pretty slick approach to this, but I think it works only with the iOS version of mobilinc. I recall that it was based upon using programs to actuate the door, and variables, and taking advantage of the iOS customization of mobilinc program status.

 

Like you, I do not have a single favorite which shows status AND controls the door. However, I tend to rely on video cameras to confirm status of garage when away.

Posted

binaryman,

 

See this post on page 2 where I describe my personal setup to controlling my garage door with a KPL and keeping it all in sync with MobiLinc using just one scene and one program for status and control:

viewtopic.php?f=53&t=7146&start=15

 

You and I have been emailing on this topic, so I thought I'd share part of my latest email response to you for other's reading this:

 

"You can’t directly control KPL buttons from Admin Console or MobiLinc. This is an INSTEON limitation. Instead you control the status of the KPL button through the scene it’s attached to. So, in MobiLinc when you tap the KPL button icon, MobiLinc looks to see what scene that KPL button is a CONTROLLER of and sends the ON or OFF command to that scene. The result looks like the KPL was turned on or off when in fact we’re actually controlling the scene where that KPL button is a controller."

 

In fact this is true of all devices. Anytime you tap a device icon (not the direct device commands found in the device details), MobiLinc looks to see if that device is in a scene as a CONTROLLER. If it is, MobiLinc will redirect the ON/OFF command to the scene instead. This mimics the real-world behavior if you walked up to the physical device and turned it on or off.

 

Hopefully this info helps.

 

Wes

Posted
MobiLinc looks to see what scene that KPL button is a CONTROLLER of and sends the ON or OFF command to that scene

I am sure I have heard this before and forgotten. Given this, I must then assume that there is another explanation for why this is not working for binaryman:

 

When I hit this button in mobilinc, it just turns the light on and mobilinc shows that the door is open (even though the door didn't really open\close and may in fact be closed). When I hit this button locally, it works as expected. Any reason this isn't working right?

 

Perhaps it is just one of those cellular data things.

Posted

binaryman,

 

As I requested in my email to you, I think we need to see your exact scene definition for all the relevant scenes and KPL buttons to be able to help move this to a solution. There's some piece of info we don't have about your setup that's preventing us from diagnosing the root of the problem.

 

Wes

Posted

Yes, I agree with Wes. Based on what I understand, this is properly set up. Failure to work as expected could be the result of a variety of causes. Isolating to a specific cause will require additional information, such as scene definitions and further troubleshooting steps.

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...