HomeSeer Beta Release 2.3.0.126 beschikbaar
Posted: Tue Sep 15, 2009 8:48 pm
HomeSeer Beta Release 2.3.0.126 is beschikbaar.
http://board.homeseer.com/showthread.php?t=137581
Er is genoeg aan gesleuteld zo te zien.
Changes since 2.3.0.122
Removed generation of caller name and number to be sent to other phones when CID detected (PRO Version only) via Way2Call as it did not work reliably.
Fixed issues related to HS devices associated with Z-Wave nodes using the sensor multilevel and sensor alarm command classes - the HomeSeer HSM100 and the FortrezZ WWA-01. With these devices, a sensor report or alarm report could be received by HomeSeer, but the data was being applied to the wrong device frequently. This has been addressed and these devices should now report their status properly. If a device was applied the wrong status in a previous beta, it may be necessary to clear the device's string value before it will begin to appear correct - use hs.SetDeviceString to accomplish this.
A new global temperature scale setting on the General tab of the system settings will determine how temperatures for all Z-Wave devices except thermostats will be reported. The initial setting for this will be taken from the HSM100 scale setting if that exists in your INI file. Regardless of whether a temperature from an HSM100 (always Fahrenheit) or FortrezZ WWA-01 (always Celsius) is provided, HomeSeer will convert the temperature if necessary to display it in the scale you choose. The HSM100 INI setting will no longer be used.
When an association is added with HomeSeer, and when HomeSeer optimizes a node, a "return route" is added to insure that a path is established between the two nodes. For example, if you associate an HSM100 at node 57 with HomeSeer at node 1, then a return route is established from 57 to 1 so that the signals can reach HomeSeer when they are issued by the source node. However, previous versions of HomeSeer did not always wait for the return route command to complete as it was not monitoring the correct return status. This has resulted in perhaps 50% or more of the return routes to NOT be established properly. In certain networks, a lack of return routes can cause routing failures - thus communication failures. While this basic error has been fixed, it is now possible for an association or optimization to succeed, but then for the "add return route" to fail if Z-Wave could not find a route. Additionally, adding more return routes than what Z-Wave allows results in a failure of the route to be added, so existing routes must be removed and routes must be re-added for the current set of nodes that a device is associated with - this means that associations and optimizations will take longer to complete because of the additional command overhead.
The Z-Wave Who Am I (/zwho) page has been modified to be more readable, and it now lists the Z-Wave Basic, Generic, and Specific node type information.
Z-Wave debug logging now produces two log files rather than one.
When a device corresponding to a Cooper Wiring Z-Wave scene controller button was clicked OFF in the HomeSeer UI, the corresponding LED did not always turn off on the controller - this has been fixed.
All of the Z-Wave controller functions that used to pop up a status window have been replaced with realtime status updates in the same browser window. This improves the performance of all of the controller functions and eliminates replication issues due to timing problems.
http://board.homeseer.com/showthread.php?t=137581
Er is genoeg aan gesleuteld zo te zien.
Changes since 2.3.0.122
Removed generation of caller name and number to be sent to other phones when CID detected (PRO Version only) via Way2Call as it did not work reliably.
Fixed issues related to HS devices associated with Z-Wave nodes using the sensor multilevel and sensor alarm command classes - the HomeSeer HSM100 and the FortrezZ WWA-01. With these devices, a sensor report or alarm report could be received by HomeSeer, but the data was being applied to the wrong device frequently. This has been addressed and these devices should now report their status properly. If a device was applied the wrong status in a previous beta, it may be necessary to clear the device's string value before it will begin to appear correct - use hs.SetDeviceString to accomplish this.
A new global temperature scale setting on the General tab of the system settings will determine how temperatures for all Z-Wave devices except thermostats will be reported. The initial setting for this will be taken from the HSM100 scale setting if that exists in your INI file. Regardless of whether a temperature from an HSM100 (always Fahrenheit) or FortrezZ WWA-01 (always Celsius) is provided, HomeSeer will convert the temperature if necessary to display it in the scale you choose. The HSM100 INI setting will no longer be used.
When an association is added with HomeSeer, and when HomeSeer optimizes a node, a "return route" is added to insure that a path is established between the two nodes. For example, if you associate an HSM100 at node 57 with HomeSeer at node 1, then a return route is established from 57 to 1 so that the signals can reach HomeSeer when they are issued by the source node. However, previous versions of HomeSeer did not always wait for the return route command to complete as it was not monitoring the correct return status. This has resulted in perhaps 50% or more of the return routes to NOT be established properly. In certain networks, a lack of return routes can cause routing failures - thus communication failures. While this basic error has been fixed, it is now possible for an association or optimization to succeed, but then for the "add return route" to fail if Z-Wave could not find a route. Additionally, adding more return routes than what Z-Wave allows results in a failure of the route to be added, so existing routes must be removed and routes must be re-added for the current set of nodes that a device is associated with - this means that associations and optimizations will take longer to complete because of the additional command overhead.
The Z-Wave Who Am I (/zwho) page has been modified to be more readable, and it now lists the Z-Wave Basic, Generic, and Specific node type information.
Z-Wave debug logging now produces two log files rather than one.
When a device corresponding to a Cooper Wiring Z-Wave scene controller button was clicked OFF in the HomeSeer UI, the corresponding LED did not always turn off on the controller - this has been fixed.
All of the Z-Wave controller functions that used to pop up a status window have been replaced with realtime status updates in the same browser window. This improves the performance of all of the controller functions and eliminates replication issues due to timing problems.
