larryllix

Got two more ISY service packages moved over to polisy now and that concludes my dependence on a RPi. My ISP IPscraper, and Outback Mate3 Modbus to ISY packages are functioning well using crontab as cyclers. I guess the RPi 3 can get kicked down to a current RPi 1 job, and the RPi 1 retired.

In the NS store (polyglot) a "Uninstall" should be showing. I think you will have to delete the NS pseudo devices in ISY after.

Finally got my NRbridge RGBWW bulb software installed under polisy! Took a lot of ownership and permission changing, moved files in with Filezilla, and entered a bash script into crontab. Not the best to start things up but I couldn't find rc.local or any other method to do an automatic startup. Only a few more packages to move over now. Boy! vi is a technology jump back to the 1970s. Started to install nano but too many necessary system things are missing to install port...whatever that is. I don't need another 50K x files on my polisy, either.

None of that is necessary. I run into it every time. Just ignore the warning, using the "visit this website". The attacker stuff is hype on your own LAN connections.

LOL! Polyglot has never had any certificates that work. On your LAN, just ignore it. Some day valid certificates will be installed, https will be dropped, or you can generate your own certificates if you believe in the security of certificates.

Running vi lessons in another thread?

Third that one!! Must be easy to load and implement??

Is there any advantage to using vi over nano? Most of the basics seem to be the same. The colon command structure makes me cringe a bit but if it can do macro things (IIRC?) it may be worth the jump to hyperspace.

Thanks! Seems to have done the job. I am hoping that is undoable in the event of polisy growth failures. Now I found my own NRbridge.py software running two copies. I found a sudo version running from rc.local and removing that seemed to speed my light responses back up to where they were originally. Poor bulbs probably didn't know who was refreshing them.

ewwww. I think I remember trying to use that in the 1970s Thanks

I use the backup/restore method and it worked like a charm with only one ecobee NS. ISY never even noticed. Now I need to know how to disable booting Polyglot on the old RPi while other ISY service apps are functioning.

How are you editing these files? Is there a resident editor in the o/s somewhere?

I got the same results a few time now.

OK....all seems to be working and I have restored my backup from my RPi PolyGlot. How do I disable the original Polyglot for starting on bootup to avid NS conflicts? I still need a few other ISY service programs running on the original RPI so I need to only disable Polyglot on that RPi. Thanks in advance!!

Same as Toddimus here. I have installed v2.4.4 in my RPi Polyglot. Seems OK but only the ecobee NS.

Now how can I get my RPi Polyglot to upgrade to v2.2.5, in order to make the version match for backup/restore?

Try this

No sign of v2.4.5 anymore here, despite reboots, and refreshes.

My RPi Polyglot would never load v2.2.5, in case that is related. Now the offer of v2.2.5 is gone from the PolyGlot everywhere.

@Michel Kohanim No such port 443 luck. IP address has not changed in router. Here is what I get. Welcome to Polisy! [admin@polisy ~]$ ps -aux | grep poly polyglot 1748 62.4 3.1 697284 128824 - R 12:32 0:04.25 /usr/local/bin/polyglot-v2-fr polyglot 1009 0.0 0.1 10768 2188 - Ss 11:39 0:00.70 daemon: /usr/local/bin/polygl admin 1750 0.0 0.1 11248 2696 0 S+ 12:32 0:00.01 grep poly [admin@polisy ~]$

Thanks Michel! It appears that all went OK (have to spell 'cryptography' correctly ) However, I seem to have lost my PolyGlot auto-launch. I can get no response from the https://192.168.0.165:3000 now. Rebooted from PuTTY a few times. Can't seem to navigate around the polisys without some standard linux basics, to investigate further.

Got my PolISY today. Thank you very much!! Avoided customs, brokerage fees, and taxes. Shipping appeared to be about 7-8 days. WLAN board had fallen out. Placed back in the edge connector and it kept springing back up. Partially snapped it down. On closer examination one of the fastener clip's metal spring was flattened down. Bent it out of the way and bent it over the board once snapped down into the good clip. Not sure if I damaged the clip or it was damaged, letting the WLAN PCB loose. Working temporarily now. Powered up but could not get it to respond to https://polisy:3000. I have no DNS server on my LAN so I don't know how this could possibly work. Accessed my router, and found new connection/MAC address. Assigned it in my DHCP reservation table. Repowered up Polisy and it came back with my assigned IP address. Browser connected to polisy using assigned https://192.168.0.165:3000. Browser complained of no certificate, with all the silly negative advice about not connecting...ignored! as I also do with RPi PolyGlot. Polyglot admin console came up, reported it found an ISY on different subnet @ 192.16.1.70:70 but required security details. Corrected IP address and installed security details for ISY connection. Upgrades are offered to PolyGlot but will not install, as I receive the complaint "platform not recognised - freebsd" each time this is attempted with the built in method. The attempt cannot completed and fails each time. I assume this may take some SSH access with the appropriate updating, at this point in development.. Swapping polisy in for my RPi polyglot needs to be investigated yet, and I am not sure what I can experiment with and what I require to be completely solid yet. I don't use many NSs so just manually replacing devices in programs wouldn't be too much work, so far. Report more later.

Most people have just left their ISY username as "admin". Are you sure about using an email address for an ISY username? Your RPi reports that WiFi is blocked due to not setting your country parameter. I hope you are connected hard-wired Ethernet and not relying on WiFi for Polyglot.

Can't find my PolISY online!! I checked my router and found no IP address. I tried the admin console standard IP address and port 443 and still no success! Eventually I did find my PolISY via another URL, ….it was just released from Canada Customs in Toronto and out for delivery!! ? ?

I use http with all my rest calls to my ISY. V5.0.16. I don't use https for anything inside my LAN and very little outside.