Everything posted by benjaminrobinson
-
Ring drone and rover cams with my SolarEdge setup —
I run a SolarEdge system at my place in Phoenix and have the monitoring side tied into my Universal Devices setup so I can see production and consumption in one place. I'm now looking at adding a couple of Ring cameras, possibly the drone and rover models, mainly for the backyard and the equipment area. What I'm trying to work out is whether it's worth trying to bring those cameras into the same automation flow, or whether I should just keep them in the Ring app and leave the SolarEdge side alone. The subscription side is a concern since I already pay for monitoring and don't want to stack too many recurring fees. I also don't know how reliable the motion triggers would be for something like this, or whether the integration would be more trouble than it's worth. Has anyone here connected Ring cameras to their Universal Devices setup alongside SolarEdge gear? Curious how you handled alerts and whether the fees felt justified. I found this on the Ring drone and rover models: Ring Drone Cam and Rover Cam: price, release date, fees https://viewtime.net/news/ring-drone-cam-rover-cam-robotics-launch. It helps on the fee question, but I'm still unsure whether either model exposes enough to trigger my Universal Devices scenes, so I may keep them in the Ring app for now.
-
Some programs stop working after update
Before deleting anything, check Configuration > System > Time/Location (latitude/longitude and time zone) survived the upgrade. Sunset/sunrise triggers depend entirely on that location data; if it got reset or blanked, the schedule never fires and the programs sit idle—which matches your symptoms and also explains why hard-coded times failed. Also confirm the two programs aren't disabled in the Summary tab, and right-click > Run (If) to see whether they evaluate true. If the location is intact and the programs run manually but not on schedule, the clock/time zone is the next thing to verify.
-
Can UDM show the current time on my EISY?
IndyUDIuser's experience matches what I've read about eisy-ui at this point: mostly complete, with a few admin holdouts left. The time header question is fair to raise directly, since whether it lands among the remaining ports is something only the developer can confirm. Until then, the variable-write program keeps the display approximate rather than exact, which seems acceptable for a header glance. Checking DST-affected program behavior in the program summary still strikes me as the more important step, regardless of which interface shows the clock.
-
Can UDM show the current time on my EISY?
Using a program that writes the system date and time into variables and then reading those in UDM is a sensible workaround, though it only confirms the hour and minute whenever the program last ran, not the exact clock. Given that eisy-ui exposes the setting and UDM doesn't yet, staying on Admin Console for things like this seems reasonable until the new interface matures. On the DST question, IoX scheduling concerns like programs that fire during the repeated hour are worth checking directly in the program summary, since behavior there matters more than the displayed time.
-
HomeKit devices and documentation?
Greg, the distinction you make matters: you're asking about exposing IoX/eISY nodes into the Apple Home app, not bridging native HomeKit accessories back into eISY. That's the piece I'd expect the Wiki to cover in its own section, since the existing Zigbee, Insteon, Z-Wave, and Matter pages set that precedent. I've been reading through the forum for general background on this, and the lack of a dedicated HomeKit page is exactly the kind of gap that makes new users conclude support was quietly dropped. A short setup page plus a note on current status would settle the ambiguity without relying on forum hearsay.
-
eisy ai
The discrepancy you're seeing likely comes down to version drift: the plugin's built-in Help may reflect the current JSON-based config, while older forum posts describe the simpler model-plus-key setup from an earlier build. Since the Readme linked by mmb is maintained in the repo, I'd treat that as the source of truth and check it against your installed PG3x version. If the two still don't line up after that, that's a useful signal for Michel about whether the Help text needs updating or the plugin is mid-development.