dwengrovitz

@glacier991 I'd be interested in learning more about your solution if you don't mind posting the info!

@Kentinada It's pretty easy to setup. I installed it on a Raspberry Pi, and the instructions available through the HA site are easy to follow. I like eisy for most of my home automation routines, but I use HA to build and customize the user interface that controls everything from my iPhone. It allows access to those devices accessible via eisy plus many others, including the Honeywell thermostats. It also has a high WAF (wife acceptance factor), at least in my case. BTW - there are lots of posts in the UD forums re: other users and HA, so you may be able to get a sense of what they experience with a few quick searches.

I ran into a similar problem when I tried getting support from Resideo because the setup for the Honeywell Node Server wasn't producing the desired results. I went through their support chat line, opened a support case, emailed their developer support address, and followed up multiple times over several months, and never did get a response. It's now been almost a year since I started down that path. I eventually gave up and just decided to integrate Honeywell thermostats into my home automation setup through Home Assistant.

Thanks, this worked for me. My node server is back online.

I'm having a problem similar to @glarsen in trying to upgrade the Kasa node server. I've tried upgrading packages and reinstalling the node server several times but it continues to show as disconnected and won't start. The logs exhibit a similar message: ModuleNotFoundError: No module named 'kasa'

Got it - thanks! Installation went smoothly.

I'm not seeing this version in the Plugins Store yet - has it been posted?

There may be a more direct way to do this, but somewhere along the line I remember seeing the following command listed as something that could show you the versions of what's running on the eisy. https://eisy.local:8443/WEB/sysconfig.txt Look for isy in the resulting list, and it should show you the full version number.

Thanks @Geddy - I appreciate the response. I had seen the node server intro in the store, which indicates what you referenced above. The github entry is a bit more open to interpretation as it states "The Ring Node Server retrieves your Ring devices and allows you to get motion and ring events, and also control floodlights." I was hoping maybe "motion and ring events" would refer more broadly to a set of events caused by other Ring devices such as motion sensors, contact sensors, etc. Sadly, I believe it's "ring" vs "Ring" and I think that just means doorbell rings. Oh well -- I am glad for the level of support provided. Perhaps one day it will expand to include events from the broader set of Ring devices. Thanks again for commenting!

Indeed - glad that worked out for you!

I'm sure this is a silly question, but you've tried right-clicking on one of the items to be grouped and selected "Group Devices", right?

I did not go so far as to delete and re-add my I3 dimmers via the eisy admin console, but sadly there doesn't seem to be any update with respect to treating these as dimmers versus binary switches in the latest software update (5.6.4). If someone sees a different behavior, please post an update.

@Panda88 - Thanks for your response. No rush on this end ... enjoy your vacation!

I have a simple watchdog program that monitors the status of my Node Servers and sends me a message when one goes offline. I've noticed that the YoLink Node Server status (associated with the YoLinkSetup entry in the admin console on my eisy) always displays "Connected" even when that Node Server has been manually stopped and isn't running. The status of individual YoLink devices seems to accurately reflect whether they are connected or not, but not the status of the Node Server. Is this working as intended? Is it possible something else might cause that status to not change? I'm running IoX v5.6.3, PG3x v3.1.37, and YoLink NS v0.8.99 if that helps.

Sorry if I've missed this somewhere, but I'm trying to get a better sense of what the Ring Node Server supports. I am aware it works with Ring cameras and doorbells (and their associated motion sensors). Does it work with the Ring Alarm or Ring Alarm Pro, or any of the sensors connected to the Ring Alarms such as motion sensors, contacts sensors, glass breakage sensors, etc.?

Like @tazman, I still got the PG3x restart message, and refreshing the browser did get rid of it. I had to restart the Ring Node Server to get it talking to eisy again, but overall this was a pretty smooth update.

It don't think the dimmer is fully supported on IoX yet. I believe the intent is to do so, but I've not seen anything that indicates when.

My experience was similar to yours. After performing the restart, all seems to be working. Will monitor and post an update if any issues arise.

I re-ran the update this morning and am able to login to PG3x again. I do see the issues @bmercier noted above, but everything seems to be working so I'll look forward to 3.1.34 being released to fix those items.

Same - rebooted and hard restarted the device, and it didn't solve the problem.

Same issues here. I updated packages but PG3x showed the same version. I restarted the system and now cannot login to PG3x at all.

I also use the Yolink sensor (but I think it's actually the Smart Door and Window Sensor). I first tried using a Yolink vibration sensor attached to the bottom of the mailbox but there were too many false alerts. The Yolink sensor works really well, and my mailbox is at the end of a very long driveway (~150 yards from the house). For old times sake, I have it set so the speaker hub plays the "You've got mail" audio file (from AOL?) when the sensor is activated.

I had similar issues but tried again a few minutes ago and was able to successfully update to 3.1.29.

I tried updating both from within the node server (by clicking Update on the node server page) as well as by reinstalling into the same slot from the production store, but neither seemed to perform the update on my system. My installed version still indicates it is on 0.8.90.

I would echo this sentiment - playing around with the Yolink devices has been a lot of fun, and the node server and developer support thus far have been great.