dwengrovitz

I've started playing around with some of the Yolink devices and have setup the associated PG3x node server. So far, it looks pretty interesting, so great job and thanks for creating it! In testing out some capabilities associated with the motion detector, I noticed this spelling error in IoX ("Motion State" is spelled "Motoion State"). Seems purely cosmetic and not worthy of an update release just to fix this, but you might want to queue up a change if you have other items to update at some point down the road.

I can't remember the exact steps I went through, but I also had some issues that I think were caused because my connection to the portal wasn't active. Just out of curiosity, does your Portal Integration show as being online?

This is a minor and mostly cosmetic issue, and I don't think it's new to PG3x 3.1.18, but I thought I'd mention it anyway. When restarting a node server from the PG3x dashboard, the node server status changes from "Connected" to "Disconnected" and back to "Connected" as expected. But the Uptime counter just continues to tick the time away as though nothing happened. It's not until one refreshes the browser screen that the Uptime counter resets to the time that's passed since the node server was restarted. Seems like that counter should reset without having to refresh the screen, but it doesn't (at least not for me). BTW, I'm accessing PG3x via Chrome on MacOS.

@asbril beat me to it on the response, but it should look something like this when you are successfully connected to the portal. I did, however, also migrate my licenses.

I had a similar issue, and approving the eisy in my Portal account helped put things on the right track. I also made sure to log out and log back in to PG3x. Not sure if that helped, but it certainly didn't hurt any in my situation.

Yes, I can access and control all of the thermostats via the Resideo app.

I recently moved into a new residence and updated a good bit of the old technology in the house (e.g., thermostats, smoke/co2 detectors, etc.). The HoneywellHome Node server was working in my prior residence where I had TH9320WF5003 thermostats installed and was using PG2, but the thermostats (RTH9585WF) installed in the new residence do not show up when I go through the process to CONNECT devices via the Honeywell Home site (see attached screenshot) using PG3. I tried chatting with their thermostat support folks online, but they didn't really have any insight or information on API access. I also tried emailing developerinfo@resideo.com (on 12/19) to see if they could provide some insight or indication of when this device might be supported for API access, but either they are somewhat non-responsive or perhaps they took a lot of time off around the holidays. If the situation changes or I ever get a response from their developers I'll post an update, but if you are looking to integrate RTH9585WF thermostats via the HoneywellHome Node Server beware. Interestingly, there's been a pretty big push on selling this model lately, including attractive prices as well as rebates from the regional energy company.

I ran update packages again and restarted with 3.1.8. Previously, both the Kasa and Wirelesstag Node Servers went offline about 30 seconds after they started. It's now been almost ten minutes and both still seem to be alive, so it looks like your update may have taken care of it. If they go offline again I will let you know and send the log, but otherwise, it seems to be working now.

I may have had a trial license at one point but it's been so long I can't say for sure. I restarted PG3 and grabbed the log for about 3 minutes, starting with the restart and ending shortly after the Kasa and Wirelesstag Node Servers go offline. What's the best way to get you the log file?

I updated PG3 to the latest version (3.1.6) and am seeing an issue with the Kasa Node Server (3.0.11) as well as the WirelessTag Node Server (3.1.6). After restarting PG3, both of these node servers show "1 New Message" next to "Details" on the Dashboard, and both Node Servers remain disconnected. Upon viewing the details, they both show a notice that says "The subscription for this node server has expired". My list of Node Server Purchases shows both of these node servers have been purchased and "Never Expire". If I restart them, the message goes away, they restart and connect to IoP, but after about 30 seconds they disconnect again. Seems like something is off with the subscription status for these Node Servers on the new release of PG3. I am happy to provide log files if that would help with further diagnosis.

Thanks for the info @dbwarner5. I tried messing around for a few hours last weekend with having my Ring Doorbell set an ISY variable via an Alexa routine and it just wasn't working as expected. Everything looked right in the setup, and it ran when I manually triggered the routine via the Alexa app, but it just wouldn't set the variable automatically when motion was actually detected. It wasn't until I disabled and re-enabled the Alexa skill that things starting working automatically, so thanks for mentioning that.

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?