JowiHue Beta december
This beta is adressing mainly the issues we see now and then on double devices, lights and/or sensors.These changes are mainly under the hood, so you migh not see much changes happening in this version. There are other changes as well, which are visible, these will be addressed at the end as a list of changes.
If you want to join the beta, as always, but this beta in particular, make sure you have a trustworthy back-up of homeseer as well as the JowiHue files under the data directory and the production version of the plugin (which you always can download with the updater).
JowiHue beta 2.0.2.15
- Changed scriptingfunctions "SetLightsRGB", SetLightsKelvin" and "SetLightsHueSat" to accept a bright value of 0 for Philips bridges, which will switch the light off.
- Major changes on the Bridge maintenance page regarding sensors. You can now remove devices from HS3 and/or remove sensors or switches from the gateways. Make sure to read the updated documentation about this feature!
- Removed a chance of creating double battery devices for sensors that are (yet) of unknown type.
- Changed the response for orphaned devices as it is possible that the sensor was removed before to be re-added later
- Changed the plugin's behaviour on xy results from lights. Those are now enforced on the Dim/Sat and Hue values of a device.
- removed a test for future change of accessing a Philips Hue bridge. This caused the bridge being unreachable for some users.
JowiHue beta 2.0.2.14
- Solved an issue creating and/or editing groups on the Bridge maintenance page. When hiding sensor groups was selected in the configuration page of the plugin, the Bridge maintenace page would hide all groups, making it impossible to edit or add groups.
- Solved a second issue with editing groups when trying to add groups to the deCONZ bridge.
JowiHue beta 2.0.2.13
- Solved the concurrent database error! That must have been the most stubborn bug in the lifetime of this plugin.. Lamptypes are now normally updated again. This will also solve the issues with dimming of certain lights and lost CT devices.
- Added the possibility to refresh all lights device values or all sensor devicevalues. This can be done on the configuration screen on the miscellaneous tab
- Added a "blink" option to all lights on the manage devices page of Homeseer. This can now also be selected as device action in events. To enable this option, you need to refresh the device values, either through properties of a device, or using the new refresh all light devices button in the configuration screen.
- On rare occasions an internal database can be corrupted. The plugin will then restart itself. One table was missed. This is corrected.
JowiHue beta 2.0.2.12
- Solved an issue when a decimal point was used in the rules of the bridge
- Did more rework on the updateusage constraint error, this is really a stubborn issue!
- Tuned the animations a bit more as now the animation would not stop if a light touched by the animation is send another command
- Added sensitivty to the vibration sensor (deCONZ needs to be on version 2.05.52 for this!)
- re-enabled setting the duration for motion sensors on the JowiHue tab
- Added reporting of Energy usage to the HS3 energy database for plugs supporting energyconsumption reporting. To enable this, you need to enable energy reporting on the configuration/miscelennious tab.
- Removed the deletion of "orphaned"sensordevices when starting the plugin. It can happen that devices appear orphaned when the bridge is starting up at the same time as the plugin. The plugin will now advice to remove it only. Double devices are still removed!
JowiHue beta 2.0.2.11
- infinite animations did stop at any command send, not only commands to lights used in the animation. Solved
- Changed behaviour of the DimAnimation scriptcommand. If the animation is not running and the animations is not a stretched animation, the animation will be started with the dimmed parameter.
- Using an underscore ("_") in scenenames could cause the webpage to not show the scene anymore. because this caused display issues The underscore is now replaced by a space for scenes to prevent this.
- Changed the timeout for getting information from the bridge
JowiHue beta 2.0.2.10
- Animations addressing scenes that use groups were not working. This was an old issue that never surfaced before. These are working now
- Updating the LampTypes table for systems that are using a "." as decimal seperator was still not working, causing some lights not to go off, or scenes to trip. This is solved
- Using the new scriptcommand "DimAnimation" has changed so that instead of using one animation name, you can also use "all". The plugin will then dim all running animations.
- The start animation action in an event can now also set the relative dim value from the first start.
- The scene action now also have the possibility to set a relative dim.
JowiHue beta 2.0.2.9
In this first beta, the plugin has two major changes under the hood. First off all, it will hold back creating devices until the plugin is fully started. This might cause a bit of a delay during startup, but I expect it will prevent creating al those doubles some of you have seen.
Secondly, in this stage, the plugin will evaluate each sensor device and check if the internal information is correct. Especially deCONZ devices from the past (one year ago) can hold old information or even wrong information due to the many beta stages we went through with both the plugin and deCONZ. The plugin will - if it finds errors - try to correct this information, by updating the devices and maybe even the bridge information. Those changes will be logged in the HS3 log at the first run. A second run should show no more lines as all issues should have been resolved.
There might be a few sensordevices that are really orphans. The plugin will proceed here and remove the orphaned devices. I have this tested with a few others, and so far the plugin did the right step. But this is for sure the reason you need that back-up! If you do join this beta and wrong devices are changed or even removed,, send me the log and explain why this should not have been done. If a sensor gets damaged, consider removing the device and joining the sensor back in deCONZ.
In the next beta phase, the same check will be done for Lights and plugs. I do not expect many issues with that, but cannot tell for sure yet.
Other changes are:
- Restyled the processes handling sensors and lights. Difficultt to measure, but especially sensor actions are handled much faster now.
- Certain sensors would not update for a few users. Cause found and solved
- Battery devices would not update for some users. Cause found and solved. When you have doubts, check the properties of the sensordevice, JowiHue tab. On the bottom you will find the information coming from the bridge, check the battery value here to the battery device value.
- Added the possiblilty to relatively dim a running animation or scene with JowiHue actions. (Not yet regression tested)
- Also added two sript commands with the plugin to activate the relative dim for scenes or animations:
Code:
Dim test As Boolean = hs.PluginFunction("JowiHue", "", "DimScene", {"MyScene", 60})
Code:
Dim test As Boolean = hs.PluginFunction("JowiHue", "", "DimAnimation", {"MyAnimation", 60})
- Solved an issue where a animation could abort when the option "Return to orginal settings after animation ends" has been set.
- Adjusted the maximum saturation level in creating scenes and using the colorpicker. This could return an unaccepted error.
- Added basic sensorinformation on the Bridge Maintenance page. For now this only shows the currently known sensors. In a next Phase the ability will be added to remove the sensor from the bridge.
- Re-enabled editing lights on the Bridge Maintanance page
- Finetuned the power consumption capabilities when a plug is used that supports the reporting of power usage. In the next phase energy reporting to the HS3 energy database will be added.
- Several users saw this errorline when starting the plugin with the JowiHueImports.xml lfile in the config directory:
Code:
[SIZE=12px]Error: (UpdateLampTypes)::Concurrency violation: the UpdateCommand affected 0 of the expected 1 records[/SIZE][SIZE=14px]. [/SIZE]
Please post issues with the beta plugin to this thread. Also I would like to hear if you experienced issues that should be solved with this beta if those are solved or still present.
I will update this first post when new updates come available
Thanks!
Wim
I updated to .29 and the hue light that should shut off at 22:00 is unresponsive. Went back to .28 and still no control over the light. Suggestion?
Comment