larryllix

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.

I was attempting to do that. Since mst of my lighting programs are based on single variable values it was very easy to move the non-Insteon lighting over. A simple ISY folder containing several variable change detection programs that NRed the values out into polisy's via it's REST interface to modified the cloned variable made that a synch. However when I thought about going further, so many devices were hooked together and dependent on each other I found it may have been simpler to "Tear the bandaide off" than suffering with many more cross-variable interlocks. The grass always looks greener on the other side of the fence and I demonstrated this quite well to myself. Two intense days did 98% of the bandaide technique but I still find the odd thing freaky. I found the odd light flashing on and then off etc...where one program was enabled again and shouldn't have been. Now I comment every program that must be disabled in the If section. ISY didn't have that capability when I started. Thank you UDI for listening to your users!! The WiFi lighting only (over to polisy) technique worked well for about a week or so, and then I just couldn't sit on my hands anymore. All in all, I am glad I made the jump. I did sweat a lot for a few days but that is why I am an ISY user...for the challenges and the solutions,... when I win at each challenge. I found another glitch last night that I need to fix and my dishwasher LD still needs linking into the polisy PLM yet. ISY Portal and Alexa speaking routines were the hardest as each time you delete all ISY Portal pseudo-devices the routines all need to re-attached from zero again. What a PITA! @bmercierWe need a better unused / defunct ISY element cleanup button in ISY Portal. Looks for unused ISY elements and removes them from Alexa. When vocals are changed, we end up with two different names in Alexa and it confuses her. Thanks.

Devices were not successfuly ported and none showed up. Different PLM anyway. Maybe moving PLM with the image may have worked better. Programs are then marked in yellow with Insteon addresses marked in comments. Enable/ disable cannot be trusted and a check box toggle at least one way and save fixes those. Variable values over 255? or maybe 16536 need to be divided by 256x256x256. If negative then add 256 after. I wrote a small ISY program and continually updated the variable names. Calculator would have been faster. NRs did work until edited and saved back as they came in. WoL still doesn't work for any devices. Devices were added one at a time using Delete all existing links. Will attempt clean up later. Not sure what will be left in devices yet. Factory reset or at least old ISY uninstall may be better but all but LD under dishwasher working well now. CAO tags ran as dual kumoapp for a while. Now only polisy. My NRbridge just needed heartbeat variable updated. Sent from my SM-G781W using Tapatalk

@Michel Kohanim I got my polisy/ISY working, then got past the commitment point and had to move everything over (commit). Daunting task took me about two days to clean up some variables (endian reversal) , program enables random, and Scenes demolished. LOL (I used Restore from an ISY backup image) Running 98% now...mostly good. Most items just needed to be refreshed to function. I am running on a USB PLM via polisy USB port. Some outstanding issues I have found: WoL seem to be outstanding and none of the 3 devices I tested work. They do work from my router so devices still receptive and functioning Some OR logic not shown properly in admin console. I have one program that refused to show two ORed conditions in the If section. Other programs show the OR text just fine. When two logic statements are ANDed they showed fine. This is only the admin console text (GUI) , and the ISY logic seems to function just fine anyway. X10 support appears outstanding. I cannot find any method to add any X10 devices in admin console. X10 module not installed, but no hard address method is available either.

Good point. As an assumed newer user he may not be aware of the dual citizenship ISY has now. ...and PLMs are assuming dual lives also. Sent from my SM-G781W using Tapatalk

There is no X10 devices to have a status. There is no method to connect to them.

Switching over to polisy, and using a USB PLM, I found I have lost any X10 features in my polisy. I am not sure if this is software or the USB PLM is incapable of X10 and polisy just reflects that in menu options loss. @Michel KohanimHopefully polisy is just adding X10 support later in the firmware and this is not a hardware deficiency.

Click on the link I provided in my post above and scroll down to the Install section. There you should see two links that will get you the choice we have been posting about, with PLM, and without PLM.