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.
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.
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:
I can use the same power source and secure the UBS with room to spare.
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:
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): http://www.vesternet.com/us/z-wave-fibaro-universal-door-window-sensor-us
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.
@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.