DigiH
DigiH
More details with the same sending of two successive WRITE commands, with decoded backtrace ``` N: [ MQTT->OMG ]: {"ble_write_address":"AA:AA:AA:DD:EE:FF","mac_type":0,"ble_write_service":"ff02","ble_write_char":"fffb","ble_write_value":"00ff000000000100","value_type":"HEX","ttl":10,"immediate":true} N: Send on /BTtoMQTT msg {"bleconnect":false,"interval":20000,"adaptivescan":false,"intervalacts":180000,"intervalcnct":3600000,"scanduration":10000,"onlysensors":false,"randommacs":false,"hasspresence":false,"presenceTopic":"presence/","presenceUseBeaconUuid":false,"minrssi":-100,"extDecoderEnable":false,"extDecoderTopic":"undecoded","filterConnectable":false,"pubadvdata":true,"pubBeaconUuidForTopic":false,"ignoreWBlist":false,"presenceawaytimer":120000,"btqblck":5,"btqsum":63,"btqsnd":41,"btqavg":1.536585} N: BLE Connect begin...
Hi @BlackEdder0815, Could you set [Advertisement and Advanced Data](https://docs.openmqttgateway.com/use/ble.html#advanced-advertisement-and-advanced-data-default-false-available-with-ha-discovery) to **true**. Then you will get the additional raw undecoded advertising data when your SwitchBot Outdoor Meter is not being decoded....
Also the SwitchBot Outdoor Meter requires to be scanned actively. What is the **BTtoMQTT** key setting for **"intervalacts"**? It is only in this interval (in ms) that the SwitchBot Outdoor...
Then you should really see properly decoded messages every 55 seconds. Please try setting the above mentioned advertising data to true and then post some messages including the advertising data...
Thanks, the manufacturerdata is not taken into account for the decoding, but the servicedata is, and seems to be correctly decoded in your above posting. Are you getting regular decoded...
`"intervalacts":1000 `really is a bit much, trying active scanning every second. This could also be detrimental to the battery life of your devices. Maybe try with something like 15000 to...
Actually my bad! Ignore my previous posts, as the servicedata is only used for the battery level of the Outdoor Meter, but the manufacturerdata should have all the reaming data...
I'm wondering if there have been some changes in 1.7.0 with publishing the manufacturerdata and servicedata together. @1technophile might have more insight on this when he is back for his...
@BlackEdder0815 could you still do another test with the 1.6.0 release? And I assume this is the same behaviour for all three of your Outdoor Meters?