@Ben_UK You're right that firmware can be updated, but actually that may not help if the device running the firmware does not have the hardware resources (perhaps RAM) to accommodate the outcome of that change.
Simplistically, from a technical perspective, each room is going to require a certain amount of RAM, NVRAM or other re-writable storage to hold the information required for a room. Let's imagine for a moment that the requirement per room is 1KB per room. The difference between being able to operate 10 rooms and 16 rooms is therefore 6KB more storage. If the device running the firmware doesn't have that extra storage space, then changing the firmware to operate for more than 10 rooms is not going to help, in fact more likely to introduce a bug.
Before anyone tells me that 1KB is tiny, and that modern computers think in MB or GB for storage like this, then I would agree (and I am illustrating the principal, not stating Tado facts). But in the world of micro power consumption (and some of these devices are running for extended periods, operating relays and motors to open mechanical valves and connecting to wireless hubs on a 24x7 basis using just 2xAA batteries) you quickly find that CPU clock speeds, storage devices and other components are working in very different capacities and speeds in order to be viable. The obvious way to solve the problem is to update the hardware platform that is the limitation as a V4 hardware release and allow people such as ourselves to purchase the higher capacity if we require it.
The underlying design question is why some of these things are now not being stored and manipulated in the cloud platform, and then the control devices (receiver) can simply be sent the command signals from the cloud platform for open/close and can transfer data points from the local measuring devices to the cloud platform. In that situation, then some of these constraints start to become much less of an issue or even disappear completely.
@Jurian I assume that the receiver is the device with the real hardware limitations, do Tado plan to increase the capacity of the system in a future hardware update ? I appreciate that the forum is the voice for a comparatively small number of fringe use case "power users", but that doesn't mean that some longer term planning couldn't accommodate these needs, even if there is no simpler answer today.
I would also refer back to some of my earlier comments about PAYG licensing based on features enabled and numbers of thermostats, TRVs and zones being used as a way to fund these kind of use cases.
It looks like you're new here. If you want to get involved, click one of these buttons!