Problems with Shelly BLU Door/Window Sensor

sebastianhe · January 25, 2024, 10:01pm

I have some problems with the blu sensors from shelly. The blu thing is going online but there are now updates. The number or the contact still display “NULL”.

Some details about my setup:

openhab-4.1.1 (Stable Version)
regular openHAB Shelly Binding
Shelly Plus 2PM (Firmware: 1.1.0 → up to date) = Bluetooth (Gateway)
Shelly BLU Door Window Sensor (Firmware is up to date)

My install routine:

Enable Bluetooth on the Shelly 2PM (Enable Bluetooth, Enable RPC, Enable Bluetooth Gateway)
Connect the BLU Sensor in the Shelly Cloud App with the Shelly 2PM
Installed the latest Firmware with the Shelly Cloud App
Check the sensor function in the Shelly Cloud App (open, close)
Enable “BLU Gateway Support” in the thing configuration (Shelly 2PM)
Check if the script “oh-blu-scanner.js” was installed
Press the button on the BLU Sensor
Check the openHAB Inbox – a new thing was shown
Add the thing with the GUI / At a another configuration, I have tried to configure with the shelly.things file
In both, the new sensor thing is displayed with the state “CONFIG_PENDING”
Click the device button again, the binding gets another event and creates the channels and thing changes status to ONLINE
Create an new item with the GUI / At a another configuration, I have tried to configure with the shelly.items

The following isn’t Working:

Every time an event is received sensors#lastUpdate and channels are updated with the reported values

What I have already tried:

Configure another Shelly BLU Sensor
Configure without the Shelly Cloud App
Check the state (open/close) in the Shelly Cloud App
Reset the Shelly 2PM to the factory defaults
I Can see in the log file the state “shelly:shellybludw:b0c7de061db1:relay#button triggered SHORT_PRESSED” Event

Any ideas? Thanks Sebastian

MiniOh · January 28, 2024, 7:19am

Hello,

I have a similar problem.
Can you check on the Shelly, which serves as your gateway, whether the script is on play or pause?

For me, I have to press play manually, then the script runs for some time (hours?, I still have to test how long).
As long as the script is running, all status changes are sent to Openhab.
At some point the script is paused and then status is no longer passed on.

I can’t say why the script on the Gateway Shelly pauses.

Olli

Andy_Co · January 28, 2024, 8:45am

Hi, I observe the same problem. Adding additional Shellies as gateways do not helped. Maybe problem is caused by weak bluetooth signal ? At my case it is showing 1 or 2 level.

MiniOh · January 28, 2024, 9:44am

No, I do not think so.
The status of Shelly Cloud works absolutely without any problems.
So BLU Device to Gateway Shelly to Cloud is error free.
BLU Device to Gateway Shelly to Openhab does not work permanently.

I’m currently testing how long it works, or how long the script on the Gateway Shelly is on play.
Maybe the ECO mode of the Gateway Shellie plays a role?

ErikDB · January 28, 2024, 10:06am

