Not seeing CO alarm with First Alert ZCOMBO detector

[johnconstantelo]

@sscopp

Thanks for the prompt reply. Yes, I know all is or has moved to local edge drivers. The edge driver on github is only listed as a First Alert smoke alarm, not the z combo I have that does both smoke and CO. If I were to try this driver, how do I remove it from the hub so I could go back to the one i am currently using? Will the old one, the one currently in use, be listed in the “Select a Different Driver” section?

I don’t know what CLI stands for. Please clarify.

Ok, cool I wasn’t sure. I have two zcombo detectors running ST’s Edge driver, and I know for sure the smoke part works. I haven’t tested in a while, but I recall the test called out CO as well:

If the one you are currently using is an Edge driver you’ve installed on your hub, then you will be able to select it again, but if it’s a DTH there’s no going back (plus you’ll be migrated anyway eventually).

To remove an Edge driver, find your hub in the mobile app. Once there, tap on the three dots in the upper right and select Driver. All drivers installed on your hub will be listed. Find the one you want to remove and tap on the blue delete button, but make sure no device is using the driver

The CLI is a new interface similar to the IDE, but it’s all command line based, not browser based like the IDE was. It’s yet to be seen what ST will replace the IDE with, or if we’re stuck with the CLI. Here are two useful discussions, especially the SmartThings API Browser tool:

SmartThings API Browser+ ... Now Available to All

NOTICE!!: SmartThings has now released its own equivalent of this app here, so you may prefer to use that instead. I have a browser-based web app that provides a point-and-click way to explore most of the SmartThings API. For the non-technical, this gives you access to an important SmartThings resource without having to learn tools like Postman, curl, or the CLI. You don’t even need a computer: a tablet or even smartphone can be used. For the more technically inclined, it provides much faster and more convenient access to those commonly-accessed CLI commands. Although I originally thought of it as a portal for the non-technical, I’ve actually found it quite useful to use during my own development activities. This is not intended as a replacement or ‘competitor’ to the CLI, mysmart…

CLI (just one of many)

Custom Capability and CLI Developer Preview

Overview At SmartThings we want to provide tooling to allow developers to get their device integrations working in the SmartThings app. These changes will allow an integrator to move from using custom commands and attributes to custom capabilities. DTH Migration For Custom Capabilities In order to follow along with the example set forth in this guide, you will want to have the CLI set up, so make sure that you take this step first. You can download the CLI here from the releases tab and read more about it in the README. It is also recommended that you familiarize yourself with the concepts: Custom Capabilities Capability Presentations Walkthrough We are going to walk through a simple example of updating our Device Type Handler (DTH) so that devices installed with the DTH will be …

SmartThingsCommunity/smartthings-cli/blob/main/packages/cli/README.md

[sscopp]

Thanks for this information. I was able to get this working and can see the real time logs from the devices.

[sscopp]

Yes, that’s the same image in my zcomb smoke co devices. I have 5 total all using the exact same driver. However, when the test button is pressed, on 2 the history lists smoke tested, then co tested, then smoke clear then co clear. On the other three it only displays the smoke tested and smoke clear. No listing for CO. Those three are newer than the other two. I called first alert and they said they should all function the same, however, this issue would be a smartthings issue.

[johnconstantelo]

@sscopp

Those three are newer than the other two. I called first alert and they said they should all function the same, however, this issue would be a smartthings issue.

Can you set yourself up with the SmartThings API Browser I linked above? Once you do that, check to see if there’s a difference between with them specifically with Mfg Code and Model.

Here’s how to find that. Go to the API browser tool, and click on Devices → Devices:

Next, find your device in the list and click on it:

Next, click on Details and then the table below will show up:

If there is a difference, ST may have to add that model to their driver. If there’s no difference, it could be the device did not get properly configured when it joined, which means removing it from ST and rejoining it back to your hub, OR selecting a new driver (we’ll cross that bridge if needed later).