Version 0.16.1 (Beta 16.1)

Release Notes

• NOTE: Due to a fundamental change in temp control you will need to edit all of your sensors and thermostats on any of your HomeKit server devices and determine if the new "Temperature value is Fahrenheit" needs to be checks so the plugin knows to convert it to Celsius. It's possible that when you add a temperature sensor or thermostat to a server that didn't have it yet that you won't see the checkbox, I believe this is only because it's an existing server, if you add it and there is no checkbox it'll be there when you edit that same item. I haven't fully tested setting the thermostat temperatures from HomeKit and I'm almost positive it won't work properly unless you are using Celsius for your thermostat so don't try to change your thermostat heat or cooling set points in this release if you are a Fahrenheit person. This release is mostly about fixing the temperature readouts and the next will fix that bug (that I didn't think about until I was releasing this version).
• Added checkbox to UI to indicate if a thermostat or temperature sensor temperature is in Fahrenheit so that it can be properly converted on a device-by-device basis
• Added new Advance Plugin Device Action to Simulate HomeKit on Server. This is different than the Plugin version that lets you simulate any device in Indigo, this specifically uses the settings for an item on a server, so you can test how a device you have already set up is being reported back to HomeKit rather than just testing a device that has not yet been sent to HomeKit too see what it'll do
• Changed how temperatures are converted, they will no longer rely on the server setting for temperature but rather on a device basis, meaning that the server setting only impacts the thermostats "view temperature as" UI setting (Issue #37 and Issue #33)
• Fixed bug where "temperature units" UI in HomeKit always read Fahrenheit regardless of the server setting, it was not geting picked up in the plugin properly and now will report back to HomeKit the correct value (Issue #37)
• Issue #37 resolved
• Issue #33 resolved
• Issue #48 resolved
• Issue #49 resolved