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.. 
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.
Also all logs are turned off and no way to turn them back on
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 
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 ?
I'm trying to configure a Shelly Door/Window (BLU) via a Shelly Plus 1 PM and am not able to get the driver to detect BlueTooth. The Plus 1PM is running firmware 1.5.1 which has Bluetooth Gateway enabled permanently. Here's the log:
Plus 1PM: Setting device info: model=SNSW-001P16EU, gen=2, ver=1.5.1
Plus 1PM: Shelly Device Info Result: {
Plus 1PM: Getting device info...
Plus 1PM: Nightly power monitoring reset is enabled in device preferences, creating nightly reset task...
Plus 1PM: Power monitoring is enabled in device preferences...
Plus 1PM: Power monitoring device detected...
Plus 1PM: Device does not support Bluetooth gateway
Plus 1PM: Enabled: true
Plus 1PM: HasBlue: false
If I rollback to firmware 1.4.4 then the driver sees Bluetooth gateway but I can not get the Door contact to report in. The firmware on the contact is 1.0.22
Plus 1PM: Setting device info: model=SNSW-001P16EU, gen=2, ver=1.4.4
Plus 1PM: Shelly Device Info Result: {
Plus 1PM: Getting device info...
Plus 1PM: Nightly power monitoring reset is enabled in device preferences, creating nightly reset task...
Plus 1PM: Power monitoring is enabled in device preferences...
Plus 1PM: Power monitoring device detected...
Plus 1PM: Sucessfully installed Shelly Bluetooth Helper on device...
Plus 1PM: Bluetooth Helper is installed, enabled, and running
Plus 1PM: Script found: {
Plus 1PM: Getting index of HubitatBLEHelper script, if it exists on Shelly device...
Plus 1PM: Validating sucessful installation of Shelly Bluetooth Helper...
Plus 1PM: Starting Shelly Bluetooth Helper on device...
Plus 1PM: Enabling Shelly Bluetooth HelperShelly Bluetooth Helper on device...
Plus 1PM: Sending latest Shelly Bluetooth Helper to device...
Plus 1PM: Getting latest Shelly Bluetooth Helper script...
Plus 1PM: Script found: {
Plus 1PM: Getting index of HubitatBLEHelper script, if it exists on Shelly device...
Plus 1PM: Enabling Bluetooth on Shelly device...
Plus 1PM: Bluetooth Gateway functionality enabled, configuring device for bluetooth reporting to Hubitat...
Plus 1PM: Enabled: true
Plus 1PM: HasBlue: true
Hello folks, sorry for the absence here, but I got hit pretty hard with basically every flu and cold that went around this winter, with a dose of pneumonia thrown in for good measure. Felt too sick to be up for much of anything for a solid 6+ weeks, then a few weeks after that spent getting caught up on all the things I'd put off around the house for most of winter.
I'll be working on getting a few more drivers out here soon, and taking a look at some of the issues posted here.
Yes, the drivers I have here will support the temp sensors. It will create a child device for each, dynamically, depending on what you have connected. If you connect/disconnect them after setting the driver up, you'll need to do a "configure" on the device to get it to redo the child device creation.
You'll need to set the sensors up on the Shelly web UI for the device like so:
Then click 'configure' in Hubitat to add them, if the device is already added to Hubitat.
The way the driver works is connects to the Shelly device and creates some webhooks for things, such as "temperature change", so Hubitat will get notified when the temperature changes, immediately. The driver is almost 100% statically compiled code, so it's pretty low load on Hubitat.
You'll get a child device per sensor:
I only hooked up 2 sensors for testing, but it'll work the same for 1-5 of these DS18B20. The DHT22 are only supported for 1 per Shelly.
Oof, glad you are feeling better these days -- take it easy settling back in!
Thanks for the notice. Looks like they removed the 'observer' flag from the JSON returned with firmware 1.5.0+ since it's always on now.
The latest version on HPM has some fixes which cleared this up for me when I tried it with a few devices with the updated firmware.
Updated version on HPM. Changes include fixes for some Bluetooth issues, properly handling devices with firmware 1.5.0+, and adding a few more of the Shelly Blu devices.
Edit: Added a patch to this, which uses a hard-coded (per driver) flag for whether or not a device supports BLU Gateway functionality. Firmware 1.5.0+ no longer has the "observer" value available to use to autodetect whether a device supports BLU Gateway or not. Doesn't look like there's a good way to auto-detect support for BLU Gateway functionality, but it's easy enough to set as a flag on the drivers, and slightly faster when running 'configure' as well.
New release on HPM adds support for Shelly Plus RGBW PM.
Another release adding Shelly Plus 0-10v Dimmer support now on HPM
Update on HPM: Add Shelly Bulb RGBW, fixes for missing state on light/RGB/RGBW components.
nice to see that you are better. All the best. We will wait for you updated drivers.
in the meantime, from my side, i will give updates on my issues. thank you for your support.
thank you. my Door/window BLU are working as expected.
Awesome! I made a fair number of changes to the Bluetooth Helper app recently, to add support for the Shelly Blu Temperature and Humidity sensor, so I'm glad that also seems to have fixed the issue you were having.
New version on HPM: add support for Shelly Plus Wall Dimmer
as i understand the Blu Button 4 is not supported yet ?
No, it should be supported. I added that a few updates back, right at the same time I added the Blu H&T.
Download the Hubitat app
