DennisC

A few things to check: Are you sure you are using the correct station ID? I am not sure what you mean by the statement and link above. If that is your actual station, after the page opens you should be able to click the top near the temperature and see data from your actual device. The landing page is Weatherflow's generic data for your area. Does the Weatherflow app on your phone show correct data? Open the app and click the Tempest symbol in upper right corner for your local data. Do you have correct data? If not, there is an issue with Tempest. In my system, my node detail address matches what is listed in the variable, your variable for temperature is blank. In node detail above, you station is shown as 141178, yet your link is showing: 48909. Which is your actual station ID? Go to the app click settings bottom right corner, followed by Stations, station name, status, and then scroll down to Station ID under Hub. Do they match what you have in pg3x? If everything is correct and you are stil having issues, go to pg3x, Dashboard, Weatherflow, Log, and place log in Debug mode. While watching the log, restart the plugin. After it starts up and has some time to collect data, look for errors in log.

Does Weatherflow data populate in pg3x? Check the error log and the configuration settings in the plugin.

Right click on the program name and select "Copy to clipboard". Then post the program here for review. Be sure to select copy to clipboard.

I would strongly suggest you wait. Especially consider the following from the upgrade instructions: "Upgrade MUST be done when you are local to your unit AND using the Admin Console." I am in the same boat for one of my installations. The other installation I upgraded today without issue.

I suggest you look at Ryse for controlling your shades. There is a Plugin and they regularly run sales. I have them in two locations and they work well with UD's systems.

Are you actually experiencing any performance issues, or is it just the red bar that is bothering you?

I am confused by this statement, what variables are you looking to add, other than what is shown? If you are going to use the built in native custom Notifications, just add what is shown in the example, substituting your system node # for what is shown in the example. So for alarm status, if your Elk Plugin is in slot 1, you would write: Alarm Status: ${sys.node.n001_area_1.ST}. You can also, just go to PG3x, Elk Plugin, Nodes, look for Alarm Status in the node list and on the far right, will be the node address for that node. Click on the copy icon and you will have it. I usually make a list in a document of what I want, and then copy them all over. If you are going to use a service like Pushover, then you would add it to a Network Resource. One of the advantages of using Pushover is having a historical record of all notifications.

Look thru the examples here: JimBo Automates - PG3 Node Serversairscape

Sounds like you need to follow the examples for setup and using the Notification plugin. Take a look at these: JimBo Automates - PG3 Node Serversairscape

You could have the unlocking keypad set a variable and run your program with the variable. Next, reset the variable back to zero after an appropriate time delay.

I don't think UD built a backup for that possibility. I think you will need to re-add all your devices. The only way to know for sure will be to ask UD via a support ticket.

There use to be. When I migrated my 994 to easy, on two systems with the Zooz dongle, I successfully migrated then both. If you don't get a zwave backup you will not migrate your zwave devices correctly. Yes it does: Preparing for Migration from ISY-994 On your ISY-994 Make sure the ISY-994 has firmware 4.x or 5.x, If you are migrating your Z-Wave network You must be using a 500 Series Board in the ISY-994 Make a backup of your Z-Wave network (Admin Console | Z-Wave | Backup) Make a backup of your ISY-994 (Admin Console | File | Backup ISY)

Just a thought, before creating the migration backup, did you perform the required zwave backup?

If you followed the steps correctly up to this point, then go to eisy.local, Nodes, and look for whatever you named your tag manager and select it. On the right side of the screen you should see a title for Monitor Tags and along side it a drop down arrow which you need to set to true. Afterwards, you might need to sign out and sign back in or you might need to restart the plugin. If you still have issues after doing this, then set the pg3 wireless tag log to debug and restart the plugin. After a few minutes check the log for errors.

Have you completed the instructions for setup on the configuration page: Installation Backup Your ISY in case of problems! Really, do the backup, please Go to the Polyglot Store in the UI and install WirelessTags. Add WirelessTags NodeServer in Polyglot Once it starts up, you should see a message in Polyglot Web which shows a "Active" link to click. Seems the wirelesstags certificate is not up to date, so in chrome you may have to click continue anyway (unsafe) selection :( The link points to https://www.wirelesstag.net/oauth2/authorize.aspx?... with necessary info Including a redirect back to the nodeserver's REST Server After you 'Grant' access you should see a message saying "SUCCESS, received our token, ..." in your web browser Open Admin Console (if you already had it open, then close and re-open) You should now have a node for each of your tag managers By default the "Monitor Tags" for each tag manager is turned off, if you want the tags to show up in your current ISY/nodeserver, then enable it. The nodeserver and tag manager must be on the same LAN since the tag mangaer sends updates directly to the nodeserver. Only one nodeserver can monitor the tags if you have multiple ISY/nodeserver's. This could be fixed by using Kumoapps, but not sure if it's necessary Once Monitor tags is enabled, you should see the tags be added to the ISY. Review the nodeserver log if they don't all show up, it may take a minute or so.