Add versioning to cache so cache can be refreshed when node/value changes

Is your feature request related to a problem? Please describe. In the upgrade to zwave-js 7.0.0, I learned that I had to clear my cache so that zwave-js could rebuild it with the v7 schema since we no longer reinterview every node on startup.

Describe the solution you’d like It would be great if there was something like a cache version, where if you install a zwave-js version that uses a different cache version from the existing cache, the cache gets wiped and recreated. If the version isn’t specified in the cache (for caches created before this change), assume version 0, and make zwave-js 7.0.0 use version 1.

Describe alternatives you’ve considered Manual rebuild is the only option I am aware of currently

Additional context Add any other context or screenshots about the feature request here. If you want to propose an API, share your thoughts how it could be used (syntax).

[AlCalzone]

That’s because it was migrated before #2107 😃 You’ll still get protocolVersion: 4 for some newer devices.

[raman325]

OK fair enough. Just an FYI, protocolVersion got migrated but it reflected the old version (in my case it was 4 which is invalid for the enum) until I wiped the cache and started fresh.