dwengrovitz

Is any information available on how to setup or configure eisy to control Matter devices? I've enabled it via the Admin Console and can see "Matter" in the menubar, but I'm not quite sure how to go about adding devices. Also - does the network connection from eisy need to be WiFi to work with Matter, or can I continue to use a wired network connection?

Thanks @paulbates - I tried the instructions you posted but couldn't get it to work as expected for my LG TV. That said, I like the concept of using ChatGPT to come up with a technical solution, though I also realize one cannot necessarily assume the solution will be correct. I'll try a few more things to see if I can get control to work via network resources. Worst case, I'm pretty sure I can create a variable or virtual switch in eisy, expose it to Amazon through my.isy.io, and use that to signal an Alexa routine to turn the device on or off.

Does anyone have any guidance on how to provide basic on/off control of LG OLED TVs (model C2) via eisy? I looked at AVRemote but unfortunately it doesn't seem to support newer webostv devices. Is there a set of network resource files someone has created that would work? Or perhaps expose a variable in eisy that an Alexa skill could pick up and run a routine on?

Thanks, that did the trick.

I installed V1.2 and all of my Ring devices have gone offline for my EISY. The PG3x log shows lots of issues with expired tokens, failing to refresh the Oauth token, and calls to the Ring API failing. Something in this release has not gone well for my devices.

I believe there is an EISY plugin for the Shelly RGBW2 controller. I don't have mine setup right now, but I did some basic testing a while back and it seemed to work in controlling some LED tape lights I was using.

@Kentinada Definitely won't hurt to have two hubs online ... and might help depending on the construction where the sensors are located. Though I have to warn you ... once you have two hubs online, you may start wondering why you don't have more of their sensors.

As far as I know, one doesn't connect sensors to a specific hub, so I'm not sure you can specify devices on one level should connect to one hub and devices on another level connect to the other. You just add all sensors and hubs into the app, and what connects to what is transparent to the user. With the great range of these devices, having a second hub online within a reasonably sized house for a small number of sensors won't hurt, but it might not help much, unless you have connectivity issues and one hub goes offline. In that case, I think the second hub will take over. BTW - for each sensor, you can check signal intensity as well as battery levels from within the app. So in your case, you might want to install the sensors and one hub, then check the signal intensity on the sensors. If for some reason you don't have good signal, install the second hub, and check the intensity again. Again, the range of the these devices is so good it might not make much difference. As an example, I placed a contact sensor on the door of my mailbox. The mailbox is about 150 yards away from the house through a somewhat wooded and hilly landscape, and there's no clear line of sight. I've setup an audio alert that says "you've got mail" on the Speakerhubs when the mailbox door is opened (and I also get text message notifications through eisy), mainly so I can avoid walking out there when the mail hasn't been delivered yet. The signal intensity of the sensor even at that distance still shows as "strong".

I have three hubs ... two are Speakerhubs and one is not. All are WiFi connected and are online at the same time. One Speakerhub is in a place where it can be heard throughout most of the house. The second is in my office/workspace, which usually has the door closed so the first Speakerhub can't easily be heard there. A third (non speaker) was placed in a location at the far end of the house to get a bit stronger signal and better reliability from a particularly remote sensor (at the recommendation of the Yosmart support staff). Audio alerts don't happen at exactly the same time, but my hubs aren't really within earshot of each other so that doesn't matter much to me.

@Kentinada I think the link you provided is for their Leak Sensor 1. It's fine, but they do have several models to choose from depending on your needs. The Yosmart website has a good overview and comparison. I believe the Leak Sensor 4 is like the Leak Sensor 1, but with a siren and the ability to also report on cold temps (in case it's in a place where pipes might freeze). I have some of each and they both work just fine. Just want you to be aware that, depending on your needs, you might want to look at some of the other options they have. On that note, they also have options for the hub. I have a couple of their Speakerhub devices because I wanted the ability to easily integrate custom audio alerts. The hubs aren't expensive, and the delta to go to the Speakerhub versus the regular hub wasn't much more than the cost of a cheeseburger these days (maybe even less). There are multiple ways one can integrate audio alerts, but having something announce "the leak sensor detected water under the kitchen sink" can be a lot easier to work with than trying to figure out where that beeping is coming from. Of course, you can also use the eisy to generate email and instant messages, and support from the plugin developer has been great. Again, the hub in the starter pack is fine, just want you to be aware there are options.

I've used Yolink sensors and they've been rock solid for me. They transmit over long distances, use a readily available battery (and battery life is very good), and they integrate well with the Eisy/Zmatter environment via a plug-in. They do, however, require a Yolink hub.

I had actually already tried a reinstall, but did it again. No change. All plugins still show as disconnected.

I checked the logs for the individual plugins and they all seem to end with this: 2024-06-11 18:27:41,658 MQTT udi_interface.interface INFO interface:_disconnect: MQTT Unexpected disconnection. Trying to reconnect in 10 seconds. rc: 7 The system log on PGX3 does have additional information populated after that time but nothing that jumped out at me as an issue (though I'm not quite sure exactly what should be there).

@Techman Thanks for the suggestion. I ran the update again, but no change.

I tried updating PG3X from my eisy via the Admin Console. The update seemed to progress ok, and I rebooted when the message came up saying it was time to. My Insteon switches came back online and appear functional, but none of my seven plugins came back online. PG3X shows it's at version 3.2.27 with status "connected", and IOX is at version 5.8.3 also with status "connected" as shown on the PG3X plugin dashboard. All plugins show as "disconnected". Rebooted from the Admin Console again, same result. Powered off and on, same result. Any suggestions? I can provide log files if needed.

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