Everything posted by DennisC
-
Tag queries or turn light on/off
Don't know if this helps, but the only time I have seen out of range is when the battery has died and the time exceeds the reporting window.
-
ISY of Polisy lost access to portal but 994i has access!!!
If you check the Configuration page on IoP, the "Portal" tab is probably missing. You can also go to Help - Manage Modules to see if it says all up to date. I had the same issue when I did my two units, this is a known bug. Completely finish setting up your IoP, then send an email to UD with your UUID # and tell them you restored a back up from ISY994 to IoP, lost your previously approved IoP license and the "Portal" tab is missing from IoP Configuration page. Also, let them know if you want your ISY 994 Portal license transferred to IoP, or just to restore your previous IoP Portal license. They respond very quickly during working hours. After they do what you need to do, you will need to go to Help Manage Modules and it will ask if you want to install. Or, it might pop up to install after logging in. Give it a few minutes, then approve and shortly afterward, your portal will show on line again.
-
Migration with Z-Wave
Whenever you add a Zwave device, it is best to exclude then include all on the device you want to add the Zwave devidc to. The way I proceeded was to leave ISY994 alone and exclude using IoP, then include on IoP. After all devices were included on IoP, you can disable or delete in ISY994. The Zwave device in ISY994 will no longer work because a Zwave device can only be synced on one Zwave controller, hence why the exclude is done as first step on new controller. Any Zwave device connected to IoP will be deleted if you restore a backup from ISY994 to IoP. Since the backup doesn't handle Zwave, Zwave is disabled automatically when you complete the restore steps. You need to enable Zwave and then save and reboot. It's not hard, just follow the script originally posted by UD.
-
Migration with Z-Wave
I wanted to add - Once you have included your Zwave devices in IoP, you can either disable or delete them in ISY994. Also, once done, I ran Zwave - Update Neighbors.
-
Migration with Z-Wave
I questioned Michel about upgrading firmware of Zooz stick and he replied that UD has not tested the updated firmware with IoP and suggested not upgrading. I followed the suggestion and stayed with the firmware the stick came with. No, go to IoP and exclude then include. It is all done from IoP. Good luck.
-
Error Log formatting
It looks IoP omitted the formatting we use to have.
-
Migration with Z-Wave
In the past week I moved both my sites over to IoP and both sites had some Zwave, although not a lot. One site has 4 Zwave devices, inuding 1 Schlage lock and the other has 3 Zwave devices. All in all it was fairy easy. Plug in the Zooz Zwave stick, select Zwave on the configuration page and reboot. Next place IoP in exclude mode, and exclude a Zwave device. Followed by include Zwave device. Each site took less than 10 minutes.
-
Get Started (v1.3)
Glad you got it working.
-
Get Started (v1.3)
Did you try power cycling Polisy? The way mine is working, is just the https://ipaddress in a browser brings up pg2 Polyglot. When port 3000 is added in browser it brings up pg3 Polyglot. Using https://ipaddress:8443 in ISY Launcher let's you click on Polisy to open admin console of IoP. If it doesn't work like that for you after a power reboot, open a ticket with UD.
-
Get Started (v1.3)
If you are trying to access the admin console of ISY on Polisy, using your example from above, try: https://172.16.1.226:8443 in the ISY Launcher (but I think your missing a block of number(s) - should be https://xxx.xxx.x.xxx:8443). If it doesn't work the first time, power cycle the Polisy and give it a chance to come fully on line before trying again.
-
ISY Polisy - WOL and URL of ISY Web Page
Hi Michel, I am casting a vote for getting WOL working on IoP. I use it twice a night to wake a Win10 machine from hibernation to insure certain processes run when they should. I had a problem last night with them not working and was forced to enable the WOL programs on the ISY994. Right now, I am fully on IoP except for this program. I never experienced an issue with authentication with the WIN 10 machine.
-
IoP - Possible Bug?
Hi Michel, I didn't extensively test to see how far it extended. However, I after I posted my initial problem I also had a problem with updating a Network Resource. I was able to both disable and enable a program.
-
IoP - Possible Bug?
I experienced something strange so I thought I would post it here to see if anyone else can reproduce it. I am also tagging @Michel Kohanimjust in case it is confirmed as a bug. Last weekend, I was at the remote location of my 2nd Polisy and decided to migrate ISY994 to ISY on Polisy, I wanted to attempt this one first since it was a smaller site. The migration went well and it has been running all week without issues, except I realized I wasn't getting a specific notification. Now that I am back at my main residence, I wanted to remote in and correct the typo I made it the notification address. I signed into the ISY Portal and obtained the admin console URL to allow me to directly remote in to the admin console via the ISY Launcher without opening a port. So far so good. I signed into the remote IoP and went to Configuration - Emails/Notifications - Settings/Groups page and proceeded to correct the typo in recipients address. I hit OK on the popup page after making the change and then clicked on Save. All looked good so far, however, I wanted to send the notification to make sure the change was successful and changed to the Programs tab. The page never loaded and I received the following error: [LIB_ERRORS-503] After logging out and back in, I found the change was not saved and had reverted back to the original text. I tried this several times with no success, receiving the same error when ever I changed pages. I then rebooted Polisy and tried again with the same result. I have tried to make this change several times over the last 3 days and have received the same error each time with multiply reboots in between. Being curious, I tried again this morning and that attempt failed. I remoted in to my offsite router and "temporarily" opened a port to IoP (the port is now closed). I made my change and tested it without issue. As I said at the beginning, I am not sure what this issue was but something was amiss, possibly a bug in(?), well not sure in specifically what.
-
SSL Certificates and ISY Launcher
I would agree that use of the UD Portal simplifies reaching your ISY or IoP by computer or with UD Mobile. The cost for two years is minimal and once you have the key you can enter it right in the ISY Launcher if you are using your computer away from home to access the admin console.
-
PG3 ELK Node server 3.1.4
I'm fine with waiting, I know you are busy. Let me know if when you have something for me to test. BTW, I ported over my main system today and this didn't happen on this system.
-
PG3 ELK Node server 3.1.4
What are you suggesting to delete - the Elk Nodeserver? I am not necessarily in a hurry, just want to know its being looked at. I would much prefer having the issue corrected so it can't happen again.
-
PG3 ELK Node server 3.1.4
@Jimbo @bpwwer Any thoughts on how I can correct this?
-
Unwanted behavior: full screen and expanded tree control
I'm not sure if this will help, but every time I go from running admin console on my notebook and then go back to plugging my notebook into dual monitors I have to delete the files listed below. You might give it a try. 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_*.* file patterns: udi_tree.state udi_frame.state udi_pgm.state udi_finder.state udi_launcher.state
-
PG3 on Polisy
You can disable any program you are not ready to use if you port it over early.
-
BUG - Node Server Info is Not Valid
Also, when you click on the name of most nodeservers in the store it takes you to GitHub and you can read info on the nodeserver. This one takes you a private website with no info on the nodeserver.
-
PG3 on Polisy
Try updating your version of PG3 by SSH.
-
Weatherflow PG3 Missing Data
Yes, for Tempest. Thank you.
-
Weatherflow PG3 Missing Data
I'm confused, I don't think I understand what you are saying. BATLVL is shown as a node in the Nodeserver on PG3. You can read the value there, but it's not in the admin console.
-
PG3 ELK Node server 3.1.4
Log package sent and thank you!
-
PG3 ELK Node server 3.1.4
On PG2 I have both the Weatherflow and Elk Nodeserver's stopped. I opened the ISY on Polisy admin console with no change. I closed the admin console and restarted Polyglot for PG3, opened admin console for ISY on Polisy with no change. Next, with Weatherflow and Elk Nodeservers on PG2 stopped, I rebooted Polisy and opened the admin console for ISY on Polisy. I am still showing "Sky Battery". I am out of things to try to correct this.