Skip to content

Releases: indigodomo/HomeKit-Bridge

Version 0.22.1 (Beta 22.1)

03 Apr 14:55
Compare
Choose a tag to compare
Pre-release
  • 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 optimized Homebridge callback POST method to replace the current GET method, in preparation for an updated Homebridge-Indigo2 script that will parse the data instead of calling back to the API (Issue #93)
  • Fixed bug in configuration builder where if an error was tripped the exception would not populate (Issue #83)
  • Fixed bug in new library that would allow Homebridge to see a duplicate camera device and would send that device to HomeKit along with the normal camera (Issue #94 and Issue #92)
  • Issue #94 resolved
  • Issue #92 resolved
  • Issue #93 implemented

Version 0.22.0 (Beta 22.0)

02 Apr 21:36
Compare
Choose a tag to compare
Pre-release
  • 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.
  • Added error trapping around building the camera configuration in case there's an odd setup that may cause the camera build to fail it will not impact the rest of the homekit devices
  • Added new action under device actions to restart an individual server
  • Added new action in the action root to restart all running servers
  • Added new action under device actions to force a HomeKit refresh for a device - this may help with Issue #87
  • Added new action in the action root to force a HomeKit refresh for all devices on a server
  • Library Change: Added minimum and maximum values to the API payload so Homebridge can dynamically change the ranges as needed - particularly in situations where the built-in ranges were incorrect, such as temperature values that couldn't go below 50F or above 100F.
  • Library Change: Optimized API payload processing method, API calls will only return what Homebridge wants with no extra fields and does it far more efficiently
  • Library Change: Moved API payload processing to new factory package
  • Library Change: Experimental change to not wait for commands to run - this may be restored in the next release but I believe waiting is unnecessary because HomeKit will be updated when the command completes anyway, the benefit of this is faster response (and if you use slow devices like curtain controls it will prevent Siri from saying 'some of your devices are not responding')
  • Library Change: Started adding the underlying structure to test the possibility of using Indigo variables as HomeKit devices
  • Library Change: Cache HomeKit devices and update dynamically, improved API performance by 600%

Version 0.21.0 (Beta 21.0)

29 Mar 16:01
Compare
Choose a tag to compare
Pre-release
  • NOTE This release begins the process of rewriting the entire HomeKit integration, small chunks at a time, so it's possible that this can break things. I'm trying to thoroughly test changes to make sure the end result is the same, but you have been warned.
  • Added failsafe when saving the Homebridge configuration that if there are no Indigo devices being passed that the Homebridge-indigo2 platform will not be loaded, this in case you are using a "camera server" that has nothing else on it doesn't cause issues with Homebridge-Indigo2 trying to load zero accessories
  • Changed model:submodel device resolution to detect if either model or submodel is an empty attribute and not pass the ":" separator if that is the case
  • Completely rewrote the SecuritySpy URL construction routine to better support users who don't store the xpassword state (Issue #81)
  • Moved model/firmware resolution out of the main plugin and into the new factory package
  • Code housekeeping and cleanup

Version 0.20.1 (Beta 20.1)

28 Mar 20:40
Compare
Choose a tag to compare
Pre-release
  • Added additional sanity check on SecuritySpy servers that if they don't have the xaddress populated to get the address from a different field (Issue #81)
  • Added 'ProgramHeat' and 'ProgramCool' to conditions for sending temperature set commands to a thermostat (Issue #79)
  • Fixed bug where if a thermostat was set to auto heat/cool that changing temperatures in HomeKit would time out in the plugin because the plugin didn't know what to set, it will now increase the heat if the target temp is warmer than the current temp and increase cooling if it is cooler
  • Fixed bug where read-only HomeKit services may not get updates if not specifically programmed (i.e., for DSC alarms) (Issue #86)
  • Issue #81 resolved
  • Issue #79 resolved
  • Issue #86 resolved

Version 0.20.0 (Beta 20.0)

22 Mar 02:15
Compare
Choose a tag to compare
Pre-release
  • Added failsafe code in thermostats that if a heat or cool set point is below 0 degrees F that the converted value will report as 0
  • Added Nest thermostat plugin support to properly indicate when it is currently heating or currently cooling
  • Added experimental support for Pi Beacon i2cTMP102, i2cBMExx, i2cMS5803 temperature sensors (Issue #73)
  • Added experimental support for Pi Beacon i2cBMExx humidity sensors (Issue #73)
  • Added experimental support for Pi Beacon occupancy sensors (Issue #57)
  • Fixed bug in thermostat status that would only show at orange (heating) or blue (cooling), now it will properly determine if the thermostat is actively heating or cooling (orange/blue) or if it is currently idle (green)
  • Fixed bug in thermostat modes where Auto mode was not properly detected
  • Fixed UI bug where "Temperature value is in Fahrenheit" only shows up if the device is edited or if it defaulted to a temperature device, now it will trigger from changing the HomeKit type. Resolves issue reported on the forum by vtmikel
  • Fixed UI bug where "Send Status Request" was enabled on the device list, causing confusion when clicking it and getting an Indigo error because it was not implemented (Issue #80)
  • Issue #80 resolved
  • Issue #73 features partially added
  • Issue #57 features added

Version 0.19.9 (Beta 19.9)

20 Mar 20:47
Compare
Choose a tag to compare
Pre-release
  • Added sanity checker to the configuration save functions to validate the folder structure and files to auto remove and rebuild the config folder if it detects something is wrong, this hopefully to finally close out the ongoing new-user-startup-issue that seems to always be resolve by rebuilding the config (Issue #12)
  • Added URL message when the server cannot be started that points the user to the wiki page explaining how to rebuild the Homebridge folder if they are unable to start their server repeatedly
  • Added threaded startup for servers when the plugin is loaded to speed up the load time on the Homebridge servers
  • Added validation on plugin preference save that will not permit the user to save plugin prefs if there are any servers in a 'Starting' state
  • Added validation on plugin preferences where if a camera field is changed it will restart any servers impacted by that change (don't blame me, Indigo API limitations) (Issue #75
  • Added new Advanced Plugin Action for devices to log the contents of the Homebridge configuration, mostly for camera debugging since it's the only thing that actively manipulates the configuration
  • Removed "under development" warnings from Advanced Plugin Actions
  • Fixed bug in plugin config's packet size validation where it would allow any value between 188 and 1316 instead of only values in increments of 188
  • Fixed minor UI issue where the 'Model' field was not automatically populating when creating a new server
  • Issue #75 feature added

Version 0.19.8 (Beta 19.8)

19 Mar 16:01
Compare
Choose a tag to compare
Pre-release
  • Changed some Blue Iris integration parameters to match recommendations from Glenn
  • Updated Blue Iris and SecuritySpy integration to incorporate max bitrate, packet size and debug logging from the plugin prefs
  • Added packet size, frame rate and debug to the PLUGIN PREFS for camera configuration so you can tweak the settings. You'll need to reload your camera server after any changes so the configuration can be rebuilt.
  • Fixed bug in Blue Iris that had authentication reversed

Version 0.19.7 (Beta 19.7)

18 Mar 23:11
Compare
Choose a tag to compare
Pre-release
  • Changed Blue Iris FPS data to pull from states but default to 30 FPS if the state is 0
  • Fixed type causing Blue Iris not to pull plugin prefs correctly

Version 0.19.6 (Beta 19.6)

18 Mar 22:15
Compare
Choose a tag to compare
Pre-release
  • Fixed bug in Blue Iris XML parsing on server rebuild

Version 0.19.5 (Beta 19.5)

18 Mar 17:24
Compare
Choose a tag to compare
Pre-release
  • Added retrieving width, height and FPS from SecuritySpy server so that HomeKit cameras represent the proper aspect ratio and frame rate
  • Added auto detect so that SecuritySpy and Blue Iris camera devices will default to a camera HomeKit type
  • Added experimental support for Blue Iris