Finally got my hands on one of these new Gen 4 Plugs, so I could iron out some issues and get it working. Has a preference toggle to enable/disable the creation of a child RGB device. When enabled, the child device works in Hubitat like any other RGB device does.
There's no point to the "night mode" stuff with this, since all that does is set a time range for the LED to dim. If you want that, Hubitat already provides a million ways to dim a light on a schedule. It would need 3 preferences to implement it in setting to enable the Shelly Night mode thing, one pref for start time, one for stop time, and one to enable/disable it. That's a lot of clutter on the preferences page for something you can already do in Hubitat natively.
I just have what I get shipped for testing, and it's in black. It's a nice plug, for sure. Quite easily the best smart plug I've ever used. Then again, pretty much all of Shelly's line is top-notch hardware.
Plug discovery worked when I tried it again this morning! App & driver updates process wasn't completely smooth, but once done Shelly plug device was created.
Both app and driver were set to auto-update in the app, but the driver part didn't auto-update for some reason. Clicked "Update All" on Drivers line and driver did not update. Clicked Update in the Driver section below and that did update the device driver.
Then clicked on + symbol in Discovery section, and the plug was added along w/additional Autoconf driver. The "Update All" action is still showing under the Action column in the App and Driver Updates section:
@daniel.winks I have loaded your app and get errors when I try to turn a Shelly device on. It’s a Shelly 1 gen4 connected to my garage door. Thanks for any help. Cheers, Tim
After a bit of thinking. I started again with Shelly and removed all devices (2) and app. I then added your app and all seems to work perfectly now. Thank you @daniel.winks
Just posting an update here. Been short on time here lately, and wiring up a bunch of Shelly devices on my test platform, fully testing them, and switching them out is really time consuming.
I think most of this works, but I haven't had a chance to personally test it. Hopefully here in the next few weeks I'll be able to get some devices wired up and move this from pre-release to beta status.
It's still definitely in development, and will be released "soon", but it'll be a bit longer before I get a chance to make sure the various drivers and devices work properly.
I can say for sure the Gen 4 plug works VERY nicely with this. It creates a child RGB device that behaves like any other RGB light, and controls the plug's LEDs exactly as you'd expect it would.
Added a few more devices for preliminary support, including the Gen 4 mmWave Presence sensor. I don't have one of these on hand, so it's been put together using documentation only. Please let me know if there's issues with it so I can get them fixed.
Also added support for the BLU distance sensor. Same thing here, I don't have one of these, so anyone with one that wants to provide feedback, it would be appreciated.
I have a Shelly Uni Gen 1. Is there a way to get just the drivers for it and not everything. From Package mgr I selected Uni Gen 1 and ended up with a huge number of Shelly device drivers.
Are you sure you're on the right forum thread? That sounds like how my HPM drivers work.
As far as I know, it should only install things marked "required" in HPM. Because there's no way to gate "user wants BLE relay" vs "user not interested in BLE relay" without maintaining a full second copy of this on HPM, those are all marked "required". I think, if you selected just the Uni, that you should end up with the Uni, the main library (which drives everything), the BLE Relay helper app, and the BLE drivers.
I have a separate project that I built out here. This project is just a single app... a HUGE one (almost 20k lines), but just an app. Then when you fire the app up and tell it to add a discovered device on Hubitat, it directly loads the driver for it (and only that device) straight from GitHub. This app is standalone, outside HPM, and it'll never be on HPM since this app has all the update and driver install/uninstall logic self-contained, so putting this on HPM would cause all sorts of issues.
If you installed something from HPM, that's likely the other project, and yes, by design (limitation) it installs a few drivers that you may not need. That said, they just take up a few kb of disk space if you're not using them, they don't cause any hub load or do anything if there's no device that uses them.
If you'd rather, scroll up on this thread to the first post and follow the steps to install the Shelly Device Manager app and give it a spin. It should only install a single driver for the Uni. If that's indeed what you have installed and Shelly Device Manager installed a bunch of extra drivers, then if you can message me with some logs, that'd be super helpful, because this app shouldn't be doing that.
Thanks, Looks like I got derailed. I did the install from HPM. I have an old "experimental" one from tomw for the Uni that still works. Thought it was toast but a Uni firmware update restored its functionality.
@daniel.winks I installed a bunch of Shelly 1PM and 2PM units via the app. The 1PM modules are fine, but the 2PM modules (which create child devices for the channels) aren't capturing status data like switch state, power, etc. If I click the ON or OFF button, it controls the device normally; it just doesn't receive the feedback.
I switched from HPM driver to Device Manager driver but had to switch back as behaviour was different.
I have Shelly BT Door Contacts on doors which trigger turning on lights, with the HPM driver when a door is opened (and left open) it triggers once on opening. However with these drivers the same door contact constantly triggers an open event every 20-60 secs and does not stop until the door is closed. I have had to revert back to HPM drivers as my outside lights where staying on all night due to the constant triggering.
