1.0.2

• Added ability for temperature sensors to use ANY device that has a state named "temp", "temperature" or "Temperature", this opens up compatibility to a large number of plugins and sensors that use this state name without having to support those plugin individually. As a result, direct support for certain plugins was removed if they had been coded to use the "temperature" or "temp" states, such as wunderground.wunderground, piBeacon.i2cTMP102, piBeacon.i2cBMExx, piBeacon.i2cMS5803 and fantasticwWeather.Weather (these devices should continue to work just fine but no longer need special integration).
• Added ability for humidity sensors to use ANY device that has a state named "relativeHumidity", "humidity" or "Humidity", opening up compatibility to any plugin device or sensor that uses this state name without having to support those plugins specifically. As a result, direct support for certain plugins was removed if they had been coded to use one of these states, such as piBeacon.i2cBMExx, fantasticwWeather.Weather and wunderground.wunderground
• Added ability to change color using the color temperature wheel in Home. Strictly speaking, color temperature is a color from white to orange (and this is how the Hue app sees it and then how the Hue app deals with it when it integrates into Home), therefore when you use the color temperature wheel it will set the color from white to orange, if you want actual colors then you use the color wheel instead. Confused? Yea, it is confusing.
• Added some UI adjustments to pretty up the UI a little
• Added color support for ALL Indigo dimmers that support color
• Removed Hue specific support in favor of generically supporting all color bulbs
• Fixed minor issue where if debugging level had not be specified (since it was added late in beta) that it will now default properly instead of showing an empty field
• Changed behavior of the HomeKit name field so that each time a device is changed it will change the HomeKit name to match unless editing an existing item, in which case the HomeKit name will not change unless done so manually
• Changed the UI button "Add to HomeKit" to "Save Device" so that it better represents the action to take when both adding and editing a HomeKit device
• Changed Speaker description to "3rd Party, Mute control in Home, Full Siri" because HomeKit updates since HomePod have allowed this device type to be used by Home but only in a mute/unmute capacity but no volume control. Volume can still be changed via Siri.

1.0.2-beta.3

• This should wrap up the changes for better supporting color in 1.0.2 and, pending any problems with the color operations, means that once the UI is wrapped up then 1.0.2 will drop and 1.1.0 will be getting worked on (yes, 1.1.0 is already in the works and has some cool new features)
• Added ability to change color using the color temperature wheel in Home. Strictly speaking, color temperature is a color from white to orange (and this is how the Hue app sees it and then how the Hue app deals with it when it integrates into Home), therefore when you use the color temperature wheel it will set the color from white to orange, if you want actual colors then you use the color wheel instead. Confused? Yea, it is confusing.
• Fixed an issue where brightness controls were incorporated into the color setting (which they are when setting the RGB values of a light) and as a result that meant that changing brightness in Home didn't actually change the bulb brightness, this has been restored to the pre 1.0.2 setting of brightness changing brightness as normal when using an RGB light

1.0.2-beta.2

• Fixed issue where a color supporting bulb that does not support RGB would cause the plugin to error (note, right now only RGB capable bulbs are supported)

1.0.2-beta.1

• Added some UI adjustments to pretty up the UI a little
• Added color support for ALL Indigo dimmers that support color
• Removed Hue specific support in favor of generically supporting all color bulbs
• Fixed minor issue where if debugging level had not be specified (since it was added late in beta) that it will now default properly instead of showing an empty field
• Note that this beta release has some UI annoyances because it is being released to test color bulbs before the UI changes have been completed
• Note that this beta release does not fully support changing color temperatures via HomeKit, only colors themselves

1.0.1

Version 1.0.1

• Added native ability to use Dave's amazing new Fantastic Weather device as a temperature sensor (current temp) or humidity sensor (current humidity)
• Added native ability to use Fantastic Weather Forecast device as a temperature sensor (todays high) or humidity sensor (todays humidity)

1.0.0

• Official release, now out of beta and will be available in the Indigo Plugin Store
• Added ability to use Device Extension Conversion Extension devices as temperature sensors, air quality sensors, CO2 sensors, CO sensors, contact sensors (when boolean), fan devices (when boolean), faucets (when boolean), humidity sensors, leak sensors (when boolean), lightbulb (when boolean), light sensor, motion sensor (when boolean), occupancy sensor (when boolean), smoke sensor (when boolean) or switch (when boolean)
• Enabled Plugin Store update checking when the plugin starts and at 10am each day
• Fixed bug in the excluded device management that would throw an error and not populate the excluded items list if any of the excluded items had been removed from Indigo

Version 1.0.0 Release Candidate 1

