dwengrovitz

Indeed you are right. I just restarted the node server and it upgraded to 3.0.12 as expected. Thanks.

According to the dashboard I have 3.0.11 installed, and I can see 3.0.12 in the store, but stopping and restarting the node server does not appear to do an upgrade of the installed version to 3.0.12 (at least not for me). Is there a way to force the upgrade via SSH?

Thanks for releasing this on PG3. I'm just starting to migrate a few of my nodeservers from PG2 to PG3 and this was one of the first I tested. Took a couple of restarts but eventually all my tags migrated smoothly. One thing I did notice is the same typo I posted about for the PG2 server -- "commumicating" vs "communicating". Pretty minor, but probably something to update at some point.

Try typing "thisisunsafe" ... without the quotes, not in the address bar, just type it on the keyboard when you hit that page.

Does Nodelink support working with ISY on Polisy? If so, are any special configuration settings required?

I never could figure out why the devices (mainly my switches) would not update unless manually queried after migrating over to ISY on Polisy, but I ended up deleting and re-adding each switch individually, and refreshing/saving any programs that used them, and they are now updating automatically as expected.

I'm seeing a similar issue with switches. I moved to a new USB PLM, and did a restore. The ISY sees my devices and can control them manually and via programs. The status of motion and leak sensors seems to update okay, as does the status of devices connected via node servers. But the status doesn't seem to be updating properly for any of my Insteon switches unless I query them.

I have a number of legacy devices from the old X10 days that I used to control via my ISY994i. Mainly things like a chime that would go off if one of my Insteon leak sensors detected a leak. I did a quick search through the forums, so my apologies if I missed this in prior posts, but will ISY on Polisy support X10 devices via an add-on module like the ISY994i did? I did not see that module as one of the ones that was migrated when I did the backup/restore from my ISY994i to ISY on Polisy.

Thanks - reseating the USB cable did the trick.

I tried doing a backup and restore from my ISY994i to my Polisy. It appears that the configurations have moved over as all of the devices and programs seem to be listed, but I am not able to restore the configuration to a different PLM and can not communicate with any of the devices. The PLM restore gets to the same point every time and fails. The error I see is: Any suggestions on how to proceed? Best I can tell, the restore routine dies when looking for a file that doesn't exist in the backup from my ISY. I could not find FF0108.REC in the zip file from my backup.

Tried that multiple times, but it didn't work for me.

I got the same mismatch between admin console version and firmware as @tazman when using: https://<your polisy ip>:8443/admin.jnlp But things matched up and worked for me when using: https://isy.universal-devices.com/polisy/5.3.0/admin.jnlp (though I had to remove the "d" from "universald").

I used Nodelink originally for years and switched over to the Envisalink node server shortly after it became available to interface with my DSC system. The integrations were rock solid, and I have nothing but praise for the developers of those platforms.

Thanks @MrBill. Much appreciated.

@carealtor - can you elaborate a bit on this? I had kind of given up seeing if I could fine tune the LED brightness since this issue has been there for so long and I was never very successful in trying to accomplish this via the admin console. I guess I never thought of using a program to do it. Would you just run a program that sets backlight levels to a set percentage?

Just curious ... are you running the same environment I am (Mac/Catalina)? On my machine, there's no simple way to ignore or get past the warnings. If I use Chrome, I cannot get to Polisy without typing "thisisunsafe" to dismiss and bypass the warning (and that's not exactly an obvious solution). And if I use Safari, there's an option on the privacy message that says "visit this website" but it doesn't work. Selecting that option just redisplays the "this connection is not private" message. I'm not worried about attacker stuff on my internal LAN ... I'm just pointing out some access issues that, if resolved, might make it a bit better experience for other Mac users running Catalina when they try to get their Polisy running.

Sorry ... I was just hunting for solutions or workarounds. Perhaps the issue I'm seeing is related to changes Apple recently implemented with TLS server certificates? I don't know how directly relevant this is to what's going on with the Polyglot/Polisy system, but at least one other person has run into the problem I'm seeing with not being able to access the app via Chrome. A bit more research on my end located the following: Apple has introduced a series of new requirements for SSL certificates to be accepted by Catalina, documented at https://support.apple.com/en-us/HT210176. To summarize: - Key size must be at least 2048 bits. - Hash algorithm must be SHA-2 or newer. - DNS names must be in a SubjectAltName, not in the CN field only. For certificates issued after 2019-07-01: - The ExtendedKeyUsage extension must be present, with the id-kp-ServerAuth OID. - The validity period may not be longer than 825 days. Interestingly ... there's a workaround on Chrome if one runs into this problem when accessing Polyglot or Polisy. When the error message is displayed about the connection not being private, you can click somewhere on the page and then blindly type "thisisunsafe". This will instantly bypass the warning. Not sure this is a great solution for the long term, but it did allow me to get to the app directly via chrome.

