[RELEASE] Shelly Device Drivers (NO MQTT NEEDED)

@daniel.winks

so, now is clear for me the architecture of it. I thing, now, i made all correct.
I mean:
. The device where the door/window ( blu ) is connect ( or, if you prefer is listening ) already have your driver in use;
. "enable bluetooth gateway for hubitat" is enable
. on that device, the script, is running and "run at startup active
. on the device of door/window the MAC address is entered correct

but... nothing happens.. :frowning:

Hi Daniel, I finally got your UNI gen1 driver installed and configured, all seems to work well, webhooks installed as planned and they report faster on HE than on the Shelly ios App.

But, I seem to have a problem with the parent driver, where I can't save preferences at all, only thing I did not try yet is reinstalling the driver. Not sure if I have a corrupt database all of a sudden, might try a rebuild or if this has anything to do with the driver code, but I doubt it, I am on Beta firmware just in case that might have something to do with it but from the release notes, I don't see anything that would cause this behaviour.
image

Also all logs are turned off and no way to turn them back on :frowning:

EDIT: Well I finally removed the device and added back in and all works as it should now. One thing I was wondering is if the fact that I clicked save a second time before I got the message that all settings saved could have corrupted something?

@daniel.winks , thanks for your work on these drivers :slight_smile:

I've been using the Fibaro Smart Implant to host DS18B20 temp sensors with great success, but these devices seem to be unobtainium right now. I have zero experience with the Shelly products.

The folks over at Aartech recommended the Shelly Plus 1 UL (Shelly Plus 1 UL - Aartech Canada) combined with the Shelly-Plus Addon Sensor Interface (SHELLY-PLUS-ADDON Sensor Interface - Aartech Canada) to host up to five DS18B20 external temp sensors as per this diagram:

It looks like the add on interface clips on to the Plus 1 and uses its serial interface for communication and power. Would your driver set work to expose these temp sensors connected to the add on interface? Aside from initial configuring with all sensors connected, should these sensors just show up as child devices? What is the "leanest" setup to do this on Hubitat while keeping traffic low? I'd like max reporting resolution on the temp sensors if possible to at least 1 minute and/or 1 degree F reporting intervals.

Cheers,
Dennis.

Anyone using the bluetooth drivers ? for the Blu door/Window device ? or the blu motion ?