This is the forum archive of Homey. For more information about Homey, visit the Official Homey website.

The Homey Community has been moved to

This forum is now read-only for archive purposes.

Slide make your existing curtains smart (kickstarter)



  • Great the creators are here, here also a backer from the start for 5 devices. Was waiting for more info about the api so i could cancel when i didn't like it but for now i will keep my order :)
  • explains a lot more about how Slide works
  • Any more news just before reaching goal about the Homey support / possible zwave support?
  • With the wifi API, Homey can surely control the slides. The HTTP request cards app is probably all you need
  • Sorry, phone emoji's don't work  :#

    Question, I really like the slide controllers and would like to order some, however I am not sure what the benefit is of ordering a 'perk' at Indiegogo as opposed to just wating?

    I guess you may eventually get them a bit earlier, but it will still take 7 months and at ~2,5 times the projected price (including shipping)?
  • Slide API available! :)

    Slide API

    The Slide App has a ton of functionality in itself, but a lot of you also wanted to integrate Slide with your existing smart home system. That’s why we added an open and documented API as a stretch goal into the campaign. Today, we’re very excited to give you a sneak peek with our first API release. This access is exclusively available to our backers on our website. Visit the Slide API Backer Connect page ( and enter your email-address (has to be the same as used on Kickstarter) to access the API. 

  • jjtbsomhorstjjtbsomhorst Member
    edited May 2017
    @MrDutchfighter  Do you have an ETA on when we , as non backers, can have access to this information? And best of all is anyone from the Athom community a backer? ;) 
  • jordenjorden Member
    @jjtbsomhorst I am a backer but I am not receiving the password...
  • bvdbosbvdbos Member
    jorden said:
    Had some contact with Thijs; as soon as the API is ready, they will give me a prototype to start working on a Homey app.  <3
    Didn't @Thijs_IIM contact you yet?
  • jordenjorden Member
    @bvdbos No, but I will try to contact them again.
  • diansdians Member
    Backed :-)
  • @MrDutchfighter  Do you have an ETA on when we , as non backers, can have access to this information? And best of all is anyone from the Athom community a backer? ;) 
    Think that there are a lot of backers here :) I'm one as well. Haven't contacted them for the API yet as I'm quite busy working on some other apps.
  • Hi guys -

    I'm definitely keeping my eye on this project. I've got two questions though;

    - Does someone know if Slide would still work without an internet connection?
    - I see that they've send out an update a few days ago via email. Does someone mind re-posting that update here or forwarding a link? Thanks!
  • anneanne Member

    Yes, slide will work without internet connectivity :+1:

    There's a short update on indiegogo:

    A more eleborate update with details on the app that's being developed was mailed to backers. It's too long to post, I can forward if interested. 
  • anne said:

    Yes, slide will work without internet connectivity :+1:

    There's a short update on indiegogo:

    A more eleborate update with details on the app that's being developed was mailed to backers. It's too long to post, I can forward if interested. 
    Thanks, Anne! That's some good news. I love what IoT can bring us but this is good news, too!

    Yeah, I was actually looking for those details when I noticed the update on IG. I'll send you a PM with my email address; would be great if you could forward their email! I'm especially interested in the app and the update on the exterior design!
  • lubbertkramerlubbertkramer Member
    edited June 2017
    @lenonline ;and others for those who want to read the update from Slide that has been sent by mail i splitted into two parts because it was to long to post.

    part one:

    Hi everyone! Thijs & Kaj here with a new update for Slide. Since our last update we’ve made progress on hardware and software and we’re excited to share that with you. Today we’re diving into the mobile app, which is starting to look and feel real good. :) We’re also releasing the first version of our API, with exclusive early access to you as our backers. Moreover, we’ll talk about hardware development, including the new exterior design for Slide. Enjoy!

    Slide App

    The Slide App is a key part of the product we’re building. With the app, we want to make sure you’re able to not just open and close curtains with the press of a button, but build powerful routines. Here’s a preview at some of the screens that we’ve built after completing the wireframes last month. Please keep in mind we’re only displaying part of the screens here, otherwise this would become a very, very long update. ;-)

    After you’ve mounted Slide and plugged the power in, Slide will create its own WiFi Access Point. It’ll automatically scan available WiFi networks and you’ll be able to select yours from within the Slide App. This is where you connect Slide to your home network.

    The screen on the left is the last part of the initial Slideconfiguration. When we developed the ‘user navigation logic’ for the Slide App we realized that if you have multiple Slides in a single room, you wouldn’t want to control them just one by one. That’s why we created ‘zones’, which allow you to group sets of Slides that you want to use in the same way. For example if you have a large living room with multiple Slide-powered curtains, defining zones will make your life a lot easier.  

    The screen on the right is about adding pre-installed Slides. There will also be many houses where different users want to have access to Slide from their own mobile devices. If someone has already gone through the installation of Slides and you just want to add these pre-installed Slide to the Slide App on your phone, that’s no problem. The app will do a quick scan of your local network and display all the Slides it finds. You can choose which ones you want to add to the app. 

    This is the current design for our ‘daily use’ screen. This screen gives you a total overview of all the Zones in your house. As you can see, the sample house here has two zones, and multiple Slides per zone (see below for an example). And don’t worry - the ‘close’ and ‘open’ buttons will be changed into toggles in the final design.  

    The ‘holiday mode’ is a useful feature if you’re out of town for a while. As you can see, you can tell Slide between which times to open and close the curtains. Using a randomization algorithm the exact time will be different each day to fool any thieves spying on your house. ;-)

    If you click on a zone in the previous screen, this is where you go. Here you’re able to control each individual Slide in the zone (as well as the whole zone). You can also set different routines, see below for more information.

    Here’s two more detail screens to wrap it up. On the left, you can see what it looks like to set a time-based routine. Other routines that you can choose from include an alarm (which is a time-based routine that also plays an alarm in case you didn’t wake up from the sunlight yet), routines based on sunset and sunrise (which are automatically loaded from the internet). The ‘only trigger when I am at home’ option uses geofencing technology to adjust what Slide does based on if someone is home or not. You can also combine multiple routines to set Slideup exactly as you like it.  

    On the right, you see the detail screen where you can change settings for an individual Slide, such as its zone and name. You can also recalibrate, remove it from the app or restore the device to factory settings.  

    That’s it on the Slide App for now! As mentioned before, we’re building this up in React Native to ensure you have a seamless experience on both iOS and Android.

  • and part 2

    Slide API

    The Slide App has a ton of functionality in itself, but a lot of you also wanted to integrate Slide with your existing smart home system. That’s why we added an open and documented API as a stretch goal into the campaign. Today, we’re very excited to give you a sneak peek with our first API release. This access is exclusively available to our backers on our website. 


    The API is HTTP/REST-based and uses a JSON-command structure. Those of you who have previously integrated other devices into platforms such as Domoticz and Home Assistant should have no trouble setting Slide up as well. We have built the API as a local API, which means your commands directly interact with your Slide devices, and are not routed through external services.  

    Please note this is still an early and incomplete version of the API, but it will give you a good idea of our direction. We’d really appreciate any input you might have on the current command structure. The best way to give feedback is directly at the API page. At the end of each section, there’s a “Suggest edit” option at the bottom right. Do let us know what you think and how we could improve the current definitions and commands. 

    P.S.: In case you have no idea what an API is or how you’d need it: no worries. It’s an extra feature for those who like to work with APIs and program their own Slide connectivity, but you don’t need to use it at all. The Slide App will include all functionality Slide has to offer. 

    New Slide Exterior Design

    In the previous update we talked about the new functional design. Now it’s time to meet the new exterior design for Slide. Without further ado:


    Over the course of the past month our product designer Jesper worked hard to design a casing around the new Slide functional design that fits the product. Our core product philosophy is for Slide to be there, but always remain outside of the sight and mind of the user. This was already reflected in the functionalities and use cases we wanted to give you with Slide, as well as the Slide App. Now, we’ve integrated that principle into our physical design as well.  

    The new Slide is sleek, minimalist and elegant, and designed to fully blend into its environment. The edges of the device have a small but subtle curve. A circle pattern at the bottom adds detail, and also hides the status LED and reset button. We’ve also crafted new connector pieces that are stronger, more robust and simply better looking – if we say so ourselves. ;-) Let us know what you think!

    Development & production status

    Last but certainly not least, an update on how far we are with the production of Slide. We know (hope? :)) everyone’s eager to get their hands on Slide, as much as we’re eager for you to receive them! Right now, we’re at the end of the development phase (turning the prototype into a durable product for larger-scale production) and moving towards production. However, there’s still a couple of hurdles to pass before we’re ready for that. In our last update, we talked about the various design weaknesses in the prototype we had to tackle, which resulted in the new functional design. The past month has been full of “one step backwards, two steps forward” moments which slowed us down.  

    Our current bottleneck is that we’re waiting for external parties to help us source some critical components. Many components we use are ‘standard’, but a few are specifically designed for Slide and quite complex. Fun fact intermezzo: since the start we’ve tried and rejected 34 different motors, each of them not meeting our noise requirements. As mentioned in our last update, we’ve decided to develop our own gearbox for the motor to tackle this issue. Prototyping this gearbox design, however, is a timely process: the gears used need to be custom milled using a high-precision CNC technique. We’re working with a partner in the UK that has an expertise in this, but each iteration of the gearbox design takes about three weeks. That’s not ideal – but it’s also very important that we do get this right and not ship out a Slide that’s either too noisy or with a gearbox that stops working after just a year. We’re running into a similar time restraint with our custom springs, whose designs also need a few iterations before we can produce them at scale.  

    We’re also designing a custom PCB (print circuit board) that fits all electronical components of Slide. As we were doing this, we realized that we need more additional input/output ports than the ESP-module we use supports. As a result, we’ve added a second microcontroller (ARM Cortex M0) to our PCB layout and are redeveloping our firmware architecture accordingly. The first prototypes of this new custom PCB will be ready by next month.  

    In the coming weeks we continue to work on iterating these so-called ‘critical components’, while at the same time moving many of the other components towards the production cycle. From next month onwards, Kaj and Jesper will be spending a large part of their time in Poland rather than the Netherlands to set up the production line. It’s a good thing Kaj is half-Polish, so he’ll feel right at home. ;) Until then, we’re not quite comfortable committing to an exact shipment date. We’ve been on the backer-side ourselves often enough to know that constant postponements lead to disappointment, so bear with us until we can give an estimate with a good degree of confidence.  

    As always, thanks for your support – hope you enjoyed the update – and let us know if you have any other questions or comments. Have a good weekend!  

    Cheers from Amsterdam,  

    Kaj & Thijs

  • jordenjorden Member
    Have had a response from Thijs en API information has been received as well. Next week they will have a documentation update for the API so I might be able to start working on a framework for the Homey app :)
  • lubbertkramerlubbertkramer Member
    edited June 2017
    jorden said:
    Have had a response from Thijs en API information has been received as well. Next week they will have a documentation update for the API so I might be able to start working on a framework for the Homey app :)
    are you not a backer then because you needed to ask for the API, just like above said in the email from them backers already have access to the API. Thought i did read somewhere you would get a prototype model?
  • jordenjorden Member
    @lubbertkramer I am a backer and had filled in the API request page but didn't receive anything. Thijs of Slide told me that they had to move servers and had troubles sending mail afterwards. They fixed it so I re-requested and received access now.

    They have working prototypes at the office now but nothing I can use yet so I will start on the framework, then fill in the software so it "should" work theoretically and then will see if we can set a date for testing. I am really looking forward to that!
  • Thanks for forwarding the message, @anne! This project still looks pretty promising - I like the fact that it doesn't seem to be a closed ecosytem (in comparison to other players in this space e.g. Somfy). But still not an indication on the shipping date...that's a bit disappointing although I do understand their perspective.
  • lubbertkramerlubbertkramer Member
    edited July 2017
    New Kickstarter update (number 9) Part 1:

    Hi everyone!  

    Hope you’re all doing well. Kaj and Thijs here with a new update on Slide. We've been making steady progress over the past weeks and we’re very excited to see things coming together. We know many of you can’t wait to get your hands on Slide, so we also want to give a fully transparent and to-the-point roadmap and production planning. Let’s get to it! 

    Mechanical Development 

    We’ve worked hard to test and optimize the so-called ‘critical components’ in Slide. As we mentioned in our previous update, sourcing some of these components has taken a lot of our time. Finding the right motor has been of the most difficult components, as we try to find a balance between power, speed and sound. Each new build, with a custom gearbox, takes about 3-4 weeks to be designed, prototyped, shipped to our lab, and tested. The good news is that after multiple iterations we’ve finally ‘locked down’ a motor that we developed together with a firm specialized in DC motor production. That means that in our Bill Of Materials (or BOM), we marked it as ‘suitable for production’. It might not seem like a big deal, but it’s a big step forward for us.

    In this photo above you see the layout of Slide’s mechanical component skeleton. It highlights the big redesign from ‘Slide 1.0’ (at the time of crowdfunding) to ‘Slide 2.0’. The entire mechanics are now aligned along a single axis. A servo in the middle (not pictured, but the servo holder is) transmits the movement on the axis (coming from the DC motor, bottom) to either the upper or lower spool. Both spools connect to a ‘spring box’ we engineered in-house. As you can see, the springs are a big and important component of the mechanics. The reason for this is that we want you to keep being able to open and close your curtains by hand. If you open your curtains, however, the Slide Wire would start ‘hanging loose’. These springs prevent that: because the springs are connected to the spools, the wire is always ‘tight’. 

    When you look at this mechanical breakdown it might look simple, but it’s taken hundreds of hours of engineering and testing to get here. All parts are custom designed and there’s been dozens of iterations in between. We’ve now locked down 90% of this design in our BOM. The 10% that’s still open relates to the connector pieces to hook Slide up to your curtains – more on that below. 

    GIF above: milling the custom springbox to fit

    Electronics Design

    Last time we talked about designing our own PCB, or Print Circuit Board. If you remember Slide 1.0, you’ll know how we used different break-out boards connected to each other with jumper wires (e.g. a separate MCU, motor driver, voltage converter, and so on). It made a lot of sense to develop our own board that has all these functions integrated: it saves space, it’s much easier to assemble and improves stability. Since our last update, we have finished designing this board, as well as proto-produced it:

    It’s a small board, but as you can see – it carries a ton of features. It also has over 65 (!) different components assembled on to it. The most important of them are highlighted, but that doesn’t mean they’re the only ones that matter. Because we have a 12V motor, 5V servo and 3.3V electronics, a buck converter on the board makes sure we can output all those voltages. That’s easy – but you also need to think about what happens if the 12V motor, for whatever reason, gets a voltage overload. In that case, you have to cut off power the motor, but you want to keep power running to the microcontroller to avoid a reboot of the software. We have designed separated circuits to achieve exactly this. There is also a small secondary PCB that holds the two magnetic hall sensors. It’s mounted next to the spools, which enables us to measure the position and movement of your curtains – also when you move them by hand.

     Above: Slide's main PCB connected to the secondary magnetic sensor PCB

     Above: Our PCB-designer Marcel going through the schematics and design

    Above: Timelapse of PCB proto assembly (a timely process :-))

  • New Kickstarter update (number 9) Part 2: 

    Software and API

    Adding a second microcontroller (or ‘MCU’) was a rather bittersweet decision, because we had hoped the ESP8266 would have sufficed by itself. The reason it didn’t had not so much to do with software, but was rather a lack of input/output ports for the functionality we needed. Because of this, we added an ARM Cortex based MCU to act as ‘second microcontroller’. It basically means we have one processor to handle higher-level firmware actions, such as WiFi communications with the outside world, and another processor for lower-level firmware actions, such as controlling the motor, servo and processing data from the magnetic sensors. 

    On the software side, this means we had to rewrite part of the code and move it to the second MCU. We had used the Arduino framework to program the ESP, which is not compatible with our secondary ARM MCU. Long story short: our firmware team is busy rewriting the hardware protocols in the C/C++ language, which will be done in the coming weeks.

    With our last update we shared the alpha version of the Slide Open API. Tomorrow, we will be updating our API portal (available at with a new release of the API documentation. We're introducing a number of new functions, including functional routine commands as well as creating and changing users (for geofencing) in the Slide memory. Check back tomorrow if you're interested!

    Above: Kaj asking our company mascot Soviet for a second opinion on the new schematics ;-) 

     Above: Kaj and Valentin testing the current sensor for the 'emergency stop' functionality

    Business Development

    We’ve been working on Slide around the clock since our Kickstarter campaign (and actually long before), but we think it’s super important to take a minute and update you on the business side of things as well. We’re extremely aware there’s so many Kickstarter campaigns that are run as a solo project, often on the side, and many of them go bust. We realize you might be scared this could happen to Slide as well. Heck – one of the campaigns I backed myself in early 2016 has been delayed by more than a year and they just announced – halfway through fulfillment – that they’re out of funds. So it’s not an unfamiliar sentiment to us. In many of those cases (including that particular one) the campaign is a stand-alone project. There’s no retail or go-to-market strategy, there’s no larger business plan.  

    For us, this Kickstarter campaign is part of the company we run – Innovation in Motion. We’ve been funded before Kickstarter, and we chose crowdfunding because it’s been a great way to see if people are even interested in Slide, and which features are most valued. You guys were the first to get on board on this journey and we’re incredibly grateful for that. As we try to show, the product itself has undergone massive improvements over the past six months (it’s why we call it Slide 2.0) and we can’t wait for all of you to be the first to receive one.

    Having said so, fulfillment of this campaign is part of a bigger business strategy for us. Over the past few months, we’ve also been working hard on business development. We’re talking with retail parties as we prepare for Slide’s market launch after shipping to our backers. Our goal is to get Slide to stores in key global markets by Q4 2017/Q1 2018, where it’ll retail for €149 MSRP. 

    Slide has gotten great interest not just from you backers, but also from potential (big) partner companies around the globe. In order to capture these scaling opportunities we're ramping up to raise a seed funding round next month. This'll enable us to scale into multiple markets and expand the patent on our mechanics, which was formally granted a few months ago, to other regions. We already have several angel investors lined up, but to complete the round we will hold a 'convertible loan crowdfunding' in August. This'll also be an opportunity for you to join us and invest in the company, and we're super excited to tell you more about it in a few weeks time.

    Production Roadmap

    We know most of you can’t wait to get your hands on Slide. In case you have missed our earlier updates, just a brief recap. After the Kickstarter campaign, we reviewed our prototype with external engineers, and made the decision – early-on – to go for a significant redesign of the mechanics to create a product that’s stronger, more reliable and of higher quality. We could have taken the prototype straight to production, but it wouldn’t have been the best possible version of Slide we wanted to create.  

    The redesign (especially the internal mechanics) has taken up most of our development time over these past six months. The parts of the Slide main unit are now as good as ready to go. We still have a few concepting steps to go on the connector pieces that connect Slide to the curtain tracks, to make sure they work on as many different systems as possible.  

    The second cause of delay has been sourcing and iteration on some of the critical components, like the motor. We’ve been working with external parties and their expertise, which unfortunately means that sometimes you have to wait multiple weeks before you’re able to test a new sample. It sucks – a lot – and there’s not much we can do to speed that up. 

    We now estimate to start shipping Slide units by October, which puts us at about four months delay past initial shipment date. Perhaps we’re just too Dutch, but we have zero intent of telling you ‘next month’ when we know it’s not true. It’s also why we didn’t commit to a new shipment date in earlier updates, because we simply didn’t know. This new date is based on our roadmap, so we have a high degree of confidence:

    Updates in the future  

    We often hear from you that our updates themselves are good, but that we need to give more frequent updates. So far we’ve been updating around once every six weeks. Our approach to updates to-date has been this: to wait until we have enough information that we believe is worth your time, combine it into a big update, and then release.  

    But we also see that as we move further away from the initial campaign, the need for information and status updates grows. We’ve decided to change our approach, and from now on update you every three weeks. This means that the next update will probably be shorter, and sometimes we might not have as much to share as we’re waiting – for example – on tooling. We hope this way you won’t lose touch with the project, because we want you to be our ambassadors in the future :) Our next updates will come out on July 23rd, August 13th, September 3rd, September 24th, and so on, rain or shine. 

     In the meantime, we keep working on Slide around the clock. There’s four of us – Kaj, Thijs, Valentin and Jesper – working (more than) full-time from our lab in Amsterdam, as well as over a dozen engineers in and around the city that help us create a professional consumer-grade product. Or as we like to call is – the best possible version of Slide. ;) We’re actually leaving for Poland at 6AM tomorrow morning, but if you have any questions or if there’s anything else you want us to clarify – shoot us a message and we’re happy to answer. 

    Cheers from Amsterdam, Thijs & Kaj  

    P.S.: Last but not least, here's some awesome photos we shot of Slide 2.0 :) 




  • and a new update:

    Hello everyone,  

    Hope all of you are doing well and enjoying your summer. Here in Amsterdam it’s been mainly cloudy and rainy, but that just makes it all that much easier to stay focused on Slide. ;-)  

    In our last update we said we wanted to increase the update frequency to once every three weeks. That means the updates – including this one – will be shorter than previously, but you’ll get them more often so you’re fully up to speed. Because there’s fewer “groundbreaking announcements” after just a few weeks, we also focus a bit more on the “behind the scenes” of Slide. 

    What we've been up to since July 2nd 

    Visiting production partners in Poland

    Jesper, Kaj and Thijs spent a week in Poland to meet with different potential production partners in the areas of EMS, tooling and plastic mold injection. EMS stands for Electronics Manufacturing Services and the EMS provider is responsible for sourcing the different electronic components and assembling the PCBs (Print Circuit Boards). The tooling partner is responsible for creating the tools (e.g. the molds) that are then used by the injection molding partner to produce the plastics. Sometimes a company does both tooling and injection molding under one roof. We focused on meeting with a dozen different companies. We had been in touch with them over the past few months, but waited with our site visit until after Slide’s redesign was complete.  

    The focus of the site visits is to meet the production partner and discuss our requirements for Slide, but also to see the factory and get an impression of how the company works. That last part is actually the most important. Crowdfund campaigns often go directly to Asia and outsource production to a company without having ever visited, only to run into trouble along the way. At the end of our week in Poland we were very happy we did not go that route. Simply put: the quality of the companies we visited varied greatly. Even more: some of the companies that we were most positive about in their online communication were actually disappointing, and vice versa. Some examples of what’s on our internal check list:

    • How is the company organized? How many people work there, and how many of them actually work in production (versus sales and marketing)?
    • Do they have experience with similar products? Can they show that? 
    • How do things look on the factory floor? Is it clean? Do they observe proper quality and safety standards, like mandatory ESD jackets for EMS and earplugs for toolers/injection molders?
    • Can they actively think along with us in our DFM (design for manufacturing) choices, or are they just a ‘production shop’? 
    • Are they likely to take this project seriously and commit? Will they go the extra mile?

    After the site visits, we kindly thanked some of these companies but decided not to pursue a partnership with them. With the others, we’re currently negotiating collaborations. (Both in Poland and in the Netherlands everyone is on holiday these weeks now so many firms are either closed or working with limited capacity).  

    .. And even more in the Netherlands

    Over the past few months we have also built similar relationships with potential production partners in the Netherlands. We visited them with the redesigned Slide and asked them to give us a quote (price) for the different parts of the production as well. We’re very keen to explore if it is feasible to begin part of the production here (for example, the tooling) and gradually move the production chain to Poland. The closer to home, the easier the communication and the faster we can work, too – but we will have to assess this from a cost perspective as well. We will also have to decide between aluminum and steel tooling.  

    We focused on meeting with partners in EMS, tooling and injection molding for now because they constitute the biggest chunk of the production with the longest lead times (amount of weeks they need to produce a component). Further on, we will also meet with prospective partners in assembly and shipping.

    Optimizing for production

    The different tooling partners we met with also provided a lot of feedback on our component designs. Contrary to 3D printing – where you can create any form – plastic injection molding is more complex, as the design needs to be “produce-able”. This involves very small details that you would not notice, but that are crucial to get it right. To illustrate, here’s some of the feedback we received:

    Close-up of spring-box. Feedback: “We recommend to increase the curve of the indent by five degrees outwards” (This is a difference of 0.3 millimeters)

     Close-up of part of skeleton: “The combination of holes and the long indent limit the possibility to use a sliding die construction. Can we relocate the holing to the outside?”

    Jesper and our mechanical engineering partner have been implementing this feedback – and other – into the CAD files for production.  

    We have made similar optimizations in our PCB (print circuit board), which houses the electronics. This included, for example, deciding on the optimal cable connection between the main board and the sensor board, the type of connector pins for the Slide Dataport, and how to optimize the design for efficient flashing of our firmware at the end of the factory line.

    Steps on software: API and ESP operating system, MQTT plans

    You may remember from our last update that we added a secondary microcontroller (ARM Cortex M0-based) to handle all hardware controls, whereas the ESP now fully focuses on handling communications. We’ve completed the firmware on the secondary MCU, which had to rewritten in C. We’re still using the Arduino framework for the ESP, but have become increasingly dissatisfied – particularly from a security perspective. Security in IoT devices is crucial and we’ve decided Arduino just does not cut it. We have decided to move our ESP firmware architecture to Mongoose OS, which is also open source but significantly more reliable than Arduino. There is also a native support for integration with Amazon AWS and Google’s cloud services – one of whom we plan to use. We’ve started the porting process last week and this will continue throughout August.  

    One of the nice bonuses of Mongoose is that it has a very good built-in MQTT broker. This means that we will be adding MQTT support to our API, which is currently HTTP RESTful only. For those of you who have been working with our API – now’s a good time to check it out anyway, as it has just been updated. There is a changelog in the website, especially the routines have been expanded greatly.

    Testing, testing, testing.

    We spent an enormous amount of time on just testing things. Every single week we run dozens and dozens of small tests on mechanics, electronics and software – and how it all works together. It is probably extremely boring for you to read, but if you want to know how we spend our time, keep in mind that at least half of it is dedicated to building test setups, doing A/B measurements, validating hypotheses and just figuring out what works best. And in practice, we don’t build a new “new release” of Slide each week, but instead conduct countless separate tests. Some sample tests to illustrate:  

    • The effect of a change in diameter of the wire guidance axis on the wear and tear of the Slide Wire  
    • The effect of different coatings on the wear and tear of the Slide Wire 
    • The added value of using metal gears instead of plastic gears in our coupling system 
    • Limiting vibrations from the motor (and therefore the sound) by using harder or softer plastic grips around the motor. 
    • Testing a new type of spring that produces the same strength with fewer rotations. 

    • And so on.. :) 


    In summary, we have had a couple of productive weeks in spite of the fact that everyone else – including our partners – are on holiday. We are on track with the planning as shared with you in previous update – and as a result, we also don’t have any further news/changes to the schedule, still planning to start shipping by the end of October.

    Our next update is coming out on August 13, so stay tuned for that. In the meantime if you’ve got any questions, shoot us a message here or directly and we’ll be happy to answer. :) Cheers from Amsterdam, Kaj and Thijs

  • jorden said:
    Good to see for when Slide will be shipped, do you already have your testing units or is this build on the API documentation? 
  • jordenjorden Member
    @lubbertkramer Only based on the documentation, no testing possibilities yet.
  • Guys, do you know if it is possible to hand operate the slide; i.e. that by pulling on the curtains, that the curtains will close or open (depending on the direction)?
  • JPeJPe Member
    Slide is the first retrofit smart curtain system that works with your existing curtains. It only takes two minutes to set up. Thanks to its wireless connectivity and integration with smart home platforms, the possibilities are endless. And don't worry: with Slide, you can still move your curtains by hand. 
    (I did read the description for you :-)

  • JPe said:
    Slide is the first retrofit smart curtain system that works with your existing curtains. It only takes two minutes to set up. Thanks to its wireless connectivity and integration with smart home platforms, the possibilities are endless. And don't worry: with Slide, you can still move your curtains by hand. 
    (I did read the description for you :-)

    Much appreciated @JPe
Sign In or Register to comment.