elgwhoppo Posted October 21, 2017 Posted October 21, 2017 Hey all, I have a few of the Z-Wave Plus PIR Multi Sensor, Temperature - Humidity - Light sensors P/N 15902 and am using them with some smart bulbs and my ISY994i ZW. I'm noticing this weird thing however, where one of the PIR sensors isn't reporting its motion sensor. I experienced this with the first one, and just ended up fiddling with it until it showed up. https://downloads.monoprice.com/files/manuals/15902_Manual_160722.pdf I've tried: removing and re-adding the devices and pairing them performing the pairing by using the pinhole on the bottom as mentioned in the manual Wondering how in the world I got the first motion sensor in there? I feel like it happened on accident almost, it just showed up at one point. Thanks for the help in advance!
Chris Jahn Posted October 22, 2017 Posted October 22, 2017 Hi elgwhoppo, Try triggering the motion sensor and see if a node is created for it. You can also open the event viewer to level 3, this should at least show whether the ISY see's the motion sensor being triggered or not.
elgwhoppo Posted October 22, 2017 Author Posted October 22, 2017 Hi elgwhoppo, Try triggering the motion sensor and see if a node is created for it. You can also open the event viewer to level 3, this should at least show whether the ISY see's the motion sensor being triggered or not. So I'm triggering the motion, and: A) the LED isn't lighting on the device B ) Nothing is reporting under level 3 event logs. C) I replaced the batteries with new known good Also I see the working motion detector reporting device 155 just fine. On this sensor the addressing is as follows: ZWave###_1 - Battery Sensory Generic ZWave###_118 - Temperature Humidity Luminosity ZWave###_155 - Motion Sensor ZWave###_157 - Tamper Alarm Sun 10/22/2017 03:17:42 PM : [D2D EVENT ] Event [ZW003_155] [sT] [0] uom=78 prec=0 Sun 10/22/2017 03:17:42 PM : [ ZW003_155] ST 0 (uom=78 prec=0) Sun 10/22/2017 03:17:42 PM : [D2D-CMP 0007] STS [ZW003_155] ST op=1 Event(val=0 uom=78 prec=0) is Condition(val=100 uom=78 prec=-1) --> false Sun 10/22/2017 03:17:42 PM : [D2D-CMP 0006] STS [ZW003_155] ST op=1 Event(val=0 uom=78 prec=0) is Condition(val=0 uom=78 prec=-1) --> true Sun 10/22/2017 03:17:42 PM : [D2D-CMP 0004] STS [ZW003_155] ST op=1 Event(val=0 uom=78 prec=0) is Condition(val=100 uom=78 prec=-1) --> false Sun 10/22/2017 03:17:42 PM : [D2D EVENT ] Event [ZW003_155] [DOF] [0] uom=78 prec=0 Sun 10/22/2017 03:17:42 PM : [ ZW003_155] DOF 0 (uom=78 prec=0) Thinking I have a bad one here and will need a replacement. Thanks for the tip on advanced logging.
elgwhoppo Posted November 15, 2017 Author Posted November 15, 2017 I found out the problem. I completely disassociated it and then re-associated it making sure to wait for the motion to trigger as a part of the pairing process. Works fine after that.
Guest How do you disassociate Posted February 25, 2018 Posted February 25, 2018 Can you detail how exactly you "disassociate" a zwave device. I only see disable or delete
danbutter Posted February 25, 2018 Posted February 25, 2018 8 hours ago, Guest How do you disassociate said: Can you detail how exactly you "disassociate" a zwave device. I only see disable or delete I believe the term here is exclude.
photogeek54 Posted March 14, 2018 Posted March 14, 2018 I'm having pretty much the exact same problems as elgwhoppo mentioned initially. PIR motion sensor at _155 not being included, the temperature and luminence sensors operating correctly. I've tried excluding and re-including the device too. I had an earlier sensor which failed after a year or so and this problem started when I tried to included a replacement. Thinking the replacement was bad I ordered another new one but see exactly the same problems so I don't think its the device. Also, I never see the LED flash to indicate terperature or that it detects motion. I have tried configuring parameters but get a failed message. I have heard there is some kind of issue with recent ISY firmware with multi sensor devices like this one? I've seen this problem with 4.5.4 and 4.6.2.
Michel Kohanim Posted March 15, 2018 Posted March 15, 2018 Hi photogeek54, Can you please open the Event Viewer, change the Level to 3, right mouse click on the node / Z-Wave / Show information / All and paste it here? With kind regards, Michel
photogeek54 Posted March 16, 2018 Posted March 16, 2018 Fri 03/16/2018 01:27:33 PM : [ZWAVE-TX ] [01030015E9] Fri 03/16/2018 01:27:33 PM : [ZWAVE-RX ] ACK Fri 03/16/2018 01:27:33 PM : [ZWAVE-RX ] [011001155A2D5761]... Fri 03/16/2018 01:27:33 PM : [ZWAVE-TX ] ACK Fri 03/16/2018 01:27:33 PM : [ZWAVE-FW ] Version 4.55 Static Controller Library Fri 03/16/2018 01:27:33 PM : [UZW-CMD 17 ] Get Dongle Version Fri 03/16/2018 01:29:17 PM : [UZW-CMD 12 ] Get Node Info : ZW034_118 Fri 03/16/2018 01:29:29 PM : [ZW-SHOW ] ---------------------------------------------- Fri 03/16/2018 01:29:29 PM : [ZW-SHOW ] ZW034_1 uid=34 type=4.7.1 mid=265 tid=8225 pid=8449 model=0 Fri 03/16/2018 01:29:29 PM : [ZW-SHOW ] - x5E V0 ZWAVEPLUS_INFO Fri 03/16/2018 01:29:29 PM : [ZW-SHOW ] - x86 V0 VERSION Fri 03/16/2018 01:29:29 PM : [ZW-SHOW ] - x72 V2 MANUFACTURER_SPECIFIC Fri 03/16/2018 01:29:29 PM : [ZW-SHOW ] - x5A V0 DEVICE_RESET_LOCALLY Fri 03/16/2018 01:29:29 PM : [ZW-SHOW ] - x85 V2 ASSOCIATION Fri 03/16/2018 01:29:29 PM : [ZW-SHOW ] - x59 V0 ASSOCIATION_GRP_INFO Fri 03/16/2018 01:29:29 PM : [ZW-SHOW ] - x73 V0 POWERLEVEL Fri 03/16/2018 01:29:29 PM : [ZW-SHOW ] - x80 V0 BATTERY Fri 03/16/2018 01:29:29 PM : [ZW-SHOW ] - x71 V4 NOTIFICATION Fri 03/16/2018 01:29:29 PM : [ZW-SHOW ] - x31 V7 SENSOR_MULTILEVEL Fri 03/16/2018 01:29:29 PM : [ZW-SHOW ] - x70 V1 CONFIGURATION Fri 03/16/2018 01:29:29 PM : [ZW-SHOW ] - x84 V2 WAKE_UP Fri 03/16/2018 01:29:29 PM : [ZW-SHOW ] - x7A V2 FIRMWARE_UPDATE_MD Fri 03/16/2018 01:29:29 PM : [ZW-SHOW ] - x98 V0 SECURITY Fri 03/16/2018 01:29:29 PM : [ZW-SHOW ] sensorType= 1 scaleMask= 3 defScale=0 Fri 03/16/2018 01:29:29 PM : [ZW-SHOW ] sensorType= 3 scaleMask= 1 defScale=0 Fri 03/16/2018 01:29:29 PM : [ZW-SHOW ] sensorType= 5 scaleMask= 1 defScale=0 Fri 03/16/2018 01:29:29 PM : [ZW-SHOW ] Fri 03/16/2018 01:29:29 PM : [ZWAVE-TX ] [01070080220000D7]... Fri 03/16/2018 01:29:29 PM : [ZWAVE-RX ] ACK Fri 03/16/2018 01:29:29 PM : [ZWAVE-RX ] [0120018041FC4000]... Fri 03/16/2018 01:29:29 PM : [ZWAVE-TX ] ACK Fri 03/16/2018 01:29:29 PM : [ZWAVE-TX ] [01070080220100D8]... Fri 03/16/2018 01:29:29 PM : [ZWAVE-RX ] ACK Fri 03/16/2018 01:29:29 PM : [ZWAVE-RX ] [0120018041FC4000]... Fri 03/16/2018 01:29:29 PM : [ZWAVE-TX ] ACK Fri 03/16/2018 01:29:29 PM : [ZWAVE-TX ] [01070080220001D9]... Fri 03/16/2018 01:29:29 PM : [ZWAVE-RX ] ACK Fri 03/16/2018 01:29:29 PM : [ZWAVE-RX ] [0120018001F84000]... Fri 03/16/2018 01:29:29 PM : [ZWAVE-TX ] ACK Fri 03/16/2018 01:29:29 PM : [ZW-SHOW ] Node 34 - ZW 034 Notify Sensor has the following neighbors Fri 03/16/2018 01:29:29 PM : [ZW-SHOW ] - Repeater - Node 1 - ZW 001 Uninitialized Device Fri 03/16/2018 01:29:29 PM : [ZW-SHOW ] - - Node 7 - [This ISY] Fri 03/16/2018 01:29:29 PM : [ZW-SHOW ] - - Node 11 - ZW 011 Multilevel Sensor Fri 03/16/2018 01:29:29 PM : [ZW-SHOW ] - Repeater - Node 12 - ZW 012 Front Porch Lights VRM Fri 03/16/2018 01:29:29 PM : [ZW-SHOW ] - Repeater - Node 13 - ZW 013 FamRm Floods VRMX1 Fri 03/16/2018 01:29:29 PM : [ZW-SHOW ] - Repeater - Node 14 - ZW 014 FamRm Ambient VRMX1 Fri 03/16/2018 01:29:29 PM : [ZW-SHOW ] - Repeater - Node 15 - ZW 015 KitchenPantry Monopri Fri 03/16/2018 01:29:29 PM : [ZW-SHOW ] - Repeater - Node 16 - ZW 016 Kitchen Under Counter, Fri 03/16/2018 01:29:29 PM : [ZW-SHOW ] - Repeater - Node 23 - ZW 023 YardLampFrnt Dim VRPD3 Fri 03/16/2018 01:29:29 PM : [ZW-SHOW ] Fri 03/16/2018 01:29:29 PM : [ZWAVE-TX ZW034_1] ... Fri 03/16/2018 01:29:29 PM : [ZWAVE-RX ] ACK Fri 03/16/2018 01:29:29 PM : [ZWAVE-RX ] [0104011301E8] Fri 03/16/2018 01:29:29 PM : [ZWAVE-TX ] ACK Fri 03/16/2018 01:29:34 PM : [ZWAVE-TX ] ZWAVE-WAIT Waiting for retry 1 of 2 Fri 03/16/2018 01:29:35 PM : [ZWAVE-TX ZW034_1] ... Fri 03/16/2018 01:29:35 PM : [ZWAVE-RX ] ACK Fri 03/16/2018 01:29:35 PM : [ZWAVE-RX ] [0104011301E8] Fri 03/16/2018 01:29:35 PM : [ZWAVE-TX ] ACK Fri 03/16/2018 01:29:35 PM : [ZWAVE-RX ] [01050013DB0133] Fri 03/16/2018 01:29:35 PM : [ZWAVE-TX ] ACK Fri 03/16/2018 01:29:40 PM : [ZWAVE-TX ] ZWAVE-WAIT Waiting for retry 2 of 2 Fri 03/16/2018 01:29:40 PM : [ZWAVE-TX ZW034_1] ... Fri 03/16/2018 01:29:40 PM : [ZWAVE-RX ] ACK Fri 03/16/2018 01:29:40 PM : [ZWAVE-RX ] [0104011301E8] Fri 03/16/2018 01:29:40 PM : [ZWAVE-TX ] ACK Fri 03/16/2018 01:29:40 PM : [ZWAVE-RX ] [01050013DC0134] Fri 03/16/2018 01:29:40 PM : [ZWAVE-TX ] ACK Fri 03/16/2018 01:29:45 PM : [ZWAVE-RX ZW034_1] ... Fri 03/16/2018 01:29:45 PM : [ZWAVE-TX ] ACK Fri 03/16/2018 01:29:45 PM : [ZWAVE-TX ] ... Fri 03/16/2018 01:29:45 PM : [ZWAVE-RX ] ACK Fri 03/16/2018 01:29:45 PM : [ZWAVE-RX ] [0104011301E8] Fri 03/16/2018 01:29:45 PM : [ZWAVE-TX ] ACK Fri 03/16/2018 01:29:45 PM : [ZWAVE-RX ] [01050013DD0034] Fri 03/16/2018 01:29:45 PM : [ZWAVE-TX ] ACK Fri 03/16/2018 01:29:45 PM : [ZWAVE-RX ZW034_1] ... Fri 03/16/2018 01:29:45 PM : [ZWAVE-TX ] ACK Fri 03/16/2018 01:29:45 PM : [ZWAVE-PROCESS ] Process value Sensor type=1 uomId=0 prec=2 Fri 03/16/2018 01:29:45 PM : [D2D EVENT ] Event [ZW034_118] [CLITEMP] [2451] uom=4 prec=2 Fri 03/16/2018 01:29:45 PM : [ ZW034_118] CLITEMP 2451 (uom=4 prec=2) Fri 03/16/2018 01:29:45 PM : [ZW-SHOW ] Node 34 - ZW 034 Notify Sensor cannot retrieve association groups Fri 03/16/2018 01:29:45 PM : [ZW-SHOW ] Fri 03/16/2018 01:29:45 PM : [ZW-SHOW ] ---------------------------------------------- Fri 03/16/2018 01:29:45 PM : [UZW-CMD 37 ] Show All Node Details : ZW034_118 Fri 03/16/2018 01:29:46 PM : [ZWAVE-RX ] [01050013DD0135] Fri 03/16/2018 01:29:46 PM : [ZWAVE-TX ] ACK Fri 03/16/2018 01:29:46 PM : [ZWAVE-RX ZW034_1] ... Fri 03/16/2018 01:29:46 PM : [ZWAVE-TX ] ACK Fri 03/16/2018 01:29:46 PM : [ZWAVE-TX ] ... Fri 03/16/2018 01:29:46 PM : [ZWAVE-RX ] ACK Fri 03/16/2018 01:29:46 PM : [ZWAVE-RX ] [0104011301E8] Fri 03/16/2018 01:29:46 PM : [ZWAVE-TX ] ACK Fri 03/16/2018 01:29:46 PM : [ZWAVE-RX ] [01050013DF0036] Fri 03/16/2018 01:29:46 PM : [ZWAVE-TX ] ACK Fri 03/16/2018 01:29:46 PM : [ZWAVE-RX ZW034_1] ... Fri 03/16/2018 01:29:46 PM : [ZWAVE-TX ] ACK Fri 03/16/2018 01:29:46 PM : [ZWAVE-PROCESS ] Process value Sensor type=5 uomId=0 prec=0 Fri 03/16/2018 01:29:46 PM : [D2D EVENT ] Event [ZW034_118] [CLIHUM] [29] uom=22 prec=0 Fri 03/16/2018 01:29:46 PM : [ ZW034_118] CLIHUM 29 (uom=22 prec=0) Fri 03/16/2018 01:29:47 PM : [ZWAVE-RX ZW034_1] ... Fri 03/16/2018 01:29:47 PM : [ZWAVE-TX ] ACK Fri 03/16/2018 01:29:47 PM : [ZWAVE-TX ] ... Fri 03/16/2018 01:29:47 PM : [ZWAVE-RX ] ACK Fri 03/16/2018 01:29:47 PM : [ZWAVE-RX ] [0104011301E8] Fri 03/16/2018 01:29:47 PM : [ZWAVE-TX ] ACK Fri 03/16/2018 01:29:47 PM : [ZWAVE-RX ] [01050013E10008] Fri 03/16/2018 01:29:47 PM : [ZWAVE-TX ] ACK Fri 03/16/2018 01:29:47 PM : [ZWAVE-RX ZW034_1] ... Fri 03/16/2018 01:29:47 PM : [ZWAVE-TX ] ACK Fri 03/16/2018 01:29:47 PM : [ZWAVE-PROCESS ] Process value Sensor type=3 uomId=0 prec=2 Fri 03/16/2018 01:29:47 PM : [D2D EVENT ] Event [ZW034_118] [LUMIN] [5278] uom=51 prec=2 Fri 03/16/2018 01:29:47 PM : [ ZW034_118] LUMIN 5278 (uom=51 prec=2)
Michel Kohanim Posted March 20, 2018 Posted March 20, 2018 Hello photogeek54, Apologies for tardy reply. We will order one of these and see where the issue is. With kind regards, Michel
glacier991 Posted March 24, 2018 Posted March 24, 2018 I have a few that exhibit odd inconsistent behaviors, not sure it isn't the device. ( I am on 5.0.12)
Michel Kohanim Posted March 28, 2018 Posted March 28, 2018 Hello everyone, We got one of these and thoroughly tested with 5.0.12. Everything works as expected including reporting. @glacier991, please describe the inconsistencies. With kind regards, Michel
DaveStLou Posted April 21, 2018 Posted April 21, 2018 On 11/14/2017 at 9:30 PM, elgwhoppo said: I found out the problem. I completely disassociated it and then re-associated it making sure to wait for the motion to trigger as a part of the pairing process. Works fine after that. I bought a 15902 and can't figure out how to get motion to work. I've tried excluding and then including again several times but only get Notify Sensor, Tamper Alarm and Multilevel Sensor. I'd appreciate any help understanding what waiting for the motion to trigger means or other insight into getting this sensor to work. Thanks in advance!
Michel Kohanim Posted April 22, 2018 Posted April 22, 2018 Hi @DaveStLou, What's your firmware version? This definitely works with 5.0.12. With kind regards, Michel
DaveStLou Posted April 22, 2018 Posted April 22, 2018 Hi [mention=5720]DaveStLou[/mention], What's your firmware version? This definitely works with 5.0.12. With kind regards, Michel I am on 5.0.12. Still haven't gotten it working.Sent from my Pixel XL using Tapatalk
elgwhoppo Posted April 23, 2018 Author Posted April 23, 2018 Hey guys, my secret to getting it working was ensuring that the motion detector was triggered...DURING THE INITIAL PAIRING. Seems if you try to add it after the fact it's a no go. That's just what I remember from my experience.
DaveStLou Posted April 23, 2018 Posted April 23, 2018 3 hours ago, elgwhoppo said: Hey guys, my secret to getting it working was ensuring that the motion detector was triggered...DURING THE INITIAL PAIRING. elgwhoppo, How are you triggering it? I feel like i'm missing something simple. I've tried waving my hand in front of it while I include it. I've tried pressing the black SW2 switch inside.
DaveStLou Posted April 23, 2018 Posted April 23, 2018 I got a different error message this time "Ignored unsupported unsolicited Z-Wave message [RX-U 01040160019B]" when I queried the device. Still no motion though...
DaveStLou Posted April 26, 2018 Posted April 26, 2018 I'm still dead in the water. I opened a ticket with Monoprice support last week. The generated email said they'd be back with me "shortly". Seven days doesn't fit my definition of shortly.
DaveStLou Posted May 10, 2018 Posted May 10, 2018 Just to update the thread - making a long story short, I finally connected with Monoprice support with NewEgg's help. Monoprice agreed the device was defective and replaced it. I received the replacement today and viola! it's working with 5.0.12. Now I just need to figure out the quirks of the motion sensor response/reporting time. I remember seeing something about that shared on the forum. Just have to do to a little research. After getting nowhere for weeks, it feels good to be making progress!
Recommended Posts
Archived
This topic is now archived and is closed to further replies.