top of page

Search Results

136 items found for ""

  • ULTRALOQ Z-Wave Smart Lock with Fingerprint ID – Works with SmartThings!

    In today’s episode I am reviewing the Ultraloq U-Bolt Pro Smart Lock. I’ll be discussing some of the lock’s features and I will take you though the setup in SmartThings. Ultraloq states that no wiring or drilling is required for the installation, which is an accurate statement. Ultraloq also states that installation is simple, and I would agree that the instructions are clear and process is straightforward. My greatest concern when first viewing the lock online was the lock’s durability. I was pleased to find that this lock has ANSI Grade 1 certification. An ANSI Grade 1 certification is the highest commercial level of security and durability for lock sets in America. This smart lock uses a standard Schlage C keyway deadbolt cylinder. It has undergone 250,000 high-strength tests and it was determined to be up to 35 times stronger than standard residential locks. It is rated for a 7 times longer lifespan than standard residential locks. The external components of the Smart Lock are built to withstand heat and cold. The lock merits an IP65 rating being dust and weatherproof. The lock operates with the Z-wave Plus protocol which shields the Z-Wave signal using AES 128-bit encryption, so it is very durable and secure. This smart deadbolt can be opened one of six different ways. By Fingerprint, by code via the number keypad, by the detection of your smart phone presence, by shaking your phone in front of the lock when you enable the Magic Shake feature, and if all else fails, you can use one of the provided mechanical keys to gain access to your home. The keypad is glove friendly and it lets you to add random digits before and after your access code to protect your pass code from prying eyes. The keypad also has a bright backlight to allow you to view it in the dark. You can control the lock with voice commands using Alexa or Google voice assistants. The four provided double A Alkaline batteries provide 3 to 6 months of battery life through regular use. You will receive a low battery notification via smart phone app. You can also use an external battery to activate your Smart Lock should the lock’s batteries expire. You can control your Ultraloq Smart Lock remotely to lock, unlock, share access. The app keeps a log of who’s entered and exactly when they each person has accessed your home. You can share a unique, onetime code remotely to your family, guests or service people. An access code can be set for either temporary or permanent access. You can also designate specific dates or periods of time. When using the provided door contact sensor, your door immediately locks when the door closes. If the optional auto unlock feature is enabled, your door will automatically unlock when you arrive at your door with your smart phone. In addition to being compatible with Samsung SmartThings, the lock is also compatible the Hubitat and Vera Z-wave Hubs. The lock is also compatible with Apple Watch. Let’s review the steps for installing the Ultraloq in the SmartThings App. Prior to installing the lock in SmartThings, first follow UltraLoq instructions to download the U-tec App from the iPhone App Store or the Google Play Store. Once you have installed the U-tec App and setup your account then you will be set to begin the installation steps in the ST App. Open your ST App, begin by tapping the "+" sign in the upper-right corner. Next tap on the word ‘Device’. Next tap on the option to search ‘By device type’ and scroll down the list of devices until you find ‘Generic Z-Wave Devices’. Tap on Generic Z-Wave Device. Tap on the word ‘Z-Wave’ and then ‘Generic Z-Wave Device’. At this point you need to open U-Tec app, and then tap on the setting gear. Now scroll down to the ‘Z-Wave Control’ setting. Tap on ‘Z-Wave Control’ and then Tap “Add to Z-Wave hub”. Tap ‘Start the Inclusion’ and the app will confirm that it is ‘Connecting to Z-Wave Hub’. Keep the U-tec App running then return to the SmartThings App. Once back in the ST App, tap the ‘Start’ button, select your Hub and Room assignments and then tap ‘Next”. During this step, be sure that you remain in the ST app until the App asks you to scan the QR code or input the PIN code. Go ahead and Scan the QR code or enter the PIN code. You can find the QR code and PIN code on the battery cover. After scanning or entering the code, tap ‘Add Device’. The App should then confirm the setup as successful. You then find and view the new device within your device list. At this point you can go back to you U-Tec app and you will find the status of Z-Wave Control reports that your lock is paired. You can now lock or unlock your Ultraloq in either the SmartThings or the U-tec app. The status of your lock will be mirrored between the two apps. As mentioned previously, one of the reported capabilities of this lock is the ability to control the lock by voice via an echo voice assistant. This sounds fantastic on the surface until you consider that it may be possible for someone outside your home to ask your voice assistant to unlock your door. Amazon has considered this possibility. If you ask your echo device to unlock your door the echo will instruct you to change to either change your lock manually or go the app and change your device’s permission settings. The device’s settings give you the ability to grant the App permission to ‘Unlock by Voice’. If you enable the “Unlock by Voice” feature, you are warned that anyone speaking to an Alexa enable device associated with your account will be able to unlock the smart lock by voice, if they have your voice confirmation code. This is obviously Amazon’s way to minimize their liability for an unintended breach of your home. So having to remember confirmation code each time you need to unlock your smart lock makes this feature a little less exciting. However, although the Amazon App requires an access code to unlock your door, the code is not required when using your voice to lock your door. So is this lock a must have smart home device? I don’t believe I have ever shared this publicly, but I have uncovered a tried a true way of discerning whether a smart device should receive a thumbs up or a thumbs down. My litmus test is whether or not my wife gets excited about a device. And I here to tell you that she has fallen in love with this smart lock. As I stated earlier, we have used it a couple of months and we both find it convenient and reliable. And you know what they say, happy wife, happy life. Hey thanks for your time an attention today. Until my next episode, keep automating and God Bless! Product, Instruction and Discount Links! Ultraloq U-bolt Pro Z-wave Plus with Fingerprint ID Use code "budssmart7" to get a 7% discount from the Ultraloq Amazon Store Ultraloq Installation Instructions Ultraloq Z-wave setup in SmartThings App PC Mag Review – Jan 2022

  • SmartThings Edge News & Resource Links!

    Before I get into the content of today’s update let me mention that I will provide you with a comprehensive list of Edge Driver information and channel links at the end of today’s article. This information will be invaluable if you have installed a lot of Custom Device Type Handlers and you need to find Edge Drivers to replicate the capabilities found in those Custom DTHs. So be sure to stay through the end of the video if this situation is applicable to you. Well SmartThings has released yet another update about the transition from the legacy Groovy IDE platform to the SmartThings Edge environment. Most notably they have moved the date for the shutdown of the Groovy IDE from October 15th to December 31, 2022. Quoting SmartThings, “Beginning September 30, 2022, we will start migrating devices and Smart Apps from legacy Groovy technology to our new technology we call SmartThings Edge. They went on to say that they have been working diligently with their partners and user community to migrate devices and they expect that a majority of supported devices to be fully migrated by December 31, 2022. I translate “Supported Devices” to mean Standard Device Type Handlers, not to be confused with Custom Device Type Handlers which I will discuss next. They then gave a reminder which was directed to users that have installed Custom Device Type Handlers. These are device handlers which you can find listed under the “My Device Handlers” tab in your Groovy IDE. Users with Custom Device Handlers are urged to take action on these devices before December 2022 to prepare them for migration and avoid any loss of features. Now if you have little or no Custom DTHs then you should not be overly concerned because most of the Standard DTHs will be seamlessly migrated. But for those of you who need to migrate several Custom device type handlers, the article provides six options for converting these devices to edge. Here is a link that Q&A article if you would like to review the provided options. I will also provide a resource link to a list of Custom Lua Edge Drivers which you can use to source available Custom Edge Drivers. SmartThings reported that there is no published schedule for when particular devices will be migrated, nor will you receive a notification that the migration has occurred. You can identify whether a device is using an Edge driver in your SmartThings app by opening your SmartThings app and selecting a device. Next, choose the More Options link in the upper right corner of your app. If your device is Edge-enabled, the dropdown menu will list the word “Driver” as an option. When you click on the Driver link you can review the driver information. The article also states that the SmartThings Groovy IDE will begin losing some of its functionality beginning on October 15, 2022. After this date, the IDE will no longer allow for the creation or debugging of Groovy DTHs and Smart Apps. SmartThings has stated that once they are confident that most users have had time to move away from legacy Groovy DTHs and Smart Apps, they plan to deprecate most features in the SmartThings Groovy IDE. After deprecation on December 31, 2022, SmartThings may allow very limited functionality in the Groovy IDE, if necessary, but will fully shut off the tool sometime in early 2023. If you need to access your SmartThings devices via a web browser after the termination of the Groovy IDE, SmartThings recommends using the SmartThings Web at A link is provided in the description below this video. To find news and information about custom Edge drivers and integrations, ST recommends that you access the SmartThings Community and Developer Portal. I’ll provide these links in the description for these resources as well. Based on the request of my Subscribers and for my own needs, I have accrued a significant list of Edge Driver Channels and Information Sources which I will make available to you in the description below. You will find these links under the heading “Edge Driver Resources”. The first item in this list is a help guide that explains How to enroll in a shared driver channel and also provides instruction for installing the shared drivers. The next item is titled “Quick Browse Links for Edge Drivers”. This is a comprehensive list of Edge Drivers put together by community contributors to help users migrate devices with custom device handlers. In addition to these resources I provide multiple driver information links as well as Edge Driver Channel links. Included in this list are drivers for Aeotec, Dome, Inovelli, SmartThings, TAustin’s Virtual Edge Driver Creator, Xiaomi, Aqara,Tuya and Zooz Edge Drivers. And finally, at the very bottom of the Edge Driver Resource list, I have included a link to a ST Community article titled: “How to Post Requests for Edge Drivers”. This will be useful if you have a device that is not found within the resources I provided in today’s episode. I encouraged to go to the SmartThings Community, (link below) and ask for the community for guidance. I have found community members to be very responsive and helpful. I am certain that you appreciate the value in these information and resource links. That being true, give this video a quick like. Also be sure to subscribe and set notifications to ensure you receive an email about future updates. Until my next episode, keep automating and God Bless. SmartThings Article: List of Custom Lua Edge Drivers: SmartThings Community: Developer Portal: Edge Driver Channel (Beta Program): Edge Driver Resources: How to Enroll a Shared Channel and Install Drivers: Quick Browse Links for Edge Drivers: Aeotec Edge Drivers Help Desk: Aeotec Edge Driver Channel 1: Aeotec Edge Driver Channel 2: Dome Siren Information: Dome Edge Drive Channel: Inovelli Driver Information: Inovelli Edge Driver Channel: SmartThings Driver Channel: TAustin’s Virtual Edge Driver Creator: TAustin’s Driver Channel: Xiaomi, Aqara,Tuya Zigbee Drivers: Zooz Edge Driver Information: Zooz Edge Drive Channel: How to Post Requests for Edge Drivers: If this information helped you, consider buying me a coffee. PayPal-Me Link Below!

  • The Third Reality Smart Zigbee 3 Function Smart Button ( Edge Driver UPDATE)

    The Third Reality Smart Button allows control individual Smart Home Devices or groups of devices via routines or scenes. It is equipped with a single button that has three control settings - Pressed, Double Pressed and Hold. It uses the standard 3.0 Zigbee protocol which means that you must have a Zigbee capable hub. Compatible hubs include the SmartThings version 2 and 3 hubs, the Aeotec-SmartThings hub, Habitat, Home Assistant or the Third Reality Smart Hub. Third Reality states that its Smart Button is not compatible with Amazon Echo Devices which have a built-in Zigbee hub. The Third Reality smart button is powered by 2 AAA Batteries. Because Zigbee devices have low power consumption, the device is capable of operating for up to 3-Years of normal use. This Smart Button requires a Custom Edge Driver. The driver setup guide can be accessed on this website in the following article: How to Install the Edge Driver for the Third Reality Zigbee Smart Button (Updated 07-12-2023) The button’s wireless and compact design permits you to easily mount it anywhere. It comes with adhesive tape and magnetic strips so that you can easily stick it on an appliance or a wall surface. The button is native to SmartThings so it is simple to install. To pair the device just select ‘Add a Device’ and then select ‘Scan for nearby devices’. Pull the plastic battery isolator tab from the battery compartment and the blue light will begin flashing on the front of the device. When the SmartThings device discovers your switch it will display as “Third Reality Smart Button”. When opening your device settings you will see the button status reporting “Standby”. Below the button status you will see the three Smart Button modes. You can assign specific actions which occur based on the three different control setting, Pressed, Double Pressed or when the button is Held. Finally there is a panel that displays the battery level. The Third Reality Smart Button is a great device to add to your SmartThings home. There are countless applications for this sort of device. It can be used to turn on or off a group of lights. It can trigger a scene when you return home or when you sit down to watch a movie. It can also be used as a panic button to trigger an alarm and send a text notification to a loved one. This device is only limited by your imagination. Check out this a many other SmartThings compatible devices in my Amazon Store. Until the next Bud’s Smart Home episode, keep automating and God Bless! THIRDREALITY Zigbee Smart Button SEE the Edge Driver Setup Guide for the Third Reality Smart Button!! If this information helped you, consider buying me a coffee. PayPal-Me Link Below!

  • SmartThings has Announced the End of Groovy Interface

    I received a email from a SmartThings Staff Member announcing the end of the SmartThings Goovy IDE interface. The Groovy IDE will be terminated effective September 30, 2022. Quoting from the email, “On September 30, 2022, Groovy device DTHs, SmartApps built on Groovy, and the legacy developer IDE will be removed from the SmartThings platform and will no longer be supported. This means that devices and automations previously using Groovy will now exclusively operate with our latest hub and cloud technology.” Continuing to quote, “Recognizing trends within the smart home industry, SmartThings has been working diligently to evolve our platform into a modern REST API framework. Lua-based Edge drivers are a major step, which is being followed quickly with the launch of the Matter protocol, providing a greater focus on interoperability and local communication. All of this platform growth has increased reliability, decreased latency, and reduced the need for data transfer outside of the home environment.” SmartThings states that the transition for most hub connected devices will be seamless, as will their abilities, which will be supported through standard Edge drivers. As I announced in previous updates, the transition is well underway and SmartThings expects to fully complete the transition over the next one and on half months. If you have devices that are currently supported by a Custom Device Handler you are reminded that these custom groovy capabilities will not be supported and you are therefore urged to contact the community member who created the Custom DTH. SmartThings have affirmed that some devices may not transition automatically and will need to be re-onboarded. They did not specify the specific devices that may be impacted nor did they give reference to the quantity or percentage of devices that would need to be deleted and reinstalled. Also and devices which are no longer supported by their manufacturers on the legacy platform will not transition or be supported on the new platform. SmartThings did provide a link to the current list of available Edge drivers. Just reference the link “Current Edge Drivers List” SmartThings also affirmed that Developers can now share drivers with specific users or groups by creating a driver channel and providing a URL to channel invitees, eliminating the need to copy and paste code. Also in this email, the SmartThings team has confirmed that it is their intent to launch Matter this fall. For those of you unfamiliar with the Matter, Matter is a smart home interoperability protocol. It was launched as a joint effort by a handful of the industry's biggest players. Over 170 companies are involved, with Apple, Samsung, Amazon, Google and the Zigbee Alliance being the most prominent names. The goal of Matter is to ensure that smart home devices can work across different ecosystems. So, as an example, with the introduction of Matter, an Amazon Echo Show display should work with a Google Nest doorbell just as it currently works with Amazon’s own Ring doorbells. I did a quick survey of my devices and I found that out of the 66 devices which are current in use in my smart home, 31 devices or about 50 percent of them have already been migrated to Edge Drivers. An easy way to check which of your devices have been converted to an Edge Driver is to login to your ST Account, (the groovy IDE) and look within the My Devices tab to see which devices have the “placeholder” designation. These devices are already using the new Edge architecture So what is the demeanor on the SmartThings Community forum regarding this change? I would characterize it as fairly somber with a lot of concern and pessimism due to how quickly ST is terminating the Groovy IDE. Briefly, here are a couple of notable items in the negative or minus column: There is concern that nearly all of the Smart Apps such as Speaker Companion and Enhanced Auto Lock Door are going to be eliminated on September 30th. As a result any the automations that you created with a Smart App will need to manually recreated in a Routines. Two Smart Apps that are not to be eliminated are the Smart Lighting and the Smart Weather Smart Apps. These Apps will be migrated to the new Edge Architecture and be integrated into ST Routines. At this point it looks like the Developers will not develop an integration for WebCore or Action Tiles, so you should not look for any support in the new Edge environment. There is some items in the positive or plus column It is confirmed that SharpTools will continue to work after the migration, and their Rules Engine looks to be the best/easiest option for complex automations. They now have an option to connect through the new API and have said they’re working on a migration plan of their own to move existing customers from the old to the new API. It was also confirmed that there will be a custom Edge Driver for the Harmony Bridge which you are able to use to integrate RF devices such as and Air Condition, Fan, TV, etc. It was also confirmed that the Philips Hue integration will continue to work. And finally, there was confirmation that there will be Edge Driver support for the use of virtual switches in the Edge Environment. The conventional wisdom on the ST Community suggests that we should be patient and not jump in to manually delete and reinstall devices. Rather we should wait and let ST migrate devices and see which device are left behind. Those currently using webcore will need to begin to rewrite their automations using ST routines. If using routines are not adequate, you can check out the SharpTools Rules Engine to see if it gives you the additional features that you need. If you need some help in setting up SharpTools there is a video I created on that topic. See the link above. To the question of will SmartThings continue to dedicate resources to improve Edge Drivers beyond the termination of the Groovy IDE, SmartThings have stated, and I quote: “As we continue to bring you more features and new tools and to move SmartThings forward in the IoT space, we will always do what we can to ensure any transition from legacy systems during this time will be as seamless as possible and keep you informed on changes as they come.” You can stay informed by checking platform updates in the SmartThings Community and also here on this channel. Thanks for watching and I’ll see you on the next episode. Keep automating and God Bless Useful Links: Virtual Things Edge Driver TAustin’s VEdge Creator Current Edge Drivers List

  • Tubular Blind Motor Replacement – Zemismart

    NOTE: This article has been updated with Edge Driver support information. On November 6, 2021 I published my first Smart blind video on my YouTube Channel. That video featured the Zemismart roller blind. Since then I have featured two other videos involving Zigbee blinds. I did a review on a SmartWings Zigbee roller blind in January of this year and more recently, I did a review on the ThirdReality Zigbee Smart Blind in June. Since this article is about blind motor battery life, I’m going to comment about my experience with battery life in the three blinds which I have installed. The ThirdReality blind was only recently installed. Like most blinds, it states that the batteries may last up to six months. What is unique about this blind is that it is powered by four AA batteries whereas the other two blinds that I have installed use a tubular motor that is powered by a lithium ion battery. The tubular motor batteries are sealed inside the tube containing the motor. Therefore, if the battery fails inside either of the tubular motors, I’m buying a new tubular motor at the tune of 60 to 80 dollars. If the batteries fail on the ThirdReality blind, I simply replace the four AA batteries for around five dollars. Let me comment on battery performance between the three blinds. The ThirdReality blind in newly installed and has only been in operation for on month. Unfortunately, when the ThirdReality blind is installed in the SmartThings App, there is no battery status so I have no read on battery health. As mentioned previously the SmartWings and Zemismart blinds have lithium ion batteries. Both blinds are automated to open in the morning and close just prior to sunset, so two cycles daily. When making the Zemismart video, I noted that my SmartWings blind had been in operation for five months and the battery level was at 27%. My Zemismart blind stopped working after three months. I’m unsure if I contributed to the battery’s demise or if I was just a defective battery. At one point I had place the blind on solar power and subsequently found that the battery had fully discharge. After I recharged the battery, the charge would only last about one week. Eventually the battery would not accept a charge so motor stopped working all together. So I contacted Zemismart and they graciously agreed to send me a replacement tubular motor. They told me that this was an improved version of the motor. You may watch the following video to see how I installed the Zemismart replacement motor: A Note About Edge Driver Support At the beginning of this video I said I would comment about a response I received from Zemismart regarding their plan for converting their current Custom Device Handler to an Edge Driver. The Zemismart blind uses the Zemismart Zigbee Blind device handler which is a Custom Device Handler. According to SmartThings, is the responsibility of the device manufacture to convert Custom Device Handlers to the New SmartThings Edge Drivers if the device manufacturer wants to maintain product compatibility with SmartThings after the switch to Edge Drivers. An email I received from Zemismart on June 3rd stated that they currently do not plan to convert the custom device handler to a compatible edge driver. If they stick to this position, the blind will no longer connect with the SmartThings hub once the switch is turned off on the Groovy IDE. The SmartWings blind and the ThirdReality blind both use a natively supported Device Type Handler. These Device Type Handlers are in the process of being converted Edge Drivers by the ST developers. So there is Edge Driver support for ThirdReality and SmartWings blinds. Support for the Zemismart Blinds in SmartThings is uncertain at this juncture. If you have questions or comments please let me hear from you in the comments below. Assuming I’ve earned it, tap on that like button. Doing so recommends this article for other viewers. I appreciate your time. Thank you. UPDATE: EDGE DRIVER INFORMATION: Edge Driver for Zemismart Roller Blind Edge drivers for non-native devices can be sourced and downloaded from developer or manufacturer driver channels. Downloaded drivers can be immediately applied by removing device from the SmartThings App and then reinstalling the device. Alternatively, you have the option to wait to see if your device is assigned a stock driver. If a stock driver is assigned, but the device is not functioning as expected, then you may download the correct driver to update the device without the need to uninstall and reinstall your device. Since the Zemismart Roller Blind is not natively supported in SmartThings, it will likely be migrated to the ‘Zigbee Window Treatment’ driver which is a SmartThings Beta stock driver. I have tested and found that this stock driver will not provide all of the features and functionality that is currently available within the former Groovy stock device type handler. The edge driver which provides proper control of the Zemismart Roller Blind is the, ‘Tuya Window Shade’ driver. This edge driver can be downloaded from the ‘Iquix’ driver channel. Channel Invitation link: Zemismart Roller Shade - iquix Channel- (Tuya Window Shade Driver Before taking any action, my recommendation is that you check your SmartThings App to see if your Zemismart Roller Blind has been assigned a stock edge driver. To confirm if an edge driver is installed, click on your device tile and then while in the device screen, click on the ellipsis to determine if dropdown list contains the word "Driver". The presence of the word ‘Driver’ confirms that edge driver is installed for your device. If the ‘Driver’ is in the dropdown list, click on the word ‘Driver’ to view the ‘Name’ of the installed driver. If the assigned driver is other than the ‘Tuya Window Shade’ edge driver, you should skip steps 1 – 5 in the driver installation steps outlined below, but follow and execute steps 6 – 10 to download the appropriate driver. After the completion of step number ten, click on the ellipsis, tap on ‘Driver’ in the dropdown list, and then tap the option to ‘Select different driver’. You will then choose ‘Tuya Window Shade’ edge driver to replace the former driver. If dropdown list does not contain the word "Driver", you will need to execute the all of the following steps: As mentioned previously, you must delete and reinstall your smart blind to be able to assign it the edge driver. However, before deleting your blind from SmartThings you will want to take a few extra steps to preserve any routines that you have written to automate your blind. If you have no routines or you are doing a new installation, skip to step #5. To preserve your routine(s), open the SmartThings App, click on your Zemismart Roller Blind. Once in the device screen, click on the word 'Routines' at the bottom of the screen. Go into every routine and add a temporary device to temporarily hold/substitute the place of the current Zemismart Roller Blind. Note: Replacing the Smart Blind with a temporary device in your routines ensures that your routines are not erased when you remove your Zemismart Roller Blind from your SmartThings App. Once you have substituted a temporary place holder device in every routine which contained the Zemismart Roller Blind you may then delete the blind from your SmartThings App. To delete your device from the SmartThings App, while in the device screen, tap on the ellipsis in the upper right-hand corner of the screen. Now tap “Edit” in the dropdown list. Then tap “Delete device” at the bottom of the screen which follows. With the deletion of the blind you may now proceed to accept the ‘Iquix’ Channel Invitation. Click on the link for ‘Iquix’ Channel invitation. Note: After clicking the driver channel link you will be required to sign into your Samsung SmartThings Account. Next you must then select ‘Accept’ to confirm your acceptance of the channel invitation. After accepting the channel invitation, choose your target hub and select 'Enroll'. Note: Sometimes you must to click the button multiple times. Next, click on “Available Drivers” and select “Install” to install the ‘Tuya Window Shade’ edge driver. Next, verify the installed driver by going to your SmartThings App, find your SmartThings Hub within the 'Devices' tab and then click on your Hub. Then while in your Hub’s device screen, select the ellipsis in the upper right-hand corner and then click on the word ‘Driver’ from the dropdown list. You will then be able to view a list of all of your installed Edge Channels and Edge Drivers. After confirming the installation of the new ‘Tuya Window Shade’ Edge Driver you may now add your device back into SmartThings App by scanning for nearby devices within your SmartThings App. Once the SmartThings App discovers your Zemismart blind, click on your device’s tile and then while in the device screen, click on the ellipsis to confirm that the dropdown list now contains the word "Driver". The presence of the word ‘Driver’ confirms that edge driver is successfully installed for your device. If the Zemismart Blind selected the wrong driver, tap on “Select different driver” and select the ‘Tuya Window Shade’ Edge Driver. All that remains to do is to remove the “temporary/substitution device” from each of your SmartThings routines and add the Zemismart Blind back into your routines. Remember to visit Bud's Smart Home Amazon Store for smart home devices which are compatible with the new Samsung SmartThings Lua architecture. If this information helped you, consider buying me a coffee. PayPal-Me Link Below!

  • SmartThings Edge Driver Update

    Today I am going to present information that I have been able to glean from my latest research about the progress of the conversion of SmartThings Drivers to SmartThings Edge architecture. I’ll provide you will a brief update about the SmartThings Edge Beta Program and the status of the Edge Driver Rollout. I will also talk about which drivers, AKA device handlers that are being converted and also comment about the device handlers may not be converted. I will show you how to check on the status of driver conversion, via a list on the GitHub website that displays converted device drivers as well as those drivers which are still a work in progress. I will also show you how to access a complete list of all current Edge Drivers and explain how to use the driver’s fingerprints to determine if the driver will work with your device. If you watch till the end of today’s episode you will get my recommendation about when to install SmartThings Edge Drivers. Should you install them now or should you wait? If you want to convert a supported smart device to a locally executed Edge Driver, you must first verify that an Edge Driver is available for the device. More on that later. You then must delete the and reinstall the device using the ST App. When you view these reinstalled devices in your SmartThings Account under the ‘My Devices’ tab, you will see that the Device Type is named as a ‘placeholder’, (more about that later). You will also note that the ‘Execution Location’ is reported as the ‘Cloud’. Although the execution location is truly local, the execution location will be reported as ‘Cloud’ due to a temporary glitch in the IDE or ‘Integrated Development Environment’. Now I am going to comment on the Edge Driver Beta program, but before I get into the status of the program, let me first explain the concept of SmartThings Edge for the benefit of those who may be hearing about this for the first time. SmartThings Edge is a new architecture for SmartThings Hub Connected devices. This new environment uses Edge Device Drivers to execute commands locally on SmartThings Hubs. Edge Drivers are Lua©-based and can be used for Hub Connected devices, including Zigbee, Z-Wave, and LAN protocols. The SmartThings developers are taking smart home events that are normally executed on the SmartThings Cloud and moving them to your SmartThings Hub. When the transition to Edge Drivers is complete, each Hub-Connected device will be defined by a driver package will include the fingerprints, components, preferences, and Lua source code for the device it is meant to control. Currently SmartThings Edge is in Beta testing. During this Beta period, the developers are transitioning existing SmartThings Device Type Handlers (DTH) to Edge Drivers. If you wish to check Developer progress toward driver conversion, you can view a list of Groovy DTHs that have ether been competed, as well as those handlers which are scheduled to be converted to Edge drivers. You can assess that list by clicking the link that provided below in the description titled: DTH to Edge Migration You should be aware that some of Custom Device Handlers may or may not be converted to Edge Drivers. So what is the difference between a Standard Device Handlers and Custom Device Handlers? Custom Device Handlers are device handlers that were written either by a device manufacture or a SmartThings Community Member. They are typically a variation of a standard Device Handler which was changed to enhance the capabilities of a particular smart device. The Developers have made it clear that they are only working to convert the standard DTH. They have also stated that it will be up to the creator of a particular Custom handler to convert it over to an Edge Driver to enable the device to work within the new SmartThings architecture. The Dome Siren is a Z-wave device that I have featured here on my channel. This siren will work fine with the standard built-in handler, which is the “Z-Wave Siren” DTH. However, with the standard device handler you get only a single siren. By installing the Custom Device Handler you get enhanced capabilities which include various siren sounds and multiple chimes, the ability to change sound and volume as well as battery monitoring capability. If the creator of the CDH is unwilling to update the handler to Edge, this device will merely function as single sound siren. By the way, I have contacted the author of the Dome Siren CDH and he has stated that he has written the driver, but he is still waiting for Dome to approve it and post it to their channel. Standard Device Type Handlers which have already been converted to an Edge Driver are the device drivers that are assigned when you install a compatible device via the SmartThings App. As an example, if you have a SmartThings or Aeotec Motion sensor currently installed, you will note that these sensors are assigned the ‘SmartSense Motion Sensor’ DTH. If you uninstall your SmartThings or Aeotec sensor and reinstall it today, as I did with my SmartThings Motion sensor, it will be assigned the Zigbee Motion Sensor DTH. However, it will be display in the list under ‘My Devices’ as a device ‘Type’ called ‘placeholder’. This is because the current SmartThings IDE, integrated development environment, is still part of the old groovy based architecture. While under the old architecture, any device that is assigned is converted to an Edge Driver will be represented in the IDE with the ‘type’ designation of “placeholder”. It is my assumption that once the new architecture is established, the ‘placeholder’ name will change to new Edge Drive name. In the meantime, it is important that you do not change the device type. Changing it to a different device type may disable the integration process How do you determine if an Edge Drive is available for your device(s). You identify a compatible edge driver by using the driver’s fingerprints. As an example, I am going to see if an Edge Driver is available for my Third Reality Motion Sensor. To do this you must identify the Product Name: Third Reality; the Model Number: 3RMS16BZ; the protocol used by the device: Zigbee; and the device type: Zigbee Motion Sensor. So now we have identified that the Third Reality device is a ‘Zigbee Motion Sensor’. With this knowledge we can then click the link provided in the description titled: SmartThings Edge Drivers and search in the list for ‘Zigbee Motion Sensor’. Once you find ‘Zigbee Motion Sensor’ you will click on it, and then click on ‘fingerprints.yml’. You then need to search the list of Zigbee Manufactures’ to see if the Product Name and Model Number of your device are in the list. If your device is listed then it will be able to function properly with the Edge Driver. You might say to yourself, if converting to Edge Driver means that my switches, lights and sensors can operate without the internet, why shouldn’t I begin converting all of my devices to now? Let me discuss why I think it may be a good idea to wait to convert your devices to Edge Drivers. The Short answer, to convert you must delete and reinstall each device you wish to convert. When you delete the device you will delete any associated routine in which that device is used. You then need to rewrite all routines associated with the device. If this does not give you concern, then by all mean convert your supported devices to Edge. However, it should be noted that the developers are hoping to convert all devices seamlessly, so that you do not need to go though the process of deleting and on boarding each device, and rewrite all of the associated routines. If you would like to install Edge Drivers on a few devices while you wait, I’ll give you a couple of tips to help make the process less painful. Assuming that an edge driver has been developed and is in place, you must first ensure that the driver provides all of the capabilities of your current device type handler. For example, the SmartThings motion sensor DTH reports temperature and battery status in addition to the detection of motion. Assuming that an Edge Driver exists and that it provides all the current capabilities of the current DTH, you then may want to proceed with the switch to an Edge Driver. As mentioned previously, to switch the current DTH to an Edge Driver you must uninstall and then reinstall the device. However, before deleting your device you want to go into your SmartThings app, click on your device, and then click on ‘Routines’ at the bottom of the screen. Here you will see a list of all routines that are using this particular sensor. Since all of these routines will be deleted when you delete the device, you need to make some notes about them so that you can recreate them once you reinstall the device. You will also want to determine if the routine is using other devices that have not been converted to edge drivers. If you don’t convert every device used in the routine you will need to covert these other devices at some future point, which means that you will need to delete the device and recreate all associated routines. This is why I am recommending that you exercise patience and wait until your devices can be migrated to the new architecture, hopefully with minimal personal work of headaches.

  • ThirdReality Zigbee Smart Shade

    An Innovative Zigbee Smart Shade Today I will be presenting the ThirdReality Zigbee Smart Blind. ThirdReality blinds feature an affordable price, hassle free Installation, multiple means of control and they are directly with compatible Echo Devices and various ZigBee Hubs so they are natively compatible with the SmartThings and SmartThings Aeotec Hubs. The blind is conveniently powered for up to six months using four standard AA Alkaline batteries. Review Disclaimer ThirdReality was gracious enough to send me this blind so that I could do this review. But as usual, they sent their product with the understanding that they would not have influence over the video’s content. As a result you will be receiving my unbiased opinions on the features I consider good, as well as some features which I would like to see improved. What’s in the Box Third Reality ships its blind with a product manual, AA Alkaline batteries, a RF remote, drywall anchors, mounting screws and mounting hardware to include two types of mounting brackets. Blind’s Power Source Smart Blind’s motor is powered by four AA batteries. The batteries are touted to last for 6 months of normal use. The battery compartment is at the bottom of the blind. The compartment can be easily accessed by removing a single Phillips head screw. Blind Material The ThirdReality blinds are made of a durable hot rolled non-woven fabric and aluminum foil. They are waterproof and have a smooth texture. The aluminum foil design gives these shades the ability to block UV rays and also provides for better insulation performance, which can result in energy savings. The shades are to be capable of blocking 90% of sunlight for improved sleep quality. The shade is offered in one neutral, sort of stone color that should match the décor of most homes. Sizing Options The blind is currently available on Amazon with width options ranging from 27 – 38 inches. The blinds length can be set to a maximum of 72-inchs. If you are mounting the blind within a window well, there is no need to set a lower limit because the blind is equipped with a bottom sensor which will automatically detect the window sill to trigger the blind to stop. For surface mounting you can program a lower limit for the shade and the shade will then remember that lower limit going forward. Blind Mounting I decided to mount this blind in my garage at a window that is behind the right side of my workbench. The reason I selected this location is because this window faces to the west. The late afternoon sun makes it difficult to work at the bench without a suitable shade. Mounting the blind was simple and straight forward. The shades can be mounted inside a window well or surfaced mounted, above the window on the wall. I mounted my blind outside the window frame using the wall surface mounts and the provided screws. The bracket’s spring clip design permits an easy and secure blind installation. You just insert the top of blind mounting track on the teeth of the clip and then snap the bottom of the blind mount into place. App Installation To install these blinds in a compatible Amazon Echo hub simply ask “Alexa” to discover devices once the blind is in pairing mode. Pairing mode is initiated by installing the batteries or just be holding the middle pause button on the blind. Paring mode is signified by when the blind’s paring light begins flashing red. To install the blinds in the SmartThings App, select add a new device and then tap on scan nearby. The read light will stop flashing once the shades are discovered and the ThirdReality Smart Blind will be installed shortly thereafter. I renamed my blind as garage blinds. Compatible Hubs The blinds may be controlled using your voice, by the provided RF remote, or via routines created in your Alexa or SmartThings Applications. The blind is compatible with Echo Plus 1st & 2nd Generation, Echo Studio, Echo Show 10, Echo 4th Generation and other standard 3.0 ZigBee hubs, like SmartThings, Eero 6, Eero 6 Pro, Home Assistant, Hubitat and the THIRDREALITY Smart Hub. Areas for Improvement One possible limitation is the blind single color offering. ThirdReality states that this “neutral” color may fit most décor, which implies that it may not be suitable for all decors. Additionally the ThirdReality blind is operates slightly slower than the other blinds I have reviewed. When compared side by side to my SmartWings shade you can clearly see that the SmartWings shade opens at a faster pace than the ThirdReality shade, which is certainly not a deal breaker. As for the motor noise, the ThirdReality blind operates at a relatively quiet noise level similar to my Zemismart and SmartWings blind motors. I have one final concern about the ThirdReality Blind’s motor which may be entirely unfounded. That concern is whether the motor will be substantial enough to last long term. The motor sounds a little labored when opening on the up cycle as compared to my other blinds which have tubular motors. I guess time will tell. Things I Like I very much like the blind appearance. The shade is attractive and its accordion like design is innovative, somewhat mesmerizing and fun to watch. The shade is offered at a reasonable base cost that is comparable to other smart blinds. There are no extra costs other than an incremental cost of one dollar per inch over the base width if you require a blind that is greater than 27 inches. There are no other up-charges for the items such as a remote control, a different blind motor, a solar panel or decorative features such as a blind cassette or valance. The shade is simple in design and it is super easy to mount. The blind is directly compatible with ZigBee hubs and setup in the SmartThings, Aeotec or compatible Amazon Echo hubs is straight forward and easy. If you are looking for an affordable blind that is attractive, easy to mount and easy to install, and if you want the convenience of powering your blind with standard AA batteries, then this blind is definitely for you. Installing the Edge Driver: Follow Bud's Smart Home guide for adding the Third Reality Blind Edge Driver Outro I trust you found today’s episode helpful. I appreciate your time and hopefully I made good use of it. Until my next episode, keep automating and God Bless. Product Links: THIRDREALITY ZigBee Smart Blind THIRDREALITY Store If this information helped you, consider buying me a coffee. PayPal-Me Link Below!

  • Aeotec SmartThings Multipurpose Sensor - SmartThings Edge Capable

    Today I want to talk about the Aeotec Multipurpose sensor and explain why it should be your sensor of choice for your Aeotec/SmartThings hub. Aeotec replicates the devices that were previously manufactured by Samsung SmartThings. They are the exclusive hardware producer of the SmartThings devices. Aeotec devices include the Multipurpose Sensor, the Motion Sensor, the Water Leak Sensor and the SmartThings Button. Aeotec also produces their version of the former SmartThings Smart Plug which features power monitoring capability, just like the former SmartThings plug. They produce a 360 degree indoor Security Camera, a Z-wave Range Extender, plus may more sensors that are directly compatible with the SmartThings platform. So what exactly is a Multipurpose Sensor and what are its capabilities? First, it is an open/close sensor (sometimes referred to as a contact sensor). It is capable of monitoring the status of a door, window, cabinet or a safe. The status of the sensor can be used in a routine to send you a notification when a door is opened. The open status can trigger an event such as turning on a light on or trigger an alarm. It also functions as a temperature sensor which can used to turn on a fan or send you a notification when a room’s temperature exceeds a certain threshold. The sensor’s orientation feature allows it to be used as a tilt sensor to notify you if your garage door is open or closed. I use this feature to check the status of my garage door when the last family member departs my home. And last but not least, it is also a vibration sensor. It can detect if someone is knocking on your door or it can detect if dryer or dishwasher has completed a cycle. It can then be used in a SmartThings routine to send you a notification. I am aware that there are other open/close sensors which are less expensive then the Aeotec sensor. And if you are merely interested in a sensor for monitor when a door is open or closed, then you should purchase a cheaper sensor. However, before choosing just any door contact sensor, it is important to know if the device manufacture intends to develop SmartThings compatible Edge Drivers. You see, the SmartThings platform is currently transitioning its application to require devices with Edge Driver support. As a result of this change all supported devices will function locally, without the need for a cloud connection. Using Aeotec products ensures that your devices will continue to function after SmartThings completes its transition to Edge Drivers. Devices without edge driver support may no longer be recognized by your SmartThings hub, absent edge driver compatibility. Aeotec is a reputable smart device manufacture who is committed to providing the necessary firmware updates to ensure ongoing compatibility of its devices with the Samsung SmartThings ecosystem. So if you want a reliable and hassle free device that is simple to install and has SmartThings Edge driver support, then Aeotec should be your product of choice.

  • Alexa Mail Announcement

    Today we’ll be installing the Ring Alarm Outdoor Contact Sensor in my mailbox so that I can get universal announcements on my Amazon Echo devices anytime the mail is delivered. Demonstrating the Alexa Routine Let’s begin with a brief demonstration of what this routine does. Every time the door on my mailbox is opened, I get the following announcement on all six of my echo devices. Installing the Sensor The Ring Contact Sensor is provided with mounting plates. These mounting plates are supplied with double stick tape adhesive strips. Therefore, mounting the sensor in our mailbox is simple. Just peel and stick. I elected to use a couple of additional 3M Command Strips on the magnet side of the sensor which I attached to the mailbox door. This made the sensor more secure. Don't be too concerned if you cannot perfectly align the magnet side with the sensor. This sensor operates will with up to a one-inch gap between the magnet and sensor. Aeotec Range Extender 7 Before I show you how to write the Miss A routine, let me show you a device that you may use to extend the range of your z-wave signal. If you install your sensor too far from your SmartThings or Aeotec/SmartThings Hub, you may experience connectivity issues due to a weak z-wave signal. The z-wave signal can be easily extended up to 250 percent using the Aeotec Range Extender 7. When the testing the range extender, I found that I was able to extended the range of my signal outside the parameter of my home, from fourteen feet without the Aeotec range extender, to the distance of 29 feet with the extender. This added connectivity range provided me with the distance needed to reach the Ring Contact sensor in my mailbox. The Aeotec family of devices are specifically made for SmartThings so they are reliable and easy to add without the need for installing device handlers. The Aeotec sensor 7 is compatible with both z-wave and z-wave plus protocols and provides 50 percent faster z-wave communication. I'll leave a product link below. The Alexa Routine I’m now going to create a simple Miss A routine so that whenever mail is delivered, I will receive a universal announcement on all Echo devices. To do this, make sure your Miss A is a connected voice assistant in your SmartThings app. Open the Miss A app. click the dash lines on the bottom right corner. Click routines. Click the plus sign to add a routine. Enter a routine name "Mailbox”. Click next. Click when this happens. Choose smart home and you have to look for the mailbox sensor. Click 'Open' I want this routine to run anytime the gate opens, so I will leave this setting as is and click next. Next you must add an action. If you want some or all your echo devices to do the announcement, scroll down and choose messaging. Click send announcement and type in the statement that you want Miss A to announce. And when you click next. You will have an option to choose some or all devices to make the announcement. I trust you found today’s episode helpful. I appreciate your time and hopefully I made good use of it. Until my next episode, keep automating and God Bless. Aeotec Range Extender 7 Ring Alarm Outdoor Contact Sensor Ring Alarm Outdoor Contact Sensor (2 pack)

  • Ring Alarm Outdoor Contact Sensor

    Today I'll show you how to install the Ring Alarm outdoor contact sensor in the SmartThings App. I'm planning to mount this sensor in our utility shed which is situated in our backyard. EDGE DRIVER LINKS AND INSTRUCTIONS!! I’ll also introduce you to the Aeotec range extender and demonstrate how it can increase your z-wave signal by 250 percent. Specifications Checking the specs for the Ring Alarm contact sensor, it is weather-resistant with an IP66 rating. The IP66 rating confirms that It is waterproof against hose-directed water and falling drops of rain or snow. It has an operating temperature range of negative 4 degrees to 120 degrees Fahrenheit. It is connected via Z-wave technology and is reported to have a 250 foot line of sight range. What’s in the Box When you open the box you’ll be surprised by the size of the sensor. The sensor’s hefty size is attributed to the fact that it is powered by two AA alkaline batteries. The sensor comes with adhesive backed mounting plates, screws and screw anchors. The two required alkaline batteries are also provided. According to ring the batteries can power the sensor for up to five years. Viewing the Sensor You can separate the sensor from its bracket mounts by sliding the sensor to the side. On the back of the main sensor you will find a reset hole and an orange setup button. You remove the rear cover to access the battery compartment. The battery compartment is opened by pushing on the two spring clips. Within the battery compartment you will find the two AA batteries. You will also see a weather sealing gasket on the battery compartment cover which is instrumental in keeping moisture out of the device. The magnet side of the sensor can also be separated from the mount by sliding it to the side. You can attach the provided mounts to a wooden surface for a more secured install. Sensor Setup To pair the sensor you will select the option to scan the QR code. When you pull the plastic battery isolator tab, the device will be flashing 3x slowly, and pause, then flash 3X again in a cycle. Press the orange button for 5 to 10 seconds and release. The device will start rapid flashing green to begin paring. After second or two the app will notify that set-up is successful. This sensor pairs with SmartThings as a generic z-wave device. So once the sensor is connected you’ll need to login to your SmartThings account at and manually set it within the My Devices list as a Z-Wave Plus Door/Window Sensor. Testing Sensor Connectivity Before installing your sensor you’ll want to test it to ensure that you have a good signal. Ring Alarm claims you can test connectivity by pressing the orange setup button. They state that a green light while pressing the button indicates a proper signal. This apparently works only with the Ring hub because I was not able to replicate the test method with the Samsung SmartThings hub. Mounting Options As for mounting options, the senor comes with double sided mounting tape, which could be used to mount on smooth surfaces which are not subject to the elements. You can also use the provided screws mount the device or you can use the slits provided on the mounting brackets to secure the sensor and magnet with metal or plastic straps. The strap mount give you the ability to install the sensor on metal gates or a frame if you prefer not to drill holes. Device Mounting Considerations As stated previously, my intent was to install the contact sensor on my utility shed doors. My Hub is in my Basement in the north side of home. The center of my shed doors is exactly 73 feet from the southwest corner of my home. Since the z-wave signal must go though several walls, I suspected that I may need a z-wave range extender. I therefore decided to purchase the Aeotec Range Extender 7. The Aeotec range extender is compatible with Z-Wave and Z-Wave Plus and is reported to provide up to 250% further wireless range. More about my connectivity experience in a moment. Testing the Sensor’s Range When testing the range of the Ring Contact Senor absent the z-wave range extender I found that I could only get a reliable connection up to 14 feet from the southeast corner of my home. With the addition of the Aeotec range extender I was able to extend my signal to 49 feet. Unfortunately, this signal range is 24 feet short of the doors on my utility shed. As a result, I was unable to use the Ring contact sensors in this particular application. Summary of Results What are the takeaways from this venture? The Ring Alarm Outdoor Sensor can be paired with the SmartThings Hub. To be fully compatible with SmartThings, the sensor’s device type handler must be changed in your SmartThings account to a Z-Wave Plus Door/Window Sensor. The operational distance of the contact sensor can be enhanced by use of the Aeotec Range Extender. In my situation, I was able to extend my operational range by 250 percent. This increase in range confirms the performance specifications reported by Aeotec. Although you may get different results based on the location of you hub and strength of your z-wave network, I surmise that if you need to monitor an outside property or pool gate, and that gate is within 49 feet of your home, you should have successful installation using the Ring Outdoor sensor provided it’s z-wave signal is enhanced with the Aeotec Range Extender 7. I trust you found today’s episode helpful. Please leave a comment at the bottom and provide me some feedback. Amazon Product Links: 🛒- Aeotec Range Extender 7 🛒- Aeotec Range Extender 7 (2 pack) 🛒- Ring Alarm Outdoor Contact Sensor 🛒- Ring Alarm Outdoor Contact Sensor (2 pack)

  • SmartThings Rollout of the New Edge Drivers

    Effective Tuesday, April 26, SmartThings will begin rolling out the SmartThings Edge drivers in support of all newly on boarded Zigbee, Z-Wave, and LAN devices that connect to a SmartThings hub. These drivers run locally on the hub and deliver improved reliability and reduced latency compared to cloud-based device handlers know as Groovy DTHs. This transition marks the start of a gradual process that will include a small number of devices initially, but will expand to cover more devices over the coming months. The steps required to onboard, (or add) devices with Edge drivers is unchanged from the existing experience, and according to the Developers, you should not need additional steps to complete this process. SmartThings Developers have provided some answers to some anticipated questions in the FAQ section of the article (Edge Drivers FAQs). In the text that follows, I will provide you with a brief summary of the information contained in the FAQ section. To use Edge-enabled devices with SmartThings, you will need a compatible SmartThings hub with firmware version 000.038.000XX or greater. To determine your hub’s current firmware version, find your hub in the devices list and tap on the Hub’s tile. Next, tap on the ellipsis, (the three dots) in the upper right hand side of your screen. Then tap on information. Your hub’s firmware version is listed under your Hub’s Name. Your existing hub-connected devices (those which you previously installed) will not be transitioned to Edge drivers. Only devices that are being newly on boarded will have the support of the new Edge drivers. In other words, existing devices will not automatically transition to Edge drivers at this time. If you wish to convert your current devices to use Edge drivers, you must manually transition the device by using the following developer resources. You can access Developer Documentation for SmartThings Edge as well as sample code and list of current Edge drivers. The developers invite you to start a thread or reply to existing threads in the SmartThings Community with questions or feedback on building or using Edge drivers. To identify an Edge-enabled device in the SmartThings app, use the following steps. First open the SmartThings app and select the device. Then tap on the ellipsis at the top right. Edge-enabled devices will list the word “Driver” as an option in the selection menu. The following link, SmartThings Edge Driver List will provide the current list of SmartThings Edge drivers which you can use to determine if a device has a supported Edge driver. If you do not transition your devices to Edge drivers before Groovy support ends (date to be included in a future announcement) those devices will not communicate with the SmartThings platform until they have been re-on boarded or migrated to Edge drivers. If you log into your online SmartThings account and see that your edge-enabled device is showing as a cloud-connected device, be aware that this is due to a known bug with the Graph IDE tool. If your device has an Edge driver it will be running locally through the hub. SmartThings has stated that this current announcement is the first of many that will be made in upcoming months as they complete the conversion away from Groovy Device Type Handlers. I will be keeping you informed of these announcements as we continue our transition to the new locally based Edge Drivers. If you have not yet subscribed, take to opportunity to do this so that you can be informed as updates occur. I’d be interested in your thoughts about this transition. Take a moment to comment below. Until next time, keep automating and God Bless!

  • Aqara ZigBee Sensors for SmartThings - Installing Custom Device Handlers

    In the video which follows, I provide you with information about the fantastic benefits that gained via the Aqara sensors. The Aqara Zigbee Door and Window Sensor which I feature in this video is very small in size making it less conspicuous, it is priced less than $20 dollars and it has an extraordinary battery life of at least two years. Each Aqara sensor requires the installation of Custom Device Handler. The code from these Device Handlers can be obtained from a repository of device code. This source for device code is known as the GitHub Repository. When it comes to adding the custom device handler code to SmartThings devices, you can either add the code manually or you can create a GitHub account and link that account to SmartThings. Establishing a link between GitHub and your SmartThings account will provide you the ability to easily install new or updated code to your smart devices. My recommendation is that you setup a GitHub Account and integrate GitHub with SmartThings, by executing the steps listed under Option 1. I provide the steps which you can follow link GitHub in the following paragraphs. However, if you do not plan to create more then a couple custom device handlers and you want an easier approach to install the device handler for the Aqara Door and Window Sensor, then skip down to Option 2. PLEASE NOTE: If GitHub Integration is Already Enabled within you SmartThings Account then it is very easy to add the bspranger repository to your SmartThings account. Just skip down to the section, 'Add a Repository to the SmartThings IDE' and add the data provided for the 'Owner', 'Name' and 'Branch' fields as instructed. OPTION 1 - Setting Up A GitHub Account and Integrating GitHub with SmartThings If you do not have a GitHub Account, I highly recommend that that you get one. It is easy to set up and your account access it gives you free access to many repositories containing many and various SmartThings Device Handlers. To set up your account select 'Create a free organization' from the GitHub plan/pricing page. For more information for obtaining a GitHub account follow the steps provided on the page titled "Signing up for a new GitHub account" or by following the Steps provided by Smart Device Life. Once you have you GitHub account set up then you need to Enable GitHub Integration with your SmartThings Account. You can follow the instructions in this link to enable this integration just log into you SmartThings Account IDE @ and then click the Enable GitHub Integration link on the My SmartApps or My Device Types page. This will launch a wizard that will guide you through the process. Then it is just a matter of following Steps 11 through 16 detailed in the content provided by Smart Device Life This is a one time setup. Going forward you will be able to use the SmartThings Account IDE to easily connect various repositories in order to access the code for various custom device handlers. How to add a GitHub Repository to your SmartThings IDE It is very easy to link to a GitHub Repository once GitHub is linked your SmartThings account. You can add a repository by taking the following actions: While in the 'My Device Handlers' tab click on the 'Settings' button Add the following information in the appropriate fields. (Note: this information is specific to bspranger's Xiaomi Aqara repository: - Owner: bspranger - Name: Xiaomi - Branch: master Save the newly added repository by clicking on 'Save' at the bottom Now you want to click on 'Update from Repo' and select the newly added repository from the dropdown list of repositories. In the next page select the appropriate device handler(s) by placing a checkmark next to the device handler(s) you wish to install Next, check the box next to 'Publish' at the bottom of the list of device handlers and then click on the blue 'Execute Update' button. Your new device handler is now published. In the next page you will tick the box next to the handler ending with 'Xiaomi Aqara Door/Window Sensor'. Be sure to check the box next to 'Publish' and then click on the blue 'Execute Update' button. Your new device handler is now published. To assign the newly added Device Handler to your SmartThings device, first add your new device to the SmartThings App. Next, log into your SmartThings account and click on the 'My Devices' tab. Now perform the following steps: Find your Aqara device in the list of devices Click on your Device Name Click on the 'Edit' button Expand the dropdown list under 'Type' Select 'Xiaomi Aqara Door/Window Sensor' for your device type handler Option 2 - Manual (Manually install a Device Handler by Copying and Pasting the RAW Code ) If you prefer not to setup a GitHub Account you can easily install the Device Handler using the RAW GitHub Code. I will provide the links to the RAW code for the device handlers of each SmartThngs compatible Aqara sensor for your convenience. To manually install the device handlers: login to your SmartThings Account at (this is also referred to as the SmartThings IDE), and go to “My Device Handler”. Click on “Create a New Device Handler” button on the top right. Select the “From Code” tab. Click on the appropriate Aqara device link below to access the specific code that you want to copy. Use your mouse to click on the code text and then hold down on the control 'Ctrl' key on you keyboard and while holding the Ctrl key tap the 'A' key. This will select all text for the RAW code. Now copy the text and go back to your SmartThings account and paste the relevant code in the white space under the "From Code" tab. Then click 'Save' and then “Publish” and “For Me”. Repeat these steps if you want to add other device handlers for different Aqara sensors. Links to Aqara Sensor RAW Code Xiaomi Aqara Motion Sensor – here Xiaomi Aqara Contact Sensor – here Xiaomi Aqara Temperature/Humidity Sensor – here Xiaomi Zigbee Button – here Xiaomi Aqara Leak Sensor - here To assign your new device handler to your device, first add your device to the SmartThings App and then login to your SmartThings IDE Account and find click on the 'My Devices' Tab. Now perform the following steps: Find your Aqara device in the list of devices Click on your Device Name Click on the 'Edit' button Expand the dropdown list under 'Type' Select 'Xiaomi Aqara Door/Window Sensor' for your device type handler If this article helped you please remember to give it a like.

bottom of page