binaryman Posted July 16, 2013 Posted July 16, 2013 So I used to be able to use the status of my morninglinc in my programs (at least the status of what the ISY sees it as). I know this is inherently inaccurate etc. etc.. Now however when I try to use it in a program, I get: and - status - "front door-on" - .... - responding and when I click "add to 'if'" I get in the program: If Status "Front Door-on" null responding Is there an issue with my setup, a change in the isy firmware, or am I doing something wrong? I really really need to use the ISY status of the morninglinc in my programs.
Michel Kohanim Posted July 16, 2013 Posted July 16, 2013 Hi binaryman, In what version of ISY were you able to see the status of MorningLinc in programs? With kind regards, Michel
binaryman Posted July 16, 2013 Author Posted July 16, 2013 That's a good question... For sure 3.x something.. I can't say when last version for sure, I just know it worked. Used the status to update a variable to keep in sync a scene/keypadlinc in the case the morninglinc was activated directly. I really wish it could be added as a controller to a scene as well as/instead of just a responder.
Michel Kohanim Posted July 16, 2013 Posted July 16, 2013 Hi binaryman, Please try the following UI and let me know if you get it back: http://isy.universal-devices.com/99i/3.3.10 I remember that we had to take it out because of security issues. With kind regards, Michel
binaryman Posted July 16, 2013 Author Posted July 16, 2013 I click the link and the applet loads, but doesn't prompt for login nor show any devices etc.
Xathros Posted July 16, 2013 Posted July 16, 2013 I click the link and the applet loads, but doesn't prompt for login nor show any devices etc. Look behind the applet window. Is there an ISY finder window? If so, use that to add the IP address of your ISY then connect from there. -Xathros
binaryman Posted July 16, 2013 Author Posted July 16, 2013 There is not, nothing behind the applet window
Xathros Posted July 16, 2013 Posted July 16, 2013 Sorry, thats all I have for ideas on this one. Will have to wait for Michel. -Xathros
oberkc Posted July 16, 2013 Posted July 16, 2013 For whatever reason, I found the morninglinc to be more marginal in communication than the rest of my devices. Perhaps your problems are completely unrelated to setup or firmware version. Have you tried temporarily moving the morninglinc closer to your PLM?
binaryman Posted July 16, 2013 Author Posted July 16, 2013 I have no problems between the morninglinc and isy, they work perfect and in fact isy\plm\morninglinc all plugged into same outlet. It's just that the options to query the status of the morninglinc are not available to my programs in the isy like they previously were, which makes things very difficult
LeeG Posted July 16, 2013 Posted July 16, 2013 I checked the If Control and the MorningLinc is not even allowed as a selection. Did not understand the security concern but a change was implemented. Since the MorningLinc Status often does not reflect the actual state of the lockset anyway, perhaps a Variable could be used to represent the last command sent to the MorningLinc. EDIT: please ignore my If Control comment. The MorningLinc nodes are Responder Only nodes so they would never have been an option in an If Control statement.
binaryman Posted July 16, 2013 Author Posted July 16, 2013 Yea I've done something similar setup with a variable. Problem is a scene change or control cannot be used to change a variable, or if my wife or me by accident when trying to open the door (we use mobilinc) toggle the morninglinc directly instead of the scene or using a program to do it, then the variable as well as all my programs get screwed up. I really need to be able to use morninglinc as a controller or be able to parse the current status of morninglinc in programs (like I could before) or be able to use 'if control of morninglinc is switched on\off" in programs' or be able to use 'if control of 'scene' is switched on\off etc in programs' All of these I would think would be easy to do... I totally get that the status of morninglinc may not be actual status (due to someone using a key, etc.) but no one in our house uses any method except the ISY\mobilinc to unlock the door unless it's an emergency (dead batteries, isy not working etc.) which never happens.... If a disclaimer needs to be attached etc. that's fine, but to limit functionality due to this issue just seems dumb.... At least put back the ability to parse the current status of the morninglinc.... OR set it as a controller... Right now my house is LESS secure, because the door isn't always being locked. on the flip side, half the time I need to pull out my phone and manually go in and unlock my door while dealing with kids, groceries, etc because the program doesn't unlock my door as it thinks it's unlocked already (I use homelink\ezx10rf or mobilinc location\gps function to open garage\door\lights when coming home and leaving). Not to mention my keypadlinc button being out of sync as well.
Michel Kohanim Posted July 17, 2013 Posted July 17, 2013 Hi binaryman, I am sure we had to remove those conditions from programs. MorningLinc can never be a controller. Furthermore - and in addition to not knowing the status - we cannot even query the status of the MorningLinc. In short, you can NEVER trust what ISY is reporting as status for this device. And, therefore, we had no choice but to remove the condition from programs. Once we have Z-Wave, I think it'll be very important for you to consider Z-Wave solutions instead. With kind regards, Michel
Recommended Posts