markens

Thank you @paulbates -- that thread refreshed my memory about looking for the "URL to ISY" URL in the tools/ISY Information menu. That gives me what I need for accessing the REST API via the portal. I couldn't find any reference to this when searching myself.

I'm bringing up a new eisy to replace a faithful ISY994i. In general, it's going ok so far, although not without a few hiccups My head is spinning from sorting through so much info about the process. I've searched for info about REST commands, but still have some questions: (1) I use the REST API on the ISY for commands from other devices. My ISY has a custom TLS certificate. I saw somewhere that the eisy does not support custom TLS certificates. Is this still the case? I can work with the self-signed cert on the eisy. But: will the REST interface continue to be supported on eisy? I remember seeing somewhere that this may not be the case. (2) I have a portal subscription. It seems using the portal is the preferred method for remote access to avoid port forwarding. I know about using the portal for access from UD Mobile, and for web access to admin functions on the ISY/eisy. But I haven't been able to find documentation on using some of the other portal functions that are available in the menus on the portal web interface. Certainly related to this: how do I use the portal to funnel REST API requests to my eisy? A pointer to relevant documentation would be much appreciated. Thanks! --Mark

I've used Namecheap for many years. They allow renewals out to a total of ten years, although without any significant (if any) discounts. At least for .com domains.

I had looked at this wiki page, but missed the key word "deactivation" and related section (focusing on the portal sections further down). This indeed seems to answer my question, thanks.

Hello! I finally got around to trying out ISY portal and node servers on my ISY 994i (firmware 5.0.16c), using the portal trial license. It's interesting technology, but doesn't look like it adds anything useful for my particular installation. So I'd like to remove the portal module and let the trial license expire. I've searched for instructions but can't find anything relevant. Neither can I find any menu items which might do this. Can someone point me to the right stuff? Thanks.

Thanks! I was hoping this was the answer.

I just had an old 2486D keypad (8 button) die. A factory reset does not bring it back to life; no leds and no response at all from the buttons. I've got an even older 2486D (from 2006) that I swapped in as a replacement, which is good for now. But it doesn't have "modern" features like settable led brightness. So I've been looking at this same question of replacement. Current product from Smarthome seems to be the 2334-222 as mentioned above. The 2334 appears to come with generic opaque "SCENE A" (etc) buttons. Custom etched are available, but I'd like to use my current clear buttons. They are currently still available and in-stock at Smarthome (2401CLB) and listed as being for "Insteon Keypads." Does anyone know if these will, indeed, work with the new 2334-222 keypads? Perhaps with an existing ("old") button frame if they don't work directly with the new switch? Related: Do the old color change kits (white/ivory/etc, similar to current 2401IV8) work on the new 2334-222? I have lots of these and it would be useful to use on the new switches if possible. But still want to use the clear buttons! The Smarthome website is somewhat confusing about compatibility. Thanks for any info!

This is such a simple example, but it really illustrates the power of ISY and insteon with regard to remodeling. I just added some long overdue path lighting in my front yard. Control of them was never an issue. Plugged the (dimmable) power supply into a lamplinc and added it to the ISY's front porch light scene. Done! No messy wiring to do and it works exactly as I want it to.

No, a windows 7 machine. I run the admin UI as a standalone applet (via jnlp link) as suggested, not in a browser.

Thanks, Michel. I did exactly as you suggested, and also disabled antivirus while running the admin app. Sadly, there is no change in behavior: anything I type in the find box still yields empty results. Everything else works fine! What now? Thanks.

I have the same problem reported in the original post in this thread: I click Find and enter a city, but the resulting "Areas containing xxxxx" window shows no results. This happens for any value I type in the find box. And it hasn't magically started working for me! I just upgraded to a new 994i PRO with 4.2.10 firmware and UI. I updated to latest java (windows 7 machine) and cleared the java cache with no change. What does work for me is entering four-letter airport codes of major airports (KXXX) directly into the Location ID box and clicking Save. I then get current data for that airport. What have I missed and how can I get Find working? I'd like to use a station closer than the nearest airport, which isn't close enough to be useful. Thanks.

LeeG: Thanks for the description of how one might use a 6-button frame in 8-button mode. That is quite useful info!

Are you asking if you can independently control the light in the bottom button of a 6-button KPL? If so, the answer is "no." The following info is the result of testing I've done on my KPLs to see exactly how they respond. The top/bottom buttons on a 6-button KPL are somewhat different than the others in that they, together, represent the local load (device 0) and cannot be controlled separately by the ISY. Note there is only one ISY device for both buttons; they are not independent. How the lights work in those buttons depends on the toggle mode set in the firmware. Luckily, the ISY makes it easy to see and set that option. I don't know if the following is true for older 6-button KPLs, but it is for newer ones: As shipped, the KPLs are in toggle mode. For 6 button KPLs, this means that the top ON button illuminates when the local load is on, and the bottom OFF button illuminates when the local load is off. This is true whether the load is controlled locally by the top/bottom buttons, or remotely via ISY or other switches. You can see this option in the ISY by selecting one of the KPL's devices and then click "Buttons Toggle Mode." For device 0 (the local load) the option will be shown as "Toggle" mode. It's easy to modify the behavior so that the top ON button comes on when the local load is on (and goes off when the load is off), AND keep the bottom OFF button off at all times: Simply change the toggle mode of the 0 device to "Non-Toggle (On)." "Non-Toggle (Off)" seems to do the same thing for this device. So you can control whether the bottom button is illuminated or not when the load is off, but that's about it. If anyone has different info, I'd love to hear it. Thanks!

Success. As I discovered and posted previously, the ISY is prepared to use exactly one SSL cipher suite: SSL_RSA_WITH_RC4_128_MD5. So any server it communicates with must allow this suite. In openssl (and apache) terminology, this is suite RC4-MD5. Most server configurations probably allow this by default, which is why the ISY https "timeout" problem is spotty. But ciphers using MD5 are considered undesirable at this point, and many security-conscious sites have disabled them. I forced RC4-MD5 to be accepted on my server, and the ISY is now happily talking to it. Yay! --Mark

Hi Michel, Thanks for the clarifications. OK, I'll stay with 2.8.16 until I'm ready to play with variables. I'm so blind! Thanks. Good to know. Just to make sure, this means that self-signed certs are ok as well? Also good to know. Well, it turns out things are a bit more complicated than that. Yes, browser is on same home network as ISY, and server sees requests from the same IP address. And both http/https requests work from the browser, and http from the ISY. Investigating ISY https request further: The server is seeing connection opening and traffic exchanged (SSL negotiation). Using ssldump, I now see what the problem is: The ISY is prepared to use exactly one SSL cipher suite: SSL_RSA_WITH_RC4_128_MD5. My server is prepared to accept many cipher suites, but not that one. Hence the SSL handshake fails. I will now research why my apache server is configured to exclude this cypher suite. Most likely I'll simply enable it and things will work fine. I'll report back with my findings in a few days. Thanks, --Mark