Thanks for all the great feedback (and bug reports). It looks like beta 11 (released last night) fixed the responder UI bug that some folks were seeing.
Below are answers and comments on a bunch of the posts up to this point. If you have an open question/comment, then be sure and read through these.
gbreeze wrote:IMHO - the link manager should probably be it's own window, available from the main "Window" menu rather than having to navigate through a device.
It isn't available via the Window menu, but I did add to beta 11 an item (and shortcut key CMD+L) to the Interface menu.
gbreeze wrote:It would like to suggest devices with valid Insteon addresses should appear in the pull down of devices in the link manager. I've got quite a few undefined modules (with undefined addresses) in anticipation of future purchases with Norm.
This is a good point and request. Unfortunately, it is a bit complicated. The problem is most of the UI shown for editing links is contextual and changes based on the device type/properties. The UI shown for a KeypadLinc is different than that of an ApplianceLinc, for example. I could, of course, add some way to specify the Device type before Indigo links up with it, but that is yet more UI and options.
gbreeze wrote:For devices like the ControlLinc, it would be really nice to see the links associated with each button.
This should be working in beta 11 now.
gbreeze wrote:This may be a bug related to the preceding item, but I can't add a new link to a responder in an "Send Insteon Scene/Group" under the Action Groups either.
Yep, same bug that should be fixed now.
gbreeze wrote:Doing one better for the ControLlink - it would be really cool if there was a "Virtual ControlLinc or RemoteLinc" GUI
Agreed. Having some alternative visual/graph representation of the links and what they are assigned to would be neat. Not going to happen for 2.5 though.
bschollnick2 wrote:But I have found is that if I change the Group number to 2, and then change it back to #1, it then draws correctly.
Should be fixed in beta 11.
snowjay wrote:Couple of questions... When I create an Action Group and then do a "Show All" all the Insteon Groups/scenes are listed as such with their number next to them. Would it be possible to populate that field with the description as well?
Yes, I'll try to get that into the next beta.
snowjay wrote:Say I create a group #10 on the Powerlinc and it controls the main load on the Living Room KPL. In that same group if I try to control button #3 on the same KPL and sync, both the above links are deleted.
Currently, this is a limitation to how Indigo manages links. Indigo only lets you define links in devices if they contain unique address/group number pairs. Indigo masks the complexity of having to define links in both controllers and responders. Every link is really a pair of links, one inside the controller device and one in the responder device(s). Indigo has an underlying (and simplifying, which means less bugs) assumption that every controller link has exactly 1 responder link per responder device. In the case you are describing you really need 1 controller link that has 2 or more responder links
in the same responder device. This gets much more difficult to manage (and sync) internally, so Indigo doesn't allow it, at least not in the current version. The solution as you have found is to use multiple scene/groups. It may not be quite as bad as you think though -- you can control multiple KeypadLink LEDs in one scene/group IF they are inside different KeypadLincs. You just cannot control multiple buttons on the same KeypadLinc (or control the KeypadLinc's main load and any of its buttons) from within the same scene. I'll consider revisiting this at some point -- I had hoped it would take longer than 24 hours for someone to find this.
bmoraes wrote:I just upgraded to 2.5 beta 11 and I'm having linking issues. Whenever I change anything on link manager I cannot link the changes.
Presuming dsnider's suggestion doesn't help, can you email me (indigo-support at perceptiveautomation.com) your Indigo database file? I need to take a look at it to see what is going wrong.
dsnider wrote:It would be nice to define a specific scene and name it.
Good idea. One can already name the PowerLinc's group/scenes, but the other remote devices cannot currently be named (or re-used). I think snowjay's suggestion is a good one though. Then you only have to have the scene programmed 1 time, versus having Indigo (even if it is automated) push the scene out multiple times to multiple devices.
snowjay wrote:I had a couple of scenes with the above sceneiro. What I did was create an Action Group that contained the Insteon commands for the scene, and then use a Trigger Action for each button press to activate that scene. Speed wise I couldn't tell any difference than if the buttons were programmed locally. Obviously this wont work if you want to turn off your computer.
Actually, I believe this should work if you upload the logic to the PowerLinc 2414U even if your Mac is turned off. That type of Trigger Action (on receive of INSTEON command, send a PowerLinc group/scene command) is supported in beta 11. So one could not define any INSTEON scenes in their remote devices, and instead program them all into the PowerLinc and use Trigger Actions to execute them all. I'm not sure if this is a good idea or not, but it is an interesting approach. Note that the PowerLinc can only send 255 unique scenes, however. And Indigo limits it to 250 since I have something else planned for a couple of those last ones.
snowjay wrote:One feature I would like to propose is the ability to add/edit the PowerLinc groups/scenes without having to edit an action. For not I just created an Action group that is not used anywhere and have been doing all my manipulation there.
Agreed. I need to address this.
Thanks again for all the great feedback everyone! I consider this a successful beta already and it has only been a couple of days!
Regards,
Matt