larryllix

Find the release announcement thread in the forum. Download the correct image, depending on whether you have a PLM connected or not. In your admin console use the pulldown menu Help and select upgrade manually. Backup when indicated and then OK. Sent from my SM-G781W using Tapatalk

El niño? Sent from my SM-G781W using Tapatalk

3. /isy/ is locked permission. I cannot access this file or directory When using sudo, /FILES/ does not exist

The time zone at the top of the admin console changes back to LA Cal. Then program events in the summary tab and variables all show last run / modified based on the LA times.

Grrrrrrrrr..... My timezone, along with sunset and sunrise times, and event times shown for programs and variables just reverted back to LA again.

I have been using variable substitution in the URL portion for years now. My WiFi lights live off them. 4 NRs do my 35 WiFi lights. Trouble is you can only use the same NR with at least one second of Wait between each calling. ISY does the substitution at send time, not at creation time and will use the second variable values for the first NR send. IOW two rapid uses of the same NR may both send the same latest values, not what was asked for.

57 NRs. I only use about half due to NSes, and bulbs styles not used anymore. 498 programs 356 Integer variables 219 state variables Doing it again it would have went much faster. I did a restore from ISY backup. Load every program, NR and store them back again. Each device had to to linked and then a restore removed the old PLM links for each device. Variables had the big endian vs little endian problems. Divide large values by 256^3 and add 256 if negative. I have a about 15 MS 1s and 5 LDs that needed manually linking in high and concealed places. Very time consuming.

I found every NR needed to be loaded into edit mode and then saved again or they just didn't function. It was like polisy just loaded them all but none registered for usage.

I get this most times when I first login. The next logins work fine after inserting my ISY creds. Later the same thing happens again. I will recheck this later and tomorrow to see if it forgets again.

To post a program, right click on it's name in the program tree (list) on the left of the admin console. Select "copy to clipboard" and then paste same into your post.

Some show d.quotations around them and one doesn't.

I think Michel would better suited to figure this out. IIRC he deleted the .env file, uninstalled udx and ISY and then re-installed them, and started them again. It many have involved mongodb also but I cannot remember exactly now.

I had that .env file setup originally for PG1 and when PG2 was released it seemed like some of the definitions actual purposes changed and the git-hub defintions were incorrect. IP addresses and port definitions changed things for more than what was stated. I had my webpage console set to port 80 = no https but it suddenly affected the ISY to polisy connection also. Everything worked except commands from ISY to polyglot. I could never get it to work right again and Michel connected in and deleted ISY and a few other packages and then reinstalled them. Voila! I was off and running again. I have never tried to install an .env file again and just live with the annoying HTTPS browser warnings since.

My settings. I got a not-connected complaint this time. Need settings??

see added .env comment in post above

I got caught on the port needed for ISY residing in the same box. I ended up using localhost:8080 just in case you forgot the port change. The .env fle should not usually exist. If an .env entry overrides the defaiults, then the defaults are changed and will not return to original settings unless a specific option is set up to restore the originals settings again. IOW: deleting the .env file will not restore defaults.

The SiLabs unit also fits both PLM cable and 700 series Zwave dongle. There must be a USB standard size anyway.

Today I sampled a few Insteon devices and found links to the old PLM still installed in every device. A simple admin console | device restore on each device fixed that up in every case that I rechecked. Took about 30 minutes for my whole system. Now I unplugged my ISY and stopped confusing the ISY Finder! One small step for home automation. One giant step for ISY!

Enter your Polyglot settings and change the location to a temporary location. Save and then set back. The automatic location grab at boot-up or install, apparently isn't working properly yet. Mine were set to locate Michel also. My sunset and sunrise were off an hour (more than DST return to EST) but now seem to have corrected themselves (next day) somehow. Rebooting polisy didn't seem to help at the earlier point either. Still need a lat/long tweak as the times are off by about ten minutes but that is minor.

After finding sunset light programs not working correctly I found my polisy admin console displaying LA, California. My polyglot settings were for Toronto. Since the settings rejected any update (no change) I had to change the location to Ottawa and then back to Toronto to get it to change. Now my sunset and sunrise times are both 1 hour too early. Owen Sound would be the nearest major community for this area. Latitude: 44° 34' 1.81" N Longitude: -80° 56' 36.56" W

I did mine on PG2 one at a time. Mind you I only use ecobee, Roku, and Inventory. Possibly they were not functioning once I started but I was past my commit point for moving over. I did move over WiFi lighting and system clocks etc. for about a week or so and then got anxious to transfer more and got past the commitment point by accident. My KumoApps were modified to send to both ISY/polisy for about a week and I just removed the extra lines again. CAI WC8 board was a snap with IP address changes. I decided to restore my backup image and keep all items in the same addresses between ISY and polisy. I was using variable injections from ISY for variables that controlled basic light controls and system / house temps, humidity before commit point.

When swapping my ISY for the polisy that my polyglot was residing on, I found I had to uninstall each NS and then reinstall it with the new (localhost:8080 - don't forget the port number). On reinstallation the nodes were self-installed into my new ISY/polisy. Admin console had to be reloaded each time to see the nodes. It went smooth once I figured out the process was longer than anticipated. 3 NS = about 15 minutes including re-linking to ecobee.

When I swap PLMs it takes almost a full day. Each and every battery operated Insteon device needs to be put into linking mode, one at a time and relinked to the new PLM. It becomes a long process with 12 or 13 MSes and 5 Leak Detectors, one under the dishwasher requiring panel removal each time. Not an easily swapped piece of equipment for larger systems.

I use two CAO Wireless Tags, averaged to operate my gathering room lights when called for. I did calculate their square roots in my kumoapp first, to compact the values, first but for only a distinct cut-off brightness level a dynamic range should work well for blinds, no problem.

ISY Portal has a Download of the database but no Restore to pull it back into the new polisy linked database. You can split your vocals between two ISYs though. I didn't bother. I just printed out the download and basically copied one by one. I did do something though. In ISY I named every program to become vocally operated a XXXX.select suffix. It makes it so much easier to pick out needed elements for vocals in the Portal. Just enter a filter parameter i ISY Portal and any program.select shows up in a different colour if not used.