Bosch Motion Sensor (ISW-ZPR1-WP13) : Smartthings v2 hub

Now I believe my sensor is defective. I think the Zigbee module of the device is going bad, in my case, anyway,. I will still try to initiate pairing, although maybe my device is a red herring in this situation, and possibly the reason that battery wasn’t reporting.

I will leave this to @OCSMITH and @Carlos_Jato to investigate, but if I have any success, I will report it.

1 Like

James my sensors will not pair with the Smartthings Hub but will pair with my Hubitat Hub C7 with no additional drivers … pairs within seconds. I don’t think your sensor is bad.

I can’t say for sure, yet I can’t get the sensor to go into the pairing LED flashing sequence as Carlos describes:

Previously, I could get to that point, but now, it just acts as though it’s already paired or, the Zigbee module isn’t allowing to be put into pairing mode.

I don’t wish to potentially conflate two issues that aren’t necessarily related, but I’m not one to just give up easily, so I’ll give it several more goes.

Notice #10 this how I got the ISW-ZPR1-WP13 to pair originally:

I added the device handler in the Smartthings IDE and just changed the type to “SmartSense Motion Sensor” Then it paired just fine… Without changing type it would not pair

Hi @OCSMITH

Here it should also pair with Zigbee Thing, it pairs with any zigbee device and then you can switch to another compatible driver.

Is the device fully removed from hubitat?

Yes, I have fully removed the sensor from Hubitat… but also tried with brand new sensor out of box I have for back up…is there a “SmartSense Motion Sensor” edge driver? These are the only ZigBee devices I have never had problems with not pairing at all…I have had some show up as just a thing and had to go into IDE to set up type…I use these sensors to cut lights on and off… also to tell me when someone is in a room…I am bedridden…

These motion sensors would never pair before unless I used a device handler then change type in IDE before pairing… That type was “SmartSense Motion Sensor”

If you remove the edge drivers Zigbee Motion Sensor Mc and Zigbee Thing Mc from your hub, then device should pair as a thing DTH and then you can switch to the smartSense motion sensor stock DTH.

If this doesn’t work either, I don’t know what could be happening, but it’s not normal, sorry

Hello, @Carlos_Jato, @field210, @OCSMITH and everyone else

We are investigating this issue. The Engineering team asked if you were able to share Hub logs so we can take a look at that information as well as part of the investigation. It is important that you reproduce the error before sending those logs since they only have a 12 hr lifetime. It would also help if you can share with us the time when you reproduce the error so we can narrow down the logs we receive.

If you don’t know how to send those logs the procedure is the following:

  1. In the IDE, enter “my hubs”
  2. Enter the corresponding Hub and go to “view utilities”
  3. Click on “send” below "send hub logs

And please let us know which Samsung Account you’re using and if you have more than one Hub, the name of the one where the device is paired. This last piece of information can be sent by DM to me directly, so you don’t have to share it publicly.

Thanks in advance

Sent…thank for the help… BTW my hub is a version 3

1 Like

Experiencing the same issue with my Bosch Motion Sensor (ISW-ZPR1-WP13). Have followed all steps as outlined in the thread, and similarly, to no avail. Happy to help test/validate whatever is required to troubleshoot further.

I’m using a SmartThings v3 Hub and previously leveraged the ‘tomasaxerot : Bosch Motion Detector’ device handler.

I’ve removed the device from my SmartThings UI (the device handler is still in the IDE platform) and installed the edge driver as suggested. I’ve used my previous motion sensor and a brand new spare one that I had. Both did not connect (by searching for a device, or adding the Bosch motion sensor).

Basic question here I think–How do you install an Edge driver? I was familiar on how to install a device handler using the ST Groover IDE. Where do I go to do that? A website?

Thank You very much for that good work with the EDGE drivers @Mariano_Colmenarejo :wave: :wave:

Have been using your EDGE driver for Bosch Motion Sensor (ISW-ZPR1-WP13), it works very well except battery status.

Using This Driver.

