So I totally agree with garthb on this one. Since I started astrophotography in 2015, ASCOM was the only choice I saw and I jumped to a network solution that same year (same reasons as garthb)… then I noticed how bad ASCOM itself was in doing that. If I want to control it via my Raspberry I need something like USB-to-IP running on it so ASCOM thinks it’s connected locally (requires a super stable connection). The only other way is to run Windows on a bigger, way more expensive, computer at the telescope and then remote desktop into it… personally I found it all a bit of a messy solution. More overhead on the network and just not as nice and stable as a dedicated client-server solution. Bonus is that I can use Linux on the Raspberry, which is also made for networking from the ground up, rock solid and never restarts for updates or so. Other bonuses are that the drivers are open-source, or at least most of them and you can write your own, granted that may be a stretch for most, but at least I can do it. With ASCOM I was having to go with drivers the companies made and some were just buggy, I almost had to buy another device just to get a better driver which I thought was a bit nuts. So I switched to INDI. Yes it was still a bit buggy back then but development is going incredibly fast, I would say that now everything is pretty stable and I’m making mosaic schedules without much effort. I still love SGP itself so to have that for INDI would be amazing.