Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
jowihue:beta [2015/12/11 11:54]
wim
jowihue:beta [2015/12/16 22:31] (current)
wim
Line 1: Line 1:
-===Beta 1.0.6.10 ===+===Beta 1.0.6.11 ===
  
 Philips has delivered a new version of the Philips Hue bridge. The main difference with the old bridge is that the new bridge is enabled for Apples HomeKit. It seems the normal API will stay the same on brth bridges, so there should be no need to jump to the new version bridge right away. Philips has delivered a new version of the Philips Hue bridge. The main difference with the old bridge is that the new bridge is enabled for Apples HomeKit. It seems the normal API will stay the same on brth bridges, so there should be no need to jump to the new version bridge right away.
Line 5: Line 5:
 An extra is that because of this change the plugin can also survive a reset of the bridge and reimport of the devices. Als in this case the plugin will adjust all needed settings in the devices and keep scenes and events intact. An extra is that because of this change the plugin can also survive a reset of the bridge and reimport of the devices. Als in this case the plugin will adjust all needed settings in the devices and keep scenes and events intact.
 Als in this plugin a large change is made on how the bridges are approached. It should be a under the hood change with large advantages for users with multiple bridges, but as the beta progressed, it became clear it caused some annoying bugs.... I am sorry for that!  Als in this plugin a large change is made on how the bridges are approached. It should be a under the hood change with large advantages for users with multiple bridges, but as the beta progressed, it became clear it caused some annoying bugs.... I am sorry for that! 
 +Aside from this, the polling part to update the devices for showing the updates on the bridge has been updated, especially for multiple bridges. This was a major change to the plugin.
  
 == Who should join in this beta test? == == Who should join in this beta test? ==
Line 10: Line 11:
   * Anyone planning to move from the old bridge to the new bridge. !!! Please read on on the steps to take !!!   * Anyone planning to move from the old bridge to the new bridge. !!! Please read on on the steps to take !!!
   * Also if you still have the '​old'​ bridge you can join in. The plugin should function as usual, without any issues.   * Also if you still have the '​old'​ bridge you can join in. The plugin should function as usual, without any issues.
 +  * When you have more then one bridge.
  
 == What is new in the plugin == == What is new in the plugin ==
Line 18: Line 20:
   - better use of the gamut (color) correction needed for the different types of lights   - better use of the gamut (color) correction needed for the different types of lights
   - Corrected an issue where the refreshrate would not be correctly saved   - Corrected an issue where the refreshrate would not be correctly saved
-  - Redesigned the status updates for light and sensors. Response should be a bit snappier when updating status of devices. Especially when you use more then one bridge you should a very noticible change in the speed of updating devices. Bridges are now handled simultanious instead of one after the other.+  - Redesigned the status updates for light and sensors. Response should be a bit snappier when updating status of devices. Especially when you use more then one bridge you should a **very** noticible change in the speed of updating devices. Bridges are now handled simultanious instead of one after the other.
   - With the redesign I am hoping to have beat thee issue with mmemory usage in Linux.   - With the redesign I am hoping to have beat thee issue with mmemory usage in Linux.
   - it is now possible to force the plugin to check an IP for presence of a bridge. If it is present, it will enable registration of the bridge.   - it is now possible to force the plugin to check an IP for presence of a bridge. If it is present, it will enable registration of the bridge.
Line 53: Line 55:
   * added an option to the configuration page to remove the colorpicker controls. Having many lights with colorpicker control can slow down the deviceutility page considerable. Removing this control through the configuration page regains normal speed for the page again.   * added an option to the configuration page to remove the colorpicker controls. Having many lights with colorpicker control can slow down the deviceutility page considerable. Removing this control through the configuration page regains normal speed for the page again.
   *  additional adjustments to support API 1.11 changes   *  additional adjustments to support API 1.11 changes
 +
 +ps. Changes since the beta 1.0.6.10:
 +  * Corrected a regulary restart of the plugin when using multiple bridges. This should not occur anymore
 +  * additional adjustments to support API 1.11 changes, especially on property pages of lights, groups annd bridges
 +  * Improved the bridge discovery.
 +  *