Everything posted by DennisC
-
Impact of 3/24 maintenance
Mine was at 8:21 am eastern time. How come yours was so late?
-
Admin Console
I reported this again when I migrated to eisy. I have been assured that it will be addressed by the addition of a scroll bar, but no time line was given. Maybe if enough people open a support ticket.........
-
Becomes armed or becomes disarmed?
Below is an example of using "disarmed" to turn a light on, if the time is 30 minutes after sunset until 11:00 pm. Example - [ID 002F][Parent 00B1] If ( 'Area 1' Armed Status is Disarmed ) And From Sunset + 30 minutes To 11:10:00PM (same day) Then Set 'Light xx' On Else - No Actions - (To add one, press 'Action') To turn off the light, you could set an Else action, but if you wanted the light on/off when you were home or on a different schedule, you would write a separate program to turn the light off.
-
Becomes armed or becomes disarmed?
Yes this is possible, I did it when using the old Elk module and I'm still doing it using the Elk node server. Which are you using? One way is to set a variable, and have it update when you arm and disarm. I use two different variables, one for armed away and one for armed vacation. The other way is to use Armed Status and/or Arm Up State. When I was on the Elk module I found the variable method more reliable. I never changed methods when I moved to the node server, but I receive a notification when arming/disarming and it includes the two states I mentioned and they have been very reliable on the node server. I actually run several different programs depending on which armed state I enter or leave.
-
my Polisy keeps rebooting, about once a week or two
If you are on Polisy, in the admin console go to Configuration and click on Upgrade Packages button. The admin console should close. Wait 15 - 30 minutes and log in to admin console again. Go back to Configuration and select reboot. Before opening admin console, you will need to clear your Java cache and download a new start.jnlp. Click on start.jnlp and it will download a new Launcher to your desktop.
-
my Polisy keeps rebooting, about once a week or two
What version firmware and UI are you on? This was an issue that was corrected in the current v5.5.9.
-
Adding Schlage BE469 lock (zWave)
Sometimes it takes more than one remove to completely remove a ZWave device. Try this: Open the Event Viewer to level 3. Select ZWave - Remove a ZWave Device Put your lock in to enrollment function (be sure to follow user manual instructions) During this process, keep an eye on the Event Viewer for any errors. Reboot your UD device (you indicated you migrated from ISY994, but I don't recall if you are on eisy or Polisy) Note: You should be on v5.5.9 for either eisy or Polisy. If not go to Configuration page Upgrade Packages. If you needed to upgrade, be sure to reboot a second time. With Event Viewer open to level 3, go ahead and re-add the lock (be sure to follow user manual instructions). Keep an eye on Event Viewer window. If after this, there is still an issue, with the Event Viewer still open try: Right clicking on lock in admin console and select ZWave - Synchronize - Update with Interview. Check Event Viewer window for errors. If there is still an issue, try right clicking on lock and select ZWave - Synchronize - Update. Check Event Viewer. If none of this works, open a support ticket with UD.
-
Adding Schlage BE469 lock (zWave)
What steps did you follow remove the Zwave device?
-
No configuration options in node server
Looks like you need to ask @bpwwer. It's possible you need to add the key fields by clicking on Add Custom Parameter?
-
All INSTEON Devices Not Reachable
Try moving it to another outlet on a different circuit anyway. Sometimes it's a combination of items on the existing circuit and the Echo circuit.
-
All INSTEON Devices Not Reachable
Is the PLM on the same circuit? You could try moving the PLM to a different circuit.
-
No configuration options in node server
In PG3 dash board what appears on the Configuration page?
-
Error Log on new EISY
Are you trying to log in to PG3? If you are on eisy, try https://xxx.xxx.x.xxx:3000, where x's = your eisy IP address. If you are on Polisy, no port number is required. Something else?
-
Writing energy monitor output to csv file
I must be missing something, where are you getting the following from: _33_3 & _72_3 Start simple using a program and an email notification so you can right click on the program, select run then and have a notification sent. Y email. Once you get the right output, then transfer the correct node address to your cvs output. Does the following work: ${sys.node.ZY014_143.TPW},${sys.node.ZY014_143.CV}
-
Writing energy monitor output to csv file
If you type the following into a browser window, click through the warning and then enter user name & password, you get a page that gives you all of the property id's for that node (if the node address is written correctly (the example is based on using eisy via https, with a node address of n001_81668 (from node server, update it for other type of nodes): https://xxx.xxx.x.xxx:8443/rest/nodes/n001_81668
-
Yale Assure Lock 2 with Zwave Plus module shows as Light Bulb
I think you will need to submit a help ticket with UD and get Chris involved in this. There is one more thing you can try: Go to the top menu and select ZWave - Synchronize - New & Deleted with Interview.
-
Can't Authenticate Node Server (Google blocks)
I apologize, I misunderstood the issue and deleted my previous post.
-
Can't Authenticate Node Server (Google blocks)
I misunderstood the issue and deleted my previous post.
-
Yale Assure Lock 2 with Zwave Plus module shows as Light Bulb
Try right clicking on device and run ZWave - Synchronize with Interview. Restart admin console and recheck. If that doesn't work, then try ZWave - Synchronize without Interview. Restart admin console and recheck. Edit: Before restarting admin console, let the synchronization finish. You can monitor this in Event Viewer set at level 3.
-
Question about semantics of Query
Yes, you can have a folder inside or under another folder. Click on the parent folder and at the bottom of the left hand tree, select make folder. The new folder will be under the folder you selected. Is that what you were trying to do?
-
Log in issues
If you are accessing your ISY locally, you should be using the Launcher. You can get it by downloading start.jnlp from the link below. Click on start.jnlp and it will place the Launcher on your desktop. start.jnlp https://isy.universal-devices.com/start.jnlp Instructions: https://wiki.universal-devices.com/index.php?title=Main_Page#Installing_the_Admin_Console_Icon_on_Your_Desktop If you are still having a problem after that, try the troubleshooting steps below: Admin Console Closes Automatically This is usually related to firewall software on your computer and especially with AVAST or AVG (including MAC). Two solutions: Use https (instead of http) to connect to your ISY Configure Your Firewall Software Admin Console Minimized/Invisible and Cannot be Restored This is usually related Admin Console state files not being updated properly and especially in case of multi monitors. All you need to do is to find the following files in Java temp directory (on Windows: c:\Users\[Username]\AppData\Local\Temp) and delete them. Or, you can simply search the computer for udi_*.state or ud_*.state file patterns: ud_finder.state udi_finder.state udi_frame.state udi_launcher.state udi_pgm.state udi_tree.state Be aware that the ISY is at end of life and will have no new development. Shortly, free support for it will end. The latest device is eisy and you may want to read up about it from UD's store page. You might want to consider an upgrade. When you get in to your ISY, I would suggest you take a fresh backup. So, not sure what firmware version you are on, but there has been a lot of development going on. You might want to read up.
-
Admin Console Java Issue
The admin console was not meant to be left open for monitoring. It was designed to do a task and then be closed. Having said that, what UD hardware are you using and what is the firmware and UI versions? If you are running on either Polisy or eisy, the latest version is 5.5.9. Some versions before that had a bug that would give error messages about open sockets not being closed. If you are not on latest firmware, you should update.
-
Update/Upgrade Packages Question - eisy
Yes, you can follow the topic here: https://forum.universal-devices.com/forum/339-current-release-announcements/ Best practices says yes, however, if I am in a hurry, I will try opening the admin console. It will let you know if there is a mis match between firmware and UI.
-
Update/Upgrade Packages Question - eisy
No, the first choice for updating should be the button in the admin console.
-
Update/Upgrade Packages Question - eisy
Then we need to get you updated to v5.5.9. Let's try to use the multi function button for the upgrade process. But first, can you ssh into eisy? If so, ssh in (login is admin/admin) and at the prompt type: sudo tail -f /var/udx/logs/log This will open a log in the window so that upgrade progress can be monitored. Next go to eisy and press the multi function button one time. This should start the upgrade process, which you should be able to monitor by watching the log. If all goes well, once the upgrade is finished, you will need to reboot, either from the admin console or from five presses of the multi function button. You will need to allow sometime for the upgrade, but when the log stops you should be ready for the reboot. Likewise, you will need to wait for eisy to completely load (up to 15 - 20 minutes), then you should clear your Java cache (check all 3 boxes to delete files & applets) and download a new start.jnlp from this link: https://isy.universal-devices.com/start.jnlp When you run start.jnlp, it should load a new Launcher on your desktop.