I'm not sure how Control4 related it is, but Monday morning (looks to be when my number came up) the network got hosed over royal (or at least it seemed that way - only really tried pinging the premiere servers, since the disc vaults were screaming murder.) Power cycling the network devices did nothing, but I managed to go in and update the network settings on the servers to add an outside DNS server, and that appears to have gotten them to behave after they rebooted - before that they'd alternate between responding or not to ping.
SR260 has been stuck in hourglass mode since last night (Tuesday,) but the app works okay (aside from being touch-only,) so maybe there's lingering affect - haven't rebooted the controller yet.
Update: The new Control4 driver for the Strato V from the Kaleidescape website restored Control4 functionality. Apparently, Control4 mistakenly finds a Strato V driver, which in fact, is the C driver. Therefore, as @J.Green indicates, the new kOS Strato V update requires the new driver from the K-Scape website, which is not yet available from Control4.Control4 uses a protocol called "SDDP" to autodetect supported equipment on your network. When Strato V was first released, it advertised itself on SDDP as a Strato C in order to allow existing Control4 systems to discover, connect to, and control the device since a Strato V specific C4 driver did not yet exist.
As of kOS 10.20.0, Strato V now correctly advertises itself on SDDP as a Strato V and thus, the Strato C driver stops working.
The fix is to replace the old Strato C driver with the new Strato V driver (which is can be downloaded from our Support website at https://support.kaleidescape.com/support/article/Control4-Control-System-Guide. The driver is still working its way through Control4's certification process so it is not yet available directly from Control4 but hopefully will be soon.
The new driver also adds support for reporting when you are playing DV vs HDR10 which was not supported with the old drivers and has been updated to check for and use the latest supported version of the control protocol (which the old driver also didn't do).
Last edited: