Hi, I've been meaning to post an apparent bug I've reproduced over and over. It has to do with GATT read, I know it's experimental on android, but the read actually works eventually.
Attached is a screen recording. I have an esp32 constantly emitting a value, its service and characteristic uuid are hardcoded, the value itself is updated every second, there's no other signal consumer hogging the connection.
Every time I take a reading, the shortcut to the flow instantly fails (NO from the GATT block). Starting the flow from inside the gui has the same result.
If I then just go into the flow, edit the GATT block, select the device with the same 2 uuids again (i.e. changing nothing), and save the flow, then suddenly it works... until next month when I have to do the same thing again, changing nothing but just saving the flow again.
I'm kinda puzzled tbh, it's like an initialization issue. Does the GATT read block not init the bluetooth stack while the device picker does, or something like that?