Releases: indigodomo/HomeKit-Bridge
Releases · indigodomo/HomeKit-Bridge
Version 0.17.2 (Beta 17.2)
- Added Indigo Plugin Store update checker, this will check at 10:00am each day and on plugin startup
- Added Indigo Plugin Store update check to the menu
- Added use of onState for air quality devices to indicate if the device is active
- Moved log notice about building configuration to the debug log rather than the info log
- Improved performance of Hue bulbs both in general operation but specifically for color changes (Issue #31), it involved a little white lie back to HomeKit to make this work but I don't think it'll be an issue.
- Fixed a few issues on the UI that caused the form to get out of alignment
- Fixed a bug when an Indigo value was "None" that it would cause a message in the log about being unable to convert (re-fixed from 0.17.0) - Issue #55
- Issue #31 resolved
- Issue #55 resolved
Version 0.17.1 (Beta 17.1)
Release Notes
- Fixed typo for setting heating and cooling setpoints that were causing errors
Version 0.17.0 (Beta 17.0)
Release Notes
- NOTE: This release represents that last of the HomeKit device types currently available through Homebridge. The next few release hopefully I can add generic enough mappings that they are usable by any Indigo device type to varying degrees so that, at the very least, you get a choice of some icons to use.
- New device type added: Camera RTP Stream Management - Don't get your hopes up, this is just experimental to give me a place to play around with video streaming
- New device type added: Fan - There really isn't a lot of difference, but this is the original HomeKit fan (fewer capabilities) and is being added for completeness and in case something different is discovered about it
- New device type added: Air Quality Sensor
- New device type added: Heater / Cooler
- New device type added: Humidifier / Dehumidifier
- Added cooling setpoint and heating setpoint options to thermostats but they don't currently seem to do anything, at least on my system
- Added additional error checking to the HomeKit update query to ensure the device or action group being updated still exists in Indigo
- Added test condition if an Indigo value is None (null, nothing, etc) then the plugin will convert that to the most negative value (0.0, 0, False) - Issue #55
- Changed target temperature range from 10 Celsius to 35 Celsius, down from -100 to 100 on thermostats, it's how it was under HB-Indigo and HBB and that's where it's staying now. From now on I'm not changing any values like this unless there are at least 10 people requesting it, it's a waste of time and energy that's better spent on other aspects of this plugin.
- Issue #37 fully resolved!
- Issue #55 resolved
Version 0.16.3 (Beta 16.3)
Release Notes
- Rapid release for bug fixes, incorporates 16.1 to 16.3
- Issue #37 hopefully resolved now!
Version 0.16.2 (Beta 16.2)
- Fixed bug in UI that was showing the header and fields for a device addition/edit when not in the device management view (Issue #50)
- Fixed bug from 16.1 that broke the ability to set temperatures if you were using Fahrenheit
- Issue #50 resolved
- Issue #37 resolved (fixed typo that broke Celsius users)
Version 0.16.1 (Beta 16.1)
- NOTE: Due to a fundamental change in temp control you will need to edit all of your sensors and thermostats 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 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.
- 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
Version 0.16.2 (Beta 16.2)
Release Notes
- NOTE: Due to a fundamental change in temp control you will need to edit all of your sensors and thermostats 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 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.
- Fixed bug in UI that was showing the header and fields for a device addition/edit when not in the device management view (Issue #50)
- Fixed bug from 16.1 that broke the ability to set temperatures if you were using Fahrenheit
- Issue #50 resolved
- Issue #37 resolved (fixed typo that broke Celsius users)
Version 0.16.1 (Beta 16.1)
- NOTE: Due to a fundamental change in temp control you will need to edit all of your sensors and thermostats 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 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.
- 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
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
Version 0.16.0 (Beta 16)
Release Notes
- Total UI overhaul - if something on it isn't working don't blame me, I was trying to implement YOUR design requests :). As a result, a good portion of the Wiki will need to be scrapped and rewritten to document this new UI.
- Added new Advanced Plugin Actions option to view the Homebridge log
- Added support for DSC Alarm plugin on Motion Sensors, Garage Door Opener, Smoke Sensor, Occupancy Sensor, Lock Mechanism, and Switch
- Added failsafe check to make sure the user didn't cancel a brand new server config dialog, which would result in a port error. Pretty minor but an error is an error.
- Added new Advanced Plugin Device action to Rebuild Homebridge Folder, this in case a folder becomes corrupt and needs to be removed and rebuilt, this is the current solution for Issue #46 but also serves additional utility for diagnostics as well so it ends up being a good solution
- Changed behavior of clicking SAVE while editing a device (Issue #34 and Issue #22 and Issue #14) so that now it will pop a warning to let the user know that the edit will be lost but they can click save again to continue
- Removed last few areas where the old FILL command was still being added to forms
- Removed automatic HBB upgrade in case that is causing a problem with not popping up the config dialong on fresh installs since it was reported that when HBB is enabled the dialog would not show but when it was disabled it would (Issue #12)
- Changed default for api port in saving the configuration in case any other users report a problem with not having the prefs file
- Upgrade will flush out any devices that still reference the FILL command
- Fixed bug in thermostat sensors that weren't honoring conversion from Fahrenheit if the device was a sensor device in Indigo (Issue #33)
- Issue #33 resolved
- Issue #12 possibly resolved
- Issue #46 resolved
- Issue #34 resolved
- Issue #22 resolved
- Issue #14 resolved
Version 0.15.1 (Beta 15.1)
Release Notes
- Added a check system to the server configuration builder to see if there are key fields missing from the plugin prefs. This is in direct response to two users reporting that their "apiport" was missing (Issue #12)
- Added ability for contact sensors, which already natively invert the on state of a device, to utilize the "invert" checkbox so that it can not invert it instead, this in direct response to Issue #32
- Added new utility to the Advanced Plugin Options (under the plugin menu) to Simulate a HomeKit device to better diagnose what may be going on, this allows you to see what HomeKit will see when your device is sent to it
- Removed all complications implementation from the plugin as it's going to be totally different when implemented than it was in the experimental implementation, yet the experimental settings were still in the plugin and causing confusion
- Changed Faucet to be 3rd Party Only since in Home it constantly says "Updating". You can use Valve instead if you want that icon and more functionality. This in direct response to Issue #38
- Fixed bug where the plugin was loading an unneeded library and might cause an error if it ran across a plugin that didn't have an info.plist file
- Fixed bug where choosing a device that could not be auto detected (for instance a "custom" plugin device) then it would generate an error about being able to "iteritems". Now non detectable devices will default to a switch and a warning will show in the log that it could not be figured out.
- Issue #32 resolved
- Issue #38 resolved
Version 0.15.0 (Beta 15)
Release Notes
- Added experimental support for LIFX color bulbs (may experience similar issues to Hue where the colors WILL change but may generate timeout issues on the plugin and it may take 30 seconds to change the color)
- Added version control for better upgrade processing
- Added device deletion detection where if any device that is currently linked to a HomeKit Bridge server is removed from Indigo the plugin will detect that it was removed and then remove it from all impacted servers (and restart them if needed)
- Added device reindexing on server device save as new device adds were not being added to the cache after saving the server which was fine 99% of the time but could cause issues in a few non critical areas
- Removed the FILL option from the UI, now the action and device list will only show actions and devices (for now, future changes to this are still possible)
- Fixed slow response time of device changes and, in particular, rapid device changes no longer beachball (Issue #17) was resolved but it may be at the cost that HomeKit won't always know immediately if the action failed)
- Fixed Nest temperature set point issue (Issue #18) as a result of fixing Issue #17. Executing the online action still takes longer but it will respond in less than 30 seconds now and no longer beachball
- Fixed issue where special characters (backslash, quote, single quote, etc) would not work, they now will appear in HomeKit as literally as they are added into Indigo (Issue #11)
- Fixed issue of the server complaining of in-use ports when trying to change the ports on a running server, it now will not allow port changes while the server is running so it can validate ports properly (Issue #4)
- Fixed issue where moving items between servers (plugin menu option) would cause the source and destination server to restart after each item moved rather than at the end of all items being moved Issue #25
- Fixed issue where deleting a device in Indigo that is attached to a HomeKit Bridge server would cause the server to throw errors when it started up (and could subsequently throw errors while running). While the solution will cause the server to start, stop and start again this is an acceptable solution given the rarity of this occurrence. For the most part this fix is a failsafe as device deletion detection was also added in this release that should proactively remove deleted devices from servers (Issue #26)
- Issue #17 resolved
- Issue #18 resolved
- Issue #11 resolved
- Issue #4 resolved
- Issue #25 resolved
- Issue #26 resolved
Version 0.14.1 (Beta 14 Release 1)
Release Notes
- NOTE: All known issues and wishlist items have been moved to Git issues instead
- Removed "FILL" from the server plugin as it was considered confusing and unused
- Added support for the Hue bulb plugin, if you use the hueBulb device then the plugin will now support the color settings of the bulb. This is functional but still under construction so expect timeouts when you change colors on the app until I dial that in, but it WILL change - just don't go doing a thousand color changes until it's completed
- Renamed the device from being "HomeKit Bridge Server" to being "HomeKit Accessory Server" to bring it more in line with what it is: a HomeKit Accessory and also in pursuance of keeping the terms as user friendly and universal as possible
- Changed max value of Color Temperature to 15,000
- Changed the description of "Fan Version 2" to simply "Fan" to avoid confusion. There is a Fan Version 1 but I don't see ever using it since the V2 does everything the V1 did anyway
- Fixed fairly large bug where conversion from an Indigo type of integer or float to a characteristic required value of the opposite (float or integer) was using the wrong value for calculation, meaning the result was always whatever the default for the characteristic was (often zero) - if you had issues with a device not reporting correctly please try it now to see if it resolved your issue
- Fixed minor bug on new server creation where if you do not add any devices you might get an error when saving the server that "key device not found in dict"
- Removed first revision service initializers (code cleanup)