<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Shelly on karl</title><link>https://karlquinsland.com/tags/shelly/</link><description>Recent content in Shelly on karl</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 01 Jan 2022 00:00:00 +0000</lastBuildDate><atom:link href="https://karlquinsland.com/tags/shelly/index.xml" rel="self" type="application/rss+xml"/><item><title>Shelly Pro 4PM teardown</title><link>https://karlquinsland.com/shelly-pro-4pm-teardown/</link><pubDate>Sat, 01 Jan 2022 00:00:00 +0000</pubDate><guid>https://karlquinsland.com/shelly-pro-4pm-teardown/</guid><description>&lt;p&gt;Yet another teardown post!&lt;/p&gt;
&lt;p&gt;Curiosity got the better of me while putting together a BOM for a project and I decided to add one of the new Shelly devices to my order to bump the total over the threshold for a nice discount.&lt;/p&gt;
&lt;p&gt;I have not seen a ton of discussion about what&amp;rsquo;s inside of a any of the new Shelly Pro devices.
These &amp;rsquo;next generation&amp;rsquo; devices appear to all use a &lt;a href="https://shelly-api-docs.shelly.cloud/gen2/" target="_blank" rel="noopener noreffer "&gt;common and more &lt;em&gt;uniform&lt;/em&gt; API&lt;/a&gt; which, apparently, is too demanding of the ESP8266 based hardware so it won&amp;rsquo;t be backported.&lt;/p&gt;</description></item></channel></rss>