plain WSS only bluetooth device not supported

[karlp]

Scale name
non-existing at this point, in development.

I've got a "compliant" bluetooth WSS service, that notifies me of weights with timestamps, and as best as I can tell from https://github.com/oliexdev/openScale/blob/master/android_app/app/src/main/java/com/health/openscale/core/bluetooth/scales/StandardWeightProfileHandler.kt#L98-L103 it should not require the user data service or time services.

NRF connect recognises it as a standard weight service and decodes the weights correctly, so I'm 99% sure I've got the WSS portion correct, are the user data and time services really required?

Still, openScale 3 just reports "not supported" for this device. The debug log contains... nothing? there's just "17 devices found, scanning stopped"

[karlp]

I re-read the WSP document, and found that the Device Information Service is required for the weight scale role, and added that, but openscale, still shows my scale as "not supported" Not really sure what else is required?

[karlp]

For comparison, I tried out the https://github.com/espressif/esp-iot-solution/blob/master/examples/bluetooth/ble_services/ble_wss/ demo, and it is also well recognised by nrf connect as a standard weight scale, but neither openscale, nor any other app I've found recognises it.

[oliexdev]

For guidance on how to add a new scale handler into openScale, see the updated wiki page: How to support a new scale

[karlp]

I'm 100% trying to not add a new scale, I want to make my own scale behave "correctly" as far openscale's Bluetooth SIG's Weight Scale Service and Weight Scale Profile behave. I believe I've implemented it correctly, and nrfConnect will happily decode the weights, but openscale simple doesn't recognise it. Do you have any guidance on what "extra" sees to be required? I can follow the kotlin code, and it only expects the WSS and DIS and CTS services, but it doesn't even get to that point, it seems to not like something in the advertising packets?