Skip to content

Version 0.22.0 (Beta 22.0)

Pre-release
Pre-release
Compare
Choose a tag to compare
@Colorado4Wheeler Colorado4Wheeler released this 02 Apr 21:36
· 18 commits to master since this release
0.22.0
f079678
  • 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%
Assets 2