DigiH

> * Manually delete the relevant HA Discovery topics from the MQTT broker (`homeassistant/sensor/*`). I even deleted the whole `homeassistant` topic, so all the previous discovery messages. Then Starting up...

Hold on ;) > "ble_time_between_scans": 600.0, So you wait 10 minutes before each BLE scan, which also means there won't be any discovery messages until at least 10, possibly 20...

> "model": "H5075", As I stated above, if this is the device you wanted discovery messages for, you shouldn't have added it to the "discovery_filter" list, as this list contains...

@Ziris85 Thanks for this addition to the discovery filtering. I haven't got the possibility to look at this closer or test it for a few days, just a comment about...

> For the `ADDRESS` the docs state, is that presumably the MAC address of the device? Correct, the white- and black-lists do take the MAC address of the devices making...

> Also I'm thinking that one filter could be used for discovery and messages instead of having a black list, white list, discovery filter. Do you mean that the above...

> Ibeacons discovery filter could be just hardcoded Yes, I agree, iBeacon discovery should be hard coded, just like in OMG. Just like all RMAC defined decoders are. With RMAC...

I'm currently away and won't be able to look at this for a while.

I assume this is the same Shelly Temperature and Humidity sensor for which chrestme is working on creating a decoder for Theengs Decoder [here](https://github.com/theengs/decoder/discussions/553)

Closing, as the ShellyBLU H&T SBHT-003C decoders have been merged into development, and will be in the next release, also currently available in the development builds of OpenMQTTGateway.