This is indeed odd behaviour and one which SW support may want to see, as the configuration is not a common one.
I would replace the local Job Engine cache files, to see if these are holding legacy polling tasks - Replace Job Engine v1 and Job Engine v2 SDF Files - SolarWinds Worldwide, LLC. Help and Support
Also as you have reviewed the Nodes > EngineID value and confirmed these are correct for the AllEngines (this is v11.5.3) table, I would suggest a review of the subscriptions table to see if anything in their is referencing old engine assignments.
Be interested to see how you get on.
Installation | Consultancy | Training | Licenses
Thanks for the reply. I hadn't tried replacing the SDFs so I tried it and I noticed that the Job Engine folder didn't have a Data directory. I was hopeful this was the problem so uninstalled and reinstalled the app and now I have the Data folder but unfortunately it didn't solve the problem. It probably fixed another problem though. I had already tried clearing the PendingNotifications, Subscriptions and Subscription Tags but I didn't stop services before doing it. It didn't work either so I stopped and disabled all the services on the polling engines and cleared them from the database again. Unfortunately, the polling engine is still polling the wrong devices. I have a case (00151195) open with support and I'm waiting to hear from an Application engineer.
I talked to SolarWinds and we tried uninstalling the JobEngine, JobEnginev2, Collector and Information Service on the polling engine with the issue and it seems to be working fine. The Uninstall/Reinstall was done through an elevated command prompt. Thanks for the help Mark!