Shelly Blu door window new version not decode

Theengs Decoder
1

Hi everyone,

I have a small issue with Shelly Blu window/door sensors.
I have several of them, but the latest ones I acquired no longer work correctly with openMQTTGateway.
Here’s what I see in MQTT Explorer:

{
  "manufacturerdata": "a90b0101000b02000a8187a8f52e3c",
  "name": "SBDW-2C8781",
  "id": "3C:2E:F5:A8:87:81",
  "rssi": -54,
  "rssi": -60,
  "servicedatauuid": "fcd2",
  "servicedata": "4400100164059808002d003f0000",
  "mfr": "Allterco Robotics ltd"
}

Whereas for the older ones…


{
  "name": "SBDW-002C",
  "id": "3C:2E:F5:BD:25:16",
  "rssi": -46,
  "rssi": -45,
  "brand": "Shelly",
  "model": "ShellyBLU Door/Window",
  "model_id": "SBDW-002C",
  "type": "CTMO",
  "packet": 212,
  "batt": 100,
  "lux": 0,
  "open": false,
  "rot": 0,
  "mac": "3C:2E:F5:BD:25:16"
}

I think they have changed the way they communicate because I was able to see them in the Shelly app.
If someone can help me.

Thank you all.

2

Hi @Freeddoo

The new Shelly Blu window/door sensors seem to broadcast a different name which breaks the current decoder. I’m just implementing a fix for this. How are you running Things Gateway and how is Things Decoder installed for you?

3

Hy @Digih
Already thank you for helping me.
I use a translator my English is basic enough to write.
I use TheengsGatway on a VM and I have two antennas with OpenGatewayMQTT.
I don’t know how to use the decoder yet.
If necessary I can try to see how to do it.
If you need other information tell me

4 
N: BT Device detected: 3C:2E:F5:A8:87:81
N: [ OMG->MQTT ] topic: home/TheengsGateway_etg/BTtoMQTT/undecoded msg: {"id":"3C:2E:F5:A8:87:81","mac_type":0,"adv_type":0,"name":"SBDW-2C8781","manufacturerdata":"a90b0101000b02000a8187a8f52e3c","rssi":-77,"servicedata":"44000b016405540b002d013f6100","servicedatauuid":"0xfcd2"}
5

Do you have Theengs Gateway installed with pip on your VM?

For OpenGatewayMQTT you can install the development build tomorrow, which will then already include the Shelly Blu window/door sensor

6

Yes with pip
Tomorrow evening I will update my two esp32dev-ble-mqtt-undecoded

7

The esp32dev-ble-mqtt-undecoded binary will actually always only publish undecoded MQTT messages, which then Theengs Gateway then will receive and decode centrally. Therefor there is not need to update your current ESP32s, as the new decoder fix will not make any changes to this particular binary. You can keep those as they are, as you’ll need to get the new decoder into Theengs Gateway.

Once Theengs Decoder has a new version released, which should not be too long away, you can just pip update it to the new version on your VM.

or if you are knowledgeable in building and pip installing the development version of Theengs Decoder, as described here

so you will get the updated decoder.

Alternatively send me a private message here and I can send you a link to the already built version, which you can then easily pip install.

8

I can’t send a private message I don’t have access.
I think I have something wrong in my forum config.
Do I have to create a new VM or can I install it on the same VM?

9

It might be because you are new to the forum. Did you get my PM ok?

10

Fixed and will be officially included in the next Theengs Decoder release.