Issues with zigbee smoke detector mc

Devices & Integrations Community Created Device Types
1

Thanks for updating the driver. I currently have version 2024-08-19T20:54:02.425672381. How would one update it please? I tried to uninstall it first in your driver channel but it couldn’t as the driver is in use.
Thanks again.

2

When you tried to uninstall it that should have forced it to update. Check what version you currently have.

3

I have another device that is using the same driver - should I remove that device as well before re-adding both? Thanks

4

If the existing device is working properly there is no need to remove it.

5

I tried adding the new device and its coming back as a Zigbee Thing. The driver listed in ST Advanced is still the older version. So how to proceed please?

6

The easiest way is to use the ST CLI to “install” the driver again which will update to the latest driver. Download the appropriate binary for Linux/Windows/macOS and use the command “smartthings edge:drivers:install”.

7

Go to your hub in the app. Open the hub tile, click 3 dots in upper right, select drivers, find you driver, click on it to open, select delete at the bottom. Delete will fail because you have another device using it. But this process will force the driver to update to the newest version. The new version won’t show at that point. But go to your existing device using this driver and check the version number. It should show the updated version. No need for CLI.

1 Like
8

Hi @Somebody

Sorry, sorry, I forgot publish new version in the public channel. Iwas testing before publish it and forgot. :man_facepalming:

Published now

9

Thanks all - now added.

Now another issue- it’s not come through to SHM even though I’ve selected all smoke sensors; only the old sensor is visible:

436×640 19 KB

How to fix please? TIA

10

I thought if it was a gas detector you wanted a gas detector profile.
Only smoke sensors can be used in STHM.
Do you want me to put it as a smoke sensor?

11

Please remember that the “request an edge driver” threads should only have two posts for each device. One with the request and then one linking to an appropriate edge driver. Otherwise, those threads become unmanageable…

Once you get an edge driver, if you run into any problems with it or questions about it, either post those in the author’s thread for that specific edge driver, or start a new issues topic for it.

I have moved all the discussion about Mariano’s smoke sensor edge driver to a new issues thread.

Thank you.

3 Likes
12

Yes please, so it’s consistent with the other device. TIA

@JDRoberts: Noted!

1 Like
13

Since it is actually a gas sensor and there may be other users who want to see it as what it is instead of a smoke detector, I have added a setting preference to change to the Smoke detector profile.

When you change a smoke detector profile first time could you need delete app cache

By default they have the gas detector profile so that other users with gas detectors on them do not notice any problems.

preferences:
  - name: "changeProfile"
    title: "Set Profile Type"
    description: "Select Profile for Gas Detector or Smoke Detector (Default = Gas Detector)"
    required: false
    preferenceType: enumeration
    definition:
      options:
        "Gas" : "Gas Detector"
        "Smoke": "Smoke Detector"
      default: "Gas"

Install this driver version and it will works

───────────────────────────────────────────────────
 Name         Zigbee Smoke/CO Detector Mc
 Version      2024-10-10T20:51:49.808255135        
───────────────────────────────────────────────────
1 Like
14

I appreciate your work on this, MC.

Just to report back, these are the devices I have:

The Heiman branded one on the right is over 5 years old, which I assume is why it chirps occasionally to inform that it reached end of life (apparently they should be replaced after 5 years)? I replaced it with another ‘Heiman’ found on Aliexpress but it came unbranded.

I managed to change the profile of the new device to Smoke Detector but it does not register under SHM nor does it report smoke detected nor cleared when the test button is pressed and released under the Smoke profile. When on the Gas Detector profile it reports detection and clearance as expected.

Interestingly, there is no option to change profile (i.e. no Settings option) on the old Heiman although they are both using the same driver.

Finally, under information the old device is on firmware version 012 whereas the new device is on version 045.

MC, is there something else missing that needs tweaking for it to register under SHM?

Thanks

15

Your new device may look the same on the outside and is actually very different on the inside.

Your real Heiman was probably on the stock driver and there was no Gas detector profile back then, there were only smoke profiles in the driver.

It’s rather smartthing’s fault that it doesn’t support Gas detectors, and I think CO, in its STHM, they should update it now that it also has Gas sensors with gas profile in its stock driver.

Install this version of the driver and uninstall and reinstall the device, the preferences in the profile should appear after clearing the cache of the android app and if it uses iO’s I don’t know because it doesn’t use iO’s.

───────────────────────────────────────────────────
 Name         Zigbee Smoke/CO Detector Mc
 Version      2024-10-11T12:01:21.665766654
───────────────────────────────────────────────────
1 Like
16

Good job, MC!

There was no need to reinstall the new device. I deleted the old driver in the hub, then changed the profile to Smoke Detector, and it was able to be added to SHM.

I will now dispose of the old Heiman as the chirping is driving SWMBO mad.

Thanks again

1 Like