First Alert Smoke/CO detector

EMERSON_VIER · August 29, 2019, 1:18am

Hi Guys, do you have an icon for Smoke and CO ?

josh · August 29, 2019, 1:39am

I don’t believe we expose the smoke icon at the moment, but I can add it to the list.

In the meantime, the fire and skull icons have been used by some people for smoke and CO2 (respectively)

Out of curiosity, are you planning on using these with the Hero Attribute Inline Icons that are in beta? Or do you have some sort of virtual device that your smoke/CO is mapped to that you want to use an icon on?

EMERSON_VIER · August 29, 2019, 2:11am

Thank you for your reply.

Yes I want to use Hero Attribute

I have GOControl WADWAZ-1 on my Hubitat, But I still looking for a nice Driver.

I found one for Smoke, but nothing for CO2 Carbon Monoxide yet

josh · August 29, 2019, 2:14am

How about a couple different options like these:

And what it would look like in the new Hero Attribute (inline icons):

EMERSON_VIER · August 29, 2019, 10:55pm

Hi I need help here again, my Icon can not change the color when I changed the status.

josh · August 29, 2019, 11:54pm

We didn’t have an ‘active’ state defined for the smoke attribute. I’ve gone ahead and added detected as the active state in beta. Can you give it a try and let me know if that works for you?

(Be sure to refresh the whole page to pull in the latest changes)

EMERSON_VIER · August 30, 2019, 12:22am

Perfect !

May I ask you to do the for Carbon Monoxide? Please see below:

josh · August 30, 2019, 12:49am

I have added it to the beta. Can you please verify?

EMERSON_VIER · August 30, 2019, 1:27am

Sorry did no work

From Hubitat

josh · August 30, 2019, 1:30am

Hm. The screenshot of ‘Current States’ from your hub doesn’t look right. It’s showing the value under an attribute called CarbonMonoxideDetector (which is the correct name of the capability), but the attribute is supposed to be named carbonMonoxide.

Is this a community developed driver or an official Hubitat one? Either way, I’m sure the driver developer would like to be aware of the issue so they can correct it.

EMERSON_VIER · August 30, 2019, 2:10am

This is not a offical by Hubitat.

I read some information here

Use this Driver to Smoke from PrayerfulDrop, works well.

github.com

PrayerfulDrop/Hubitat/blob/master/drivers/kiddie-firealarm.groovy

/**
 *  GOControl Contact Sensor:Smoke/Carbon Monoxide Detector
 * 
 *  importUrl: "https://raw.githubusercontent.com/PrayerfulDrop/Hubitat/master/drivers/kiddie-firealarm.groovy"
 *
 *  Copyright 2019 Aaron Ward
 *
 *  Original code ported and modified for hubitat from: https://github.com/luder888/SmartThingsPublic/blob/master/devicetypes/luder888/zwave-door-window-sensor-as-smoke-detector.src/zwave-door-window-sensor-as-smoke-detector.groovy
 *
 *  Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except
 *  in compliance with the License. You may obtain a copy of the License at:
 *
 *      http://www.apache.org/licenses/LICENSE-2.0
 *
 *  Unless required by applicable law or agreed to in writing, software distributed under the License is distributed
 *  on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License
 *  for the specific language governing permissions and limitations under the License.
 *
 * ------------------------------------------------------------------------------------------------------------------------------
 *

This file has been truncated. show original

For Monoxide Detector
I use this information below from Ryan780 to modified the Driver

Please see below new print from my Hub:

But on my Dashboard did not work.

josh · August 30, 2019, 2:33am

Thanks for the additional details. Since you’ve updated to a new driver there are two things you might need to do:

Complete the authorization process again
This causes SharpTools to resync your devices over. If any of the underlying capabilities or attributes change when you change drivers, this gets them in sync.
Refresh the dashboard
Since the proper attribute wasn’t available originally, the dashboard probably wasn’t able to setup the requested subscription. When you refresh a dashboard, it will kickoff a healthcheck that looks for missing subscriptions and corrects them.

EMERSON_VIER · August 30, 2019, 11:52pm

No lucky yet, please see the log from Hubitat

josh · August 31, 2019, 12:54am

Emerson-
That looks like the logs directly from the custom device driver. What about the steps above?

Complete the reauthorization making sure your CO2 device is selected and synced over.
- Since it likely doesn’t implement one of the core capabilities, you’ll need to use the process noted in: How To Authorize Unrecognized Things - #4 by josh
After completing the authorization, wait several minutes to make sure the device synchronization is complete and double check the device details in SharpTools.
- If you are adding new devices, you can watch the location details screen and the devices will sync over in real time. From your user page, tap the ... next to your location and you’ll see a list of things for that location. Once the device is synced over, you can click on the device name to view the details of it and make sure it is reporting the correct attribute name and value.
After the synchronization is complete, manually refresh your dashboard page to kick off the healthchecks.

EMERSON_VIER · August 31, 2019, 5:16pm

Josh I did all of your steps.

I am think something wrong on my Driver, I never modifier a Driver, I will ask for some help on Hubitat Community to check the Driver.

Thank you!

EMERSON_VIER · August 31, 2019, 7:46pm

Hi Josh,

I have new Driver, work well on Hubitat DashBoard, please see below.

But did not work here, the value never changed, aalways show “detected”

josh · August 31, 2019, 7:51pm

Thanks for the screenshots. That attribute doesn’t appear to be subscribed at the moment as indicated by it being grayed out. Add it to a dashboard in a Hero Attribute Tile or a Trigger in a SharpTools rule and it will automatically get subscribed when the dashboard/rule is saved.

EMERSON_VIER · August 31, 2019, 8:12pm

Congratulation work well now!

You are really helpful.

Wendy_Reed · May 10, 2020, 2:17pm

SmartThings: I was able to add the smoke detectors in STs Classic / SharpTools under Additional Devices (which sensors section) but they don’t show up when I try to authorize them on SharpTools web. When I go back to SharpTools in the STs Classic app I see the smoke detectors have disappeared.

josh · May 10, 2020, 3:47pm

Welcome to the community and thanks for posting.

After authorizing the devices via the web, you can go back and add the extra devices via the SmartThings app and it will sync them over automatically.

It has to be in that order though - the web authorization only lists the core capabilities and will drop the ‘extra’ selections, so you want to do web first then modify it via the mobile app.