Neil Enns

> I've done some testing here and this only appears to occur when deploying a stack from Git and the Relative path volumes option is enabled - otherwise, a comma-separated...

> I believe that one is fixed in our upcoming 2.20 release Shush!!! Don't get me all excited 😂 This issue I can easily work around in my own code...

With the changes you added to handle ambiguous boards we could. Requires: 1. Building and bundling a nano built firmware 2. Adding the nano board.json

That would work but would mean every nano is ambiguous. ________________________________ From: elral ***@***.***> Sent: Wednesday, November 16, 2022 10:22:27 AM To: MobiFlight/MobiFlight-Connector ***@***.***> Cc: Neil Enns ***@***.***>; Mention ***@***.***>...

Ahhhh right. Would need to report two different MobiFlight type which is weird because they would be identical otherwise. Hmmmmm.

It just seems wrong to ship two firmwares that are identical other than MobiFlight type. This can probably be solved in the desktop side by grabbing all matching boards. I'll...

Thinking about this more on the drive home the Nano is a giant pain. Even if we had firmware that reported two different MobiFlight Type values we still wouldn't know...

Ah, I thought the baud rate mattered when talking to the board after flash as well. Ok, let me go investigate some stuff on the Mobiflight board.json side of things.

Opened a PR to support multiple baud rates in a given board.json file. No idea if it works. Someone with the two different Nanos should try it 😀 https://github.com/MobiFlight/MobiFlight-Connector/pull/1015

@DocMoebiuz This is stale, we should just close it as "never gonna do". Heck, I'd even forgotten I opened it.