v6.0.4

v6.0.4 Fixes a bug with LinkedTypes not using global Constants
v6.0.3 Simplifies the schema for the upcoming Homebridge-UI integration. You may need to adjust your config.json accordingly, but highly unlikely. Sorry for the inconvenience.
v6.0.2 Solves an issue for future homebridge-ui integration and schema display for possible constants. There should be zero affect.
v6.0.1 Resolves bug#116. A day one bug where Cmd4 tried to validate the users state_cmd. This was never a good thing to do.

When Cmd4 was first implemented, I tried to be considerate in allowing either lower or upper case key/value pairs. Unfortunately as Homebridge has evolved and to use homebridge-ui you require a config-schema.json which accurately describes the Cmd4 Schema. This is impossible to achieve when the key/value pairs can be either lower or upper case; Especially when Cmd4 supports so many characteristics and devices.
To this end; Cmd4 Version 6 will be the version that prepares you for the change by Warning you that your config.json needs to be corrected. The duration of this preparatory stage will be pretty generous as I am still working on the config-schema.json integration with Homebridge-ui. I had to stop when it became evident what changes were required for Homebridge-ui integration.

Here are the rules / changes:

1. No script changes are required. Cmd4 still sends: Get/Set < value >
2. Constants are still fully capitalized. i.e. "statusFault": "NO_FAULT" or "category": "TELEVISION"
3. As before Device Types start with an upper case. i.e. "type": "Television"
4. Cmd4 directives and characteristics start with lower case: i.e. "polling": [ { "characteristic": "volume", "interval": 10 }]
5. For advanced devices like the AirCon, Queue types remain the same:
   i.e. queueTypes: [ { "queueName": "MyQueue", "queueType": "WoRm" }]

Finally
I tried to make the warnings very explict for what the correction should be and believe me; I am more sorry to have
to do this than you may think.

Thank you,
John Talbot