BRK Smoke detectors and Ecolink door sensor

[groundzero2010 (Bobby Solis)]

I just recently purchased and installed a BRK relay kit and Ecolink door sensor. The BRK relay kit is connected to my smoke detectors and using the outputs to make my door sensor show closed in Normal state, and opened when the smoke detectors are going off. Everything is working fine but I’m wanting to change the name of the sensor state and preferably change the icon in Smartthings. I have no clue where to start or even if it’s possible.

Anyone have suggestions on changing the icon and state names?
Looking to change ‘Closed’ to ‘Okay’ and change ‘Open’ to ‘Detected’ (or something along those lines)
And the icon’s aren’t necessary, but would be nice to represent a smoke detector.

[MarkTr]

You’ll need to switch the Ecolink to use this device handler, or a similar one.

[OBSOLETE] Contact Sensor as Smoke or Carbon Monoxide (CO)

I made two modification of the standard Z-Wave Contact device so it can be used as a Smoke or a Carbon Monoxide sensor for those that are hard wiring their sensors in. The smoke device type also will appear in Smart Home Monitor as a available device. I did this because of recently adding my Kidde Smoke & CO sensors into some contact switches project I did here: Either pull from the GitHub or add my GitHub to your IDE. Hopefully someone finds them useful. GitHub: vseven - SmartThings_VSeven - master

If you’re new to custom device handlers, here’s an explanation:

[OBSOLETE] FAQ: An Overview of Using Custom Code in SmartThings (SmartThings Classic, Groovy Code)

The original FAQ information in this thread refers to the original smartthings architecture, which was in place through the end of 2022 and a little beyond. Custom code was written in the groovy programming language and ran in the smartthings cloud. As of May 2023, you can no longer add new Groovy DTH‘s or smartapps to your smartthings account. So if you came here because of a link in an old forum thread, or on another site, I’m afraid the Groovy information is no longer usable. All of this was replaced by a new architecture. Cloud to cloud integrations use the smartthings API. Hub connected devices, mostly Zigbee and zwave, now use “Edge Drivers,” written in the LUA programming language. Here’s the official announcement on those: The process for using a custom Edge Driver in the new …

[groundzero2010 (Bobby Solis)]

Thanks for the info! I’ll read through it and see what I can come up with.

[groundzero2010 (Bobby Solis)]

Got the new DH added and working. Thanks again for the help!

[derekwbeck]

With your relay setup, is it possible to force trigger the detectors to go off, as they would in response to the interconnect feature? In effect, is it possible to use the ST connected relay to start the detectors on demand and use them as if they were sirens? (Irrespective of code and ordinances)