To install an edge driver, you have to access an URL:
Example, to install drivers from https://github.com/Mariano-Github/Edge-Drivers-Beta

Click on: https://api.smartthings.com/invitation-web/accept?id=6b68563b-1905-4654-8d2b-e677a2997424
Remember to delete the Old Legacy Device Handler.

Hi @robert.haugen
To analyze why the battery does not work, it would be necessary for you to send me the logs with the CLI of the sensor pairing, to see how it is configured and to see what data it sends

Will Do.

Checket again. 1 of 3 sensors are showing battery status.
They might have different FW.
I will send you the logs when I am back home.

1 Like

Hi @robert.haugen what version of hub do you have the sensors connected to?

@robert.haugen Can you confirm, that you are able to get these devices to join using the Community Driver?

Bosch Motion Sensor (ISW-ZPR1-WP13) is not working at all with the “SmartThings Drivers (Beta)”" drivers. No matching fingerprint. Working with “Mariano Shared Beta Driver”. 2 of 3 devices have problem with battery status. Will do further investigation. Using Hub V2.

Using Hub V2

Bosch Motion Sensor Kjøkken is working
Bosch Motion Sensor Bod is not working with battery sensor


smartthings edge:drivers:logcat 00425c55-0932-416f-a1ba-78fae98ab614  --hub-address 10.2.5.101 --log-level info
connecting... connected
2022-11-11T22:22:20.105157711+00:00 INFO Zigbee Motion Sensor Mc  <ZigbeeDevice: 6d3998e5-fbe6-43ea-9589-2bd2679ee05a [0x846A] (Bosch Motion Sensor Bod)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x846A, src_endpoint: 0x05, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: TemperatureMeasurement >, lqi: 0xFF, rssi: -58, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x94, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Int16, MeasuredValue: 2259 > > > >
2022-11-11T22:22:20.120386920+00:00 INFO Zigbee Motion Sensor Mc  Executing ZclClusterAttributeValueHandler: cluster: TemperatureMeasurement, attribute: MeasuredValue
2022-11-11T22:22:20.125076545+00:00 INFO Zigbee Motion Sensor Mc  <ZigbeeDevice: 6d3998e5-fbe6-43ea-9589-2bd2679ee05a [0x846A] (Bosch Motion Sensor Bod)> emitting event: {"attribute_id":"signalMetrics","capability_id":"legendabsolute60149.signalMetrics","component_id":"main","state":{"value":"<em table style='font-size:70%';'font-weight: bold'</em><b>GMT: </b>2022/11/11 Time: 22:22<BR><b>DNI: </b>0x846A  <b> LQI: </b>255  <b>RSSI: </b>-58dbm</em><BR>"},"visibility":{"displayed":false}}
2022-11-11T22:22:20.135984420+00:00 INFO Zigbee Motion Sensor Mc  <ZigbeeDevice: 6d3998e5-fbe6-43ea-9589-2bd2679ee05a [0x846A] (Bosch Motion Sensor Bod)> emitting event: {"attribute_id":"temperature","capability_id":"temperatureMeasurement","component_id":"main","state":{"unit":"C","value":22.59}}
2022-11-11T22:22:23.596232752+00:00 INFO Zigbee Motion Sensor Mc  <ZigbeeDevice: 53bbe3f2-479d-4b75-8062-a8b1fb15077c [0xD0A0] (Bosch Motion Sensor Hall)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xD0A0, src_endpoint: 0x05, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: IASZone >, lqi: 0xFF, rssi: -43, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x81, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0002, DataType: Bitmap16, ZoneStatus: 0x0020 > > > >
2022-11-11T22:22:23.699867460+00:00 INFO Zigbee Motion Sensor Mc  Executing ZclClusterAttributeValueHandler: cluster: IASZone, attribute: ZoneStatus
2022-11-11T22:22:23.703953794+00:00 INFO Zigbee Motion Sensor Mc  <ZigbeeDevice: 53bbe3f2-479d-4b75-8062-a8b1fb15077c [0xD0A0] (Bosch Motion Sensor Hall)> emitting event: {"attribute_id":"motion","capability_id":"motionSensor","component_id":"main","state":{"value":"inactive"}}
2022-11-11T22:22:24.294749127+00:00 INFO Zigbee Motion Sensor Mc  <ZigbeeDevice: 53bbe3f2-479d-4b75-8062-a8b1fb15077c [0xD0A0] (Bosch Motion Sensor Hall)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xD0A0, src_endpoint: 0x05, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: TemperatureMeasurement >, lqi: 0xFF, rssi: -43, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x82, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Int16, MeasuredValue: 2414 > > > >
2022-11-11T22:22:24.309565752+00:00 INFO Zigbee Motion Sensor Mc  Executing ZclClusterAttributeValueHandler: cluster: TemperatureMeasurement, attribute: MeasuredValue
2022-11-11T22:22:24.388614544+00:00 INFO Zigbee Motion Sensor Mc  <ZigbeeDevice: 53bbe3f2-479d-4b75-8062-a8b1fb15077c [0xD0A0] (Bosch Motion Sensor Hall)> emitting event: {"attribute_id":"signalMetrics","capability_id":"legendabsolute60149.signalMetrics","component_id":"main","state":{"value":"<em table style='font-size:70%';'font-weight: bold'</em><b>GMT: </b>2022/11/11 Time: 22:22<BR><b>DNI: </b>0xD0A0  <b> LQI: </b>255  <b>RSSI: </b>-43dbm</em><BR>"},"visibility":{"displayed":false}}
2022-11-11T22:22:24.399098294+00:00 INFO Zigbee Motion Sensor Mc  <ZigbeeDevice: 53bbe3f2-479d-4b75-8062-a8b1fb15077c [0xD0A0] (Bosch Motion Sensor Hall)> emitting event: {"attribute_id":"temperature","capability_id":"temperatureMeasurement","component_id":"main","state":{"unit":"C","value":24.14}}
2022-11-11T22:22:40.852813581+00:00 INFO Zigbee Motion Sensor Mc  <ZigbeeDevice: 6d3998e5-fbe6-43ea-9589-2bd2679ee05a [0x846A] (Bosch Motion Sensor Bod)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x846A, src_endpoint: 0x05, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: IASZone >, lqi: 0xFF, rssi: -58, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x95, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0002, DataType: Bitmap16, ZoneStatus: 0x0020 > > > >
2022-11-11T22:22:40.900445665+00:00 INFO Zigbee Motion Sensor Mc  Executing ZclClusterAttributeValueHandler: cluster: IASZone, attribute: ZoneStatus
2022-11-11T22:22:40.904084081+00:00 INFO Zigbee Motion Sensor Mc  <ZigbeeDevice: 6d3998e5-fbe6-43ea-9589-2bd2679ee05a [0x846A] (Bosch Motion Sensor Bod)> emitting event: {"attribute_id":"motion","capability_id":"motionSensor","component_id":"main","state":{"value":"inactive"}}
2022-11-11T22:23:22.884950571+00:00 INFO Zigbee Motion Sensor Mc  <ZigbeeDevice: 57d5e204-753b-4467-91cc-0f0bec3a10d0 [0x900E] (Garage)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x900E, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: IASZone >, lqi: 0xFF, rssi: -61, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x40, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0002, DataType: Bitmap16, ZoneStatus: 0x0020 > > > >
2022-11-11T22:23:22.899320405+00:00 INFO Zigbee Motion Sensor Mc  Executing ZclClusterAttributeValueHandler: cluster: IASZone, attribute: ZoneStatus
2022-11-11T22:23:22.903006821+00:00 INFO Zigbee Motion Sensor Mc  <ZigbeeDevice: 57d5e204-753b-4467-91cc-0f0bec3a10d0 [0x900E] (Garage)> emitting event: {"attribute_id":"motion","capability_id":"motionSensor","component_id":"main","state":{"value":"inactive"}}
2022-11-11T22:23:42.664273900+00:00 INFO Zigbee Motion Sensor Mc  <ZigbeeDevice: 6d3998e5-fbe6-43ea-9589-2bd2679ee05a [0x846A] (Bosch Motion Sensor Bod)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x846A, src_endpoint: 0x05, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: PollControl >, lqi: 0xFF, rssi: -58, body_length: 0x0003, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x19, seqno: 0x96, ZCLCommandId: 0x00 >, < CheckIn ||  > > >
2022-11-11T22:24:33.314798554+00:00 INFO Zigbee Motion Sensor Mc  <ZigbeeDevice: 53bbe3f2-479d-4b75-8062-a8b1fb15077c [0xD0A0] (Bosch Motion Sensor Hall)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xD0A0, src_endpoint: 0x05, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: IASZone >, lqi: 0xFF, rssi: -45, body_length: 0x0009, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x19, seqno: 0x84, ZCLCommandId: 0x00 >, < ZoneStatusChangeNotification || zone_status: 0x0021, extended_status: 0x00, zone_id: 0x00, delay: 0x0000 > > >
2022-11-11T22:24:33.387433971+00:00 INFO Zigbee Motion Sensor Mc  Executing ZclClusterCommandHandler: cluster: IASZone, command: ZoneEnrollResponse
2022-11-11T22:24:33.391149013+00:00 INFO Zigbee Motion Sensor Mc  <ZigbeeDevice: 53bbe3f2-479d-4b75-8062-a8b1fb15077c [0xD0A0] (Bosch Motion Sensor Hall)> emitting event: {"attribute_id":"motion","capability_id":"motionSensor","component_id":"main","state":{"value":"active"}}
2022-11-11T22:24:37.605574970+00:00 INFO Zigbee Motion Sensor Mc  <ZigbeeDevice: 53bbe3f2-479d-4b75-8062-a8b1fb15077c [0xD0A0] (Bosch Motion Sensor Hall)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xD0A0, src_endpoint: 0x05, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: IASZone >, lqi: 0xFF, rssi: -42, body_length: 0x0009, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x19, seqno: 0x85, ZCLCommandId: 0x00 >, < ZoneStatusChangeNotification || zone_status: 0x0020, extended_status: 0x00, zone_id: 0x00, delay: 0x0000 > > >
2022-11-11T22:24:37.618962595+00:00 INFO Zigbee Motion Sensor Mc  Executing ZclClusterCommandHandler: cluster: IASZone, command: ZoneEnrollResponse
2022-11-11T22:24:37.622625470+00:00 INFO Zigbee Motion Sensor Mc  <ZigbeeDevice: 53bbe3f2-479d-4b75-8062-a8b1fb15077c [0xD0A0] (Bosch Motion Sensor Hall)> emitting event: {"attribute_id":"motion","capability_id":"motionSensor","component_id":"main","state":{"value":"inactive"}}
2022-11-11T22:24:51.745221467+00:00 INFO Zigbee Motion Sensor Mc  <ZigbeeDevice: de255418-698c-45b4-a255-a416feb2f96a [0xBC89] (Bosch Motion Sensor Kjøkken)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xBC89, src_endpoint: 0x05, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: IASZone >, lqi: 0xFF, rssi: -55, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0xB9, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0002, DataType: Bitmap16, ZoneStatus: 0x0020 > > > >
2022-11-11T22:24:51.760380008+00:00 INFO Zigbee Motion Sensor Mc  Executing ZclClusterAttributeValueHandler: cluster: IASZone, attribute: ZoneStatus
2022-11-11T22:24:51.788081925+00:00 INFO Zigbee Motion Sensor Mc  <ZigbeeDevice: de255418-698c-45b4-a255-a416feb2f96a [0xBC89] (Bosch Motion Sensor Kjøkken)> emitting event: {"attribute_id":"motion","capability_id":"motionSensor","component_id":"main","state":{"value":"inactive"}}