DennisC

Wondering if you need to increase Java memory? The upgrade firmware post has instructions if you want to check.

Here is a link to the Polyglot Nodeserver Store to see all of the Nodeserver a that have been created.: https://polyglot.universal-devices.com/ Currently, you can run these Nodeserver via a Raspberry Pi or a Polisy. Soon however, Nodeserver will only be supported on Polisy. This is expected to happen when Polyglot v3 comes out. In addition, some Nodeserver can run from a cloud version of Polyglot available thru the ISY Portal. At some point in the future, the software running on the ISY will be moving over to Polisy, and the ISY will be phased out.

The code will run anytime the If statement is evaluated, which happens when ever the If is changed. Therefor, it will run with a change from On to Off and from Off to On. While not necessary, I usually give a brief pause when updating variables one after the other. The Init is very handy when there is a sudden reboot of the ISY, like a power failure. It will restore the variable to what it was before the power failure. The run at start up might take a few seconds or a minute or two to run, depending on how big your system is and how many run at start up there are. This way covers all possibilities and as soon there is a change registered by the If portion of the program, the ISY updates. Correct Custom notifications are available, there should be examples in the ISY Cookbook, or you can read about it here: https://wiki.universal-devices.com/index.php?title=ISY-994i_Series:EMail_and_Networking_Substitution_Variables So, you can write something like the following: ${elk.zone.#.name} will give you the name of the Elk zone that caused the program to run. The # allows the zone that caused the Elk program to run to substitute its name for the # sign. Like wise, ${elk.zone.#.status} will return the status of the zone that caused the program to run. In the near future, there will be an Elk Nodeserver so tif using that, the names would change slightly, but the principle will be the same. The collective group might be able to give you more direct and specific programing examples if you start a new post and explain clearly what you are trying to accomplish. When the concepts are piece meal it is hard to get the big picture. There are a lot of folks here who already have Elk programing and notifications in ISY working. Many are willing to share.

If Elk Output x is On Then VariableX = 1 Wait 5 seconds VariableX Init To VariableX Else VariableX = 0 Wait 5 seconds VariableX Init To VariableX Enable run at start up for this program. Whenever Elk output x is on, variable will be set to 1, when Elk output x is off, variable will be set to 0. In addition, you are setting the Init variable to the same value as the Variable (wait of 5 seconds just makes sure variable has been set) so on start up, the variable will have the same value as when the ISY shutdown, but the program will run shortly after start up to set variable to current state of Elk output. It is also good practice (but not necessary) to begin variable names with the type of variable it is, for example: $s_ISY_Home (State Variable) or $i_ISY_Home (Integer Variable). This helps for troubleshooting down the road. It reminds you of what type of variable it is.

All you need is one simple program that changes the variable to 1 when the Elk output is on in the then portion and when off, then set variable to 0 in the else portion. Set the program to run at start up and you are done.

For what it is worth, on the Schlage site, buried in the FAQ there is a question about using the zwave locks with Alexa. The response indicates all of the zwave locks that are part of the "Connected" line can be opened and closed by Alexa, work with their Nexia service and will report the user accessing the lock. It might be worth the time to contact Schlage again and attempt to speak with a more advanced person to question regarding status. I would think if the lock is reporting the user it also has status available.

@IT Solutions out of curiosity, could you check the box and the documentation that came with the door lock and see if any of it says "Connect" on it?

Pages 123 - 128 deal with variables and operators (math).

I am not sure I understand what you are trying to accomplish, but just to answer your question, select at start up and only test for the condition you want to be true. You can also disable a program through a program. I thought from your original question you wanted the program to check an Elk output on start up and then have a variable set and follow the on/off of the output?

You appear to have a lot going on which is making it hard to point you in the right direction. I would suggest rebooting your computer and use the ISY Launcher to attempt to gain access. It appears you are running v5 firmware, if that is correct, then download the ISY Launcher from this link: https://isy.universal-devices.com/start.jnlp After trying to start from the Launcher, tell us what is happening.

While climate module is EOL, there are several Weather Nodeserver that take place of the Climate module. Check the Nodeserver store.

Answers to most of your programming questions can be found in the ISY Cookbook. It would benefit you to read through the document. http://www.universal-devices.com/docs/production/The+ISY994+Home+Automation+Cookbook.pdf

What you are looking for is called run on start up. Instructions can be found here: https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Program_Summary_Tab

Yes, my lock reports status back whenever the door is locked or unlocked. I find it hard to believe Schalge would release a lock that doesn't report status after locking/unlocking.

Your troubleshooting results do make sense, they just don't fit your predetermined conclusion. You are having a communications issue because of your mesh. It is time to stop and go back to the beginning. Add a dependable zwave repeater following the manufacturers instructions, not necessarily how you think it should be added. Aeotec Gen 7 repeater is a reliable example of what to use. Next you need to read the lock instruction manual and follow the procedure to factory reset the lock. Again, it is important to follow the manufacturers instructions. Follow this by moving the lock to within 2 feet of the ISY (this is very important step), exclude the lock from the ISY at least 2 times. On rare occasions it takes tow excludes to complete the process. Next, re-add the lock to the ISY, following the instructions. After the lock has be added move the lock back to its home and do an update neighbors. Only then, try locking and unlocking.

Schlage FE469CNXV

This is a good example of having communication problems. You need to improve the zwave mesh around that lock or any lock you are having issues with. As others have said, figure out the root cause of the communications issue. I have had my Schlage zwave lock for over 5 years and it has never failed to lock or unlock.

Since the process of flashing a new SD card is rather simple if you have a good backup, I would suggest you might be better off spending the time to insure you have regular uncorrupted backups.

You may want to take a look at the ISY Cookbook. It has examples of many different concepts and programs. https://wiki.universal-devices.com/index.php?title=Main_Page#ISY_Cookbook

That error is 10 SMTP_FROM_TIMEOUT Try setting timeout higher just to see if it makes a difference.

Check the error log for any errors. You might also try increase the timeout on the configuration page.

The are currently 3 ways to run Nodeserver. On a Polisy (dedicated box from UD) an Raspberry Pi, or Polyglot Cloud (available through UD Portal). I don't believe the camera Nodeserver is available on Polyglot Cloud.

Thank you.

@asbril does the Zooz double switch report status (at least the top light switch) back to the ISY? Thinking of an application that I need to use status in a program. Thanks

I really think you should open a support ticket with UD. They are very helpful and usually respond quickly.