Upgrading JowiHue from HS3 to HS4
When you are planning to install the HS4 version of the plugin over the HS3 version:
Make sure to have a backup!
Before installing the HS4 version of the plugin.
The conversion of devices is a one time, one way step. Once the conversion has started, be sure to let the plugin finish the conversion otherwise you might experience issues that only can be resolved by restoring the backup and redoing it. If you have to interrupt the first run, please restore a backup.
Below a global description what is going to happen during the conversion of HS3 JowiHue devices:
Conversion of devices
If you have an existing installation of the HS3 version of JowiHue, the available devices will have to be converted to the new structure HS4 is using. In HS3 devices were handled as Standalone devices or as Parent/Child devices. HS4 does no longer work with standalone devices (like the White only bulbs or the Philips Tap buttons) other then handling it as a legacy device. The Parent/Child devices are now handled as Device(s) with Features.
As an example: A physical Multi-sensor device will now be added as a single device with several features (like temperature, motion and lumen capabilities) Views will show the device as one (tile), with the extra features shown as small icons or - when in tile view - with the features and their values below the device.
The conversion for devices that are standalone will add a feature and use the old device as device, doubling the buttons in fact.
**Important!** events controlling the previous standalone devices will have to be updated, so the event will address the feature device from there on.
Using the tile view has a challenge for devices that hold many buttons. HS4 will try to show the controls, but when there are too many, HS4 will combine those controls to one button called "Controls" The JowiHue uses (too) many buttons on on/off devices for Lights. The buttons were added for dimming sliders, dim up/down, on/off and Alert/Blink.
Known issues at this point
Not really an issue, but a limitation: The new tile view of HS4's device page has a limitation on the number of buttons and sliders. If a device has more buttons the tile view will only show one button "Control", which will popup a window showing all controls of the device. This is the case for On/Off devices for lights or groups.
During conversion of the devices a new device will be created with the name of the light or group with "(Extra)" added to it in preparation of limiting the number of buttons on ad device. This device holds several of the buttons of the On/Off device. But the conversion will not remove the same buttons from the on/off buttons as there might be device actions that control these buttons. This will give you time to update those events (using the new HS4 search functions will easy your job finding these)
Once all events are updated, enable the setting "clean On/OFF buttons" that will be visible in the settings page in the near future. this will clean the on/off devices and hide this same setting for the future.
Make sure to have a backup!
Before installing the HS4 version of the plugin.
The conversion of devices is a one time, one way step. Once the conversion has started, be sure to let the plugin finish the conversion otherwise you might experience issues that only can be resolved by restoring the backup and redoing it. If you have to interrupt the first run, please restore a backup.
Below a global description what is going to happen during the conversion of HS3 JowiHue devices:
Conversion of devices
If you have an existing installation of the HS3 version of JowiHue, the available devices will have to be converted to the new structure HS4 is using. In HS3 devices were handled as Standalone devices or as Parent/Child devices. HS4 does no longer work with standalone devices (like the White only bulbs or the Philips Tap buttons) other then handling it as a legacy device. The Parent/Child devices are now handled as Device(s) with Features.
As an example: A physical Multi-sensor device will now be added as a single device with several features (like temperature, motion and lumen capabilities) Views will show the device as one (tile), with the extra features shown as small icons or - when in tile view - with the features and their values below the device.
The conversion for devices that are standalone will add a feature and use the old device as device, doubling the buttons in fact.
**Important!** events controlling the previous standalone devices will have to be updated, so the event will address the feature device from there on.
Using the tile view has a challenge for devices that hold many buttons. HS4 will try to show the controls, but when there are too many, HS4 will combine those controls to one button called "Controls" The JowiHue uses (too) many buttons on on/off devices for Lights. The buttons were added for dimming sliders, dim up/down, on/off and Alert/Blink.
Known issues at this point
Not really an issue, but a limitation: The new tile view of HS4's device page has a limitation on the number of buttons and sliders. If a device has more buttons the tile view will only show one button "Control", which will popup a window showing all controls of the device. This is the case for On/Off devices for lights or groups.
During conversion of the devices a new device will be created with the name of the light or group with "(Extra)" added to it in preparation of limiting the number of buttons on ad device. This device holds several of the buttons of the On/Off device. But the conversion will not remove the same buttons from the on/off buttons as there might be device actions that control these buttons. This will give you time to update those events (using the new HS4 search functions will easy your job finding these)
Once all events are updated, enable the setting "clean On/OFF buttons" that will be visible in the settings page in the near future. this will clean the on/off devices and hide this same setting for the future.
Comment