auger66

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.

Not really enough information, but is your Portal subscription expired? All of the intermittent UD issues I've had with Echo's were due to Amazon changing something. If not your Portal subscription, I would try relinking the skill. If that doesn't work, try deleting and redo the skill. Not updating in ten years could also be an issue. 🤨

Upgraded with no issues on eisy.

Well, since you said "Goodbye Universal Devices" a few minutes before this post and you want to control your Insteon devices, I would say the Insteon Hub is your only choice. It's certainly not "plug and play" as you will have to start over from scratch with your devices, scenes, and programs. I recommend a factory reset on every device you have and start rebuilding from there with the Hub. There are other issues you will run into, but since you seem done with UD, the Insteon Hub is the only choice that I know of. Good luck.

Same. The two portal accounts affected came back online three hours ago.

I have two different UniFi routers at different locations. UD Portal went offline for both of them. I have a third portal account on an AT&T router that is still good. Looking in the UniFi app, it shows both UD devices connected to the internet. Anyone else having this portal problem with UniFi? Thanks.

It added one node named "YoLink Valve" with a NodeDef of "yomanipu." Restart log attached. This package is a Valve Controller 2 with an Evo Valve Operator. I thought this would fit my existing valve, but it doesn't. I'm saving it for another location, though. I'm going bite the bullet and install a 3/4" and 1" version of this package. That won't happen until January. Different valve actuators, but it's the same controller. I've reconnected it after node server testing. It's just sitting on the floor. You can have access. Let me know how that works. YoLink_12-7-2023_64527_PM.zip

I'm pleased to report YoLink's Valve Controller 2 works with the node server; even though, it's not on the list of supported devices. This controller has valve control and sensing, but only one node was added. I opened and closed the valve on the admin console just fine. I also opened and closed the valve manually with the handle. That also correctly reported open and closed on the admin console. I don't know where it's getting its information from, but it works. I've only used the node server for a few days with many leak detectors, but so far, it's rock solid.

Is your Hue bridge on a DHCP reserved IP or static? Have you tried a custom key with the bridge local IP address? https://forum.universal-devices.com/topic/36609-new-router-now-hue-node-doesnt-work-all-others-do/?do=findComment&comment=343219

I had a MyLink setup with an ISY-944 in a condo I used to rent out. I used network resources to control it with Alexa and keypadlinc buttons. Still works as far as I know. I found the MyLink specifically (and Somfy in general) has terrible range, but I finally found a spot to plug in the MyLink that worked. I'm still using an Autelis and urtsi in my own place also controlled with network resources on an eISY. Autelis is long gone so if it fails, I'll need a new solution.

Pretty sure the answer is no. It may unofficially or partially function. You'll need an eISY for new products. The last update for the 994 was almost two years ago.

I updated to it yesterday with no issues. It would be nice to have release notes beforehand. The update didn't require a power cycle to function this time. Just the usual reboot. No differences noted, but my setup is pretty basic.

OK, sure thing.

Looked into it. They did. CEO of Sonos: For now, Google Assistant is absent from both speakers. Sonos says this is due to changes that Google has implemented for companies that want to run the voice service on third-party hardware. Patrick Spence claims it’s unrelated to the ongoing legal battle between the two companies and insists Assistant is now more of a “heavy engineering lift” than it was before. “Right now, we don’t see it being worth the effort. We hope Google will take another path that will allow us to continue to offer it in more of a lightweight manner the way we do today. But we also feel well covered with what we have with both Alexa and Sonos Voice Control.”

Not that it helps at all, but I found it interesting Sonos dropped support for Google Assistant on their latest speakers. I'm guessing Google pulled a vintage Apple.

Thanks. I looked for but didn't see that support thread, but my comments are still the same about 3.1.25 on eISY. All good, except having to repower to get everything running again.