<?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" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Tobias Braun on Medium]]></title>
        <description><![CDATA[Stories by Tobias Braun on Medium]]></description>
        <link>https://medium.com/@tobias.braunt?source=rss-b4ccc4982382------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*uOUz5dIjD-42-gGh.jpg</url>
            <title>Stories by Tobias Braun on Medium</title>
            <link>https://medium.com/@tobias.braunt?source=rss-b4ccc4982382------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 21:55:19 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@tobias.braunt/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[How I finally managed to make my switches work again (in a smart home).]]></title>
            <link>https://medium.com/@tobias.braunt/how-i-finally-managed-to-make-my-switches-work-again-in-a-smart-home-1c0a53bca21d?source=rss-b4ccc4982382------2</link>
            <guid isPermaLink="false">https://medium.com/p/1c0a53bca21d</guid>
            <category><![CDATA[life]]></category>
            <category><![CDATA[raspberry-pi]]></category>
            <category><![CDATA[smart-home]]></category>
            <category><![CDATA[alexa]]></category>
            <category><![CDATA[internet-of-things]]></category>
            <dc:creator><![CDATA[Tobias Braun]]></dc:creator>
            <pubDate>Thu, 12 Dec 2019 09:55:07 GMT</pubDate>
            <atom:updated>2019-12-12T09:55:07.801Z</atom:updated>
            <content:encoded><![CDATA[<p>I started my smart home journey round about a years ago. As a normal couple going straight to their thirties, we decided to buy a house, get a second child and, as another bad decision, make our new home smart. It is the beginning of a long, inconvenient journey.</p><p>To start our new smart home “project”, my wife (a studied computer linguist) and I started thinking about how to start. We struggeled with some pretty normal questions:</p><ul><li>What is a smart home?</li><li>What a useful scenarios we want to cover?</li><li>Do we have trust issues with companies producing components?</li><li>What systems are we committed to?</li><li>Which communication protocols do we use?</li></ul><p>In the end, we decided to use wireless standards with a commitment to Amazon Alexa without any trust issues, starting with some pretty normal scenarios as light control, multi room audio and smart video doorbell. Couldn’t be that hard. Just as getting kids.</p><p>As the wireless smart home market has a strong focus on rented apartments, our first step was onto smart bulbs. You have a wide choice of different suppliers, a great compatibility with Alexa and no need for using hubs. So we started with some bulbs from Osram, Phillips, Yeelight and some no-name asian products. The introduction of the bulbs into our environment went without a hitch.</p><p>Unfortunately, we didn’t thought it through. Having a three years old learning how to control the world without being about to have a clear pronunciation lead to some issues. As the bulbs a controlled by a logical trigger (voice) and traditional switches disconnect the circuit, there were some serious confusions. Our smart home lead to more running around helping our son turn on and off the bulbs per voice. It was more effort to control the smart home helping our son than advantage by our new smart home (especially because Alexa is sometimes more a beta product than a final system. If you try to turn on the light in a different room, Alexa also starts other electronic devices like the vacuum robot and the TV. This isn’t helpful in a scenario with a three years old). But we stayed strong and sticked to continuous improvement process.</p><p>After some detour via smart switches (which aren’t that smart in Alexa environment — they also cut the circuit, but with voice. This isn’t helpful, if you try to control a bulb), we finally found a promising solution. After reading into the literature, I started to understand, that a switch is a device with two states (open and close circuit) controlling the state of another electronic device (or more complex circuit). If you use a smart bulb, the state isn’t determined by a physical but logical state controlled by multiple actors. As Alexa don’t have open logical states controllable by other devices than Alexa and some very limited smart devices such as Alex Buttons, we started to research. What we needed were:</p><ul><li>A state control</li><li>A physical trigger changing the state</li><li>A bridge telling Alexa to change the behavior of a smart device following a logical state.</li></ul><p>Starting with the trigger, I realised that we need a trigger, which is a complete different component than a switch. This trigger should than send a signal to a component, which is able to trigger Alexa changing the bulb (yes, we keep the control of the devices on Alexa but introduce another system controlling Alexa. That way we can keep the “convenient” way of using the Alexa ecosystem but help out in the beta features of automation in Alexa). With this concept in mind, we still had traditional switches and I didn’t found any wall trigger, which are compatible to Alexa (ok, there’re Alexa Buttons — but this isn’t a option if you have any interest in design).</p><p>As I walked down our staircase, I realised, that the light went out after a while after the trigger by its own and asked myself, how this magic is even possible? After some more research, I found out about relays, which get an input and then decide to open or close the circuit following some rules (like time). This would be the perfect smart home component, if I were able to get the input signal and trigger the output state separately. So, after a long search, I found Shelly and Sonoff.</p><p>These companies offers smart relays which can be programmed, triggered by a switch or trigger or whatever can supply power, to make a web call by an input and to be triggered by Alexa to switch the circuit. As sugar on top, these actions can be totally separated in the apps.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XlYoJQz7GN--VPJKBIYgDg.jpeg" /></figure><p>The introduction of the output control into our Alexa environment was, as usually, quite easy. Wiring the Shelly according to some tutorial on a dutch website about a hotel forum, adding the Shelly into the Shelly Cloud by the Shelly app, activating the according Alexa skill and then perform a short search — and we were able to open and close the circuit (and to disable the function by the input). As happy as I were, this wasn’t in any way helpful for our problem — there aren’t any scenarios but emergencies, in which I wand to cut the circuit, if I have a smart bulb.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XlYoJQz7GN--VPJKBIYgDg.jpeg" /></figure><p>So I started researching again hoping to find a way to trigger an Alexa routine by calling an URL. As IFTTT doesn’t support triggering routines by URL Stringify is only available in USA and UK, I almost gave up. After some nights searching the internet about possibilities, I looked back on our concept. We needed an trigger and a state control, connected to Alexa over a bridge. With our new Shelly, I was able to check the trigger. But how would I be able to have a logical state controlling Alexa?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XlYoJQz7GN--VPJKBIYgDg.jpeg" /></figure><p>I thought back about some experiment regarding multi room audio I performed earlier and got OpenHAB in mind again. So I set up my RPI again, installed OpenHAB, connected Alexa, activated the classic UI and… got a callable URL to trigger a routine on Alexa! Adding this into my Shelly App and creating some Routines for starting and stopping the bulb by voice, I am now able to send this signal via OpenHAB directly by only using a switch.</p><blockquote>I would never have thought that I would be happy to be able to operate my devices in a Smart Home via a conventional light switch again, without failing due to the discrepancy between logical and physical states.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1c0a53bca21d" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>