It is a Z-wave interface for hardwire alarm systems
Donāt know, I have two on backorder, no reason that it shouldnāt.
Will need a custom device and smart app in order to expose both channels.
It is (still?) a challenge in SmartThings to make one Z-Wave or ZigBee device appear as many, if the physical device has a single identifier.
Ideally a Device Type should not require a custom SmartApp to function, as the architecture of SmartThings explicitly abstracts and isolates hardware from applications.
So perhaps some clever Device Type coding can do this āthe right wayā and make it look like 2 distinct contact sensors (ācapability.contactSensorā), each with its own label, thus being instantly usable in dozens of existing SmartApps.
Iām interested in seeing this play out for more and more multi-channel Device Types.
Yea, I get what needs to be done on the ST side, multiple duplicate capabilities per device is in the pipeline from what I hear.
However, Iām a āget it working the way I want right nowā kind of guy.
If/when ST updates the schema to support this, Iāll spin back around and clean up all my virtual devices and manager smart apps that I currently use in these situations.
I totally agreeā¦ I was hoping that you might know if ST had fixed this limitation already in a more direct mannerā¦
The use of Virtual Devices with necessary SmartApp is the workaround that came to me as wellā¦ Though Iād appreciate if you share your actual implementation when the time comes.
Thanks!
Will do, unless the Fibaro Master ( @wackware ) beats me to it.
I am surprised that ST has not created their own UBS. I am waiting to order a couple myself. I am trying to get my security systemās physical output, which I have programmed when it is armed to turn on the ouput, to then connect to the UBS which then ST will see and change modes in ST automatically to House is Armed so I donāt have to always open the app to change modes and know eactly when the system is armed.
You can do this with a mimolite today.
1 Like
Yes but the UBS is insanely small, giving you options to make a dumb device smart. I would like to make this perimeter sensor smart:
http://www.amazon.com/B006Z9581G
I can use the same power source and secure the UBS with room to spare.
1 Like
Yea, exactly, the mimoās huge compared to this thingā¦
Can I confirm that we are referring to this device; or is there a better reference?
The OP can put this (or better) link the in Topic opening post if appropriateā¦
Nope, this guy:
http://www.vesternet.com/us/z-wave-fibaro-universal-sensor-us
Ahā¦ OK. The Door/Window I originally linked seems to include the same terminals (but perhaps different limitations, size, costā¦). With the Door/Window you get a āfreeā magnetic reed sensor built inā¦
And it is the same cost ($49.95): Brands - Fibaro ā Vesternet
Here is a photo I found on the Internet:
I donāt think it is available in the states yet.
1 Like
Has someone updated the device type for this to get battery status working properly and any other features this device offers from Fibaro?
This thread is about the binary sensor, not the door/window sensor.
AFAIK, currently there isnāt a device driver for the binary sensor.
I know but since it has an input on the window/openclose sensor I was thinking about using it for something temporary until Fibaro actually starts selling the UBS to itās distributors.
1 Like
@codytruscott Hey man I saw in one of the thread you pointed out the Fibaro UBS and was wondering if you have a device type for this or have on in your setup? This is the thread where you pointed it out 
can I link to this thread, 1st input is working but could do with some help getting the 2nd input to be seen by smartthings
Ooo. Thatās my question.
Since then Iāve figured out how to get the device responding to both inputs. Iām not familiar with the methodology used and so may well be doing it all wrongā¦
Iāve got my device sending āswitch1ā, āswitch2ā plus āopenā/āclosedā which I can check in my āsmartappā.
I havenāt figured out how to make the simulator work (but then it doesnāt work on my computer at all anyway), nor have I figured out how to make it behave like two distinct switches (or even if itās possible).
Iām still fiddling around, the muddy waters have cleared a little and things are a lot less hit and miss than they were but I think Iāve still got a long way to go before I have it figured out well enough to implement stuff properly.