DennisC

Be aware, you can not migrate from ISY with 300 series Zwave board, you will need to recreate your Zwave network. Also, per the migration documentation you must be on a minimum firmware of 5.3.4 to migrate.

If you haven't read the read me file yet, it is a good place to start: https://github.com/UniversalDevicesInc-PG3/udi-poly-ELK/blob/master/README.md Most programing is done as it was with the Elk Module, but some of the verbiage is a little different.

I use one motion sensor outdoors as an alert of someone coming down my driveway. It is tied into my Elk alarm and when activated turns on an Elk output. Based on the output turning on, ISY sends out network resources to position the cameras.

Ok, now I understand my confusion. Just for future reference, the values displayed in the admin console are not variables, they are nodes. In the admin console, variables are only displayed on the Programs - Variables tab and you have to create them. There are two kinds, Integer & State. Notification substitution will only display the value. Node servers map the values to verbiage to display words. You could start using UD Mobile and send your notifications via UD Mobile Notifications if it is important to have the notifications in word equivalent of the numbers. UD Mobile has the ability to read map values and you can map a value to a word yourself. I hope that makes sense.

I'm sorry, but I still don't understand. I receive many status notifications, including battery voltages, from ZWave devices, without having to store them as variables. If the item in question is in the admin console, you can receive the nodes value in a notification without having to create a variable, through the use of email substitutions. A low battery alarm would most likely send a value of 0, unless it is actively in alarm. Are you sure that is the value you are looking for? I would suggest you provide some additional information, maybe even some screenshots showing the admin console node page, along with the output of the node inquiry I posted above, so we can assist you better.

I'm not clear why you are reporting on variables if the ZWave device reports status in the admin console? Why not just use that value in your notification? In either case, you can determine the values and property id of ZWave devices from the command listed below. Just type the command in your browser, replacing x's with your IP address & the main node address with the main node in the admin console (as shown in the example below): https://xxx.xxx.x.xxx:8443/rest/nodes/n001_81668 You can also find all info by right clicking on the node in the left hand tree of the admin console and selecting Xray, in the next window select Node Info, and then Go.

Since I don't use this node server and do not have any Blink devices, I can only guide you based on the information the node server creator provided, which I posted above. These instructions should have been on the Configuration page, if not, follow the link for Blink in the store and you should see a "More Info" button. Clicking that button will take you to the github page for the node server and the readme file is there. If, when the node server tries to login, you receive a verification code of the same number of characters the node server Configuration page is looking for, yes that should be what you enter on the Configuration page.

I currently control Foscam and Amcrest cameras from a Polisy and an eisy at two different locations. I am sending commands to control start/stop recordings and to move ca.era position via network resources. I haven't tried sending an image back.

Besides everything mentioned above, check to make sure everything is correct on the Configuration tab of the node server.

From the directions: "If you change a Elk object name it will not be automatically reflected on the ISY (currently). You will have to delete the node in the Polyglot UI Node's page for the node server, then restart the node server." You will also need to restart the admin console.

ouch

When I first migrated in early March, when the factory query ran some of my UD Mobile notifications were being triggered. This was corrected after the first upgrade. As it always done this since you migrated or is this something new? Have you rebooted recently?

Follow the instructions here exactly: https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide#Migration

Let us know if you experience any additional unexpected reboots and be sure to check logs.

Not sure what you have tried or what part of the instructions you have questions about? Here is the setup instructions: Setup User needs provide username and password used for the Blink App. A one time/2way authentication may also be needed. In the case of 2 way autenticantion. Obtain the code using the Blink app and enter the data under configuration The user must specify the sync unit(s) where the cameras are registered - A comman separated list is ok if more than 1 sync unit is being used. If no sync unit is used specify NONE Note, the API does not handle special characters in the camera and sync names - please remove/rename those before setting upthe node ShortPoll is heart beat from controller node, LongPoll updates data. Do not run update too often, as system may get throttled by Blink - Suggested to be more than 60sec between updates Still to be done I only have 3 camera types - Mini, doorbell and Outdoot (new) - I do not know the older camera's name. If you have those please enable debug and click update camera and provide log file and I can update this Plan is to add ability to send pictures of emails/videos taken.

You should be on the latest firmware. Upgrade to v5 6.0 and be sure to clear Java cache and download a new start jnlp to get a new Launcher to access the admin console. Try looking in the event viewer around the last time of your reboot to see if there is any info.

Great & thanks for updating us.

Do you know what firmware version you are running on your eisy? Have you rebooted eisy after the last upgrade? What version of PG3x are you on? It should tell you on the bottom of the initial PG3x screen. Your eisy should be on v5.6.0 and PG3x should be on v3.1.25. If your are on these versions, try rebooting eisy by 5 presses of the multi function button. If you are not on the most current versions listed above, try updating by 1 press of the multi function button. After eisy restarts you should clear your Java cache, including checking all 3 boxes when you delete files, and download a new version of start.jnlp. Run the downloaded file and you will get a new IoX Launcher on your desktop. After confirming you can get in, reboot eisy one more time by pressing the multi function button 5 times. Then check on PG3x again, if you were not on the latest before, you should see a note that PG3x needs to be restarted. You can do that from the System tab.

Try going to the tab in PG3x that says Node Server Store. When the list comes up, look for the node server in question in the left hand column. Click on the name of the node server, and if you have successfully purchased the node server, you should see a line that indicates version, price and under Purchase column there should be an Install button. When you click on install you should be able to select a slot. Also note, if the node server was already installed, half way done the page there should be a button that sats Reinstall here? next to the slot the node server is already installed in.

Before beginning the migration also make sure your eisy is up to date with the latest firmowhich is version 5.6.0. Make sure you follow the . migration instructions.

What firmware and UI are you on?

Glad you are up and running.

Are you using the IoX Launcher? Clear you Java cache being sure to check all 3 boxes to delete. Then download start.jnlp from here: https://isy.universal-devices.com/start.jnlp Click on the downloaded file to run it. The IoX Launcher should be added to your desktop. The IoX Launcher should automatically find your eisy, if it doesn't, click add and enter: https://eisy.local:8443/desc If that doesn't work, check your router for the eisy IP address and click add in the Launcher and enter: https://xxx.xxx.x.xxx:8443/desc Replace the x's with your eisy IP address. If you are still having a problem try the troubleshooting steps here: https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide#Can't_Find_eisy

Read through the post here: Does this sound like a similar issue?

According to UD, they eliminated the ability to use static IP addresses in eisy because of the overwhelming support calls for issues that were traced back to the use of static IP addresses. It can work fine and then all of a sudden it causes issues. Can't think of any reason to continue with static IP when DHCP reservations in your router take care of the same function but without the potential for problems down the road.