In my case (https://community.openhab.org/t/shelly-blu-door-window-frozen/153404) the script also stopped working. Strangely enough it did also break the connection with the cloud: in the Shelly app no changes to lux or the window opening/closing were detected. As soon as I manually ran the script again, the changes were reported.

I’ll also monitor how long the script stays active.

ErikDB · January 28, 2024, 12:02pm

Not even 2 hours…

MiniOh · January 28, 2024, 12:55pm

Here only between 1 and 2 hours too.
ECO mode on or off makes no difference.

There may be something in the logs as to why the script stops.

ErikDB · January 28, 2024, 2:19pm

You mean the Shelly logs? Where would those be hidden?

Andrew_Rowe · January 28, 2024, 2:36pm

This thread is a little weird because you guys seem to be operating in a vacuum. I noticed you have tagged the thread with the shelly tag. I’m surprised the developers of the binding haven’t replied. Good on you guys for trying to figure the issue out on your own.
Have any of you posted in the shelly binding thread?
I don’t want to ping them directly but maybe post in that thread and provide a brief description of your issue and a link to this thread

sebastianhe · January 30, 2024, 1:00pm

Sorry for my late answer, the script is in this Status. I have tried also a reboot.

sebastianhe · January 30, 2024, 1:02pm

No, a weak bluetooth signal is not the problem. In the Shelly cloud app the sensor updates his status very fast. I think the script or the binding are buggy.

sebastianhe · January 30, 2024, 1:06pm

I have ping this post at the thread

Norman_Trapp · March 12, 2024, 6:23pm

Any news about this topic?
I’m running in the same problems since weeks.
My Bluetooth Gateway (Shelly USB-Stick) at openhab is on ERROR:CONFIG
My both Bluetooth Door/Windows are in CONFIG:PENDING

I added the oh-blue-scanner.js scripts to all Bluetooth devices.
One D/W sensor ist connected to the Bluetooth Gateway.
One D/W sensor ist connected to my Shelly PlugS with Bluetooth Gateway enabled

Both sensors are working in the shelly App!

Any known solutions for Shelly USB-Stick “ERROR:CONFIG”?
How to troubleshoot integration issues with openHAB?

Taidy5 · May 18, 2024, 12:17pm

same/similar? problem: my script is not stopping - at least it is shown as running. In any case after while - eg. after one day - the status OPEN/CLOSE is not transmitted any more.

I run openHAB 4.1.2 Release Build.

I took version 0.3 from github and tried to run this version. But after one day again, it does not work.

github.com

openhab/openhab-addons/blob/3e3558f9c058221eb3a031ab80a5cd5558b9a367/bundles/org.openhab.binding.shelly/src/main/resources/scripts/oh-blu-scanner.js#L2


      
          /*
           * This script uses the BLE scan functionality in scripting to pass scan results to openHAB
           * Supported BLU Devices: BLU Button 1, BLU Door/Window, BLU Motion, BLU H&T
           * Version 0.3
           */
          
          let ALLTERCO_DEVICE_NAME_PREFIX = ["SBBT", "SBDW", "SBMO", "SBHT"];
          let ALLTERCO_MFD_ID_STR = "0ba9";
          let BTHOME_SVC_ID_STR = "fcd2";
          
          let ALLTERCO_MFD_ID = JSON.parse("0x" + ALLTERCO_MFD_ID_STR);
          let BTHOME_SVC_ID = JSON.parse("0x" + BTHOME_SVC_ID_STR);

stop/run the script does not work.
A reboot my Shelly PlusPlugS does help.
Hope for a solution / further hints here.

SHUred · July 28, 2024, 10:51am

Hello there,
seems like im in the same boat:

Acqired Shelly BLU Door Contacts
Shelly BLU Gateway Dongle
Adding the dongle (in the Shelly app and OH) was no problem
Adding the door contact in the Shelly app was no problem and updates fast
Contact does not get discovered in OH
oh-blu-scanner.js runs on the dongle

What i have now discovered via debug-stuff on the gateway dongle is that as long as “bluetooth gateway” (shelly web ui seting) is active on the dongle, the debug log tells me that the script can not run

As soon as i deactivated the checkbox for the gateway function (but left it active in the OH thing configuration) OH immediately discovered the contact because the script then is able to do its job

Maybe all of you knew that already but for me it was weird

ErikDB · July 28, 2024, 11:01am

It’s even in the binding documentation

SHUred · July 28, 2024, 11:58am

Youre absolutely right
Sorry for that

Having my things added im struggling with the usb dongle which seems to automatically activate the “Enable Bluetooth gateway” checkbox after a reboot

It seems that i have to disable the checkbox, then reboot the stick (which re-enables the checkbox) but afterwards the stuff seems to be starting to work with OH

Seems to be a bug in shelly Firmware or target behavior?

igi · July 28, 2024, 2:38pm

The BLU Gateway is the main functionality of the BLU Gateway USB dongle and cannot be disabled on this devices. But you can use any other main powered Gen2+ device as OH gateway where the option can be deactivated.

SHUred · July 28, 2024, 2:44pm

Understood
Thank you for clarification

Taidy5 · August 3, 2024, 9:49pm

Since openhab version 4.2 it works for me. Stable and for days.