marksidell

Michel got back to me (very quickly!) with a fix: sudo pkg install -f udx sudo service udx restart (wait two minutes) sudo service isy status Spouse is happy again

I was able to ssh into the dead eisy. This looks bad: [admin@eisy /var/log]$ tail messages Mar 11 18:15:33 eisy kernel: pid 64484 (isy-freebsd-x64), jid 0, uid 349: exited on signal 11 (core dumped) Mar 11 18:15:54 eisy kernel: pid 65354 (isy-freebsd-x64), jid 0, uid 349: exited on signal 11 (core dumped) Mar 11 18:16:14 eisy kernel: pid 66177 (isy-freebsd-x64), jid 0, uid 349: exited on signal 11 (core dumped) Mar 11 18:16:35 eisy kernel: pid 66928 (isy-freebsd-x64), jid 0, uid 349: exited on signal 11 (core dumped) Mar 11 18:16:56 eisy kernel: pid 67800 (isy-freebsd-x64), jid 0, uid 349: exited on signal 11 (core dumped) Mar 11 18:17:17 eisy kernel: pid 68624 (isy-freebsd-x64), jid 0, uid 349: exited on signal 11 (core dumped) Mar 11 18:17:38 eisy kernel: pid 69385 (isy-freebsd-x64), jid 0, uid 349: exited on signal 11 (core dumped) Mar 11 18:17:58 eisy kernel: pid 70248 (isy-freebsd-x64), jid 0, uid 349: exited on signal 11 (core dumped) Mar 11 18:18:19 eisy kernel: pid 71071 (isy-freebsd-x64), jid 0, uid 349: exited on signal 11 (core dumped) Mar 11 18:18:40 eisy kernel: pid 71828 (isy-freebsd-x64), jid 0, uid 349: exited on signal 11 (core dumped)

This release bricked my eisy. Oh well. Now what? Update: I am able to ssh into the eisy. Any way to diagnose what's wrong?

Thanks for the responses. I am able to restore the programming of the keypad from the eisy, and do other updates, such as scene changes. So, I think the eisy is able to communicate with the keypad. The z device is a leviton plug-in dimmer. It does work in an eisy scene with a different keypad as the controller.

More: I've determined the problem is that the eisy is receiving no event when I press a button on this particular keypad. More specifically, it receives events when the "main" on/off buttons are pressed, but not when one of the other four buttons is. I recently upgraded to an eisy. Is it possible the programming for this keypad didn't get set up correctly? I've tried restoring the device. That succeeded. Also, the device is able to control other Insteon devices, but of course that doesn't depend on the eisy doing anything. How can I fixe the device programming short of deleting and re-adding it?

Is it possible to add a z wave device to a scene with an Insteon device as the scene controller? I was able to add a z wave device, but turning the Insteon device on and off has no effect. Insteon responders in the same scene do work.

yes, both.

I'm running 4.5.4.

I've had this problem for years, and am wondering if anyone has a solution. When I launch the Administrative Console, it prompts me to login three times in a row before it's finally happy. There's a brief pause before each request. Any ideas? (Of course, I'm running the latest everything.)

Thanks to everyone for the suggestions. I added the ISY to the Java site list, but I still get multiple login prompts. I know the java program is connecting to the ISY, because it initializes the devices list, and I can start working with devices, but shortly after logging in I get one or more addition login prompts. Just now I got three and then everything was fine. What exactly is happening that is causing the login prompts? Is it because the java program loses its connection to the ISY?

Thanks for the suggestions. I'm not running an anti-virus program. What do I have to do to get Java to trust the ISY's address? It's a local address on my LAN, of course. Another strange thing is that this used happen, and then it stopped happening for a long time, but in the last couple of weeks it's started happening again... with the exciting new development in 4.4.6 that the admin program quits after the second, or third or fourth, login prompt.

Sorry if this has been asked before... First, I cannot launch the admin console from the ISY web interface running in Chrome. I assume this has to do with java being disabled in Chrome. So instead I click the "Install Admin Console" button and launch from the resulting admin.jnlp shortcut. All fine. But, after I login to the admin console, and the console appears to be operational, a few seconds later it prompts me to login again. Sometimes it prompts a third time. If I cancel any of these subsequent prompts, the only menu option that works on the console is File. Got any idea why it keeps prompting me to login even after I have successfully logged in? I'm running version 4.3.26 (firmware and UI). And wow, it just went from bad to worse. I upgraded both the firmware and UI to 4.4.6 (and cleared the java cache). Now, after it prompts for a login the second time, the program just... quits.

Wow, exciting. Ok, I've done steps 1-5 above and everything appears to be working again. Phew. I held off doing step 6 -- Restore Devices -- because it sounds kinda scary. But I'm sure there are devices with garbage data, which seems to accumulate over time in Insteon devices. Questions: Is Restore Devices safe? Does the ISY verify the data it writes and tell me which devices couldn't be written correctly? Many thanks to all here who helped. Y'all a great!

Thanks for the replies. I want to make sure I understand what I should. Is this correct? Restore the ISY from a backup Unplug the ISY and PLM Plug in the PLM Plug in the ISY Restore Modem Restore Devices

Yes, I do.