There definitely is a way, but right now I’m not sure if there’s an easy way. If there is an easy way, it looks like Inovelli’s current driver code should remove that notification child device if you un-set all of the preferences for that particular notification (color, level, effect, and duration), though I haven’t tested that (I don’t use Inovelli’s custom drivers) and don’t know if Hubitat will truly let you un-set a preference and let the driver actually work in that way.
If not, you could switch to Hubitat’s generic “Device” driver and run one of the commands there that will clear all child devices. (I think this is coming in 2.2.4, so if you’re on 2.2.3 or earlier, you might not see it yet, but maybe soon!) However, this would delete all child devices; you can’t choose specific ones. That may or may not be a problem for you.
If nothing else and you’re using (or could use) a custom driver, the code could be modified to just delete specific child devices based on their DNI, perhaps most easily as something that will run when you save the driver (like
updated()), then removed so as to not continue to cause this in the future. If it comes to that and you’re not Groovy-versed, I could throw together a quick mod. But hopefully one of the above helps (or will soon)!