dwengrovitz

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

I recently ordered and installed nine SmartWings woven shades, and I went with the Matter motor. For now, I use Amazon Echo devices to handle the automation (e.g., opening in the morning, closing at night, etc.). The Matter motor has been just okay so far. On some days, I notice a shade that didn't open or close as expected, so reliability hasn't been rock solid, but I can't say if that's the shade motor fault or the controller side. As other stated, there is always the remote. That works flawlessly, and I like that it can open a single shade or multiple shades in a group with one click. The battery operation and design of how one can customize various operational parameters (e.g., setting upper and lower limits, pairing motors to various remote channels, etc.) is really kind of elegant. I did run into a couple of issues where I needed to contact customer service, resulting in some shades that needed to be remade. On one, a clip came loose inside the rod during transit and it made an odd noise whenever I raised or lowered the shade. On a couple of shades that were supposed to be light blocking, there was a defect that allowed light through in several points where the back of the shade was stitched to the guide for raising/lowering. Their customer service folks were excellent to work with and they fully addressed the issues I experienced. Overall, I'm very pleased with the end result. The jury is still out on whether going with the Matter motor was the best decision. It adds a lot to the price, and a fully reliable implementation still seems more promise than reality at this point. Like others, I am hoping the UD team releases an update to eisy so I can run my shade automation from that instead of the Alexa app.