Sorry for the Custom Namespace reference. This does not apply for Sparkplug messages. I see you are using Sparkplug sending from Ranger?
I don’t believe there are any videos, but we have tutorial pages.
Getting back to the provider issue, I am at a loss as to why you’d want another separate Tag provider? All incoming messages coming into Engine hit the MQTT Engine Tag provider. My original answer did not get to that either but as your question is for Sparkplug, not MQTT messages the answers can get complicated, have caveats and need clarification.
You can create another Realtime Tag provider and create reference Tags from the MQTT Engine Tags. IA likely has a video for creating that Realtime Tag provider and those Reference Tags.
But I wonder the need for the separate ‘pump’ Tag provider?