Balok

Thanks, that's helpful. Until my 994 goes down or I can't get serial modems any longer, I do not see replacing it. Maybe if Insteon releases enough new devices, or if I decide Insteon isn't reliable and go with a different technology. I am assuming that as a Polisy successor the eisy does what Polisy did, supporting a lot of different technologies and an extensible architecture, but I haven't researched it beyond what someone (you?) said that part sourcing troubles is why Polisy has been superseded.

Just received notification that the i3 (dial dimmer) is available for sale. It looks nice but without some kind of clear indication that it works with my isy994, I can't see purchasing it.

Agreed. The form is very nice but function is what matters most to me.

These devices look very nice, but I need to know my ISY will support them before I buy. Insteon, one hopes, realizes this and will do everything it can to help, not hinder, third party developers.

Thanks. I am running Windows 10. I found those files (where Java said it stored temp files, which is a subdirectory of that path). I had to use a finder app to see them; they do not appear in regular File Explorer despite it being configured to show hidden items. They showed having been created yesterday, the last time Admin Console appeared full screen with the tree control fully opened. I take that to mean that at some point something deleted them, but I don't know what. My antivirus software is not allowed to delete anything without asking. Unless Java is. I can't find a setting in Configure Java for controlling this. I gave Java a little more space for temporary files, but it really shouldn't need that; I don't have a lot of temporary Java files.

Version 5.3.3, but it has been the case since at least 4.8. If I have not opened the Administrative Console in awhile (maybe two weeks?), it frequently opens sized to take up my entire window, and with the tree control on the left side (where devices and scenes are displayed) fully expanded. Can this be turned off somehow? It's most disagreeable to me. Ideally, I'd like it to remember how it was sized, and what was open, when I last closed it. Can that be done?

Okay, thanks. This has answered my question. I got us both doing the same thing, using the launcher instead of directly accessing the admin console.

I already had 5.3.3, and when I looked at 5.3.4 I decided the single identified and fixed issue wasn't worth a new download, that's all. I really don't think upgrading to that is going to fix this problem. I believe my brother and I both use launchers. When I click the icon, I see a white rectangle splash screen which reads "Universal Devices", similar to what's on the ISY enclosure. That then loads "ISY Finder" which displays a line for the single ISY I have, and second or two later automatically starts the admin console for that ISY. My brother's icon starts a launcher with a blue square splash screen with "UD" similar to what's at the top of this page. It also launches a finder, but that finder has a larger font and does not automatically start the admin console. He has to click the single line, then select how he wants to connect. Neither of us is launching the Admin Console directly (http://<ip address>/admin.jnlp). That does not work for me. It wants to download "admin.jnlp". Attempting to run that, from a shortcut or a browser, does not work for me. I get "Unable to launch the application", and the name, publisher and URL it attempted. I also tried "http://<ip address>/" in a browser. That connects, but not to the admin console. And when I try to open the admin console from that page, I get a page that tells me to leave it open and... nothing else happens. I have ad blocking and anti-virus software running; it could be these links will not work for me because of that. In short, the only way I can open the admin console is through the finder. It does not seem that this is a common problem. Thanks for looking at it.

I upgraded my firmware from 4.9 to 5.3.3 and it seems to work. I got a finder which looks different (smaller font) from the old finder, and has a white splash screen with Universal Devices. Choosing Help -> About shows 5.3.3 for both the Firmware and the UI. This finder automatically opens the ISY (since I have only one, this makes sense). I then had my brother (we live in the same house) clear his Java cache and sent him to https://isy.universal-devices.com/start.jnlp to get a new admin console for his desktop. Since the ISY was at that point updated to firmware 5.3.3 I used that link. When I updated it, I used http://isy.universal-devices.com/994i/5.3.3/admin.jnlp since at that time I was updating from 4.9. His finder is larger and has the older blue square "UD" splash screen. In addition, it does not automatically open the ISY admin console as mine does. But when he logs in and chooses Help -> About, his About box also shows 5.3.3 for both the Firmware and the UI. It looks like he got the new UI, but an old finder. What did I do wrong and how can I fix this for him? (I tried launching the admin console from the direct link, but this does not work. It just tries to save admin.jnlp and when I do that, that icon produces only an error message.) Thanks.

Got mine backed up and this version installed using the automatic option with no difficulty. I have no interest in navigating the apparently hazardous path from 4 to 5 - I think I'll wait until my ISY quits and I get another one!

I assumed they'd make other changes than just the caps to make a very high reliability unit. If they didn't get the power supply right, there's probably other things they didn't get right as well. So I just sort assumed somewhere around 150% of the current price.

It shouldn't even cost that much. The caps aren't that much more expensive. They ought to be able to boost the reliability significantly and still come in well under $200.

This was one of the symptoms I saw when mine quit. The LED would take a long time to light, or wouldn't light at all. Also seen: intermittent communication: the ISY was able to read the address and thought it was connected, but it could not retrieve status information. Interestingly, this did not generate errors; I guess there is limited error handling in the protocol (when I disconnected the PLM, the ISY detected that reliably). When I installed my new PLM, I had to restore from a backup (which I'd made when signs of trouble appeared) before the File -> Restore Modem command would work. There were some reported comm errors, but the setup is working as expected. Weird.

It is not a comm problem. I temporarily reassigned a button on an eight button keypad that's in a table enclosure, positioned it as electrically close to the wall-mounted keypad as was feasible, and it behaved correctly. In addition, all other buttons on the wall mounted keypad work fine and reliably. Finally, the wall mounted keypad used to work fine, until I changed it from a six to an eight button keypad. Something about doing that affected the way the keypad handles this kind of scene. It's not a big deal; at some point I'll replace the six button keypad with an eight button keypad. I'm posting this mostly so that folks know that a six button keypad transformed to an eight button keypad is apparently NOT the same thing as an eight button keypad right out of the box. That, or there is some difference about how the ISY handles a six button keypad changed to an eight button keypad.

This check was among my debug efforts, yes. All the buttons command their scenes/devices properly, except the one that's supposed to respond to the follow scene.