Michel Kohanim

Hello everyone, Sincere apologies for tardy reply as I was not in the office today. You can use any SD Card up to 16GB; this said, since we still do not know the root cause (yes, it does look like SD issue but we are not certain), I would stick with anything you can find at the moment. With kind regards, Michel

Thank you. I responded to your email. There are a few things that stick out: 1. ISY cannot get an IP address from your router ... this has to be resolved 2. 192.168.1.13 trying to hack into ISY (does not use the correct credentials) Apart from that, we need to isolate as many variables as possible. Does the IOLinc relay control anything? With kind regards, Michel

Hi Tim, Thank you. This is quite odd. The only things I can think of are: 1. Perhaps the WB variable was not being populated 2. If you have spam filters on your SMTP server, perhaps it didn't like the contents With kind regards, Michel

Hi hbsh01, Thank you. Can you tell me whether or not you have any programs based on the status of this IOLinc? With kind regards, Michel

hbsh01, Two comments: 1. We have had at least 3 reports of conductor causing a crash on 3.2.6 ... we are investigating but it's difficult since Brad is no longer maintaining conductor 2. If you have Mem/Err blinking, it's quite possible that after the upgrade, your ISY got a new IP address which is now in conflict with some other device on your network. This is only the case if your ISY is not setup with static IP address And, finally, what's your router's make/model number? With kind regards, Michel

Hello hbsh01, In addition to Error Log (as Xathros suggested), please go to http://your.isy.ip.address/rest/config and send the result to support@universal-devices.com . Also, do programs continue to work when the unit is locked up? With kind regards, Michel

Hi Tim, What did you change it to so that it works? Is your WB still reporting properly? With kind regards, Michel

Hi Wuench, Yes absolutely but it's very low on our priority list (currently). Are these devices unplugged? Is it always the same devices? With kind regards, Michel

Hi Tim, The fact that you have to reset your PLM to get status is NOT good and must be fixed. Also, this could explain why your notification program does not work: If the program depends on status of a device, it's quite possible that the PLM is not sending status updates to ISY because either it no longer has the link to that device (you factory reset) or it's dead. Now, what happens if you right mouse click on that specific program (for which you have notification problems) and then choose Run Then? Do you get the notification? With kind regards, Michel

Hi Rich, This is not a fair question to ask us! We should have a beta this coming week and we'll let you decide on your own. With kind regards, Michel

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