<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Need some help understanding code flow.  IE: ESPHome, YAML, and code pulled from github.]]></title><description><![CDATA[<p dir="auto">Hi!</p>
<p dir="auto">**My ask up front: **Can someone walk me through the process of how a github project written in python winds up interacting with YAML on an ESP32?  Looking for some orientation so I can "RTFM" better.</p>
<p dir="auto"><strong>Background:</strong><br />
I have Espectre up and running in my house, which is cool.  What I <em>also</em> have in my house is LED crown molding controlled by WLED.</p>
<p dir="auto">I think the ESP-32s I'm using for the lighting have enough juice to run both items of code (and probably a few other sensors).  However, I don't know how to combine them.</p>
<p dir="auto">What I'm specifically confused about is when I provision a device with ESPHome, I'm not actually clear on what it does.  As in: I gather it's making a framework specific to the board to handle running the code in the YAML, but I'm not sure what that looks like specifically.  Which means I don't know how to take the code from WLED or ESPectre and also include it (is it as simple as an include?) so that I can make YAMLs that utilize the functionality those to projects provide.</p>
<p dir="auto">I am especially confused what is happening when YAML code calls specific github projects.  Is it literally pulling code from the repository?</p>
<p dir="auto">For context I have decent capability and experience, but mostly <em>within</em> code, bridging multiple architectures like this is new.  I have stumbled on for years doing some fairly advanced projects, but I mostly am a very determined monkey banging on a type writer.</p>
]]></description><link>https://fedi.wiki/topic/e92a4424-f829-4030-98f0-61b7888bbeac/need-some-help-understanding-code-flow.-ie-esphome-yaml-and-code-pulled-from-github.</link><generator>RSS for Node</generator><lastBuildDate>Fri, 23 Oct 2026 03:20:30 GMT</lastBuildDate><atom:link href="https://fedi.wiki/topic/e92a4424-f829-4030-98f0-61b7888bbeac.rss" rel="self" type="application/rss+xml"/><pubDate>Mon, 28 Sep 2026 13:19:58 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Need some help understanding code flow.  IE: ESPHome, YAML, and code pulled from github. on Mon, 28 Sep 2026 13:52:53 GMT]]></title><description><![CDATA[<p><span><a href="https://lemmy.world/u/batmaniam">@<span>batmaniam</span></a></span> <a href="https://infosec.exchange/tags/esphome" rel="tag">#<span>esphome</span></a> uses python to read a yaml file and generate C++, and then compiles the result. In general, you can’t just trivially combine two esp32 projects into a single firmware. However, esphome has a component that accepts the <a href="https://infosec.exchange/tags/wled" rel="tag">#<span>wled</span></a> udp broadcast protocol from software running elsewhere on your network. This may or may not end up being a simplification - there are a small number of existing “senders”, mostly designed for coordinating large lighting installations such as Christmas light displays across multiple ESP32s.</p><p>Additionally, esphome has a number of built-in lighting effects (fewer than wled, and less flexible), which may be enough for your purposes. If so, you should be able to consolidate two esp32s into one.</p><p>Then again, the positioning of the esp32 probably plays a role in its ability to detect motion using the espectre component, so there may still be tradeoffs involved. Ie the led controller may be positioned near the ceiling where it is less able to detect movement.</p>]]></description><link>https://fedi.wiki/post/https://infosec.exchange/users/RoganDawes/statuses/117348995785305504</link><guid isPermaLink="true">https://fedi.wiki/post/https://infosec.exchange/users/RoganDawes/statuses/117348995785305504</guid><dc:creator><![CDATA[rogandawes@infosec.exchange]]></dc:creator><pubDate>Mon, 28 Sep 2026 13:52:53 GMT</pubDate></item></channel></rss>