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.

Yes, that's what I assumed about the name - it's just an artifact. The ISY does see all eight "nodes" or buttons, so I am sure I have converted it properly. I checked the release notes to see if an issue of this sort was mentioned, and it was not. I generally do not upgrade software unless I am trying to fix a problem that I know the upgrade addresses. Upgrading "because it's there" has disappointed me on a few occasions, and broke me of the habit years ago. I did check the program to ensure it was addressing the correct button. I'm certain that's not the issue.

I'm running 4.2.30. I've experienced no reported errors. I tried using Restore Device (from the Admin Console) on all involved devices under the theory that one of them had become corrupt. This behavior started when I converted the 6 button keypad to an 8 button, which makes be suspicious that either there's some kind of error there, or some kind of problem with the way the ISY handles converted keypads. I notice, for example, that it continues to call the keypad a "(2334-2) KeypadLinc Dimmer 5 buttons v.43". However, when I added the converted device the ISY correctly detected 8 buttons. In addition, the 8 buttons all work (can be added to scenes and can then control them properly).

I had a six button keypad (2334-232). Button D on it was the sole member of a "follow scene". It was meant to follow my living room light, controlled by a dimmer 2477D. One program ran when the Living Room Wall Switch 'Status' was "not off" and turned the follow scene on. The other ran when the Living Roomn Wall Switch 'Status' was "off"; it turned the follow scene off. The idea was that that button "D" would track the state of the Living Room Wall Switch even if it was turned on by a scene to which button D did not belong. Button "D" was also a controller of a scene to which Living Room Wall Switch belonged. The Living Room light could be turned on using button D, Living Room Wall Switch, or from a scene activated from a different keypad, or programmatically. The idea was that button D would track the state of the Living Room even if it was later added to other scenes. And this worked fine. Then I converted the 2334-232 to eight buttons using the conversion kit Smarthome sells, removed it from the ISY and then added it back in, and - I thought - put everything back the way it was (working from notes). The ISY thinks the keypad is working properly; when I turn off the Living Room Wall Switch from inside the Admin Console, the button on the keypad shows off. But it is still lit. When pressed, it goes out. I'm not sure what the problem is, here. If someone with some experience in follow scenes or converted keypads has seen something like this, I'd appreciate hearing about it. Or maybe I'm trying to do something too complicated and there's a better approach. Thanks.

Thanks!

I'd like to change a six button keypad to an eight button keypad. Is the best way to do it inside the ISY Admin console to just delete it and then add it back? Are there any hazards to watch out for (i.e. like the problem reported when changing RemoteLinc2 number of keys)? Thanks.

Okay, thanks. My theory was that since the router has a firewall and all my internal machines have software firewalls and run AV software, and I'm careful what sites I visit, I was reasonably safe from downloading malware that could then make holes for itself without me knowing about it. But you're probably right; it should be shut off. Thanks for the help; it seems to be working with manual port forwarding.

It might be... if I knew better how to do that. I think I have it working. I set the external port to the same value as the internal port and chose the correct IP address, and that seems to have solved the problem. Can you recommend somewhere I can read why UPnP is a security risk? Thanks.

My router supports UPnP, and that function is turned on. No configuration changes were made to the router between a period where the ISY could communicate, and a period where it could not. And its firmware has not been updated. The only firmware update recently is to the ISY. I did that to get the security improvements (doesn't use SSL any longer); I sure hope it wasn't a mistake, because I haven't got an installer for 4.2.18, the version I was using. I've been burned a few times by software and firmware updates, as a result of which I don't generally take them immediately, and then only when I am trying to solve a problem.

My ISY can run programs and adjust scenes. The router's port light shows amber, meaning 10/100, and blinks periodically with activity indicators, leading me to remove "bad cable" from the list of possibilities. The cable hasn't changed since I installed it years ago, and no part of it is damaged. I doubt it's that.

Somehow, despite my not having changed settings since August (when I changed a port number to resolve a conflict - the settings didn't change for a long time prior to that), my ISY-994i became unable to reach the Internet. That is, when I choose File -> Enable Internet Access [my system name] I get the Busy screen with progress bar for a second or so, and then a message "Failed Enabling Internet Access". I've tried rebooting both the ISY and the router, and it did not help. The ISY shows up in my router's list of attached devices. UPnP is selected on the ISY configuration screen and enabled in the router. Automatic DHCP is turned on on the router, and the router is configured to reserver a particular IP address for a device with the ISY's MAC address; the address that shows up in the attached devices list is the correct address. I'm not sure what's wrong. The ISY isn't even two years old; it seems unlikely that it would fail so soon. I did upgrade to 4.2.30 a few weeks ago, but communication was possible after I did that. Anyone have any ideas what I could try? What can cause the Administrative Console to issue this message? Thanks.