Glad it worked for you. If anyone else is interested, the email I got says it’s only for today and tomorrow (7/14 and 15), and only one use per customer.
I have purchased the Monoprice door lock:
http://www.monoprice.com/Product?c_id=122&cp_id=12212&cs_id=1221201&p_id=10798&seq=1&format=2
The only catch - the battery indicator doesn’t show up =(. It only shows “–.” Any ideas on how to get this to work? It is currently set to “Z-Wave Lock.” Unfortunately I don’t have the Groovy programming know-how (yet) to write the device handlers that florianz did for the door/window and motion detectors. Thoughts?
(And yes as far as locking/unlocking, showing locked status, responding to commands everything else on the lock works like a charm.)
1 Like
I am still attempting to get the battery indicator to show up properly on the Monoprice door lock that I have purchased. Everything is working on it using yracine’s door lock code except for the battery, which displays “–.” Is there a simple fix to get the battery indicator working properly? I still don’t understand Groovy well enough to identify and correct the bug. Ironically I would think polling the battery report would be one of the easiest things to do!
Code:
Post:
Manual:
http://www.monopricehub.com/files/manuals/10798_Manual_131204.pdf
Spec:
@kmugh: I’ve played around with @florianz code a bit and was able to get the long inactivity trigger & battery to work.
It’d be great if you can send me preliminary feedback on it:
Details on how to get it here: Monoprice Door Sensors & Motion Sensors Available again
Disclaimer: presently alpha, so your mileage will vary. but works perfectly for me.
Still can’t see battery with the motion detector. Is it supposed to work?
@RichardH Yeah. Its supposed to. At least it works for me.
Did you open/close the motion sensor as I described?
Otherwise, can you send me the logs in the Live Logging?
Maybe I’m not sure what you mean by open the motion sensor. The app device or the actual unit?
Awesome, thanks @kranasian. I will pull in the changes as soon as I get a chance. Any idea whether there has been a hardware revision that would make the battery reporting work?
@RichardH: the actual unit. You have to open it to force it to wake up… But by now, it should have woken up by itself. 
If it hasn’t open the Live Logging tab and open/close the actual unit. Then send over the logs…
I don’t actually know… I just bought mine a couple of months back, but I had been busy so I was not able to start investigating until a few days back.
Does your device fingerprint match mine?
5001d6cb-df46-4f2f-a1e2-ef77c1765572 7:23:54 PM: debug Parse returned [[descriptionText:Unhandled: Office: AlarmReport(alarmLevel: 255, alarmType: 7), displayed:false, isStateChange:false, linkText:Office]]
5001d6cb-df46-4f2f-a1e2-ef77c1765572 7:23:54 PM: trace Parse Raw: zw device: 14, command: 7105, payload: 07 FF 00 FF 07 02 00 00
5001d6cb-df46-4f2f-a1e2-ef77c1765572 7:23:54 PM: debug Parse returned [[name:motion, value:active, handlerName:active, descriptionText:Office detected motion, isStateChange:false, displayed:false, linkText:Office]]
5001d6cb-df46-4f2f-a1e2-ef77c1765572 7:23:54 PM: trace Parse Raw: zw device: 14, command: 2001, payload: FF
5001d6cb-df46-4f2f-a1e2-ef77c1765572 7:23:53 PM: error java.lang.NumberFormatException: For input string: “” @ line 116
5001d6cb-df46-4f2f-a1e2-ef77c1765572 7:23:53 PM: trace Parse Raw: zw device: 14, command: 8407, payload:
5001d6cb-df46-4f2f-a1e2-ef77c1765572 7:23:50 PM: debug Parse returned [[descriptionText:Unhandled: Office: AlarmReport(alarmLevel: 255, alarmType: 7), displayed:false, isStateChange:false, linkText:Office]]
5001d6cb-df46-4f2f-a1e2-ef77c1765572 7:23:50 PM: trace Parse Raw: zw device: 14, command: 7105, payload: 07 FF 00 FF 07 03 00 00
5001d6cb-df46-4f2f-a1e2-ef77c1765572 7:23:30 PM: debug Parse returned [[descriptionText:Unhandled: Office: AlarmReport(alarmLevel: 255, alarmType: 7), displayed:false, isStateChange:false, linkText:Office]]
5001d6cb-df46-4f2f-a1e2-ef77c1765572 7:23:30 PM: trace Parse Raw: zw device: 14, command: 7105, payload: 07 FF 00 FF 07 03 00 00
5001d6cb-df46-4f2f-a1e2-ef77c1765572 7:23:10 PM: debug Parse returned [[descriptionText:Unhandled: Office: AlarmReport(alarmLevel: 255, alarmType: 7), displayed:false, isStateChange:false, linkText:Office]]
5001d6cb-df46-4f2f-a1e2-ef77c1765572 7:23:10 PM: trace Parse Raw: zw device: 14, command: 7105, payload: 07 FF 00 FF 07 03 00 00
5001d6cb-df46-4f2f-a1e2-ef77c1765572 7:22:50 PM: debug Parse returned [[descriptionText:Unhandled: Office: AlarmReport(alarmLevel: 255, alarmType: 7), displayed:false, isStateChange:false, linkText:Office]]
5001d6cb-df46-4f2f-a1e2-ef77c1765572 7:22:50 PM: trace Parse Raw: zw device: 14, command: 7105, payload: 07 FF 00 FF 07 03 00 00
5001d6cb-df46-4f2f-a1e2-ef77c1765572 7:22:30 PM: debug Parse returned [[descriptionText:Unhandled: Office: AlarmReport(alarmLevel: 255, alarmType: 7), displayed:false, isStateChange:false, linkText:Office]]
5001d6cb-df46-4f2f-a1e2-ef77c1765572 7:22:30 PM: trace Parse Raw: zw device: 14, command: 7105, payload: 07 FF 00 FF 07 03 00 00
5001d6cb-df46-4f2f-a1e2-ef77c1765572 7:22:10 PM: debug Parse returned [[descriptionText:Unhandled: Office: AlarmReport(alarmLevel: 255, alarmType: 7), displayed:false, isStateChange:false, linkText:Office]]
5001d6cb-df46-4f2f-a1e2-ef77c1765572 7:22:10 PM: trace Parse Raw: zw device: 14, command: 7105, payload: 07 FF 00 FF 07 03 00 00
5001d6cb-df46-4f2f-a1e2-ef77c1765572 7:21:50 PM: debug Parse returned [[descriptionText:Unhandled: Office: AlarmReport(alarmLevel: 255, alarmType: 7), displayed:false, isStateChange:false, linkText:Office]]
5001d6cb-df46-4f2f-a1e2-ef77c1765572 7:21:50 PM: trace Parse Raw: zw device: 14, command: 7105, payload: 07 FF 00 FF 07 03 00 00
Looks like this is the error. You can fix it quickly by entering the Preferences pane and setting the Inactivity Timer field with 1 or any setting you want.
I’ll double check later why this broke.
Thanks for the bug report.
that worked! Thanks!
Glad that it did! ---------------
@kranasian Great! Was seeing the same error as @RichardH. Just changed the prefs, will report back soon.
1 Like
Hi Fellow Smarthings enthusiasts.
Hi Kmugh,
I come to you guys, to ask for help. I’m a newbie, working in medical field. I was able to install some of the switches but I had a hardtime in monoprice sensor. Well actually my hub/app accepted as Z-wave sensor but no luck it has no smartapps (no activity).
So if anyone could help step by step (sorry!) very appreciated. My monoprice sensors are sitting duck in my drawer.
Kindly teach me communicate or install the smart apps that they were posting.
Thank you so much.
Pogs