The domoticz update script (quite reasonably) uses the value returned from running
uname -m. The Vero4K returns a value of aarch64, whereas the Pi returns either armv7l or armv6l, depending on architecture.
Unfortunately, the value of aarch64 returned by the Ver04K is positively unhelpful since all userland applications should be either armv6l or armv7l. Similarly, we cannot use
setarch armv7l on the Vero4K because it doesn’t recognise it as being a valid architecture:
osmc@osmc-4k:~$ setarch armv7l uname -m
setarch: armv7l: Unrecognized architecture
osmc@osmc-4k:~$ setarch --list
and prefixing the command with
setarch linux32 also doesn’t help, with
uname -m returning a value of armv8l that setarch doesn’t recognise:
osmc@osmc-4k:~$ setarch linux32 uname -m
osmc@osmc-4k:~$ setarch armv8l uname -m
setarch: armv8l: Unrecognized architecture
Unless you really want
uname -m to return a value of aarch64, it might be better to create a wrapper on the Vero4K for /bin/uname, much like you do for apt-get.