dwengrovitz

@IndyMike Thanks. I opened the event viewer in the AC and it does see the links via in the Admin Console, but the new eisy-ui doesn't appear to show them.

I tried Show PLM Links Table on eisy-ui (beta 1.3.11_1), but all I see is this ... should it be displaying actual data or are my links really hosed?

I'm running the latest eisy-ui from the beta repo. When we previously updated the device code via the Admin console, it almost always required a reboot. However, when updating the code via eisy-ui, it generally says the update is done (but doesn't say anything about reboot). Can someone clarify what to expect re: code updates and reboots when using the new eisy-ui? Should I reboot or not after an update, or will the UI always tell me when a reboot is needed? Also - if one elects to manually reboot - the status message displayed is yellow on a white background (when in light mode) and is pretty much impossible to read (as shown below).

I'm seeing this same issue on my system. I haven't made any changes in PG3x, and I've restarted the eisy and Admin Console multiple times. I don't think this has anything to do with restarting after making changes.

Yes ... this was absolutely the case. I ended up removing the Genie skill from Alexa to help minimize any confusion. We'll have to do more testing to see how that goes over time.

After a few trial and error exercises, I ended up configuring up a virtual switch and setting that up as a device with open/close status via the ISY portal. That exposed the device to Amazon/Alexa for voice control (e.g., open or close the door), and the eisy integration for Home Assistant exposed the virtual switch there for initiating an automation, which successfully bypasses the requirement to verbally provide the PIN. Works great - thanks all for your comments and input!

I am not entirely sure - it can open the garage door via the app UI (without a PIN) but the voice control I am using in HA is currently Alexa - and that seems to require the PIN. Thanks - it does. I am currently using a Genie opener, which has an integration for HA but not eisy (that I know of). I'm mainly trying to get around the commercial integration and what appears to be Alexa's requirement to provide a verbal PIN when opening the door by voice. Thanks, Guy - I'm familiar with setting up a virtual device and letting Alexa see it as on/off then triggering an automation of some sort. I just wasn't sure if the voice control would then have to be "turn on the garage door" vs "open the garage door" which seems a bit less natural for others in the house. I'll keep playing around with more ideas on this - but I appreciate you guys all providing some input!

I'm trying to better understand if and how this plugin can assist in providing a virtual garage door that's easy to control via voice. I'd like to be able to ask my Alexa devices to open/close the garage door and have the door do that. I can currently accomplish this with the garage door integration that Alexa already knows about, but the Alexa devices want me to verbally state a PIN to take action (which I understand is for security, but the concept of me having to state my PIN out loud seems relatively insecure). Can I use this plugin to establish a virtual garage door device that Alexa knows about, and when I ask to open the garage door, the virtual device would trigger an automation in Home Assistant to control the real garage door (which HA already knows about)?

I've had good success with Yolink sensors. They are reasonably priced, reliable, battery life is great, and there's a super developer (@Panda88) with a well supported plugin for eisy. You need a hub to go with them, but their hubs are also reasonably priced. Last I checked, a single sensor was about ~$45 on Amazon, ~$55 if you also get a hub, and ~$81 for a hub plus two sensors. Just a warning - they are kinda like that old potato chip commercial - bet you can't get by with just one [okay, so maybe the commercial was "bet you can't eat just one"]. I started with a couple but liked them so much I now have their motion sensors, leak sensors, vibration sensors, door sensors, temperature sensors, and even a few of their no-neutral switches in my environment. All integrated with eisy and Home Assistant.

A short press on each of the buttons did indeed update the status from Unknown to ON (DON). I'll experiment a bit more with that function, but it looks like the issues I was seeing are now resolved, thanks again! Still happy to send you a Flex Switch if you want one. :-)

Thanks for the update. At first glance, my temp sensors now all seem to work correctly. The Flex Switches also appear to work, but the status of the additional two button controllers appears as unknown in the Admin Console. I can live with that, as I don't really use that function, but if you'd like to fully support that just let me know and I'm happy to assist with logs, testing, and whatever else might be needed. Heck - message me your shipping address and I'll have Amazon send one to you to test with just to say thanks for the great community support!

@Panda88 - I tried sending you a debug log with some screenshots, but the UD message system just said "Panda88 cannot receive messages."

I am seeing some unexpected things since updating to the latest release. My Local hub now says "Alert" under "Supply Status" in the devices View, and in the Current State when listing devices via the Admin Console. I don't recall seeing that before (but perhaps just missed it) and am not quite sure how to address that if it's a real issue. The Current State and multiple other values appearing in the Admin Console device view show as "Unknown" for several devices and device types, including my Flexswitch devices (YS5709-UC) and some but not all of my temp/humidity sensors (YS8006-UC). If I manually update the device status for those devices via the Admin Console, the values seem to get updated but many return to show "Unknown" statuses again shortly after update. When updating status manually via Admin Console, I occasionally get "TCP client read response failed" messages (NS-70-YolinkLocal).

I definitely agree with that statement. I had integrated MyQ with my ISY environment way back when and it really pissed me off when they shutdown access through their API, so much so that I eventually got rid of anything MyQ-related. I've had good success with YoLink as an add-on replacement, though I used their Garage Door Controller rather than their Finger Controller.

I consistently have issues with status deltas across the various UIs, to the point where the only one I can really use is the Admin Console when logging in with my ISY credentials. Does your question apply to just the device status or also flag status? For example, in the Admin Console (login via ISY credentials), all of my devices and device flags have current states. In the Admin console (login via portal credentials), most devices are missing flag status. In eisy-ui, most devices are also missing flag status.