You're luckier than I am with Safari. I wonder if something needs to be updated on the certs being used by Polyglot and Polisy to fix this.

Is anyone else using a Mac with the Catalina OS on it to access Polisy? Ever since upgrading to this OS, I've been seeing issues with accessing Polyglot using different browsers on this platform. Unfortunately, the issues seem to also apply when accessing Polisy. I can access Polyglot/Polisy using Firefox, but if I use Chrome I get an error (see attached "Privacy Error 1.png") and am unable to proceed. I see a similar issue when using Safari (see attached "Privacy Error 2.png"), but while it looks like you can get to the site by clicking on "visit the website" ... that doesn't actually work. I've tried this using two different Macs running Catalina and the results are the same. I've also tried accessing Polyglot/Polisy using Mojave and, while a privacy error is displayed, there's an option that still allows me to get to the app. Just wondering if this is something unique with my systems, or if there's an underlying compatibility issue with MacOS, various browsers, and Polyglot/Polisy. I think Catalina tightened down a few things from a security perspective, but it would be a shame for MacOS users running the latest OS to run into this when broader distribution occurs.

I'm seeing similar issues to others. My Polisy had a noticeable rattle so I opened it up and the wifi card wasn't attached to the main board. Reseated it, and went through some of the update steps described in prior postings. I can still SSH into the box, but the web UI isn't accessible. Glad to see Nodelink running on this. I hope that's a supported option going forward as i could then totally repurpose the Pi I've been using to previously run Nodelink and Polyglot.

I re-ran the install script on my Pi. Is the latest version V0.10.1 or V0.10.0? My system shows the latter, but the release notes only show V0.10.1 with no mention of V0.10.0. In addition, the auto-update doesn't seem to see the proper files and I'm getting a 404 error. Here's the startup (w/o IP addresses) on my system: 2019-10-26 23:47:43 - ISY NodeLink Server v0.10.0 started 2019-10-26 23:47:43 - OS: Linux raspberrypi 4.19.75-v7+ #1270 SMP Tue Sep 24 18:45:11 BST 2019 armv7l GNU/Linux 2019-10-26 23:47:44 - Web config server started (http://192.x.x.x:8090) 2019-10-26 23:47:44 - ISY resolved to 192.x.x.x (5.0.16) 2019-10-26 23:47:44 - ISY Node Server config detected (profile 1) 2019-10-26 23:47:45 - Auto-Update: Error updating file: The remote server returned an error: (404) Not Found.

Wow ... your timing could not have been better. I was literally in the process of re-building the NodeLink setup on my Pi 3 b+ late last night when I saw your notice so I switched plans. Installation on Debian 10.1 went fine, and the interface to my DSC panel and Honeywell thermostats seem to be working. The NodeLink web interface on the mono version would frequently show periodic errors for me, like timeouts or problems with the stats responding, but so far this morning the panel is error free. I am also running Polyglot on the same Pi. Will let you know if anything crops up but so far all is well.

Has anything changed with respect to reading or setting backlight levels in the latest code versions? I'm running V5.0.15A, and am seeing some really odd things with the backlight setting. If I set the backlight level on one device (for example, a 2466D), I see the settings for a number of other devices updated to reflect whatever I set the value for on that one device. I'm not sure the actual devices get updated (they definitely don't all seem to reflect the setting if I look at the LEDs) but the value showing up in the admin console does. For example, I have around 35 Insteon switches, with a mix of types (2477D, 2466D, etc.). To start, I set every switch backlight individually to 100. Then, I set one switch to 50, and I now see the backlight levels for 26 other switches now showing as 50.

I ordered one ... will let you know what I learn when trying to integrate it with my ISY.

Not sure if you ever heard from anyone on this question ... but I would also be interested in hearing about experiences with this device. I see that there is a Nodeserver for SenseMonitoring in the Polyglot NodeServer store. Might be kind of interesting to be able to have some integration with ISY when various devices are on or off in the house.