dwengrovitz

I noticed an update was available for PG3 today, so I ran the commands to run the update and installed the latest version (3.0.45) as well as the latest IoP (5.4.1). All of my node servers came back online with the exception of the WirelessTag node server. I am running v3.1.3 of the WirelessTag node server, but it just shows as being in a "Disconnected" state on the dashboard, and restarting the node server, PG3, or IoP don't seem to have any effect on restoring the connection and bringing it back online. The last few lines in the logs were from about an hour ago after I ran the updates and they just say: 2022-03-09 16:57:07,008 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message stop 2022-03-09 16:57:07,010 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING stop 2022-03-09 16:57:07,011 Command udi_interface.interface INFO interface:_handleInput: Received stop from Polyglot... Shutting Down. 2022-03-09 16:57:07,012 Thread-1505 udi_interface DEBUG Controller:handler_stop: Node server stopped. Anyone else having issues w/ the latest PG3/IoP updates and WirelessTag?

Using the revised instructions did the trick. Thanks very much for the update @bpwwer.

@bpwwerSo I upgraded PG3 to 3.0.39 yesterday, and saw that release 3.0.40 was announced today, so I updated again. I followed the instructions in the 3.0.40 release announcement to correct the issue with all node servers showing as "unmanaged" but that did not seem to address the problem for me. All of my node servers still show as "unmanaged" under PG3 3.0.40. Any suggestions?

I updated my Nodelink server (running on a Raspberry Pi) to V0.11.2. I couldn't get the upgrade to fully execute by hitting the "Check for Update" button on the System Config page, so I just re-ran the install script and that seemed to take care of it. However, it seems like there is still an issue with not being able to update the node definitions on an ISY running on a Polisy device. It tries to update them, and says they were updated successfully, but restarting Nodelink continues to present the same error indicating they need to be updated (see screenshot below).

I'm on a fairly recent version, but am also having issues with the update. Should I also rerun the install script to complete the update?

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?

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.