MikeBro

Is this issue actively being addressed, or do I need to open my own support ticket?

I have the same problem. I don't understand; are you saying I have to buy a new piece of hardware, that they cannot or will not fix a software certificate problem? Why would I buy again from such a company?

Well, I just needed to unplug the device and plug it back in again, and now all is well (knock wood). D'oh.

I have an isy99i. It's been a long time since I've run the admin console. When I do, and after I enter my name and password, I get a requester "I have read and agree to the terms ...". (Clicking "read" shows the UDI PDF). After I click "Agree", the program shuts down after about ten seconds, even if I do nothing. This happens every time, using IE or Chrome. What can I do? ---Mike

As usual, your support was superlative. I thought I had done everything correctly, but of course I must have missed something. ---MikeB

Ok. Did that, rebooted, and no change; still fails to run from the icon, or when I click on the link in Michel's message. It never asks me to accept a certificate.

Michel, I don't see how to remove all (or any) certificates in the ISY Configuration Utility. I see "generate", "receive" and "install" selections in the menu. ---MikeB

I get an exception now when I launch the console from my desktop icon (Win7), even in administrator mode or using compatibility settings (suggested XP mode). No problem when launching from Internet Explorer. Any ideas? JNLPException[category] at com.sun.javaws.LaunchDownload.checkSignedResourcesHelper(Unknown Source) at com.sun.javaws.LaunchDownload.checkSignedResources(Unknown Source) at com.sun.javaws.Launcher.prepareResources(Unknown Source) at com.sun.javaws.Launcher.prepareAllResources(Unknown Source) at com.sun.javaws.Launcher.prepareToLaunch(Unknown Source) at com.sun.javaws.Launcher.prepareToLaunch(Unknown Source) at com.sun.javaws.Launcher.launch(Unknown Source) at com.sun.javaws.Main.launchApp(Unknown Source) at com.sun.javaws.Main.continueInSecureThread(Unknown Source) at com.sun.javaws.Main$1.run(Unknown Source) at java.lang.Thread.run(Unknown Source)

Not sure if this is a question or an answer, but when I query an (old) EzRain or a (new) EzFlora that has one valve ON, my ISY99i changes its status to OFF. It doesn't actually turn it off, though. I discovered this while using my iPhone app, which uses REST, but it's true from the Admin console as well. I also discovered that querying anything but valve 1 does nothing (which is fine with me). I'm using v3.2.6.

I don't think I explained clearly. I don't want to query the controller (e.g. an X10), but I want the ISY99 to know the state of the responder, which *is* linked, regardless of how the state was changed. If I can't trust the ISY to know the state of every responder it is linked to, then I presume I need to make sure I query the device before trusting what the ISY99 tells me. Not a big deal, but I'll probably want to make that somewhat automatic.

Not sure if this is related, but I've noticed that at least some of the time the ISY is unaware of changes to any of my devices when controlled by a controller that is not itself linked to the ISY (X10 or Insteon) until I query the device. Is this normal?

Thinking about what you said, I did a "restore device" on both the IOLinc and the KPL, and now it's working, so apparently one or both lost it's link records. It's not the first time this month I've had to do a restore. What causes this? Perhaps I should schedule the ISY to do an occasional restore.

I have a garage door IOLinc grouped in scenes with a KPL button. If I use the KPL or the ISY99 software to toggle the garage door, all is well, but if I open the door with the original button or remotes, status is not updated. If I "query" from the admin panel, the ISY status is updated correctly (but not the KPL button). This seems to be true with other (more ordinary) scenes as well, including when I trigger them from a grouped KPL button, but I've only fully verified it with the garage door system. I notice I have a "query all" program that runs every day at 3am. Should I just set that to run say every five minutes?

Duh. Thanks again Lee! P.S. For those reading this thread, a big disadvantage is that although the light on the keypad is now "reversed" properly, all the software shows the garage door sensor being "on" when the door is closed, which is less than ideal. The moral is to indeed use an OC (open circuit) sensor.

I had tried "trigger reverse" (and just tried it again); it does not seem to do anything.