dwengrovitz

Thanks for the suggestions, it's been pretty reliably used here for years as well. I can login to the UD portal via browser, and it shows my portal license is good through mid-2024, so I don't think this is a trial issue. I'll let it go a bit more and will put in a ticket if it doesn't resolve.

I am currently running three node servers, and they all seem to be working properly and populating in the admin console. Also, this is not a new account, it's been used for years, and was previously working successfully on the eisy (though I cannot say exactly when it stopped working on the eisy as the software there has been a bit fragile lately).

Sometime since upgrading to 5.5.7, the portal integration on my eisy went offline and now continues to show as offline. I've tried rebooting, and powering on/off, with no change. My system also displays a popup stating "Some updated packages are available for your system" upon startup, but running update packages doesn't seem to remove that. Update: a few more cycles of power on/off seem to have removed the message about "Some updated packages are available ..." but the connection to the portal is still offline.

I've enabled debug and will send you a copy of the log. Hopefully it will shed some light on the situation. Thanks!

I purchased a handful of YoLink devices to test in various scenarios, and so far really like them as well as the YoLink Node Server. Thanks so much for the development and integration work on this. Of the devices purchased, I have a couple of temperature/humidity (TH) sensors, including both the 8003 and 8006 (X3) models, and I am running current software versions on an eisy (ISY v5.5.7, PG3x v3.1.22, and YoLink Node Server v0.8.20). While reviewing the Admin Console , I've noticed that the "Current State" for the X3 sensors regularly changes from "Connected" to "Not Connected" after about 5-10 minutes. If I query their status, they immediately update and the status changes to "Connected", but after another 5-10 minutes they drop back to show a "Not Connected" state. This doesn't happen with the 8003 sensors, and I don't think this is actually a communications problem with the device, as they immediately update when requested. It seems more like an issue with how the Node Server is detecting status or perhaps a difference in what and when the two different TH sensor models report. They both show up in the Admin Console with Device Type of "Yolink THsensor", so maybe the Node Server treats them the same when they actually behave differently? Any idea what's going on here?

No rush on this end, but I am having a similar problem as @sjenkins noted. I've tried restarting eisy and PG3x multiple times, tried stopping, starting, and restarting the YoLink node server, and it just doesn't seem to fully start.

I tried rebooting the eisy and restarting PG3x multiple times, and no change. When trying to stop the YoLink Node Server via the PG3x UI it says: Node Server Stop: YoLink not running. When trying to start or restart the YoLink Node Server it says: Node Server Start: Node server already starting.

Upgraded again, and PG3x now seems to start as expected, but the Yolink node server doesn't appear to be operational any more. It doesn't start, and trying to start or restart it manually just exhibits the message "Node Server Restart: Node server already starting".

Same problem here. I ran the update on eisy and can no longer access PG3x.

Not sure if you logged out and back in (for PG3x) as part of your regular troubleshooting fixes, but I sometimes find that is needed for things to work properly after I upgrade.

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.