Beta 4.0.1.0 (RC1)
- Added an initial add button on the scenes tab of the creativity page when no scenes are present yet.
- On Linux installs an error was logged when setting a bright level on a light. This issue is resolved.
- Solved an issue where the CT command would throw an error in deCONZ 2.05.77
- Solved an issue where a dim command for groups would no longer work.
- Solved an issue with the latest firmware of Philips Hue bridges, which would throw an error in the plugin during scan for bridges
Beta 4.0.0.22
- Solved an issue where brightness was not set correctly through JowiHue actions
- Also on JowiHue actions, transition time was ignored. Solved
Beta 4.0.0.20
- Events were no longer converted with the latest HS4 beta. Plugin has been updated to correct this issue
- Creativity scenes and animations could no longer be edited, but were still working fine when triggered. You can edit them again
- The plugin can now recognize fan devices that are combined with a light. For the fan part, an extra device is created as child of the light device to control the fan.
- basic updates are done to support control of IKEA blinds
- Solved an issue created by the latest deCONZ release where the coordinator is also presented as a light. The plugin would create devices for it that are incomplete. Now the plugin will ignore these devices.
- Enabled creating a battery device for the IKEA blinds as sensor
- You can now set a default location and location2 in the settings of the plugin, used for creating new devices.
- I noticed that events with conditions based on white only lights - single devices in HS3 - will not work and might loop as only the parent device in the event is addressed after converting the device. You will have to edit these events after the conversion to include the feature device. This cannot be done by the plugin as events cannot be changed by plugins.
- Updated the plugin to follow the setting for brightness in the settingspage. If it is set to percentage, all brightness values are now shown in percentage anywhere in the plugin. Earlier only the device would be set to the percentage value.
- Conversion of event actions are now complete, without issues. Including time delays.
If your events are using the JowiHue actions to update these lights the conversion will be done.
Earlier version of the beta could not do a complet conversion of JowiHue actions. Starting with this version conversion of events are complete.
Beta 4.0.0.17
- Group devices would never update to the off value. Solved
- Added a new settings page for naming features after changing a device's name
- Added buttons on the settings pages to jump straight to other common pages of the plugin
- Correction settings for temperatures, created in the HS3 version of the plugin are now saved on the bridge or gateway and applied to every app using the same bridge or gateway
- Solved an issue on Linux causing sensors to not update the devices anymore.
This is a release candidate. If you miss functions or find issues, please let me know? I am implementing the last few points on my list now, once those are finished and no real issues arise, I will publish it as release.
The new settings page enables you to set the extension name of features of a device. If you rename a device (not a feature) the connected features will be named as the device with an extension according to the settings. I have implemented a default set, which you can change on this new settings page.
A sample: a sensor device is reporting motion, temperature and lightlevel. You name the sensor device "Living room Sensor". The features will then be named "Living room Sensor Motion", "Living room Sensor Temperature" and "Living room Sensor Lightlevel" (and "Living room Sensor Battery") or whatever you configure on this new settings page. Please note that the length of the device name is limited to 32 characters as this is an enforced length on the bridges/gateways.
You still can rename a feature if you like, the plugin will not do anything with that unless/until you rename the device.
Beta 4.0.0.15
- Solved an upper/lowercase issue on Linux
- Animations are now complete! This makes all functionality of the HS3 plugin now also available in the HS4 plugin
Beta 4.0.0.14
- Solved a major issue with the conversion HS3 to HS4, which was introduced in the 4.0.0.13 version. If you ran the plugin for the first time with the 4.0.0.13 version (and thus did the conversion then) you need to redo it with tthe 4.0.0.14 version!. If you ran the conversion already on a earlier version there should be no problem as the conversion to HS4 devices has already been done.
- Solved an issue while saving scenes with selected groups
- Preset light selection for testing is cleared every time scenes or animations were selected. Selection is now retained until next restart of the plugin
- Clicking any undo action during edit of a scene clears the scene name. The name is now retained.
- The miscelannious hunt is now ended :-)
- Using the scene option for switching off lights, was not working correct for groups. This is working correct now.
- Solved an issue that could occur during the conversion of HS3 devices to HS4 devices. This issue could stop the conversion completely, causing lots of errors afterwards
- Another issue during conversion of devices could occur when location2 in HS3/4 is not activated. this would result in a looping error creating features. This should be solved now.
Beta 4.0.0.12
- With a Lux level setting diabled on the settings page, the plugin would throw errrors while creating the lightlevel features.
- In edit scenes the "Swtich Off" option and transition field were not available. Both are added now.
- When creating a new scene the version could be missed. A restart of the lugin will then go into a loop. This is solved,
- Trace options were not correctly saved, causing the trace would never start at initalisation of the plugin. This is solved
Beta 4.0.0.11
Two issue solved
- Plugin forgets to use correct port for deCONZ gateways while registering bridge.
- For some users a "Daylight sensor" device was created in the past. This would cause issue while removing a bridge and its devices. The bridge will now remove succesful.
Added extra information while removing a bridge.
Beta 4.0.0.8
- Enabled removing bridges with the bridge maintenance page
- corrected updating device properties (JowiHue tab) on device propeties
- Solved an issue where a JowiHue action could show an inaccurate error message when updating an action created in HS3.
- Updating functionality of Animations, but still work in progress....
- Caught a few minor bugs
Beta 4.0.0.7
- Solved an issue with a constraints issue while initializing the JowiHue database
- Re-enabled access to editing scenes
- Completed support for Hue Play HDMI Sync Boxes
- Before installing the HS4 version of the plugin, the HS3 version has to be disabled
- If the device name has a apostrophe (') in the name errors occur
I finished a first working beta. This beta has been running for the past few days to check its stability, so for those who would like to test, please join? I do not have all the devices supported by this plugin, so I am sure it needs more testing.....
Comments for the beta 4.0.0.6 of this plugin
Please be aware that the updater for HS4 shows 2 versions of the plugin as beta. Make sure to install the 4.0.0.6 version as the 4.0.0.5 version has in issue for the deCONZ installations.
The plugin has many, many changes. Most visible is the makeover of webpages for settings, Creativity and Bridge Maintenance. Under the hood there also many changes, more efficient coding, some old issues resolved and some important changes on Scenes and Color Temperature settings (the latter for especially IKEA lights).
One new and shiny possibility is now incorporated, support for the Hue Play HDMI Sync box!
There is also one yet unfinished item, animations. If you copy the \Data\JowiHue\JowiHue.db file over to the HS4 installation, you will have the animations from the HS3 installation and you can just use them. But editing, or adding animations is not yet finished. Working hard on that part it will become available again, but this is one of the tough parts of the plugin, so I have to take my time on this.....
At this point there is only a beta version of the JowiHue plugin for HS4. There is still development needed, like creating the responsive animation pages and some new developments that are on its way.
Conversion of HS3 devices is now enabled and ready to test.
When you want to use this plugin for your beta testing, keep these remarks in mind:
It is beta. Be aware of that. The plugin is subject to large changes and may not be stable. do not use it for production systems until it is released. There will be issues. I have been trying to catch the most of them myself, but I will need your help in this too.
A (work in progress) help document will be installed in the Docs folder of the HS4 installation.
If you are testing the plugin, please make sure have a backup. It is probably not yet fit for production. Do not forget to enable the tracing options "detailed log" and "log to file" in the settings page. This will ensure you can grab the log when any issue occurs. I suggest you do not post these logs on the forum, but instead create a post in the Beta thread describing the issue and sending the log to jowihue at ziggo dot nl
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 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.
Using the tile view has a challenge for devices that hold many buttons.HS4 will try to show the controls, but when there are to 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.
Naming of devices
Naming of devices and features has changed a lot. During conversion the plugin does not rename devices yet. But later on, once conversion is done and you decide to rename a device, the plugin will rename the features according to their 'feature' function. It is really like the HS3 version does already for color lights, it creates a set of childs (features) with (Hue), (Sat) etc naming behing the light's name. This method now also used for sensors and switches.
Check the documentation about renaming devices for more details on this subject
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. 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 reorganize the old buttons for on/off devices and the setting will be hidden from then on.
For lights that were not holding a parent device (simple plugs or white only bulbs) the same buttons will stay on the parent device after conversion. I have not found a way around this. You will need to convert eventual events that use direct device control by hand. The plugin will put warnings in the log for that situation.
If you are trying this beta, please report any findings on the beta in this thread. so I can find issues easier in one place?
Updates on the beta will be done in this post.
Happy testing!
Wim
Comment