Do wildcards not work in Event Streams Tag Event paths for remote tag providers? Individual tags work OK, multiple fully expanded tags work OK, but introducing a wildcard ends up not firing on any that did work with the full path. Trying to use wildcards as I'll likely end up with a couple hundred matches that I don't want to have to manually maintain when a change is made at a remote site.
Replicating the same data using MQTT Transmission and then pulling it via MQTT Engine, the same Event Stream is happy to accept the equivalent single * or double ** pattern, just using the [MQTT Engine] provider. So that kind of leads me to thinking it's a remote tag provider problem.
I can't see anything described in the docs to differentiate behaviour on provider type. And can confirm both gateways are running the current 8.3.6 Wildcards in Tag Paths | Ignition User Manual