Replies: 3 comments 4 replies
-
|
OK, I just downgraded bleak to 0.19.5 and now I can consistently get the hub name again, so it seems to be something with bleak 0.20.0 |
Beta Was this translation helpful? Give feedback.
-
|
Fixed in pybricksdev v1.0.0-alpha.41. |
Beta Was this translation helpful? Give feedback.
-
Which hub and which firmware version? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Up until now, I've relied on the bleak device "name" property to find and store names for discovered hubs. This worked every time to get the name I define in the firmware install process.
Today, I upgraded my hubs to the latest firmware on master (+ frozen module), and this has become very unreliable. It seems that the name property now pretty much is always
Noneexcept for some very few exceptions, where the expected name comes out. It happens so infrequently that I have not managed to reproduce it in isolation.Output
Connecting to a device discovered using
find_device(name)still works as expected though.Has something changed about device discovery? What would be the recommended way right now to discover the pybricks name?
Also, I've been wondering for a while, it doesn't seem that the bluetooth address changes at all for my hubs, wasn't a random bluetooth address implemented a while ago? Even when removing the battery, the bluetooth address seems to stay the same. See: #600
Beta Was this translation helpful? Give feedback.
All reactions