Security Issue with a Fifteen Exterior Door Church

I’m tired today, so I can’t go into a lot of details, but are you aware that smart things only allows for one hub per “location”? It’s pretty hard to tie two hubs together and each one can only report on the devices that are joined it. I don’t know how action tiles handles multiple locations, though, Since I know you’re mostly interested in the display. @tgauchat Will have to comment on that part.

What makes you think that you’ll need two hubs?

In lieu of other details, I’m going to link to a how to article in the community – created wiki on automating an out building which has a lot of discussion about two Hub management.

http://thingsthataresmart.wiki/index.php?title=How_to_Automate_an_Outbuilding

Well, couple things, the distance involved and the fact that the sensors will all be non-Z-wave plus. I’m certainly open to suggestions to hub and mains-power repeater placement. If I can get away with just one, that would be great.

I was reading this… Maybe I’m missing something? The thread talks about Ring doorbell, Google Home, Alexa, etc. Don’t want/need all that. I am looking toward an easy end-user notification system.

Based on what I’ve read, if you are using SmartThings for the hub(s) and sensors, then ActionTiles is the ideal app solution for “seeing at a glance the door status” in your scenario, Bob.

A single ActionTiles Panel can connect to unlimited number of SmartThings Accounts and/or Hubs. The Panel can be securely restricted from all functionality besides the view-only monitoring that you wish to provide. A simple inexpensive WiFi tablet (such as an Amazon Fire 7" or 8") is all that is required to view the status of all the sensors.

2 Likes

Sounds like ActionTiles can handle it if you need two locations, but I’m not seeing any devices which are more than two hops from the hub on your drawing. Or is the issue that you’re planning to put sensors on the doors on the far left as well?

By the way, it won’t matter if the sensors are Z wave classic as long as the repeater is Z wave plus. You’ll get the extra range from the repeater anyway so you pick up more distance that way.

1 Like

Sorry, I’m taking a little bit to reply, most busy on weekends.

Yes, exactly what is needed if we do multiple hubs or not.

We are planning on doing the doors on the far left, but perhaps as a second phase. Sorry, should have mentioned that. I may rethink the two hub scenario. Depending on the repeater placement, I could try to get the hops to follow the hub down the hallway toward the remaining five doors on the far left? I could replace the hub with a mains-powered device, add another somewhere in the middle and the hub at other end of the hallway. The block walls might be the biggest problem (Heavy lines are block, thin are new construction drywall.) Anyway, I say thank you again for all the help.

1 Like

I like the hub right where it is. :sunglasses: Then get a zwave plus repeater at the far end of the hallway that picks up signal from the hub and you should have plenty of coverage on the left side of the building as long as you are using zwave plus repeaters.

I don’t know if it helps any, but Z wave bulbs are good repeaters for Z wave. (Zigbee bulbs can be fussy depending on the brand, but that’s obviously not an issue here.) sometimes there’s a place to put a lightbulb when there isn’t any outlet for other repeaters. Just make sure its zwave plus, you’re going to need the range.

https://www.amazon.com/Enbrighten-Wireless-Dimmable-Equivalent-35931/dp/B01KQDIU84/

2 Likes

The light bulb idea is great and looks to be a good cost saver, however I can only think of one place (that main hallway) where a bulb is on all the time. We have other places where we have A type bulbs, but they are not going to be on all the time. I’m assuming a bulb like this would have to be energized to work as a repeater. Please check my assumption.

Anyway, I got the go ahead on this project. My next step is to get the hub in it’s place; run a network line and figure out power to it where there is no power currently. After that, switch my hat to DIY for one of the doors and engineer the micro switch implementation for the lock status, run the wires, and put in a raceway/conduit to hide/protect said wire. I also will need to add in repeaters somewhere, probably light switches. Then, for each of the ten doors, it’s rinse, lather, repeat. So, with that I’ll be and have been busy with these steps. I’'ll be responding and updating as needed. Thanks, -Bob

1 Like

The bulb has to be on power, but can look dark. That is, the light will appear to be off, but the radio will still be on and available as a repeater. :sunglasses:

2 Likes

I’m using the GoControl door/window sensor with the device type handler that enables a secondary device out of the contact terminals for an external sensor. Is there a way to have it report locked/unlocked instead of closed/opened in the SmartThings app?

