hass(improvement): stop specific values from populating

[varet80]

Some values cause too much chatter in Hass, we remove these from discovery populating

[coveralls]

Pull Request Test Coverage Report for Build 596251330

• 8 of 13 (61.54%) changed or added relevant lines in 1 file are covered.
• 12 unchanged lines in 1 file lost coverage.
• Overall coverage decreased (-0.02%) to 19.152%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
lib/Gateway.js	8	13	61.54%

Files with Coverage Reduction	New Missed Lines	%
lib/Gateway.js	12	20.07%

Totals
Change from base Build 596224557:	-0.02%
Covered Lines:	2022
Relevant Lines:	10831

---

💛 - Coveralls

[robertsLando]

I prefer to move the check in discoverValue function

[varet80]

wouldn't that iterate all values and just return, instead of stoping earlier?

[robertsLando]

@billiaz discoverValue could also run 'on fly' and in that case this values will be discovered because you rely on the filter done by the prioritized cc function.

[zwave-js-assistant]

🚧 It seems like this PR has lint errors 🚧

I should be able to fix them for you. If you want me to, just comment
@zwave-js-bot fix lint

[varet80]

@zwave-js-bot fix lint

[robertsLando]

I like this but for now there are much other cc we are ignoring, IMO this check should be done inside the CC switch-case, like if(property === x || property === y) return

[aretakisv]

thought of. looking if we have second class, otherwise i will move it under. the idea was to cover all

[robertsLando]

With zwavejs 7 deltaTime and previous value will not be available anymore so this can be closed