Issues with Smoke detector devices

Same issue here I think @nayelyz

  • 1 Z-wave device out of maybe 10 that keeps constantly going online and offline. It IS the only battery powered z-wave, the rest are in wall plugs, etc. But plenty of zigbee battery powered things still working fine.

  • Happening since 1st or 2nd week in October.

  • First noticed with my older First Alert Smoke detector (ZCOMBO) (that was working for years) but the problem CONTINUED when I replaced it with the latest model. (SMCO410)

  • Its sitting in my garage maybe ~50 feet from hub in the house (3rd Generation (GP-U999SJVLGDA), firmware 0.58.10)

  • A TEST of the alarm makes it through to smartthings every single time

  • Repeated z-wave repairs do not help.

  • If I remove from the network and add it back near the hub IT STAYS ONLINE all night with no more bounces ← Scooby-Doo clue? But the second I move back to garage it starts flaking out, even with another zwave repair and pressing TEST button to force it to talk to the hub. (Test always fixes it when disconnected but goes out again within an hour or so).

  • The closest device in route is an IN WALL zwave switch within 10 ft in the garage (GE/Jasco 14292 in-wall switch in garage (SmartThings shows mfr/prod/model 0063-4952-3037))

  • In the house I have 2 other similar z-wave in wall switches AND two Aeotec Range Extenders (ZW117-A01) so i dont see how there could be a signal issue. Unless tooo many repeaters causes issues??

  • Switched hub to beta, rebooted, didnt help.

  • I had ALREADY been signed up for beta “Z-Wave Smoke Alarm“ drivers for a while when it started happening.

  • Also annoyed because there doesnt appear to be an easy way to find the exact Z-WAVE route! I tried switching to the “Z-wave explorer” driver but it doesnt seem to be working. And no hint of the route info up in the advanced web site. WHY? Are you going to make me switch over to Home Assistant which has a nice route interface? I’ll dooo iiit I swear.

Based on days of troubleshooting with ChatGPT, it suggests making sure “Device Health thresholds/ping strategy for FLiRS devices didn’t change in the most recent firmware release”. That First Alert device DOES have a really long time between calling home - I think its over an hour.

I did also start case #309572418 and dump the hub logs and give permission.

Thanks!!

This description definitely helps.

The engineering team needs to check which route the device is using and also check the hub logs of the offline events to see why it’s happening.

Is this a case with Customer Support? Have they provided any info about your report? We’re not the same team so, I just want to avoid duplicating efforts on this.
I’m guessing they asked you for the following info, can you confirm, please?

  1. To dump the hub logs after an offline event
  2. Provide the date and time on when this happened, right
  3. Provide the name of those devices to look for them in your account.

Yes with regular support. I preemptively did the dump and gave permission but they dont seem to care about it because my new First Alert model is not yet ‘supported’. Even though the issue started early October with the last model from I think 2018 (ZCOMBO). Since it happens ever 1-2 hours offline and online constantly I didnt provide an exact time. Let me know what else you need on my end. Thanks!

Hi, @VorlonCD

Ok, since we can’t see the details of that ticket to check its status or see any past communication, then please share the following information with us:

  • So, you’re currently using the model “SMCO410”, the one of “ZCOMBO” is no longer active, right?
  • Can you provide the label assigned to the SMCO410 device, please?
  • If the device has remained offline, please get the device near the hub to make it online again.
    * When this happens, please submit the hub logs and take note of the date and time, and share them with me, including your timezone. For example, Oct 29th, 11:00 hrs CST.
Instructions to submit the hub logs
  1. In the Advanced Users app, enter the “Hubs” section
  2. Enter the corresponding Hub and click on “Dump Hub logs”
  3. Confirm the process by clicking on “Dump Hub logs” again in the pop-up.
  4. You’ll get a green box at the top confirming the Hub logs were requested.
  • Then, take it to its usual place, when it becomes offline, take note of the date and time as well and submit the hub logs again.

Also, provide support access to your account:

  1. Confirm the email account registered in the forum is the same one you use for SmartThings. If not, please share it with me over DM
  2. Enable support access to your account:
  1. Go to the SmartThings Web (my.smartthings.com)
  2. Log in to your Samsung Account
  3. Select Menu (⋮) and choose Settings
  4. Toggle on Account Data Access
  5. Select the time period and confirm - In this step, please select “Until turned off”, once the team finishes, we’ll let you know so you can disable it again.

See more information about this access here: https://support.smartthings.com/hc/en-us/articles/36170233944852-Enabling-Account-Data-Access-for-Support

Yes, SMC0410 label “First Alert garage“.

It happens ALL day long every few hours offline/online so I’m not going to provide an exact time.

I already gave access to the hub logs last week. It should have been the day after I brought it near the hub, disconnected and reconnected to z-wave network and it stayed connected all night. Then as soon as I brought it back to the garage its online/offline all day and night. But cant be a signal issue since the TEST button on the smoke detector always immediately notifies the hub/app, and always brings it back online if offline for that time period.

Same email I used for forum registration.

Thanks.

Ok, thanks for the information.
I created a report for the engineering team. Once I get their feedback, I’ll let you know.

The custom Snapshot first alert 2025 drivers do the same thing. Offline/online all day.