CentraLite Water Leak Sensor 3315-G Issues V2 Hub

Around the holidays I took advantage of the sale on getvera.com and picked up a 3 pack of Centralite Water Leak Sensors. I have a few of the older Iris branded versions (model 3315-L) of these that have saved me extra aggravation in the past with basement water and leaking faucet issues.
I received the new sensors and immediately paired one w/ my V2 hub. Everything paired normally and I placed it where I needed it. After I couple of days I checked on it and in the new app it reported as offline. I started playing w/ it, swapping batteries, pushing the button while inserting a new battery and nothing would wake the device up or make the onboard LED light up.
Checking the device in the IDE I noticed that about an hour after I paired the device it went offline. It looks like it also checked for a firmware update.
After emailing back and forth with CentraLite support they had me try another Device Hander when pairing the 2nd & 3rd sensor.
They also bricked around an hour after joining.

Centralite deemed them to be hardware defective and issued me an RMA.
I received 3 new sensors with the same 3315-G model number (although the packaging says 3315-C). I paired the fist one successfully and it paired using the Device Handler they had me install previously. You guessed it, after an hour or so the sensor was offline/unresponsive. I started thinking that because they all fail within around an hour of being joined something must be trying to update these and they fail in the process.
In the IDE you can see a newer firmware version available

  • Current Version: 0x00000064
  • Target Version: 0x1F075310
    I have Zigbee OTA Enabled on my V2 hub.
    I emailed CentraLite w/ my hunch that these devices were trying to update w/ Zigbee OTA enabled and that they were being bricked. I asked them how they’d like to proceed.
    They had me delete the Device Handler previously used and disable Zigbee OTA. Then pair another sensor. I checked back in on it a couple hours later and it was still online so I tested it and it still worked. I have since paired the 3rd sensor and it is also working now.

CentraLite stated they’ve tested this with a V3 hub and have no problems. As I stated I’m on a V2 hub. For the time being I will be leaving Zigbee OTA disabled. CentraLite says there’s not much they can do about it.
My support ticket w/ SmartThings support was underwhelming as well, with lots of useless suggestions about how to enable/disable Zigbee OTA (gee thanks) and a link to a support article about firmware updates. I requested my ticket be escalated so hopefully CentraLite and SmartThings can take a look into why these 3315-G sensors brick on a V2 hub.

Just thought I throw this out there in case anyone has any ideas or suggestions.

1 Like

TLDR, but I think I got your message. Sounds like you have interference or range issues. What happens when you rejoin one of those next to the hub and leave it there for a few hours? How many Zigbee devices do you have? How many of those are Zigbee repeaters/routers?

I have 8 of those devices on my v2 hub.

You can’t rejoin the dead ones, or at least I’ve not been able to and CentraLite didn’t have any pointers on that either. I tried the reset process I found in the device instructions but that didn’t revive them either. I’ve tried all sorts of combos of pressing the button/inserting new batteries and get them to come alive again.
They were all paired in my 2nd floor office some ways away from the hub on the 1st floor but the first failed one I paired I did have next to the hub shortly after pairing, which is where it died.

Looking in the IDE I have 52 Zigbee devices:
17 SmartPower outlets
2 SmartPower Dimming Outlets
1 Arrival sensor
3 SmartSense Open/Closed Sensors
12 SmartSense Motion Sensors
2 SmartSense Multi Sensors
4 SmartSense Moisture Sensors
2 Homi Gas Detectors
3 King of Fans Zigbee Fan Controller
1 ZigBee Switch Power
1 Bosch Motion Detector
2 ZigBee RGB Bulbs
1 ZigBee RGBW Bulbs
1 SmartSense Button

The water leak sensors that I’ve never had problem with are CentraLite model 3315-S (current/target firmware 0x1F075310) and 3315-L (current/target firmware 0x1C005310.
The new ones I’ve been having problems with are 3315-G, Current Version: 0x00000064 | Target Version: 0x1F075310)

You definitely have enough repeaters/routers, but wow you have an issue I’ve not seen before. I’m mobile right now, but as soon as I get home I’ll look at what my firmware versions are. Stay tuned.

It turns out I have 11 water/leak sensors, but none of them are the 3315-G models. I literally have every derivative of 3315-something, but not G.

You got no LED acknowledgement when holding that reset button down and inserting the battery, or just inserting a battery? What happens when you hold that button down for about 30 seconds after reinserting, or just press and hold it for 30 seconds? Do you get the LED to light up if you just press the button once, 5, 7, or 10 times? I’ve done goofy button presses like that because some devices have undocumented button press sequences used for testing/resetting (like old PEQ devices).

No matter the combination of reset button/battery insertion I can’t get the LED to acknowledge. I’ve tried all the ways you suggested and then some. New batteries too, and I checked voltage on the batteries as well.

I’m waiting on an RMA for this dead sensor I have so anything anybody wants me to try let me know.

You can see in the device handler Groovy that the 3315-G is in there.
SmartThingsPublic/smartsense-moisture-sensor.groovy at master · SmartThingsCommunity/SmartThingsPublic · GitHub

