DennisC
-
Joined
-
Last visited
Posts posted by DennisC
-
-
As a follow up, it is possible the update did not complete correctly. First try getting in through https://eisy.local
If that doesn't work, then go back to admin console and run update packages again. Be sure to reboot after the upgrade is complete.
-
2
-
-
Not sure what you are showing in your screenshot labeled eisy.local, but your screenshot shows admin console, not eisy local.
Have you tried: https://eisy.local
This should be done from your home network and you should accept the security warnings and continue.
-
1
-
-
If you are trying to access pg3x from a browser window, the port number is :3000, not :8443. However, accessing it with :3000, can cause some plugins to disconnect and reconnect.
As suggested, try https://eisy.local.
-
1
-
-
A few things to check:
Are you sure you are using the correct station ID?
13 hours ago, pete_balkus said: My station ID key (48909) was obtained from the following command:
https://tempestwx.com/station/48909/
Any thoughts on where to go from here?
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.
13 hours ago, pete_balkus said: Node Details
Node Name 1
Address
NodeDef
Primary Node
Hint
Enabled
Is Primary
Delete
ST-00010151
141178
tempest
controller
0x00000000
true
false
In my system, my node detail address matches what is listed in the variable, your variable for temperature is blank.
13 hours ago, pete_balkus said: https://tempestwx.com/station/48909/
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.
-
-
-
EISY 6.0.5
in eisy
-
Edited by DennisC
SpellingI 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.
-
1
-
-
-
8 hours ago, JLevy02 said: but don't see how to add those variables in my setup
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.
-
-
-
-
Edited by DennisC
Spelling2 hours ago, Guy Lavoie said: Thing is, I'm not migrating from a ISY994i. I'm migrating from the Zooz dongle to ZMatter. On a eisy.
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.
-
1
-
-
51 minutes ago, Guy Lavoie said: There is no zwave backup option with the Zooz dongle.
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.
54 minutes ago, Guy Lavoie said: The migration process also doesn't mention doing a zwave backup.
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)
-
-
8 hours ago, Bernstein-B said: Yes, I followed all the steps, except:
"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."
I couldn't find where to do that.
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.
-
6 hours ago, Bernstein-B said: I have the paid version of the WirelessTag NS version , 3.1.9 installed in PG3x version 3.3.18. I can see the controller in the UD Console, but I don't see any of my Tags. I have 5 13-bit temperature and humidity tags installed and I see them on the phone APP. I also see them in IFTTT. How can I get them to appear as nodes in UD?
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.
-
3 hours ago, Bladerunner said: December 24th, Michel helped me past the Eisy not coming back online.
From that point forward, I don't see the Elk connecting.
The settings look good still, and I have made no changes to the Elk.
Any ideas?
It's still just disconnected. Since it has always worked, I really don't know where else to look other than the settings and IP addresses, all are still good.
First, make sure you are using the correct IP address for Elk, the non secure port, the correct area number, and you have the address and port configured correctly in pg3 to match the help documentation for the plugin.
If all that is good, open eisy UI and go to pg3 Dashboard, Elk plugin, Log tab. Set the log to debug and restart the plugin while watching the log entries.
Do you see any errors?
One other thing, only one connection can be made the the Elk at a time, so make sure you are not trying to connect to Elk with anything else (like RP2).
-
An alternative is to use the Notification plugin. You could use the built-in notification in UD Mobile for a limited number of notifications, or move over to the full Notification plugin and Pushover.
Been doing this for a number of years now and have never had a failure.
-
1
-
-
Edited by DennisC
Spelling10 hours ago, SJacobson said: I thought the backup file might give the developer some insight as to the problem.
The Elk is connected to the eisy. All the Elk-driven programs in the eisy work.
The only errors I see pretain to some wireless Elk devices where the batteries are dead. I know about these. It is a good way to know if the eisy plugin is connecting with the Elk. Those errors are showing up in the PG3 log. When I get the exclamation problem resolved, I will replace the batteries in those devices. ALL THE DEVICES are showing up with red exclamation marks
I wish the developer of the Elk plugin would respond.
Steve
The backup log wouldn't help with your problem. What is needed is a log package set in debug mode when the issue happens.
As long as you accept the risks involved in posting potential sensitive information on the Internet, on a forum open to non-members, who could potentially create an account just to obtain that information, then by all means leave it.
Most members try to help when someone posts about a problem. I apologize for trying to offer some guidance.
If you only want response from the developer, send him a private message with information I stated above. He has posted before he is very busy with work and home life, but he will respond to you at some point.
Best wishes resolving your issues.
-
1
-
-
-
55 minutes ago, Guy Lavoie said: I imagine that this would be something you'd have to subscribe to, like the portal?
It's an interesting idea, widening the potential user base towards a less technical audience.
While nothing was mentioned, for the demo, it was built right in to eisy.local. We will need to wait to find out, unless @Michel Kohanim , can provide some insights?
29 minutes ago, Sticklizard said: The nucore.ai code is on github but with very little documentation. I was anxious to install and run something like Michel was running but I couldn't even figure out where to start. Does it actually run on eisy or does it run on another computer that interacts with eisy?
Runs on eisy and the interface is eisy ui.
-
Suspend option?
in ELK
As long as you are not in the Elk plugin at the time, you should not have to stop the plugin manually. Just start and connect with ElkRP.
The Elk plugin will reconnect when the connection is available again.