Condition for service_uuids?

[melyux]

There's a condition for uuid but this is for the service data UUID. My device's advertisement data has no service data, but it does have a service_uuids. Is there a way to write a decoder with a condition on that instead?

[DigiH]

If it is in the advertising data, yes, it can be used in the model condition of a decoder.

Is the actual decodable data in the manufacturerdata then?

[melyux]

How do I use it in the condition? This family of sensors have a service_uuid of ef090000-11d6-42ba-93b8-9dd7ec090ab0 (in the service_uuids list)

Yeah the actual data is in manufacturerdata (temp, humidity, pressure).

[DigiH]

You can check in the model condition for the unique 16-bit part of the uuid, but are you sure that the uuid is in the Bluetooth BLE advertising data?

Can you post an example of what undecoded data you are receiving, with Advanced and Advertising Data set to true?

https://docs.openmqttgateway.com/use/ble.html#advanced-advertisement-and-advanced-data-default-false-available-with-ha-discovery

[melyux]

Is there a model condition? I only saw name, uuid (service data UUID), service data, manufacturer data, and no-mfgdata in the code and docs. I don't see one for the service UUID.

I did a quick hack by changing the code and setting the servicedatauuid to the first service UUID in case the servicedata is empty. Here's the undecoded data with adv data on:

{"id":"18:04:ED:XX:XX:XX","mac_type":0,"adv_type":0,"manufacturerdata":"0011ef464343b7","rssi":-65,"servicedatauuid":"ef090000-11d6-42ba-93b8-9dd7ec090ab0","brand":"SensorPush","model":"HTP.xw","model_id":"HTP_xw","type":"THBX","cidc":false,"tempc":-16.4225,"tempf":2.439499,"hum":39.19283,"pres":300.0039}

Here's the raw advertisement data received in the ScanAndDecode.py example in this repo:

8F00AD5F-262D-10C7-A7AD-D025FC1BXXXX:AdvertisementData(manufacturer_data={256: b'w\xe4\tV\xb7'}, service_uuids=['ef090000-11d6-42ba-93b8-9dd7ec090ab0'], rssi=-86)

[DigiH]

I don't see one for the service UUID.

Service (data) uuid, as seen in your advertising data. The model condition check for it is just call "uuid", which for your above case seems to have the unique 16-bit "0000".

Your above data sample seems to already contain the decodings for temperature etc.

[melyux]

Service data UUID and service UUID are different though, uuid filtering for this doesn't work unless I change the code. The Theengs Decoder library doesn't have support for condition filtering on the service UUID right now

I'll make a PR with my current solution of overloading of the service data UUID, since they seem to be semantically related. Like, if this device did have service data, its service data UUID(s) would be same/similar to the service UUID(s), probably. That's what I need some insight on

The decodings are after I added my new decoder so ignore those