parse min/max/step values for thermostats
use this/bind instead of that
added genericType ignore
added batter state charactersitic
preliminary thermostat controll mode
use new characteristic.setProps() method
some minor cleanups
Instead of matching with a regex, we use a config of supported device
types to attempt to load in. This allows the user to whitelist just the
ones they want to add.
LightwaveRF lights could not be dimmed properly as they require a dim level
of betwene 0-32. The Domoticz documentation incorrectly states this should be
0-16.
Other devices may use different values which is why the MaxDimLevel property
should be used rather than hardcoded value.
Also refactored the code slightly.
Apparently, if TargetHeatingCoolingState is not writable, you can’t add
a thermostat to a scene. This fix makes it writable from HomeKit, but
it still always remains set to HEAT.
Cleaned up some more old cruft, added config-sample.json entry, and now
there’s a different default grouping of characteristics, which makes
for more optional characteristics on fewer services. The older behavior
(more services per accessory) can be switched on in config.json. The
new default works better in Eve, other clients not so much.
* 'master' of https://github.com/nmelo/homebridge:
[MiLight] Swap cooler/warmer direction for white bulbs, and add note about delay
[MiLight] Update config-sample.json to replace MiLight accessory with MiLight platform
[MiLight] Add missing callback from hue function
[MiLight] Modify logging to show the zone name when used as a platform accessory
[MiLight] Converted accessory to platform. Not fully tested yet
