Michael
I've made a robust attempt as setting up mcsTemperature 5.14.6. I want to thank you again for your assistance in getting me through the hard parts.
During my setup I encountered things that I felt could be better. I know your working on a new version of Temperature, so I think my timing is good with this information. Let me know if you have any questions on this. Hope it helps.
1. Graphing.
a. Allow adjustment of right Y axis separate from the left Y axis.
b. Ability to control which trace is attached to which Y axis.
c. Min and max value.
d. Graticule scale and number of significant digits displayed.
e. Ability to control trace color and data point symbol.
f. Number of data points plotted per X axis division. Currently the 72 hour time scale could use a few more data points, but the others look OK as is.
g. All of these settings should be save-able with the Group, not global.
2. Temperature Control Loop pages.
a. Current layout, text, and formatting in the HS Events are very unintuitive.
i. Documentation or balloon help needs to explain what the purpose of Trigger Limits are. This is counterintuitive to a new user. Only the action tab limits are real.
ii. Action tab should group the two ONs and two OFFs. Use better text formatting. Put the two Enable check boxes near the conditional boxes.
b. Interface Setup tab for Priority needs more (especially faster) options. Currently the Run at Above Normal Priority option is about 1 minute updates. Would like a 10 or 20 second update option.
c. The Control function in the status is not linked to HomeSeer robustly. If the name is changed in the Status page it may not work correctly any longer, something gets out of sync (not sure of details).
3. Weather display.
a. Let the Screen and Chart Dimensions also apply to the Weather page. This will give the ability to scale the weather display, as is done with graphs.
b. Add support for animated radar, such as the .php files used by NWS.
c. If you click on the radar image it would be preferable to toggle to the alt radar URL instead of opening a new browser window.
4. Sensor page.
a. Undocumented Feature warning: Changing the device type in the Sensor page will overwrite HomeSeers device info. This can screw up devices, especially if your device is not something on the list. It changed my universal module into a switch device (closest item I found on list). After that my universal module did not work, I had to change it back to a universal module in the Status page. Can you give us user specified device capability? Would also like to choose N/A as a list option so that it does not overwrite HomeSeer’s data.
5. General.
a. In the interfaces page confirm the option Set Bad Reading to Zero works. Appears to me it always uses previous value, not sure.
b. Give ability to choose what house code is used. Currently fixed at [ and \.
c. How about using balloon help like in Sprinklers?
6. Plug-in Installation.
a. Confirm installation directory requirements. Be sure install dialog boxes state whatever is necessary.
b. I had a lot of problems with default settings and data entries not “sticking”. Never really figured it out. Seems to get better as the database fills out.
I've made a robust attempt as setting up mcsTemperature 5.14.6. I want to thank you again for your assistance in getting me through the hard parts.
During my setup I encountered things that I felt could be better. I know your working on a new version of Temperature, so I think my timing is good with this information. Let me know if you have any questions on this. Hope it helps.
1. Graphing.
a. Allow adjustment of right Y axis separate from the left Y axis.
b. Ability to control which trace is attached to which Y axis.
c. Min and max value.
d. Graticule scale and number of significant digits displayed.
e. Ability to control trace color and data point symbol.
f. Number of data points plotted per X axis division. Currently the 72 hour time scale could use a few more data points, but the others look OK as is.
g. All of these settings should be save-able with the Group, not global.
2. Temperature Control Loop pages.
a. Current layout, text, and formatting in the HS Events are very unintuitive.
i. Documentation or balloon help needs to explain what the purpose of Trigger Limits are. This is counterintuitive to a new user. Only the action tab limits are real.
ii. Action tab should group the two ONs and two OFFs. Use better text formatting. Put the two Enable check boxes near the conditional boxes.
b. Interface Setup tab for Priority needs more (especially faster) options. Currently the Run at Above Normal Priority option is about 1 minute updates. Would like a 10 or 20 second update option.
c. The Control function in the status is not linked to HomeSeer robustly. If the name is changed in the Status page it may not work correctly any longer, something gets out of sync (not sure of details).
3. Weather display.
a. Let the Screen and Chart Dimensions also apply to the Weather page. This will give the ability to scale the weather display, as is done with graphs.
b. Add support for animated radar, such as the .php files used by NWS.
c. If you click on the radar image it would be preferable to toggle to the alt radar URL instead of opening a new browser window.
4. Sensor page.
a. Undocumented Feature warning: Changing the device type in the Sensor page will overwrite HomeSeers device info. This can screw up devices, especially if your device is not something on the list. It changed my universal module into a switch device (closest item I found on list). After that my universal module did not work, I had to change it back to a universal module in the Status page. Can you give us user specified device capability? Would also like to choose N/A as a list option so that it does not overwrite HomeSeer’s data.
5. General.
a. In the interfaces page confirm the option Set Bad Reading to Zero works. Appears to me it always uses previous value, not sure.
b. Give ability to choose what house code is used. Currently fixed at [ and \.
c. How about using balloon help like in Sprinklers?
6. Plug-in Installation.
a. Confirm installation directory requirements. Be sure install dialog boxes state whatever is necessary.
b. I had a lot of problems with default settings and data entries not “sticking”. Never really figured it out. Seems to get better as the database fills out.
Comment