Encountering an error in MQTT Engine while evaluating Ignition v8.3. Running the most recent Ignition 8.3.0-beta4 with most recent MQTT Engine version 5.0.0-beta2.
Unable to associate a Namespace Server Set to a Custom Namespace. Same action for Default Namespaces using the exact same Server Set is working correctly, so appears to be isolated to Custom Namespaces.
Red error message that appears within the Add New Namespace Server Set popup is “Invalid reference: ‘[Namespace]’”
Hi,
I checked this on Ignition 8.3.0-beta4 and Engine 5.0.0-beta2 both by adding the set directly in the custom namespace wizard and by editing the custom namespace and it appears to work ok:
However, I know this was an issue in previous versions. Can you tell me if you did anything special to come across this?
Thanks,
Segan
I don’t think I’ve done anything special. The server was upgraded from 8.1 and did have MQTT Engine configuration working correctly. Have applied 8.3beta1→8.3beta4, and had Engine 5.0.0beta1→5.0.0beta2 (same fault in beta1, but figured I’d give it some time before reporting).
I deliberately upgraded rather than installing a clean 8.3 from scratch, to evaluate whether there might be migration issues - maybe something related? I haven’t yet attempted a clean install. I had a # wildcard in the namespace subscription, but doesn’t seem to change anything with/without it. While it was an upgraded system, I have since removed all the servers/sets/custom namespaces and rebuilt from scratch. I can also confirm that servers are connecting and I can do arbitrary publish commands via scripting.
Even with a brand new set with no servers associated still seeing the same thing - Default namespaces happy to add it, Custom gives the same error.
Thanks for the extra info. I tried it out by upgrading rather than a clean install and Engine actually didn’t upgrade successfully, though there were no error messages. Can I have you double check your modules page and confirm if it says you’re on the most recent Engine version? For me, the version there remained 5.0.0beta1 despite having gone through the upgrade process.
I failed to check the version had actually changed in the modules page. That indeed was the same problem, was stuck on beta1 despite having attempted the upgrade. Now behaving as expected.
For anyone else following along, MQTT Engine configuration is retained despite the uninstallation of Engine. So at least it’s not going to result in lost config if this needs to happen in a production environment, but hopefully root cause of whatever is responsible for upgrading modules to not work can be addressed before exiting beta.
Thanks for the help. Good job identifying that, could have wasted a bunch of time not realising the new version hadn’t actually applied.
