dwengrovitz

I ended up installing Home Assistant on a Raspberry Pi. I still use an eisy for the bulk of my home automation and control functions, but I found the interface I could create via Home Assistant worked really well in providing a simple customizable UI for the family to access via their portable devices. It allows them to control a subset of my total devices (e.g., turn lights on/off with dimming, view/set temperature on thermostats, control Sonos and other media devices, control ceiling fans, open the garage door, etc.).

@Geddy Thanks for your response. Yes, I rebooted the admin console after adding the plugin, and I read the content on github, but I wasn't able to get the node server to auto discover anything. After manually adding the RGBW2 device on the PG3x node server configuration screen it did show up in the admin console, and it appears to function. The docs re: the node server on github are somewhat sparse, so I'm not quite sure what else to expect to see in the admin console. In many node servers there is some type of controller as well as devices, and in my case for this node server I only have a device. The option to add a controller appears to be available through the admin console but there's no info in what to put in any of the fields. I've tried guessing at what to enter based on some of my config details but the results just come back as "Bad Request" so I'm clearly not putting the proper info in there.

I recently installed the ShellyRGBW2 node server and was able to successfully add a Shelly RGBW2 device to my eisy to control some LED strip lights. I had to manually add the device to my PG3X config, as I could not get discovery to work. It doesn't look like the node server is really being maintained any more by the original developer. Does anyone have any insight on how to add the RGBW2 Controller to the configuration? When attempting to do so through the admin console, the following dialog box is requested, but I wasn't able to find anything that indicated what data should go into the fields and how that should be formatted. Any insight would be greatly appreciated.

I installed V1.0.7 and it seems to have resolved the issues I was seeing with the garage door and water leak sensors. Thanks again!

Awesome - thanks! And thanks for the ongoing work on the Yolink node server. It's worked really well in my environment, and the reliability, range, and integration of the devices in eisy is great.

These are the four devices that show up as being "Not Connected" in the easy admin console, but the Yolink app all shows them as being in a "Normal" state.

FYI - I sent you the log package via PM.

I updated to V1.0.6 this afternoon and noticed a few of my sensors don't seem to be reflected as expected. My Garage Door Controller (YS4906-UC) shows as "Not Connected" until I open or close the garage door, then it shows as "Connected". My leak sensors (YS7903-UC) all show as "Not Connected" even though the Yolink app shows them as being online. I haven't tried to manually trigger them, but can do that if it would help. I'm also happy to send you logs if needed.

While I'd like to see this product become available, I'm not sure this is real just yet. Seems like a real product announcement might include some actual technical details on the product. I emailed their customer service folks just a few days ago to ask about the new hub and this was their response: "Thank you for reaching out to us and for choosing YoLink products! We're thrilled to share that we have exciting plans to launch our new hub, YS-1605, in mid-2024. One standout feature of this upcoming YoLink hub is its capability to support a SIM card. However, as the device is currently undergoing its final development stages, some features are yet to be confirmed pending thorough testing. We kindly ask you to stay tuned to our website or Facebook page for the latest updates and further details as they unfold." There doesn't appear to be any news on their Facebook page, so perhaps this is just a placeholder to generate some marketing buzz? Plus, it's listed on their website as "Cellar hub with battery backup".

If possible, I'd like to see support for: Manufacturer Name: Inovelli Model #: Blue Series Smart 2-1 Switch (On/Off or Dimmer) Link: https://inovelli.com/products/zigbee-matter-blue-series-smart-2-1-on-off-dimmer-switch Key/desired function support: On/Off and Dimming Functions

@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.?