<?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[Review]]></title><description><![CDATA[M5Stack review]]></description><link>https://community.m5stack.com/category/43</link><generator>RSS for Node</generator><lastBuildDate>Sat, 06 Jun 2026 17:40:26 GMT</lastBuildDate><atom:link href="https://community.m5stack.com/category/43.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 12 Jan 2023 14:59:33 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[4Relay Module UIFlow]]></title><description><![CDATA[@domi
Are you using the "4Relay module" or the "4Relay unit" or the "2Relay module" ?
If you still get an error, try to make a simple Uiflow programm scanning the i2c bus with the 4Relay connected:
[image: 1675006854907-cfe4a152-de11-4d5b-8158-f44191defe28-image.png]
You should get the number [38, 117] displayed as Label0, 38 is the decimal for 0x26.
If you get 37 you have another firmware than I have (I2C address 0x25).
If you only get [117] your 4Relay module is not connected to the M5Stack core. 117 (0x75) is the I2C address of the battery management chip.
]]></description><link>https://community.m5stack.com/topic/4974/4relay-module-uiflow</link><guid isPermaLink="true">https://community.m5stack.com/topic/4974/4relay-module-uiflow</guid><dc:creator><![CDATA[crami25]]></dc:creator><pubDate>Thu, 12 Jan 2023 14:59:33 GMT</pubDate></item></channel></rss>