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

@DNewkirk I don't have a direct answer to your question about how well the I3 devices are supported under AC, so feel free to shame me for providing a suggestion, but I do have a good number of I3 switches on an eisy running beta code. From what I've seen, the I3 devices seem to be much better supported in the browser versus the old AC, so much so that I've stopped using the AC altogether.

Given the AC is going away, and you also have at least one I3 device, I might suggest considering your migration to eisy-UI sooner than later. It takes a little getting used to, but it's pretty functional now and the I3 devices seem to be well supported there, especially with recent updates specific to the I3 (as shown in the release notes - see screencap below).

Also - see https://wiki.universal-devices.com/Insteon_-_i3 for more details specific to the I3 devices.

We made recent enhancements to i3. However these changes were not added to the admin console.

The reason? The admin console has static profiles that must be bundled in each build making it difficult to manage. eisy-ui and newer clients, like UD Mobile, use dynamic profiles retrieved from firmware by request, making them easier to manage as all clients now have a single point of Truth.. So it is a business decision to save time, and push users to the new interface as the old is now obsolete. if using a firmware version that supports new i3 implementation eisy-ui is very close to feature parity with the Admin Console. This is the first real functionality divergence between the two clients.

@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