You could use a custom Device Type Handler; but if you’re just using a Contact Sensor, will it really be indicating that the door is locked and not just closed?

It’s already enabled via a DTH; the custom DTH (@krlaframboise) transforms the GoControl WADWAZ-1 into a multipurpose device. Internal magnet activated reed switch, and separate external micro switch sensor… I’m using the internal reed sensor to report the status of the door (open/closed). I’m using the external switch to report the status of the lock (locked/unlocked). Right now the lock part reports as open/closed. I’m wanting it to report as locked/unlocked. Hope I’m not clear as mud. :wink:

Post or link to the custom DTH code, and I can likely tell you whether or not changing the status to read “locked/unlocked” is easy or difficult.

The thing is, if so, I’d recommend having the DTH claim Capability “Lock”, but then ActionTiles and other SmartApps will assume it actually supports the Commands lock() / unlock() too.

Child…

I think I found a quick kludgy fix… Drawing on my former life as an UNIX/Linux Sys Admin …
In the Child I changed lines 106-107 from:

				label:'Closed', 
				icon:"st.contact.contact.closed",  

to:

				label:'Locked', 
				icon:"st.locks.lock.locked", 

and lines 110-111 from:

				label:'Open', 
				icon:"st.contact.contact.open",

to:

				label:'Unlocked', 
				icon:"st.locks.lock.unlocked",

It works, but me NOT being a coder, there’s probably a better/proper way.

-Bob

Your implementation is fine.

Umm, uhhh, here’s some pictures…

First things were to remove and open the box where all the levers and lock business is at

If you remember from my first post I was going to use the rotating cylinder with an added cam that would activate the micro switch. No can do. The cylinder, via the post pushes the lock slider back and forth. Lock is 360 degrees from unlock. The switch would activate on both lock and unlock.

So, I modified the switch lever to reach a point of activation at the end of the lock slider…
Once mounted we get Locked and Unlocked. (Hint: I used the ‘normally closed’ terminal and the ‘common’ terminal.)

Then, solder on the wires, drill holes where the red marks are. (Down the red hole and under and out the opposite side the latch is on.) Attach the other end of the wires to the terminals in the sensor.

Reassemble the box, mount the sensor and magnet, and then add some raceway to protect the wires.

I have yet to place the hub in the spot previously mentioned.

2 Likes

Looks like the changes for the status text and icon in the DTH does not transfer into ActionTiles. Is there a way to modify the DTH or to configure ActionTiles to achieve this?
Thanks, thanks

Funny… When thinking of what methods to suggest to solve the original problem, I tried to keep ActionTiles in mind, but I deferred in order to ensure you got the quickest and easiest solution you could implement yourself.


ActionTiles has no access to the DTH definitions, and thus cannot automatically replicate any special customizations made to them. ActionTiles only references the standard “Capabilities” claimed by the Thing.

So there are only three options for your scenario:

  1. Continue to have the DTH claim Capability “Contact Sensor” and use one of the custom icon selections available in our Tile Settings. We don’t offer a “lock” icon - yet. We might consider adding one to the list, but would hesitate to make it identical to the default Lock icon to avoid confusion. We’re also working on a broader and more generakized icon library.

  2. Make more substantial changes to your DTH to claim and conform to Capability “Lock” (with null Commands though, because your locks are “read-only”).

  3. or Add Virtual Lock device instances to be kept ij sync via SmartApp like “Universal Device Translator” (not sure of that name) or CoRE.

Option #1 is the simplest but least satisfying. The state on the Tile will still read open/closed.

Option #3 is the most “proper”, but adds clutter.

Option #2 is the best choice if you insist on making your Contact Sensors pretend to be Locks. It is just a few more changes to the DTH.

Thanks for your quick reply.

“A broader and more generalized icon library” sounds great. But until then, I’m leaning toward option #2.

Great!

Basically you have to change all references from:

  • contact to lock
  • open/closed to locked/unlocked
  • possibly include code in the Command methods to sendEvents reinforcing the current state of lock; else ActionTiles may assume that a tap on the Lock is actually successful. If you are using read-only Panels, then you won’t have to worry about this.

(Let me know if you get stuck.)