Finally spent some time with the recent PH release, which has the new Insteon Explorer in it. That's the only piece I was really reviewing.
I found some things I really like and some I really don't and some that seem like a good start and I'd expect to change.
My raw notes:
Notes
"Tab Scrollbars"
When I turned on "tab scrollbars" it messed up the tab views a bit if a given tab was scrolled at the time
"tab scrollbars" makes reports unreadable - they are scroll-happy.
The "<> Remove Ctlr" thing on links is WAY to the right.
Misc Notes:
really like the "pending operations" and "completed operations" and "sdm log" stuff. Very useful information.
Pending operations should have option to eliminate or otherwise isolate recurring pending operations, such as regular polling.
Same for completed operations. I don't want to see recurring pending or completed UNLESS there's something wrong with them like too many NAKs or whatever.
TX lines should not be red. Red is bad. Should be green or blue or something.
If TX colored, RX should be colored something else. only NAKs or other errors should be red.
Even better, user-selectable based on config preferences
LOVE the idea of tracking NAK/ACK count.
Don't like the method of getting Insteon devices in.
Data entry or auto-learn only?
Should have spidering.
Should have option to learn from attached PLC device.
Should have import device option (with defaults to ID and description or whatever other required data fields).
Don't like that a missed critical field causes the whole record to be deleted and start over. Should have a default value. If the field is a unique field, the software should create a default unique field data element.
Links:
Shouldn't require "refresh" to see devices already created in the Devices (middle) section.
The < > method of adding and deleting links... yikes. drag and drop? right-click? something else...
When a device in the controllers / responders sections is "ID NOT FOUND", it should have the right-click option to "add"
Overall look & feel of Links section is great if you have 3-5 devices... but becomes a scrolling nightmare with 50+
Needs a left pane for devices instead of a center-pane.
A method to make a given device invisible in all controller/responder windows. I have every device - and every button of every KeypadLinc - linked to one PLC now; they'll be linked to three PLCs eventually. I don't want to see eighteen PLC links on every KeypadLinc I look at. I'd like to have a "don't display links" option on a per-device basis.
Huh... just noticed the "< > Remove Resp" at the bottom... man, that's a weird way to do it.
Should the "button number" for the load of any device be "1"? as in HouseLinc? similar to the Group number?
Default on level and ramp: can PH learn these from the device then use them as they are currently learned when sending a standard "on"?
PLC Groups:
How do I assign them to a button? I create a group name... and... uh...
How do I assign devices and their functions to the group number I create in PH?
KPL Config:
Why doesn't the KPL show up?
Reports:
Why are all the "good" things expressed in red?
I found some things I really like and some I really don't and some that seem like a good start and I'd expect to change.
My raw notes:
Notes
"Tab Scrollbars"
When I turned on "tab scrollbars" it messed up the tab views a bit if a given tab was scrolled at the time
"tab scrollbars" makes reports unreadable - they are scroll-happy.
The "<> Remove Ctlr" thing on links is WAY to the right.
Misc Notes:
really like the "pending operations" and "completed operations" and "sdm log" stuff. Very useful information.
Pending operations should have option to eliminate or otherwise isolate recurring pending operations, such as regular polling.
Same for completed operations. I don't want to see recurring pending or completed UNLESS there's something wrong with them like too many NAKs or whatever.
TX lines should not be red. Red is bad. Should be green or blue or something.
If TX colored, RX should be colored something else. only NAKs or other errors should be red.
Even better, user-selectable based on config preferences
LOVE the idea of tracking NAK/ACK count.
Don't like the method of getting Insteon devices in.
Data entry or auto-learn only?
Should have spidering.
Should have option to learn from attached PLC device.
Should have import device option (with defaults to ID and description or whatever other required data fields).
Don't like that a missed critical field causes the whole record to be deleted and start over. Should have a default value. If the field is a unique field, the software should create a default unique field data element.
Links:
Shouldn't require "refresh" to see devices already created in the Devices (middle) section.
The < > method of adding and deleting links... yikes. drag and drop? right-click? something else...
When a device in the controllers / responders sections is "ID NOT FOUND", it should have the right-click option to "add"
Overall look & feel of Links section is great if you have 3-5 devices... but becomes a scrolling nightmare with 50+
Needs a left pane for devices instead of a center-pane.
A method to make a given device invisible in all controller/responder windows. I have every device - and every button of every KeypadLinc - linked to one PLC now; they'll be linked to three PLCs eventually. I don't want to see eighteen PLC links on every KeypadLinc I look at. I'd like to have a "don't display links" option on a per-device basis.
Huh... just noticed the "< > Remove Resp" at the bottom... man, that's a weird way to do it.
Should the "button number" for the load of any device be "1"? as in HouseLinc? similar to the Group number?
Default on level and ramp: can PH learn these from the device then use them as they are currently learned when sending a standard "on"?
PLC Groups:
How do I assign them to a button? I create a group name... and... uh...
How do I assign devices and their functions to the group number I create in PH?
KPL Config:
Why doesn't the KPL show up?
Reports:
Why are all the "good" things expressed in red?