Connecting to WeDo SmartHub: no characteristic found about pylgbst HOT 7 OPEN

You may also want to try with different underlying BLE library. Specifically the bleak looks the most stable today. Maybe it would behave differently.

from pylgbst.

Hi,
It looks like WeDo type of hub has some different identifiers of hardware. These identifiers are hardcoded here:

If you know the right values, you can override those in the beginning of your script. That would require some experimenting and researching, not too easy.

from pylgbst.

Wow that was quick, thanks for your answer! I will check if Dr. Google can find if anybody has cracked the UUID for the WeDo hardware, otherwise I guess I will try another route. Thanks @undera !

from pylgbst.

Mmh, weird the docs in https://github.com/LEGO/lego-ble-wireless-protocol-docs seem to indicate that WeDo 2.0, Boost and Train share the same hardware UUID...

from pylgbst.

Ah, found it in https://github.com/pybricks/technical-info/blob/master/assigned-numbers.md: 00001523-1212-efde-1523-785feabcd123

from pylgbst.

Mmh, now it times out with

5432    DEBUG   pygatt.backends.gatttool.gatttool       Sending cmd=char-write-req 0x0f 0100
35483   ERROR   pygatt.backends.gatttool.gatttool       No response received

(bleak not working for me on a raspi 3)

from pylgbst.

This is nice that you have some progress. I would do experiment using a regular computer, to remove potential problematic chain for experiment.

from pylgbst.