auger66

😀 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?

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.

Yes, please. Gaping hole in my system, but I've been limping along with Alexa routines.

I'm not sure I understand exactly what you want, but I believe you want three thermostats to work in the out building with internet connectivity. The way I would do this is to get internet in general to the out building. Everything else will fall into place, and you'll have much more flexibility if want to do anything else in the out there. Run fiber in the conduit to the out building from your existing gateway, router, or switch. Consider making two runs for redundancy. Use a wireless bridge between buildings. Physical connections are always better than wireless. Assuming you want all of this on the same network and existing internet provider, connect an access point and switch to the out building fiber or wireless bridge. Some APs are also switches. For sensors, YoLink wireless devices have very long range, and there's a Polyglot node server for YoLink. But if you have internet and wifi in the out building, range shouldn't be an issue for anything. I've been extremely impressed with my YoLink devices. Plus, their customer service is great. Another way is to have your internet provider provide separate service to the out building and run that building on separate everything. I don't know if that's practical for your situation.

Straight out of eisy as a system variable in seconds. No conversion. Not quite six hours, but it's close. I thought you wanted to know what time solar noon is every day, including DST? This is the way. Works very similarly to the month/day program I posted earlier, and uses the same eisy system info in my example. Should be very reliable, too, since all the information originates and stays in the eisy, i.e., no nodes.

IoX can provide sunrise and sunset every day, and the next day, to a variable. In my location today, sunrise = 26727. Sunset = 70316. 70316 - 26727 = 45589 45589 / 2 = 21794.5 26727 + 21794.5 = 48521.5 48521.5 is solar noon today at my location. Doesn't that give you exactly solar noon in seconds every day? Including DST? I'm I missing something? You would need to make the state variable = to an integer variable at the end so you could do something with it in a program.

You may get some ideas from this post. I use part of this program someone posted a long time ago to calculate day and month. I think using something like this would make it relatively easy to calculate solar noon in seconds.

This is supposed to be their Matter firmware upgradable hub. Matter should bring local control. A lot of future ifs. While I would also very much like local control, the core function of my Yolink leak detectors is to close two shutoff valves. Yolink's current D2D paring will do what I need in the extremely unlikely event I have a water leak and internet outage and/or power failure at the same time.

I find it mildly interesting I have the same issue on an eisy but not on an ISY-994.

I'm not sure if you mean "not displaying" in the node or on the IoX page of the admin panel. If you're talking about the admin panel, I can tell you the Hue node will show exactly what you're talking about on power-up. You have to reboot "eisy System Settings" from the configuration tab on the UD admin console. The node values will populate on the IoX page after a reboot. Unfortunately, the Hue node has been like this for a long time. So, if you have a power failure, for instance, you have reboot IoX every time to get the Hue node to work at all.

I don't have any temperature sensors, but my leak detectors display the temperature in Farenheit on the admin console. I assume in the node custom configuration parameters Key TEMP_UNIT has Value F, correct?

Just log into your portal account and click on the ❌ next to the UUID of the device you want to remove.

I saw an old post about this, but it's closed. Just wanted to say after a power outage, the Hue node says it's running on the Polyglot dashboard, but no lights are running on the admin console. The lights themselves do not respond to eisy. A node restart does nothing. An eisy reboot from the admin console gets the lights going again, and that's reflected on the admin console. The Hue node not working after a repower but getting it back with a reboot is very consistent.