Paulus Schoutsen
Paulus Schoutsen
That's not how it works. We request a port, and then we open it with a specific baudrate ([docs](https://developer.mozilla.org/en-US/docs/Web/API/SerialPort#opening_a_port))
If it makes your life easier, you could open a PR first to extract it into a single constant. That would make it configurable later on easier too.
How does this show up in the logs? Do we get a write failure or just a timeout when writing above a certain %? Right now we show a generic...
We definitely should avoid raising any false positives, claiming a device is fake while it's not.
Ubuntu UI will actually run the CLI tools in the background. This is not the case here, it is fully implemented in JavaScript. There is no log output.
We're not using the firmware but are using a bootloader to install the data.
We do show some information in the JavaScript console 
@AlCalzone your explanation got me in the right direction I think. We would always update the value with the info that was in a value notification because we accidentally shared...
Oh well maybe I caught an unrelated bug 🤣
Good catch @kpine. We should add that check to `notification` and `firmware` events too.