I have a balenaSound application running on a Pi 3. I wanted to incorporate my Zero W to the same application, but the Device type list only shows the Zero W v2, and mine is a v1.1. I’m wondering if this is related to the issue described in this GitHub thread (Pi zero W missing from device list · Issue #47 · balenalabs/balena-sense · GitHub), or if I’m just doing something inept? I really just wanted to add an additional device and I’m not using this Zero W (with Adafruit Audio Bonnet) so thought I’d use it here. Thoughts, suggestions?
I just checked with some of my fleets - and your assumption is correct.
If you built your fleet for something better than the RPi1 platform, you won’t be able to add RPi Zero W (1) to it. due to this issue.
Easiest thing would probably be to open a second fleet, build it for RPi 1 and then migrate the other device to this as well. I guess.
Cheers
Ugh. Would this be considered a bug or a feature? Perhaps at least a big flashing note could be added to the “before you begin” notes. And a word about the Bluetooth/WiFi interference on the Pi3 would help as well. Knowing these things before a deployment can save a lot of frustration on the part of neophytes like me.
I cannot really answer that question, maybe @Marc or @dtischler can help you.
You maybe could create an RPi 1 fleet and add the RPi 3 to it afterwards (because the application would be build for ARM 32 bit then, which would run on both platforms) - but I don’t know if Wifi on the RPi 3 would work then. Mixed fleets are possible, but when the RPi generations / hardware drift too far away from each other, it becomes problematic, hence balenaCloud does not let you checkout an RPi 3 image which will not work on RPi Zero W.
So my takeaway is that these builds don’t really have a distinct “OS layer” and an “app layer;” these are kind of unified. The entire build has to be able to run as a unit on the architecture that you’re targeting, or it’s a no-go. I can live with that, if that’s what it is. I just didn’t realize that, going into it! It’s all experimentation for me anyway, so perhaps this live-and-learn approach will serve me well. 
Hi @k9gardner, Nico is correct, you can’t add that Zero W 1.1 as you likely have a 64-bit Fleet, and that Zero W 1.1 won’t support the containers that were generated during the Release build. With that said, you can work around it by sticking with 32-bit as Nico suggested…however, just a word of caution: Over the years, as balenaSound has grown, added features, etc, it has become more and more difficult to run on a Pi Zero (1.1). You will want the absolute fastest SD Card you can get, and even then, you might experience stuttering and buffering, as the CPU is basically maxed out while running balenaSound. They are single core devices, unlike the quad-core on the Pi 3 or the new Zero 2. Hope that helps, thanks!