DNewkirk

What were historically referred to as scenes are now "Groups" in EISY-UI. Your existing ones should still show up, but now to create a new one click the "+" sign at the top of the nodes screen, and choose "New Group". To add members, right click the node you want to add and choose "Add to Group" and select the group in the mis-named "Scene Selector" dialog box. Scenes still exist, but they refer specifically to the settings specified for a specific controller in a group, since each group controller have their own settings on how bright the lights are, etc. See https://forum.universal-devices.com/topic/47346-groups-vs-scenes-suggestions for additional explanation of scenes. To edit the parameters for each group controller, click on the group in the Nodes screen, and then expand the controller (click the ">") in the right hand pane. From there, you can edit the brightness and other parameters of each responder to that controller.

Mine is similar. My 2844-222 (Motion Sensor II) does not respond to any options changes in EISY-UI. Even if it did respond, the options exposed in the Configuration>Options menu us significantly reduced from the options exposed in Admin Console:

@Jimbo.Automates Version 2.1.0 no longer makes the paired device nodes as children of the main Homekit Hub node, but puts them all at the root of the tree. Is this by design? After installing this update, it also renamed all of my thermostat nodes to generic "T9 Thermostat" or "T9 Plus Thermostat", although it kept them in their previous folders in the node tree. Dave

Yes, the node info is the same in mine: But if you right click the node and choose Configuration, there is no "Options" option in the configuration screen: Dave

@Javi None of my Insteon Plug in Dimmer Modules (2457D2) expose any configurable options in EISY-UI (or in AC). The module supports the 4 options typical of most Insteon devices (i.e. Program Lock, Transmit LED, No LED and Beep) as well as Resume Dim and Load Sense On/Off. There is no "Options" button on the Configuration menu in EISY-UI, nor is there an Options button on the node screen in AC. Most of my modules show up as "(B2457D2) LampLinc BiPhy v.43" although a couple are v.41. The behavior is the same for both versions. Is this by design, or is there some corruption in my installation? Thanks, Dave

Eastern Time Zone on production repo 1.4.6. System time changed with no issues. The sunrise and sunset times on the graphic on the configuration page are an hour early, but my programs that run at sunset have the correct next run time, so go figure.

On the Insteon protocal page, you can turn off "Automatic Writes to Devices" or "Automatic Writes to Battery Devices" similar to the buttons on the top of AC. I didn't find a Write to All Devices command, so I assume that once you turn this back on all of the stale devices will write but I haven't actually used this option either in AC or EISY-UI.

I am on EISY-UI 1.4.6. If this has been corrected in 1.4.8, please disregard. I use a lot of Insteon Micro Modules to control my lighting. I install these behind either standard wall toggle switches or, in many cases, Victorian push button switches. Either I have misunderstood the programming of the options on these units, or the options menu in EISY-UI has reversed the logic of some of the micro modules options both from how they actually operate and and how they were presented in AC. By default, the modules are shipped configured for a latching switch (Momentary option is off). If a momentary switch is used, the Momentary option must be enabled. The modules come with two sense wires. By default, the module only listens to the sense #1 wire (yellow). This way the module works with a standard single pole switch. If a double pole switch is used and connected to both sense wires, then the Dual Line option must be enabled. A third option determines how the switch responds to the power on the single sense wire. By default, it will switch the load when the sense wire either senses power applied to the sense wire or when power is removed from it. This way, throwing the switch will always switch the light either on or off, even if it was previously switched by a different controller. This is the default and it is called 3 Way mode. It is active when the Line High always mode is turned off (i.e. not selected). If it desired that the light always follow the attached switch, the option must be enabled (i.e. 3Way mode turned off). If this is done, it may be necessary to flip the switch twice to control the light (i.e. if the light is on but the switch is off, turning off the light with the switch will require you to turn the switch on so that it matches the light and then turn if off to turn off the light). In AC, these options were clearly labeled, and the additional explanatory text in red made it even more obvious that you had to deselect the option to choose the option in red (the default mode). In EISY-UI, the logic has been reversed. The options have been labeled with the AC red actions, which are NOT what you will get if you select the option. The options in EISY-UI should be labeled "Momentary" rather than "Latch", "Dual Line" rather than Signal (?) Line, and "Line High On, Line Low Off" rather than 3-Way. Even better, the wording from AC should be used directly, providing the information of what turning the option on does, as well as what leaving it off does. In addition, the option labeled "Ramp Dim" in EISY-UI should say "Resume Dim". Enabling it makes the light come back on at the light level it was at when it was turned off. It has nothing to do with ramping. If I have misinterpreted these items, please correct me. Thanks, Dave

The ability to present as main node and "subnode" is defined by the node. If a node has a defined parent (or child), right clicking on the node will include "Group Nodes" among the options. Choosing this option will move the subnode to be below the main node, where the tree can then be collapsed to show only the main node. This is not to be confused with the ability to "Add to Group". There has been some discussion to change the nomenclature of combining nodes and subnodes for clarity. I am not sure what controls if the nodes/subnodes are grouped by default. Some node servers generate main nodes with subnodes that are introduced into IoX with heirarchy, while some seem to come in flat (i.e. with the subnode next to the node rather than below it). One beta node server I have used (LG ThinQ by @TJF1960 ) came in heirarchal in EISY-UI and flat in AC in my installation for some reason. Dave

