I had the question asked if it was possible to change the MQTT Transmitter tag pacing period dynamically, depending on if a user was logged in or not. Going through all the steps in my head, the sticking point would be is that there would have to be some way to script that since it's a Gateway module setting and not in the project itself. Is that setting exposed to scripting in some way?
The reason I'm asking is because I have a project going on where the customer wants to save as much data as possible without compromising usability. We have a Cloud project synced with an Edge Project (using the EAM). The Edge project transmits to a broker, and the cloud project reads the tags from that broker. Changing the tag pacing period from 1,000ms to 3,000ms as well as enabling compression has greatly improved data usage, but we're still using a fair amount, and increasing the pacing period further affects usability of the Cloud application (value changes from the cloud have very high latency and may cause confusion with end users who will type in a value for it to seem like it hasn't changed for several seconds, until the changed value comes back from the edge). I was asked if we could have the Pacing Period be set really high if no one was logged into the Cloud, but then set it to it's default if someone is logged in.
EDIT: I just realized why this wouldn't be a good idea. Changing the tag pacing period triggers a connection refresh, so the transmitter will disconnect and reconnect to the broker when I do that. It'd be a very undesirable experience for a cloud user, because if they were the first one logging in, they'd see a bunch of red for an extended period of time before the data started rolling back into the broker.