Lol, I was just looking there too. Please update your post as you figure this one out because I’m curious how this turns out. I’m helping my parents with more “smart stuff” for their home, and water/leak sensors like these are on my list.

I just had the same experience. Bought three Centralite 3315 sensors from a different vendor (box says C model, barcode says G model). I immediately setup two of the devices and they paired fine using the default device handler and my V2 Hub, but then stopped responding at all after one hour. After reading this post I turned off Zigbee OTA updates and paired the third sensor using the default device handler. It has been running fine for several hours now.

Not a huge PITA if I have to leave OTA updates turned off, but I hate to have to do it for one device that can’t play nice. I’d imagine this is a pretty widespread issue given the number of V2 Hubs still in use.

I picked up a couple of the Lowe’s Iris branded versions of these sensors back when Lowe’s was trying to get their foot in the smart home game. They use a different device handler that has cloud execution instead of local like these newer ones, but they’ve been rock solid for many years. I really like the formfactor and price of these sensors, so hopefully they can get this issue resolved.

One little quirk I’ve noticed with the older sensors since switching to the new ST app: it displays the temperature in Fahrenheit values, but with a Celsius symbol. It doesn’t really affect anything (pretty sure my laundry room is not 68 C/154 F), so I haven’t tried to change to the newer DH on those, just something I found odd.

1 Like

Sorry I’m not the only one w/ the problem :frowning: :slight_smile:
Have you contacted Centralite support on the problem? I should be receiving my 4th RMA’d sensor from them today. They told me to take it up w/ SmartThing support but this time let me keep my latest sensor that was bricked rather than sending it back to them. So if anyone has any ideas on bringing it back from the dead I’m all ears.

SmartThings support wanted me to turn Zigbee OTA back on, pair a new sensor, and then if it bricks a sensor (and probably the other ones running fine now) send them logs from my Hub…wtf. I told them to buy their own sensors and do their own testing. Some support.

I have a mix of SmartThings branded, older Iris, and these Centralite sensor and all are using the DTH “SmartSense Moisture Sensor” and showing Local execution in the IDE.

FYI @tpmanley and @BroderickCarlin

I received this from support yesterday:

“Appreciate your time and patience.
Your ticket actually gave us a lot of information on this issue and we really appreciate your efforts that helped us figure out the problem with the Centralite sensor.
Our developers know about this issue now and we are also tracking users with the same issues so that we can resolve this.
I will also go ahead and submit this ticket as a feedback to fix this issue.
I hope that the sensors are working fine right now without the OTA updates, we’ll let you know when it’s safe to turn on the updates.
Please feel free to contact us if you have any questions and concerns.
SmartThings Support Team”

1 Like

I have 2 that I just purchased that bricked on my V3 hub. Stopped responding after 20 mins. Where did you find the model number?

Mine had the 3315-G model number on the inner white box, on the same sticker as the serial number. Very small print on the label.
It is also in the IDE if you view the device under My Devices
Mine look like this


  • endpointId: 01
  • manufacturer: CentraLite
  • model: 3315-G
  • zigbeeNodeType: SLEEPY_END_DEVICE

Centralite told me they tested w/ a V3 Hub with no problems so be sure to let them know

i contacted centralite. i mentioned the OTA update as a possibility. They said thanks for the info- and no replacement as its not their fault. Great customer service :frowning:

Wow, that’s absolute BS. I’d stay on them about it. My contact specifically said they had tested w/ a V3 hub.

It took some time, partly because of delays on my end due to a crazy work schedule, but my bricked sensors are being replaced, including paid shipping, by Centralite. When I submitted the service ticket I explained that it happened when they tried to update firmware, and a third sensor worked fine with the updates turned off. They didn’t even ask any further questions.

I’m having a similar experience with 3 sensors purchased from Amazon. My older, Iris, sensors are all fine but the 3 new ones are all bricked. I’ll return them and try to get replacements. It sounds like I will need to disable OTA updates. How do I disable updates?

Thank you all for taking the time to report these troubles to us. Please see the following post on the Ezlo Community for an update on how Centralite and SmartThings have worked together to address this situation:


“An upcoming SmartThings Hub firmware update (v36) will begin excluding newer Centralite devices from receiving the OTA update. By excluding the Centralite devices from further updates, devices joined to the hubs after the update will no longer experience the operational issues.”

How can we expect already joined Centralite sensors to react if after receiving the v36 Hub firmware we turn on Zigbee OTA updates? I don’t want to brick my sensors that I joined before Hub firmware v36 after turning off Zigbee OTA update. I currently have version 000.036.00005 on my V2 Hub.
Does the above quoted statement from the Ezlo Community mean we should delete/unjoin existing Centralite devices and rejoin after our hubs have v36+ firmware?

I want crystal clear guidance as it’s been some time since I received the RMA replacements for my sensors that were bricked. If my sensors were to be bricked again I’m not sure I’d get manufacture replacements easily if at all this long after my purchase.

They will not receive any OTA updates, as the Hub Firmware now blocks them from requesting the incorrect versions regardless of when they were joined. Hope this helps clear up any remaining confusion.