auger66

Probably/maybe. I think every software company claims "security" when they don't want to do it. Plus, Google has done almost nothing with Nest since they bought it. Funny how some companies can make APIs safely and some can't/won't. Regardless, the new thermostat has Matter, and that's probably going to be the easiest way to integrate Google into UDs ecosystem now.

Yep, I forgot about this. Mine updated automatically.

I saw that, but I still had to try. 🙂 Nest thermostats haven't had a working plugin in a long time. Since it's such a big gap in UDs integration, hopefully it will get a little Matter priority.

IP via wifi

I tried to add the new Nest thermostat (Matter) with the updated UD android app via QR code. It wouldn't add. I didn't think it would work through my non-border router, but I had to try.

Followed the directions. After upgrade, my eisy was offline on the Portal, UD mobile, locally, etc. The eisy did show up on my network at the usual reserved DHCP address. Eisy also did not show up the ISY finder, even if I typed in the local IP address. I tried run ssh in windows and putty, but it wouldn't allow me to paste or type in a password. I repowered the eisy as felt I had no choice. My eisy showed up immediately in the ISY finder, and I was able to log in without issue.

I have the same issue.

I just installed the new Nest thermostat and Nest plugin. I have the same problem as the OP.

I just today received my 13th replacement Tempest in two years. Replacements were mostly due to a failed baro pressure sensor. My last failure was the hygrometer. I had a couple completely fail. If you go with Tempest, I highly recommend putting it in an easy-to-replace location.

I can't try it until I get home in three months, but I definitely will. Thanks for your effort on this.

😀 No kidding. I have Tesla FSD. Matter is running neck and neck with FSD on broken promises. When FSD went to "end-to-end machine learning" several months ago, the improvement in my urban area was dramatic. FSD went from horrendously bad to really terrible. I just got to my seasonal, very rural NW Georgia location. FSD is actually much worse than last year. I guess the "machine" hasn't "learned" this "end" of the road yet. 🙄 It will be interesting to see how quickly or if the machine learns this area before I leave. It certainly won't be from a lack of my autopilot disengagements and sending audio comments.

New thermostat coming out. I don't know if you know. It does have matter. Just an fyi. https://store.google.com/product/nest_learning_thermostat_4th_gen?hl=en-US

On my eisy, Alexa routines work correctly. However and as @Geddy said, many times over the last several years on my eisy and previous ISY, Alexa stopped working. Fortunately, Alexa is not really important to my system. Every time I can remember, it's been on Amazon's end. I always rebooted the UD device just because. That typically didn't work, so I waited a few weeks for it to come back up. Sometimes it did. If it didn't, I deleted the skill and reinstalled. That usually did the trick. I personally don't think Alexa is a priority for Amazon.

Updated eisy from .22 to .27 without issue. All plugins started.

True, but if you're not home, you can get notified of a power loss recovery, and reboot with the UD Mobile app.

Dim what kind of light? A new light? The old Hue light?

There's not nearly enough information to give a comprehensive answer, except nothing time-based will work without the ISY. The ISY will work without the internet, but the clock will very slowly drift. It sounds like it is unknown how you set everything up; i.e., loads vs scenes vs programs. All things considered and like Techman said, I would remove the ISY and factory-reset every Insteon device. You/they will probably end up doing this anyway if you don't have the ISY login name and password. https://www.youtube.com/watch?v=V1aPQX8rjJ4 Otherwise, I would just leave it, and let the new owner figure it out if he wants to. It will work as you left it for a while, at least. But what functionally makes sense to you may not to them.

Mine just started working again. I changed nothing.

Yes, it says, "Motion detected" in the Alexa app, but the routine does not trigger. Over the years, ISY/eisy motion triggers for Alexa have come and gone. I believe Amazon is the culprit for most, if not all, of the issues I've had. Based on your first post I quoted, do you still want me to open a ticket?

I was and am on 5.8.3. Variable motion triggers still don't work.

I have the same or similar problem. I have two variables set as motion sensors. All these two routines do is trigger an announcement. Neither works.

Same. UD Mobile for Android says "Attempting Connection" and the admin console gets stuck at "Initializing: Starting Subscription" on four different ISY-994s. The Portal accounts report online. I can still see/control the devices on UD Mobile. I cannot do anything on the admin console. This started two days ago, right after I updated my eisy.

Upgrading my eisy went fine. But I have four remote ISY-994s I can no longer access. UD Mobile says "Attempting Connection" and the admin console gets stuck at "Starting Subscription." The Portal accounts report online.

I have this after a reboot. It will eventually show connected if you leave it alone. If you want it to show connected in eisy right away, open the valve icon in the YoLink app. That being said, I'm pretty sure the valve controller 2 has a YoLink bug in it. My signal strength will fluctuate from the -40 or 50s to over -100s dBms without moving the device. Sometimes I get communication errors with the valve controllers in the app. I don't have any issues with my leak detectors. I have two valve controllers. I made an eisy program to monitor the connectivity status for a while. Both valve controllers reported "not normal" at least once a day. I also have these valves D2D paired with my leak detectors. They have never failed to close with a leak test. I have had one not close (or open) when trying to move them with the app. I think part of this is me sending two valve commands at the same time, but I'm fairly certain there's a YoLink bug here.

In stock for those interested.