• Final fixes for SenseMe fan/light support (Issue #97)
• Adjusted acceptable value range on Heat and Cooling set points to allow for wider changes (Issue #97)
• Added automatic server restart if the Homebridge debug option is changed
• Removed Simulated Device Dump from plugin actions (still remains in device actions) in Advanced Plugin Actions menu since the recent changes have rendered that somewhat inoperable
• Removed 'use new library' option from plugin config until needed again
• Removed 'performance options' from plugin menu as it is no longer needed
• Removed 'development testing' from plugin menu in preparation for release
• Changed Homebridge debug checkbox in the server advanced options to a combobox that will allow the user to debug Homebridge-Indigo, Homebridge server, neither or both to allow for a full comprehensive debug if there are issues that require seeing what Homebridge is doing
• Changed server device re-caching to only happen when the included devices or actions are changed in a server rather than on any properly or attribute change
• Issue #99 resolved
• Issue #97 resolved

Version 0.23.1 (Beta 23.1)

• Fixed bug in SenseMe support where fans and lights were not populating their HomeKit characteristics
• Updated Homebridge-Indigo2 to 0.2.4

Version 0.23.0 (Beta 23.0)

• NOTE As stated earlier, the entire HomeKit engine is being optimized and rewritten for various reasons. There is a new plugin configuration option that allows you to revert to the previous method if the new method is causing problem, but this is on a release-by-release basis, meaning that only changes in this release will roll back to using the old methods, the next release will not be able to roll back anything from this release. The functions impacted will be noted in the release notes as 'Library Change'. Please report any issues that are caused by the new library that are resolved by returning to the old methods. Each revision will re-enable this option automatically if it gets turned off.
• NOTE All minor revisions can still be rolled back for Library Changes until the next full beta version is released
• Removed all functions that were moved to the new package (Library Changes) made in the last three releases, they are now a permanent part of the plugin
• Added support to independently change heat/cool set points in HomeKit and have it translated properly to Indigo (Issue #97)
• Added experimental support for SenseMe fan/light level custom min/max pass-through (Issue #99)
• Added debug checkbox to advanced server parameters to enable debug logging in the Homebridge server
• Fixed bug in device actions where the device ID could not be acted upon, resulting in 'invalid literal' messages when trying to 'Delete', 'Delete and Hide' or 'Delete and Exclude' as reported on the forum thread by spiv and thread by srkindard, this was neglected in the move to change how the plugin references devices in the UI in preparation for complications
• Updated Homebridge-Indigo2 to 0.2.3
• Issue #99 partially addressed
• Issue #97 resolved (pending testing by end users)

Version 0.22.2 (Beta 22.2)

• NOTE As stated earlier, the entire HomeKit engine is being optimized and rewritten for various reasons. There is a new plugin configuration option that allows you to revert to the previous method if the new method is causing problem, but this is on a release-by-release basis, meaning that only changes in this release will roll back to using the old methods, the next release will not be able to roll back anything from this release. The functions impacted will be noted in the release notes as 'Library Change'. Please report any issues that are caused by the new library that are resolved by returning to the old methods. Each revision will re-enable this option automatically if it gets turned off.
• NOTE All minor revisions can still be rolled back for Library Changes until the next full beta version is released
• Added changeMinMax parameter to API JSON payload to notify HomeKit that min or max values need to be changed from the HapNode defaults
• Added failsafe to prevent any CameraRTPStreamManagement services from attempting to contact Homebridge when there is an update - this should never happen anyway because no camera states are monitored but this was added as an extra measure in case something slips through for one reason or another, particularly since Homebridge-Indigo2 wouldn't know what to do with it since it's Camera-FFMPEG handling camera integration
• Changed UI form so that editing is a true edit rather than a remove-edit-add method, this allows a device to be edited in the plugin and not lose it's room or scene assignment in HomeKit as a result of an ID change
• Changed simulation output to be formatted for easy copy-and-paste to both the Indigo forum and Git so that it appears properly as a code block without any additional editing so long as the user reads the instructions also added to the output
• Changed watched-for states from Nest thermostats to be more inclusive and to better trap Nest changes. Because Nest can update every 10-30 seconds it had to be specifically filtered because it causes far too much unnecessary activity otherwise
• Library Change: Moved HBI2 API calls to new factory package
• Homebridge-Camera-FFMPEG updated to 0.1.8
• Homebridge-Indigo2 updated to 0.2.1 (implements POST method added in 0.22.1)
• This release may help with issues where servers disappear from the live HomeKit config or become unreachable
• Fixed bug in Homebridge Buddy migration where model and firmware fields were not being populated in the migration, causing the server to crash during the JSON population and that was then causing Homebridge errors because it wasn't complete and the ID wasn't being passed