Issues Adding Device and Inconsistent Communication

[chris87]

Right click on I/O Linc relay node, click Options at the bottom of the right side, click Query button in the Options popup.

 

Also click Help | About to confirm the update to 4.2.15 was successful. 

It appears that my update was successful.  This is what I see in the log when I click Query:

 

Sun 09/28/2014 09:26:12 PM : [iNST-TX-I1  ] 02 62 2B F9 CD 0F 1F 02

 

Sun 09/28/2014 09:26:12 PM : [iNST-ACK    ] 02 62 2B.F9.CD 0F 1F 02 06          GOF    (02)

 

Sun 09/28/2014 09:26:12 PM : [iNST-SRX    ] 02 50 2B.F9.CD 2C.08.F0 27 1F 00    GOF    (FLAGS)

 

Sun 09/28/2014 09:26:12 PM : [std-Direct Ack] 2B.F9.CD-->ISY/PLM Group=0, Max Hops=3, Hops Left=1

 

Sun 09/28/2014 09:26:12 PM : [iNST-TX-I2CS] 02 62 2B F9 CD 1F 2E 00 01 00 00 33 01 00 00 00 00 00 00 00 00 9D

 

Sun 09/28/2014 09:26:12 PM : [iNST-ACK    ] 02 62 2B.F9.CD 1F 2E 00 01 00 00 33 01 00 00 00 00 00 00 00 00 9D 06        (00)

 

Sun 09/28/2014 09:26:12 PM : [iNST-SRX    ] 02 50 2B.F9.CD 2C.08.F0 27 2E 00           (00)

 

Sun 09/28/2014 09:26:12 PM : [std-Direct Ack] 2B.F9.CD-->ISY/PLM Group=0, Max Hops=3, Hops Left=1

 

Sun 09/28/2014 09:26:13 PM : [iNST-ERX    ] 02 51 2B F9 CD 2C 08 F0 11 2E 00 01 01 00 14 20 00 20 00 C5 28 00 00 00 B9 

 

Sun 09/28/2014 09:26:13 PM : [Ext-Direct  ] 2B.F9.CD-->ISY/PLM Group=0, Max Hops=1, Hops Left=0

 

Sun 09/28/2014 09:26:13 PM : [iNST-TX-I1  ] 02 62 2B F9 CD 0F 1F 00

 

Sun 09/28/2014 09:26:13 PM : [iNST-ACK    ] 02 62 2B.F9.CD 0F 1F 00 06          GOF    (FLAGS)

 

Sun 09/28/2014 09:26:14 PM : [iNST-SRX    ] 02 50 2B.F9.CD 2C.08.F0 27 1F 1A    GOF    (1A)

 

Sun 09/28/2014 09:26:14 PM : [std-Direct Ack] 2B.F9.CD-->ISY/PLM Group=0, Max Hops=3, Hops Left=1

[LeeG]

Did the 'Options' display of the Momentary modes change when the 'Options' Query was done?

[Michel Kohanim]

Hi chris87,

 

Please do not hesitate to contact our support (links below) and we'd be delighted to help you find the root cause.

 

With kind regards,
Michel

[LeeG]

chris87

 

Exactly what button is being used?

 

If the button is sending Direct commands to the IO Linc Relay it has to be an On command.   Direct commands do not use the Momentary mode characteristics.  On turns the relay On, Off turns the relay Off.   Since the relay reacts to the timeout value the Off command does nothing.

 

Only Scene commands react to each Momentary mode characteristic. 

 

I also moved an I2CS IO Linc (what you have) to my test system and confirmed that Scene On and Off commands turn the relay On in Momentary B mode.  I set the mode to A to confirm only On commands work.  Then changed it to momentary B and verified Scene On and Off commands do turn the relay On.

[chris87]

chris87

 

Exactly what button is being used?

 

If the button is sending Direct commands to the IO Linc Relay it has to be an On command.   Direct commands do not use the Momentary mode characteristics.  On turns the relay On, Off turns the relay Off.   Since the relay reacts to the timeout value the Off command does nothing.

 

Only Scene commands react to each Momentary mode characteristic. 

 

I also moved an I2CS IO Linc (what you have) to my test system and confirmed that Scene On and Off commands turn the relay On in Momentary B mode.  I set the mode to A to confirm only On commands work.  Then changed it to momentary B and verified Scene On and Off commands do turn the relay On.

 

I have been testing it on the Mobilinc app.  What I am trying to accomplish is to where I can open/close my garage door with one press of the button.  Does this mean that I have to set up a scene to accomplish this, rather than a device?

[LeeG]

Yes.   Direct commands to the Relay would have to be Direct On only.  The Direct Off command has no affect.

 

Define a Scene with the Relay as a Responder.   I don't use MobiLinc but I think I have read where it will use a Scene if one has been define.  Some sort of sync is likely needed for MobiLinc to be aware of the new Scene.   

[oberkc]

Yes, mobilinc can use a scene.

 

I take it one step further and use tasker, integrated with mobilinc, to create a true one-step operation.  From my android homescreen, I have a tasker icon which, when pressed, operates the door, just like an opener.  The icon action sends a scene ON command to the relay.

 

Yes, when changes are made to the ISY configuration, one must resync mobilinc for it to recognize the changes.  (Based on my experience with android mobilinc.)

[MWareman]

Yes, mobilinc can use a scene.

 

I take it one step further and use tasker, integrated with mobilinc, to create a true one-step operation. From my android homescreen, I have a tasker icon which, when pressed, operates the door, just like an opener. The icon action sends a scene ON command to the relay.

 

Yes, when changes are made to the ISY configuration, one must resync mobilinc for it to recognize the changes. (Based on my experience with android mobilinc.)

You can do that without MobiLinc as well. That way, unless device, scene or program IDs change you don't have to resync. I also have near realtime status sent from ISY to Tasker vars as well... though I may change this solution to use io_guy's ISY Linc solution to get the actual dim levels sent.

 

I'm working on a description of my setup at the moment.

[oberkc]

You can do that without MobiLinc as well.

 

Through the network module?

 

One of these days, I should learn to exploit this ability.