@Javi Continuing our side discussion started in https://forum.universal-devices.com/topic/47304-no-scenes-in-eisy-ui/, my understanding of the programmatic intent is as follows (please correct any misinterpretations I have made): Groups: Are a collection of various nodes that have been associated together to act in concert. They appear in the node tree in IoX as a separate entity and contain other nodes, some defined as controllers of the group and others defined as responders to the group. Groups can have multiple controllers and multiple responders. They are analogous to what were referred to as Scenes in Administrative Console. Scenes: Are a defined subset of a group, associated with a specific group controller, which specifies the on level or other parameters of the responders in the group when the group is activated from that controller. Scenes are designated by the group controller which activates them, have no separate name, and do not appear in the IoX node tree as separate entities. Every controller assigned to a group has an associated scene, which by default contains all responders and controller/responders in the group at an on level of On or 100%. When the first node (controller or responder) is added to a group, IoX creates a virtual controller of the group (with a name to match the group) which also has an associated scene. The virtual controller's scene is invoked whenever the group is controlled programmatically by IoX, and the scene associated with a specific controller is invoked whenever the group is triggered by that physical controller (switch, keypad button, mini module, etc.) Since IoX (and Insteon) need to know what you want to happen when you press a physical button, every physical controller can only be assigned (as a controller) to one group, and therefore has only one scene associated with it. Although every controller's default scene that is assigned when the controller is added to a group contains all responders at full brightness, each scene can subsequently be modified in EISY-UI (and in AC). Each responder in a scene can have its brightness, ramp rate and retries changed. Responders in the group can effectively be eliminated from a scene entirely by setting their on level to off, even while they remain in the group. It should also be noted that these scenes are implemented in native Insteon commands (at least for Insteon nodes) and will therefore continue to operate in the absence of IoX and the EISY controller. Implementation of scenes can also be mimicked programmatically in IoX by creating programs that set individual on level for each desired responder node. A couple of suggestions for future updates to EISY-UI to reinforce these distinctions:Right clicking a node in the EISY-UI node list brings up the option to "Add to Group". Subsequent dialog boxes, including the Scene Selector and Add to Scene should be changed to Group Selector and Add to Group. Throughout EISY-UI (and UD Mobile for that matter) most references to Scenes should be changed to Groups. Since Scenes are not separate entities, they don't actually appear anywhere in the node tree. In generic Insteon linking (i.e. without a hub or controller), the linking process actually creates a group and automatically modifies the associated controller scene since the responder is linked to the controller at whatever on level the responder is currently set to. In IoX, the addition of a controller to a group sets its scene at full on for all responders. Similarly, adding a responder sets it at full on for all controllers. This is understandable, since the association is being made remote from the physical entities and if a controller were added to a group when all of the responders were turned off it would appear that the linking failed since none of the responders would come on with the controller. However, to reinforce the availability and customizability of scenes, it would be desirable to add an additional radio button to the Add to Group dialog box so that when a node is added, a separate option allows the user to "Customize Associated Scenes". Leaving this unselected would preserve the existing behavior: all responders would be added at full brightness to new controllers and new responders would be added at full brightness to existing controller's scenes. However, if Customize Scenes was selected, it would bring up a dialog box listing existing responders (for added controllers) or existing controllers (for added responders) and what their associated levels should be for the added node. It is my impression from forum comments and threads that many users, particularly new users, aren't aware of the possibility of customizing scenes within an IoX group. As you have indicated, this has been further muddied by the nomenclature that has been used in the past. This enhancement (with associated documentation on the wiki) might go a long way to clearing up the confusion on this issue and providing users additional flexibility in the way that they utilize their systems. Dave

That might work, although combining them doesn't necessarily collapse the combination as it could still stay expanded in the tree. To me, collapsing is what you do to the tree after they are "grouped". Maybe associate, combine, cluster, or unite? Of these options, I think I am leaning towards associate or cluster, but maybe others can chime in on what terminology would be clear to them. Dave

@Javi I appreciate this explanation. I was confused by the switch from scenes (which has been referenced by every resource up to now, including the forums, wiki and even Insteon documentation) to groups. I understand now what you are trying to clarify. You might also give some thought to how to refer to devices or nodes that have "subnodes". Right now, this is also referred to as grouping nodes in Eisy-UI, not to be confused with groups previously scenes. Some other term might be better for this consolidation of subnodes under the prime node, although I can't come up with any recommendations off hand. Dave

@Jimbo.Automates Thank you, Jimbo. 2.0.20 installed and appears to have addressed the noted issues. Dave

@Javi Thanks for the explanation. I know that eventually the point will be moot, but I was just curious if my current (6.1.2_7) installation of AC was corrupted, or if this is by design (or more accurately, purposeful omission) in AC. You have answered my question. Dave

I recently installed my first I3 device (an I3 dial) in my Insteon network. I am using an EISY on the latest production version of IoX/Eisy-UI (6.1.2_7/1.2.2) so I installed it through Administrative Console. After installation, I could see both the I3 dial and I3 dial flags nodes, but when I click on the I3 dial node, AC would not show any data, and I could not control the light. Clicking on the I3 flag node would correctly populate the various flag values. I also could not select the I3 node when trying to control this light via a program. In Eisy-UI 1.2.2 I can see the I3 dial node and flag node values and control the light. I know that AC is going away, and the Eisy-UI is the up and coming way of managing Insteon devices, but is this normal with the 6.1.2_7 AC console or is my installation missing some type of configuration file? I was under the impression that I3 devices could be fully managed under the current iteration of the AC. Any insight would be appreciated. Thanks, Dave