HS-MS100+ Showing up as "Ring Alarm Retrofit"

🛎️ Get Help
1

When adding a HS HS-MS100+ via z-wave, it should show up as a "Zooz Motion Sensor ZSE18", which the second one I added before did without a problem, it shows up as a "Ring Alarm Retrofit" with all the sub-devices (contact 1 through contact 8).
Normally, I would think, not a big deal, simply change the device type to the Zooz, and it should be fine. Nope :slight_smile: It does not remove the sub-devices.

Not a big deal, as the sensor works just like it should, but there seems to be no way to remove the sub-device leftovers from the incorrect Ring Alarm detection...

Thoughts on how to clean that up?

2

If you are on 2.2.4, you can temporarily change to Device driver type and there is an option to Delete Child Devices. Then switch back to correct one.

3

If you switch to "Device" please click on get info and post the fingerprint from the log so we can fix this

5

fingerprint mfr:"000C", prod:"0201", deviceId:"0009", inClusters:"0x5E,0x85,0x59,0x55,0x86,0x72,0x5A,0x73,0x80,0x9F,0x71,0x30,0x84,0x70,0x6C,0x7A"

After resetting the device several times and adding/removing it in HE, it was added correctly. Not sure if it is a defective sensor or a bug in the detection routine, so don't spend too much time on investigating this!

Thanks for the quick help!

1 Like
6

I'm seeing a similar issue with my Homeseer HS-WS100.
I just received my C7 Hubitat hub today, and this is the first device I've paired...
It's appearing as a "Ring Alarm Retrofit"

  • zwaveSecurePairingComplete: true
  • S2: 3
  • deviceId: 12339
  • deviceType: 17479
  • manufacturer: 12
  • inClusters: 0x5E,0x55,0x9F
  • secureInClusters: 0x86,0x25,0x85,0x59,0x72,0x5A,0x73,0x70,0x2C,0x2B,0x5B,0x6C,0x7A
  • firmwareVersion: 50.03
  • protocolVersion: 6.01
  • hardwareVersion: 255