If you are finding your geofence is triggering when you are home or there is a substantial delay in your geofence triggering a scene, we suggest you increase the size of your geofence radius to compensate for this.
It seems there are some differences on how some mobile devices handle their GPS locations with other apps on that device therefore your experience with a geofence can be different depending on the device and service you use.
We suggest using a minimum radius of 150m but if you are experiencing your geofence triggering when you are inside your fence, or delays in scenes triggering when entering or leaving, we suggest you take it to 300m or more. This will give your control system time to get the signal that you have entered or left your geofence.
It is pretty easy to do this.
If you would like to see how big your fence is now become, hit the "Back" (Top Left) after saving and you can see the map and how big your fence now is in relation to the roads near your home.
If you would like to turn on of off notifications when entering and leaving your fence, check the "Notify" box.
Make sure the "This is my home" box is checked if you would like mode changes based on actions with this geofence.
This entry will show you how to get your Smartthings hub to work with the dual relays we use our lineup of Z-Wave Outdoor Motion Lighting. (Monoprice 11990 & Vision ZL7432)
First let me say that I am not a ST user nor do we have a ST hub, so we have no way to test our products with this controller and these instructions but apparently they do work.
Apparently the Smartthings hub is not equipped to work with these relays that have multi channel command classes built in them. Our entire lineup of Outdoor Z-Wave Motion Sensing Lights went to version 2 a few months back and now uses a multi channel command class to communicate with the controller and for some reason, ST does not know how to handle this without a new handler.
First, let me thank JustInTime over at Github for putting this together.
Here is his post.
Here are the instructions.
Custom Device Type for Monoprice 11990 Dual Relay Module
The code in this repository will interface with the Monoprice 11990 module in a way that allows both switches to report near real-time status back to the SmartThings Hub. SmartThings ships with a "Z-Wave Device MultiChannel" device type that will (sorta) work, but you'll quickly find that switch 2 doesn't update it's status in the SmartThings app. This device type will do just that.
The bulk of the work for this was done by Eric Maycock for the Philio PAN04 module. All I did was remove the parts that didn't work with the Monoprice module and publish it. Special thanks go to him for all of his work.
Install the Custom Device Type.
First, we need to install the custom device type into your SmartThings account. Don't worry, this wont hurt a bit.
Install the dual relay adapter SmartAppSmartThings doesn't really allow you to interact with the individual switches on a multichannel device very well. So, we'll be creating two "virtual switches". These virtual switches will look like a normal on/off switch to the SmartThings app, but in reality will just be associated to one of the two switches on our relay.
Installing the virtual switches.
We have had some reports that the SmartThings hub is not seeing the status of the Enerwave ZWN-RSM1S. We use this relay in our Z-Wave outdoor motion lighting products.
If this is true in your case, we recommend you visit this page and see if this fix, can fix the issue.
Please use at your own risk as we have no way to test this potential problem solver.
Let us know if it helped you as we would like to know to recommend it to others.
In this demonstration we show how LED light bulbs and Z-Wave dimmer switches sometimes do not work together. Then we demonstrate a fix for the problem and a way to make them play together and just work the way they are suppose to!
Items used in this demo.
Dragon Tech Z-Wave Dimmer WD-100
Intermatic CA600 - Discontinued
007 Systems Lighting Accessories