<?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[Topics tagged with unit-4relay]]></title><description><![CDATA[A list of topics that have been tagged with unit-4relay]]></description><link>https://community.m5stack.com/tags/unit-4relay</link><generator>RSS for Node</generator><lastBuildDate>Tue, 28 Apr 2026 21:04:05 GMT</lastBuildDate><atom:link href="https://community.m5stack.com/tags/unit-4relay.rss" rel="self" type="application/rss+xml"/><pubDate>Mon, 09 Mar 2026 17:40:26 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Issue with unit 4 relay on cores3]]></title><description><![CDATA[On the cores3 (module connected through port A), I see no devices found on i2c scan when using esphome. It finds OK on the atom-lite.
If using the "Cores3 test" binary from m5stack, I can see the address found on the i2c scan app.
]]></description><link>https://community.m5stack.com/topic/8126/issue-with-unit-4-relay-on-cores3</link><guid isPermaLink="true">https://community.m5stack.com/topic/8126/issue-with-unit-4-relay-on-cores3</guid><dc:creator><![CDATA[ngolf]]></dc:creator><pubDate>Mon, 09 Mar 2026 17:40:26 GMT</pubDate></item></channel></rss>