FYI: Text sometimes work when calls don’t. Text use much less bandwidth.
Sure.... but.... not all municipalities let you text 911. And with the way modern phones are being implemented with VoIP+LTE and iMessage/RCS and some of the very exciting failure modes of modern networking... I'm having a very real concern that even if my municipality lets me text 911 (I don't remember offhand but I think mine does) that if I actually needed to dial 911 under relatively prosaic emergencies like a silly little power outage, I might be out of luck.
IoT devices are, to be quite honest, a shitshow. Where your Sovol counts as such.
Either the device needs to call upstream to get updates or it's going to ship with a security bug that can be exploited. Or, in may cases, it'll have an unpatched security vulnerability and it'll call upstream to get updates.
It costs money to keep the necessary cloud infrastructure in place, both in terms of hosting costs as well as devops time. Either they will eventually need to brick the device, leave it unpatched forever, charge you some maintenance fee, go bankrupt, or fund the whole thing by selling your data.
It's not hard to write a bot that would scan for signs of a Sovol printer, try the default SSH password, and do nefarious things. And people are generally really bad about the default SSH password regardless.
There's not really a good answer here for IoT devices. There's not even a really great answer for home brew IoT devices with the thing where Home Assistant's reverse-tunnel service had a nasty vulnerability that let you remote HA instances.
Aaand.. IPv6 is great. But unfortunately the way things are now means that giving everything on your network a publicly routable IPv6 address is a very bad idea.
Klipper provides a lot of protections but all of that hinges on the microcontroller, so presumably an attacker can upload a substitute firmware using the update mechanism that would go full send on the heaters, which has the potential to actually melt some things.
The problem is that if you want Klipper, you need a full Linux. This is not actually a problem for the Klipper devs, mind you, because they wrote a cool tool for people comfortable modding their printers and only BTT and Obico sponsor Klipper. This was a lot less of a problem when we were talking about Marlin printers. Except that if people weren't using Klipper, it's just too damn easy to write a two-piece controller software in the same fashion of Klipper and get the expediency of writing code in Linux instead of in an os-less microcontroller.
tl;dr: there is no safe way to buy a printer with klipper on it, it just looks like it works right now.