Over the last few days, I upgraded my EISY as I wanted to give the new eisy-ui a try. I ran Upgrade Packages to upgrade IoX from v6.0.4 to v6.1.2._10. Then I ran Upgrade Packages again to update the following:
eisy-ui = from v1.4.4_2 to v1.4.5
PG3x = from v3.4.27 to v3.4.28

Background Info: I added an 'i3' suffix to the name of all my i3 devices to tell them apart from older insteon devices. After the upgrades, I was looking around the new eisy-ui and comparing it to the old java-based Admin Console (jAC).

jAC Issue 1 - Programs with i3 in IF Statement Displays Unsupported Ruleset
I noticed that the jAC can no longer handle 11 of my 13 Insteon i3 devices. I first noticed this in the jAC while looking at a program that triggers on an i3 paddle switch device's status. It appeared as follows. Notice the Unsupported Ruleset in the IF statement. I was unable to edit the IF condition in the jAC. My best guess is that this is because the jAC cannot correctly read these i3 devices statuses.

The same program containing the i3 device showed the IF condition correctly when veing in EISY-UI.

jAC Issue 2 - i3 Paddle Switch Not Displaying Status of Primary Node
The next symptom I noticed is the primary node of the same i3 paddle switch does not display its status in the jAC at all. Below I recorded a video to demonstrate this. Watch as I move between standard devices and i3 primary devices. When selecting an i3 device, the jAC continues to display whatever it was displaying just before selecting the i3 device. This happened on 11 of the 13 i3 paddle switches I have. The flag (65) node seems to display correctly.

On 2 of the 13 Insteon i3 devices, the primary device displays correctly. Below is a video of 1 of the 2 switches that display correctly. I created a test program using the working i3 device below in the IF statement as in Issue-1 above. I did NOT see the Unsupported Ruleset message.

jAC Issue 3 - Cannot Add i3 Device to Scene as a Controller
Because of the above issues, I initially thought that I had a problem with the particular i3 device being corrupted in EISY. Therefore using the jAC, I deleted the 'Front Lantern Lights i3' device from my EISY and then added it back in. However, when I attempted to add the i3 device to a scene, I found I could not switch from Responder to Controller. (When I clicked the Controller/Responder button in the scene Confirm Add dialog, nothing happened.) I could add the i3 device as a Responder but NOT as a controller. I eventually figured out how to add the i3 device to my scene by using the Add to Group right-click menu item. It would have been better if this was called Add to Scene though...

Other Info:

• I do not currently have an issue as I managed to figure out how to add my i3 device back into the scene as a controller. I just thought that perhaps others may benefit from reading my post.

• Thinking that I was using an older version of the admin.jnlp, I found the little icon in the upper right corner of the eisy-ui page and used it to download the admin.jnlp file to run the jAC. It made no difference.

• I do not have any of the 4-button i3 switches.

• I cannot figure out what is different between the 2 devices that work vs. the 11 that do not. All of my i3 paddle switches show as being v.54 firmware.

• I discovered that the i3 devices have additional flags under the flags node. There are new flag items (Night Mode, Hop Powerline on RF, Night Max On Level, Night LED Brightness, Night Ramp Rate, etc.) I have never seen before.

-Emile

Edited 1 hour ago1 hr by EVictory

Admin Console is deprecated, please only use eisy-ui. New i3 features are the first thing not included in admin console. From here out divergence from Admin will increase.