Tradfri scene fixes and other cleanups.

[chas-iot]

The Scenes buttons and property on the TRADFRI remote control are functional again. While working through I found a number of cleanups. I sequenced these into a series of commits from most straightforward through to possibly intrusive.

Therefore I suggest that this is reviewed on a commit by commit basis, rather than looking at the PR as a whole.

[mrstegeman]

• 434bb19717ecb475d815c112a31971ba90d3fd2e -- node.onOffProperty is actually still used in some places. That doesn't seem to be the case for node.levelProperty.
• 7fd367b673526effd034b5daf68ef14f8cca69c6 -- type isn't actually used anymore, so this commit will effectively do nothing.
• 8f74bb0c15cf5928e62ad69c6b915e1cf28807c9 -- ditto.

[chas-iot]

regarding node.type, it is still used to build the node.defaultName and node.name see ```zb-classifier

  classify(node) {
...
    // Now that we know the type, set the default name.
    node.defaultName = `${node.id}-${node.type}`;
    if (!node.name) {
      node.name = node.defaultName;
    }

regarding node.onOffProperty - oops, my fail, I thought I searched for this. It still needs a change - if there are multiple endpoints, I assume that the first endpoint should have precedence, not the last.

[mrstegeman]

regarding node.type, it is still used to build the node.defaultName and node.name see ```zb-classifier

  classify(node) {
...
    // Now that we know the type, set the default name.
    node.defaultName = `${node.id}-${node.type}`;
    if (!node.name) {
      node.name = node.defaultName;
    }

Ah, ok. Makes sense.

regarding node.onOffProperty - oops, my fail, I thought I searched for this. It still needs a change - if there are multiple endpoints, I assume that the first endpoint should have precedence, not the last.

Yes, probably the first should have precedence.