dwengrovitz

I have an old X10 remote chime in my setup. Not sure if that's the same as the X-10 ding-donger you are referencing, but it works just fine on my IoP.

I tried the Minoston Z-Wave Mini Smart Plug Dimmer (MP21ZD) a while back when I started playing around with Z-Wave on my IoP. The price point was good so I ordered three of them just to try things out. One of them quit working after a month or so. I tried emailing the vendor for support but got no response. Maybe I just got a dud, but given my experience I don't think I'll be purchasing any more of them.

@bpwwer I was going to say the same about you! Thanks for the quick fix(es). I've got some more testing to do, but most things seem to be working for me. The one problem I've seen in my quick round of testing is with a Kasa outdoor plug/switch that the node server sees but cannot seem to control. I'll have to do some more testing on that one. Thanks again!

I was also seeing problems with the upgrade to 3.0.55. I did the upgrade via SSH. First time I ran it the system updated to 3.0.55, but I could not access PG3 via browser. I ran it again and noticed the upgrade to 3.0.55_1 ... but still could not access PG3 via browser. I ran it again and noticed the upgrade to 3.0.55_2. The upgrade via SSH still throws an error after trying to restart PG3 via command line (see below), but I am now able to access PG3 via the URL. The error I see via SSH is: [admin@polisy ~]$ sudo service pg3 restart cat: /var/polyglot/pg3.pid: No such file or directory usage: kill [-s signal_name] pid ... kill -l [exit_status] kill -signal_name pid ... kill -signal_number pid ... Stopping polyglotcat: /var/polyglot/pg3.pid: No such file or directory ps: option requires an argument -- p usage: ps [-aCcdefHhjlmrSTuvwXxZ] [-O fmt | -o fmt] [-G gid[,gid...]] [-J jid[,jid...]] [-M core] [-N system] [-p pid[,pid...]] [-t tty[,tty...]] [-U user[,user...]] ps [-L] done cat: /var/polyglot/pg3_daemon.pid: No such file or directory usage: kill [-s signal_name] pid ... kill -l [exit_status] kill -signal_name pid ... kill -signal_number pid ... Starting pg3.

Thanks @macjeff. I changed the log levels and restarted the node servers, and data for WirelessTag and Sense devices now seem to be populating. Data for some of the Kasa devices now shows up, but not all. Harmony Node Server Profile now seems to work but the hub itself showed "offline" for a brief period, then came online and data populated for devices and activities.

3.0.53 broke a lot of already installed node servers for me. When looking at the IoP admin console: WirelessTags shows the Node Server Connection as "1" and "Commumicating" is "False" and no data is being received for any tags in the console. Harmony shows Node Server Connected as "Connected" but Profile Status is "Uninitialized" and doesn't change if I try to install, build, or update the profile. No data is being displayed for any devices. Kasa shows Node Server Online as "Connected" but no data is displayed for any devices. Sense shows Status as "True" but no data is being received for any devices. I've restarted/rebooted IoP (5.4.1) and node servers and that doesn't help.

@bpwwer I was able to restart the node server. Thanks for looking at this one.

I tried restarting the node server, and captured what was in the PG3 log. I can send that to you if you would like.

Sorry - the version of IoP is 5.4.1 not 5.2.1. Topic title corrected.

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.

I just ran into this same issue and am hoping there's a way to change the link to the ISY on Polisy without having to delete and start over.

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.