dwengrovitz

Ahh, got it. I updated pg3x to 3.1.24 and the issue with not being able to update the node server via a restart was still there, but I was able to successfully delete and reinstall the node server to get the latest version. Thanks very much for the assistance!

I tried upgrading via PG3x (by either restarting the node server, or attempting to delete and reinstall). I wasn't aware there was a way to upgrade node serves from within the AC.

I am running V0.8.50 and am seeing some installation issues with trying to upgrade to the latest version (0.8.88) of the YoLink node server. If I restart the node server, it briefly reflects that the version was updated to V0.8.88, then a few seconds later it displays V0.8.50 again. I think this issue has been there for a little while, but I was able to previously get around this by deleting the old Node Server and doing a clean install of the latest version, but that no longer seems to work. If I try to delete the existing Node Server I get an error "Failed to remove Node Server YoLink from slot 60: Cannot read properties of null (reading 'filename')". Any suggestion on how to install the latest version?

Thanks, Bob. I appreciate the response (and the fact that it's a big change to address). If you decide to make the node server fee-based instead of free due to the level of effort required, I would happily contribute.

Has anyone had any luck using the Roomba Node Server on PG3x with a Roomba i8+? I gave it a try, but it seems the process for enabling the node server to communicate with the Roomba is different on this model than some of the older ones? Pressing and holding the home button doesn't make the wi-fi light flash on this model, and the node server starts password discovery but never gets a response from the device.

Things have been pretty stable since the update, and I don't think the X3 has lost connection since. I think it looks pretty safe to say this one has been solved. Thanks again for the assistance!

I installed v0.8.41, but noticed an odd issue with installation of the node server update. My assumption is that restarting a node server when there's an update available should automatically install the new version, correct? After restarting my YoLink node server, it looked like an update was applied, and the version number increments to 0.8.41, but shortly after (a few seconds) it displays the old version number like the update didn't fully complete. I think I saw something similar in behavior with the last version update, and the only way I could get around it was to uninstall and reinstall the node server and that seemed to address the problem. After trying that with this update, the running version displayed shows 0.8.41 as expected and it sticks. That said, I'll test out the new function and will report back on how the X3 looks. So far, it shows up as connected, and data seems to be flowing.

You're correct - and thanks again for your comments. Intervention was indeed needed, but in this case, I think it's all on my end. I did some more digging, and noticed that for some reason my firewall started blocking requests to proxy.isy.io and proxy2.isy.io. After adding a rule to allow that, connection to the portal as been restored.

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.