Official Monoprice Smart Plug/Plugin Receptacle Device Handler - Version 01.01.01
- Added support to show numbers with 1 decimal place
@RBoy Any chance that Monoprice will restore the discount?
We’ve working to get a special for Presidents day - subscribe to our facebook page for updates. Spread the word, the more folks who make use of it the better chances of getting more promos in future
Thank you for the quick reply and updates. Much appreciated!
I’ve been fighting the delay issue for 2 months with multiple tickets and multiple failed z-wave repair, so trying to eliminate variables one by one. Appreciate the help!
I’ve been spending some time diving into why some devices are failing and in the case of a rouge device, which makes sense per the prior reply, will cause nothing but problems
With Z-Wave being a black block within ST, step one for me is isolating the root cause based on known data in the IDE, which is seeing what variables are different. I believe part of this is captured and defined within the DTH, and the other part is how the hub processes along with how/what the device itself responds with.
Since I have 20 of the exact same 15654 MP Receptacle purchased not far apart, in theory all data should be close if not exact across all devices, but, as my luck would have it, that is not the case.
1) Any idea why there would be a mix of manufacturer = “null”, data in role, ff, and ui across devices? Pictures at bottom to illustrate. Summarized table below. This is a small sample of my 20 devices, all of the 15654 receptacle
|1||Existing||“null”||tag not present||tag not present||tag not present|
|3||Existing||tag not present||05||8700||8700|
|4||Newly Included with DTH Automatically assigned||“null”||tag not present||tag not present||tag not present|
1a) Existing Devices, DTH Updated Post Inclusion:
1b) Newly included after RBoy DTH added via IDE. Exclusion was also done prior to inclusion.
2) It also does not appear secure inclusion is working despite following the instructions to the tee as none show the S after the zw in the raw description. This is true even after a fresh exclude/include. I do see the S with other MP devices as outlined in this thread, but just not seeing here on this device.
Steps to reproduce #2 Put the hub into inclusion mode, physically verify a blinking green light on the hub (which doesn’t always happen when using the ST mobile app - it’s a crap-shoot), THEN plug the MP outlet in the wall which produces a rapid blink and the LED goes dead which per docs indicate the device was securely included.
If this belongs in another forum or should be reported to ST Support, please let me know. I do appreciate the replies and help. BTW, the updated DTH for this is working perfectly now. Thank you!
The manufacturer can be safely ignored. That’s collected by ST after inclusion but during the configuration phase, there’s a VERY short window for the hub to send this request after inclusion before the devices goes to sleep, so it’s a hit or a miss depending on if the command makes it in time or not. Anyways, it’s completely FYI only and has no bearing on anything.
What’s key is to look the raw description, those should be identical for all the devices. If they are not that would mean the inclusion had a problem or the device has a problem (with the exception of ZW which could have L or Ls if it’s securely included).
The best way to identify a rogue device is to exclude your devices. Add one device, do a Z-Wave repair see how it goes, then add the next device, do a Z-Wave repair and so on an so forth. It’s a slow process but the only reliable way. Note the Z-Wave repair is important since the route determines a LOT to do with Z-wave performance and responsiveness. You can see this quite easily, after pairing/doing a z-wave repair, now unplug the device and take it across the home and plug it in. You’ll notice it’s very sluggish in it’s response because the network mesh isn’t updated. Eventually after a few hours of discovery and optimization the mesh sorts itself out but it’s best to do a Z-Wave repair.
You’ve got this backwards, a fast blinking light means it was included WITHOUT secure inclusion.
To do a secure inclusion the light should be blinking slowly (see the first post), quoting:
MANUAL SECURE INCLUSION
a. The light should be blinking slowly (not rapidly), if not you may need to exclude it first (see below) and then press the power button once
b. Press and hold the power button on the device for 3 seconds and then release it when the lights starts blinking rapidly
c. It should complete pairing within 30 seconds
Hope this helps.
Thank you! Your insight here is very helpful as clearly I missed the 3 second part. Triple tapping also worked, but apparently that is Non-Secure mode. I appreciate the help and will give that along with the exclusion tip a try.
I bought a pair of the Monoprice 27481 smart plugs and used one of them in the bedroom where the LED is too bright. Looking for a way to disable it, I came across this page and found to my dismay that the only way appears to be to pay $38 for access to a suite of apps and device handlers that I won’t use, apart from the one associated with the 27481. Is there any a la carte option? $38 is more than I paid for the plugs, so that’s not going to work. Is electrical tape my only resort? Thanks!
I bought these plugs from Monoprice and the USB ports are always on but the AC outlets are controlled by the smartthings. I called the tech support and they told us to reach out to Rboy to find out how the USB ports can be controlled through smartthings. I have the Rboy app subscription. Is it possible to control the USB ports?
Not on these models. It only controls the A/C outlet and the LED lights. You can find a full list of supported features in the first post.
Agreed. I’d appreciate a cheaper option for those of us that just want that one feature for one product. Maybe an option for a one time code purchase without Github or whatever other method Rboy uses to distribute code updates?
I’ve purchased a few sheets of these dimming stickers over the years to place right over small LED lights on TVs, Routers, etc.
I’ve run two of the 27481 with the default handler for a bit over a year now. I’m buying an RBoy license as I’ve just bought another sensor. My question is, is there an easy way to update the device handler?
I second this. I bought the Monoprice outlet to control USB devices and while he main outlet turns on and off, the USB stays on. This sounds more like a Monoprice problem but if Rboy can fix it that would be great.
Does the DTH support disabling the on/off functionality of the switch? I’m using the device as a power meter on my washer machine and don’t want to accidentally turn off the switch.
My other option is to create an automation to turn it back on if it’s turned off.
Yes the switch can be turned on/off using the ST mobile app (in addition the the power readings). If you’re using the new ST app, it has the option to set a timer on the device page.
If you’re using the Classic app then you can setup a simple rule in SmartLighting or CoRE
First off, I am a paid customer of the wonderful RBoy smartApps and Device Handlers and am grateful for all the wonderful additions they add to SmartThings.
I have recently moved to the new app (v.3) and I am confused to why the v.2 screens give so much more information and settings then what we get from the new app. The Monoprice Smart Plug (27481) device handler is just one of the RBoys this way.
Why? Is the new app forcing everything to look the same or is it RBoys only wanting to write for the single platform?
I for one like the new app (recent release) and when I migrated I was able to deleted a couple of DH since the devices are now directly supported in ST.
The New App does not support the “legacy/Groovy” method of describing device handler UI tiles in the Metadata section of code.
The New App uses HTML5 based “plug-ins” to permit significantly richer UIs - but I don’t know what the hold-up is on getting developers to use this and SmartThings to publish them.
I bought the 27481 to use as a repeater for my Yale door lock & RLA. You’d think that if I could figure out how to input custom code and publish, I’d be able to figure out how to add the device to my Smartthings app and hub. But I can’t!! The instructions on Rboy’s page state, " 1. Now pair your device with the hub (see the SmartThings manual for pairing instructions). I can’t find pairing instructions, and I don’t understand why they can’t be detailed on the site since everything else is so nicely detailed. So, the repeater is plugged in, and I have no idea how to get it to be recognized by my hub.