I’ve managed to avoid more complex Ignition setups in the past, but that time is coming to an end.. Disclaimer: I haven’t put much thought into this as yet, just starting to think about it out of hours… We have a project coming up where we’ll be designing an Ignition rollout that involves multiple…

I've got a client running a hub and spoke setup like you described with one hub and 7 spokes. Here's some details on the setup. Network topology: Hub: full-fat Ignition gateway with unlimited clients. This is a beefy instance on a VM as it is connected to every device and will handle as many clie…

Full disclosure I haven't scaled a project to that level but my initial thoughts on it are 100 RTPs on each site is creating a mesh network not a hub and spoke model and you're already on the right track thinking that's not a valid route. Instead I would set up each site as a remote tag provider on …

I would consider having “regional” hubs, so maybe 4 regional hubs with 25 sites each, and then a central hub that connects to the 4 regional hubs (or some sort of mathematical combination of sites/hubs that makes sense). I would also only have one master parent project, all other projects inherit f…

How much data are you talking about between sites? Real time control? Occasional data access for charts/reports? We run a hub spoke with 70+ gateways, mostly for historical data but also for reporting,charts, status, etc. I would not suggest trying to run actual control systems across the network …

Is Remote Tag providers what you really need? Or would an MQTT Broker be the better route. Each site only has to publish a value once rather than deal with potentially a bunch of remote gateways polling.. Also, MQTT makes it so if you are ever performing a major upgrade that has incompatibilitie…

Hi Nick, I would push for a single project and drive your application entirely on configuration. Project inheritance for me has always been a headache (multiple designers, delayed updates, etc) and is the last tool I reach for. For 5-10 gateways the GAN is manageable from a configuration standpoin…

Thanks all for the replies, I will get back to this topic, but currently my focus is on a couple of other projects so I haven't had a chance to look into this any further. I’m interested in looking into MQTT further for this, although I've been scarred by MQTT before with disappearing tags and thei…

Just remember that they disappear. MQTT Engine is NOT the place to do any tag config. Make reference tags in a regular provider and do your configurations/scripting there.

I almost think MQTT could get messy here also. If you have that many clients subscribing to all the tags from all sites, it's going to get messy also. I think the hub and spoke may be better, but use proxy connections where you only connect each site to the hub, and configure each site to allow 2 h…

[image] tgarrison: MQTT Engine is NOT the place to do any tag config To receive buffered MQTT data for history retention if comms drops, I thought this was the only option? We tried everything to get buffered events to come through to the ref tag but nothing worked.

Hub and Spoke Gateway Setup - Sites with Central hub

Ignition

michael.flagler March 30, 2026, 8:55pm 13

See this thread/post where I was able to get it working without using MQTT tags for history.

2 Likes