New version of custom capability - not installed on the hub

[nayelyz (SmartThings Developer Support)]

@Davec

new version of a capability does not get seen by an edge driver on the hub?

By a new version, do you mean if you changed the capability’s attribute or command name, or added more of these elements?

People used to comment in this thread on new issues they found:

SmartThings Edge Developer Beta | Known Issues and Bug Tracking

This is a list of currently know limitations, issues, and bugs related to the Edge Drivers platform: Installing Drivers There’s an auth problem with in the live logging system. If you see a 403 error when running the logcat CLI command, change the “Location Mode” (Home/Away/Night by default) of the location your hub is in, this will force a resync of the same message to the hub containing your account’s auth verification information. Device Automation Driver-based devices do not work with Groovy SmartApps, including SmartLighting. Drivers do support Rules as automatons in the App or via the API, or Endpoint Apps. Device Discovery When a device is discovered it does not pop up in the app as having been discovered. For now watch your driver logs and back out of the discovery pages…

But I don’t think the main list is being updated.