![]() The ability to write your own device handlers and SmartApps using the SmartThings web IDE environment is an impressive and powerful feature. While these apps support a great deal of flexibility and customization, including the ability to write your own rules or use code developed by others, there is little consistency in their naming conventions and interfaces, and often quite a bit of overlap in their capabilities. The SmartApp capability is perhaps one the SmartThings Hub’s greatest strengths as well as the most confusing aspect of its mobile interface. The SmartThings automatic rules or actual automation capabilities, such as lighting automation, home monitoring, general push and text notifications, as well as the aforementioned CoRE are provided by SmartApps that need to be installed from the Marketplace menu. Despite this internet dependency, direct device control is very responsive, with hardly any perceptible delay. Many of the hub’s automation triggers are still able to operate if your internet connection is lost, however, you will not be able to directly control your devices from your mobile device without an internet connection, even if you are connected directly to your home network. The software has been fairly stable for me, although the mobile app is at times bewilderingly confusing. In general, I’ve been pleased with the SmartThings Version 2 Hub. SmartThings SmartTiles Web Client running on an otherwise unused iPad. I also added a virtual switch device handler to the hub and defined it as a “Rain Mode” that can be toggled by current weather conditions via IFTTT for incorporation into garden watering rules. For IOS and Android users – and those with more complex scenario needs, the free CoRE (Community’s own Rule Engine pioneered by Adrian Caramaliu) allows for extremely sophisticated rules and triggers. For Apple IOS users, the $9.99 Smart Rules is a very straightforward way to add simple rules to your devices. There are a couple of 3rd party rule engines available that fill this glaring gap in the base system. After adding my devices, I also installed a user developed Rule Engine using the SmartThings IDE. Some of the most useful capabilities for the SmartThings hub come from user-developed content. SmartThings has a very strong user community that is constantly improving the base capabilities of this unit using the SmartThings web-based Integrated Development Environment (IDE) based on the Groovy language. The SmartThings interface has a convenient method to first exclude your Z-Wave devices from any previous network, so I did not need to manually reset the devices or even access the hub that was controlling them before. Within minutes of setting up my account, I was able to add several of my existing wall switches, energy monitors, flood sensors, and a Nest thermostat to the hub. Initial set-up requires that you connect your hub to your home network via its ethernet port, download the mobile app for either Apple IOS, Android, or Windows mobile, and set-up an account on the SmartThings cloud. The back of the unit includes a reset switch and unlabeled ports for the power adapter, ethernet, and two USB connections, which Samsung says are for future USB expansion capabilities. Samsung claims about 10 hours of battery-powered hub operation in the event of a power outage. Mostly from making minor changes to exisiting ones to customize them, however I do not know what to do to start from scratch and create the device.The package contents include the 5″x4.5″x1.25″ hub itself, a 5V, 2A AC/DC power adapter, ethernet cable, the SmartThings Hub Quick Start Guide, and 4 AA batteries (which gives the otherwise featherweight unit enough heft to keep it from flying away in a strong wind). I have a little knowledge of device files and smart apps. Not sure how to test the POST in a browser to open and close the door. I have been able to make the GET API calls using a webbrowser with no problem and can see check the door state. Finally, you make an HTTPS POST to the server and can change the door state (open or close the door) Then using the security token, you can make another HTTPS GET request and get the door state. It returns a JSON response that includes a security token. To use the API, I need to make a GET request via HTTPS to a cloud based server. With some research, I have found some info on its unpublished API. But i would much rather it be integrated into Smart Things. Cant use a relay to trip the door, since it uses serial communications from the button to the door. ![]() It uses a proprietary system for remote access. I have a chamberlain MyQ garage door opener.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |