Michel Kohanim

Hi Tim, There are no errors so I wonder if they were actually sent. Are you sure the programs were run? Also - and just to be on the safe side - have you checked your junkmail? With kind regards, Michel

Hi Wuench, Unfortunately not. With kind regards, Michel

Hi Xathros, Yes, I think having two ISY's on two different locations, communicating via network resources, would work fine. With kind regards, Michel

Hi Marcos, I am so very sorry but, unfortunately, the only way to fix it is to have them ship you one with a different firmware. With kind regards, Michel

Hi Marcos, For 2411T, you have to make sure you have a specific firmware (SH usually helps updating your firmware to work with ISY). You need V1.3. If you have problems, please contact our support (links below) and we'll help you out. With kind regards, Michel

Hello pauliep, There's a solution for Pentair by Autelis: viewtopic.php?f=78&t=8766&p=66692&hilit=pentair#p66692 With kind regards, Michel

Hi pikach, This I cannot answer. You can do it with two ISYs communicating with one another. Unless, the distance between campuses can be covered by INSTEON RF but I doubt it based on your description. With kind regards, Michel

Hello PLCG, I am so very sorry to hear. Please bear in mind that the floorplan is legacy code that will eventually be removed. So, please do not count on it. Now, please do the following: 1. Clear your Java cache 2. Go to http://www.universal-devices.com/99i/admin.jnlp ... this will install an icon on your desktop which you can use to launch the Admin Console Please let me know if this helps. With kind regards, Michel

Hi BrianH, Yes, indeed ... I wished we had definitive algorithms for figuring out these quirks. With kind regards, Michel

Hi Bill, Got it. It does make sense and we do actually trap that (if you look at the logs, you see the commands issued to the scene). The only problem is that this is only trapped when a scene is activated from an ISY client and not a controller within a scene. I guess this would still be OK, correct? With kind regards, Michel

Hello everyone, Actually, we have all sorts of problems with many devices: 1. SWL Relay v41 2. Motion Sensor V22 (sticker) 3. IOLinc 4. 2441TH Initially, at least (still investigating), it seems that these devices report as i2 but expect i2cs. With kind regards, Michel

Hi Dennis, No it's not. Unfortunately we could never get them to provide us with their APIs. With kind regards, Michel

Hi Bill, It's technically possible but philosophically it's not since we never got a consensus as far as what constitutes status of a scene. With kind regards, Michel

Hi Rich, Please return it as I am not sure to what level we can fix these issues in ISY and what problems are thermostat firmware related. Especially since you only have one week to return. With kind regards, Michel

Hi Tim, What firmware version are you running and can you check your error log for -5000x errors and copy/paste them here. Or, you could take a look at: http://www.universal-devices.com/mwiki/ ... MTP_Errors With kind regards, Michel

Hi Bill, We currently do not have the means of sensing scene status ... this is a long story. Can you tell me if Roomie can send commands to programs? With kind regards, Michel

Hi RichTJ99, Still working on it. If all goes well, we should have a beta by the end of next week. With kind regards, Michel

Hi Brian, Only those you are having problems with. With kind regards, Michel

Hello rsstansbury, Please submit a ticket (links below) so that we can login to your computer and see what's going on. With kind regards, Michel

Hello OmegaQuest, Thank you. Do you have Windows Firewall? This is indeed really odd because all the symptoms point to the fact that ISY can not establish a connection to the Admin Console and thus expires the session. If you go to Help | About, is the UI version 3.2.6? With kind regards, Michel

Hello rsstansbury, I am so very sorry to hear about all these problems you are having. Indeed it must be quite frustrating. As far as the thermostat, I truly believe the probelm is the thermostat itself because the symptoms are as if the thermostat is reporting as a regular device but expects i2cs commands. But, now, we have much bigger problems to fix: 1. Do you actually get the login prompt and you can actually login without any errors? 2. If the above is correct, would you be kind enough to try httpS://your.isy.ip.address/admin instead? If httpS works, then the problem is firewall and especially Windows Firewall. If not, please do let me know so that we can schedule a remote session and figure out what's going on. With kind regards, Michel

Hello rsstansbury, Would you please let me know what's your ISY's firmware version? If not 3.2.6 (official), please upgrade and then remove and register the thermostat again. If 3.2.6, I can only suspect a defective thermostat. You might want to try Right Mouse Click on the Thermostat | Diagnostics | Query Insteon Engine. With kind regards, Michel

Hello osurh18, Do you have a good backup? If so, factory reset your ISY (press and hold the reset button for about 30 seconds) and then restore your ISY from your backup. Once Admin Console tries to restore your network configuration, it checks to see whether or not the current configuration is the same as the one you are trying to restore. It's up to you to decide which you want to keep. With kind regards, Michel

Hello OmegaQuest, Would you please try httpS://your.isy.ip.address and let me know whether or not there are any improvements? With kind regards, Michel

Hello nowandthen, Paid modules will not be reset by factory reset. So, your observation is correct. With kind regards, Michel