I have had a Blue Charm BC021 for several years and it is working fine with Open MQTT Gateway and the “BT: Publish Only Sensors” enabled. I ordered a second one the other day and it does not show up when I set it up like I did the first on. If I disable “BT: Publish Only Sensors” this new Device seems to show itself in MQTT Data as a BC021 Pro instead of a BC021 though I ordered the same device. I also noted that they both require different KBeacon Programs to configure them. The old one uses KBeacon, and the new one uses KBeacon-Pro. Neither Device will work with the other App. My original device MAC Starts with DD:34 and the new Device works with DD:88.
Can I get this new device to work with the “BT: Publish Only Sensors” enabled?
Can you leave BT: Publish Only Sensors OFF and also turn ON BT: Advanced and Advertising Data, and then monitor and copy and paste a few of its MQTT messages here, which will now contain the undecoded raw servicedata.
I can then see if it can be easily be included in the decoder, or if it might need a few more raw data MQTT messages along with the current details from the native app.
Not quite as straightforward as I hoped for as the KSensor Pro 0xfeaa servicedata now includes its Bluetooth MAC address in reverse, which the standard BC021 didn’t have, and there is also an additional second 0x2080 servicedata.
Could you post another message sample as above, but with the temperature, accx, accy, acc and volt and/or battery level data as show in the KSensor Pro app at the same time?
As mentioned in my first post the two different Blue Charm devices use different KBeacon Apps. The original device can be accessed with the KBeacon App. When connected I can see the temperature, accx, accy, acc and volt and/or battery level data in the KBeacon App. However, when I connect the new Pro-version device with the KBeacon Pro I cannot seem to see the accx, accy, acc, etc in the MQTT Explorer. There appear to be 6-Slots presented for different “Adv Type” in the New App for the New device which can have different configurations for KSensor, iBeacon, UID , TLM, URL and System. Looks like several can be enabled at one time. However the options for the slots appear to be different from one slot to another. When I enable KSensor in some of the different slots I see the accx, accy, acc, etc in the KBeacon Pro app on my phone but not in MQTT Explorer. Kinda confused so I will look at it later today and let you know what I find. Hoefully I can figure it out….. I added some screenshots from the KBeacon Pro App on my phone……
So, I have done quite a bit of testing with the new the BC021, the BC021Pro, the KBeacon Apps, and MQTT Explorer. After several hours of trying to configure the BCP021Pro I have found no way to get the accx, accy, acc, etc to be visible in MQTT Explorer though it is visible in KBeacon Pro as shown in the previously attached images. I also verified that I am on the latest version of MQTT Explorer. TOtally confused at this point. If you have any other suggestions on how to get you this info I am willing to try. Thanks!
as the KSensor Pro 0xfeaa servicedata now includes its Bluetooth MAC address in reverse, which the standard BC021 didn’t have, and there is also an additional second 0x2080 servicedata.
