Do you have HPM 1.9.3 shown in top right corner on main page?
Older versions of HPM have issues with the current hub platform and code will be duplicated.
Also FYI the latest "Home Assistant Device Bridge" App shows 2.15 as the newest change in the changelog in the code. The last 2.16 release may have not had any changes to the app itself. Code is here and has not changed for 2 months: HE-HA-control/haDeviceBridgeConfiguration.groovy at main · ymerj/HE-HA-control · GitHub
I also did confirm the packageManifest has a possible problem. However it looks like it has been this way for 4 years. This issue can cause Match Ups to go wrong and result in duplicated code.
Notice the name here. This is SUPPOSED to exactly match the name of the app in the code. The match up works by matching the namespace and name.
Here is the actual app code:
Name is not the same. So what this can do is cause the MatchUp to not detect this as being part of the package. So when you run the match then update it will install a new version of that code, not updating the original.
The dirty fix is to first Unmatch in HPM, then edit the name in your in-use code to match the manifest. Then run a matchup again. This should make it match that code to your existing install. Now if you repair or Update it should not create a duplicate. At this point it is matched on the UID number of the app code so it will retain that match even if the app name changes (as long as you don't unmatch it again).
@ymerj There is a fix for this which could be applied to the manifest. There is an option for alternate names in case you rename an app or driver. So you could either fix the name in the manifest and add the old one as an alternate, or add the current app name as the alternate. I could mock up an example if needed. The alternate name is not well documented but I have it in my ZEN17 driver package. Hubitat/packageManifest/zooz-zen-relays.json at main · jtp10181/Hubitat · GitHub
