Michel Kohanim

Hi, If you have ISY99i PRO and if you are in the Batch Mode, then ISY does not ask you to do anything till you either click on Write updates to device menu item (right mouse click on the node) OR you get out of the batch mode. If neither is the case, then this must be a bug. With kind regards, Michel

Hi Tim, Even if ramp rates on the secondary buttons were adjustable it must have been a bug since secondary buttons do not have any on level/ramp rate associated with them. If you are talking about ramp rates/on level for devices responding to a secondary button, then that must be a bug. Is this the case only for your LL? With kind regards, Michel

AnthemAVM, What does ISY report for the firmware version on your IOLinc? With kind regards, Michel

Hi Illusion, yes, please wait for our next update which has the X10 issues fixed. With kind regards, Michel

Hello 87boosted, We are very interested in supporting both Modbus and Bacnet. The only issue is ROI: how many can we sell? Currently, you are the only one requesting for this solution! With kind regards, Michel

Hi ergodic, I think our choices are pretty limited: it's either ISY or the PLM. After power failure, ISY and the PLM are powered up simultaneously and thus they should work immediately. Now, if the power circuitry in the PLM is defective, when they are both powered on, the PLM might not have enough juice to power up ISY while it's going through its start up sequence. Of course, the best test would be to either replace the PLM or ISY and see if the problem is solved. If you do not have an extra PLM, please contact us and we'll send you a replacement (refurbished) ISY to test with. With kind regards, Michel

Hi Bob, Thanks so very much for the update. It seems that the issue lies with your PLM (not connected) and thus ISY is now in safe mode (you cannot save any programs nor can you see them). What I recommend is this: 1. Unplug your PLM and leave it unplugged for 1 minute 2. Make sure the cable between ISY and your PLM is connected securely at both ends 3. Plug your PLM back in If you still see v.0.0.0/not connected then I strongly recommend getting a replacement PLM. With kind regards, Michel

Hi Tim, I am so very sorry! This has been fixed in 2.7.7 and above. If you want to upgrade to 2.7.7 (very stable), please send an email to tech@universal-devices.com. If you want to go to 2.7.9 alpha which supports V2 thermostats as well, then please register here and you'll be sent the instructions: http://forum.universal-devices.com/viewtopic.php?t=930 With kind regards, Michel

Hello ctviggen, I am so very sorry to hear this. Would you be kind enough to go to Tools | Diagnostics | PLM Status/Info? Also, please do ensure that you have cleared your Java cache. With kind regards, Michel

Hi helipal, I must conclude that your computer's firewall blocks Java (or other application) access to network. You do not have any issues with corporate firewall since you can get to the homepage via your browser. Is this something that your IT dept can help with? If not, do you know what firewall software is running on your computer? With kind regards, Michel

Hi hart2hart, It was a design decision on our part to fake the PLM into thinking that it was sending a direct command. PLM's group commands caused major network issues for us and they do even to this day and thus the decision. One of the issues is that since ISY is very adamant about receiving each and every signal, when PLM sends a group command the process of counting the the acks may be interrupted by any other signal. And, thus, we could never count on its accuracy anyway (just like KPLs that might blink one time and not other times). This is especially the case for large scenes. With kind regards, Michel

Hi ergodic, Thanks so very much for the test. My premature conclusion is that one of those devices on the powerstrip is the cause for your troubles. So, the next time this happens I would unplug those devices (excluding the PLM) one at a time to see if there's any improvement. If none, then the problem is either the PLM or ISY (I tend to think it's the PLM but only because of past experiences). With kind regards, Michel

Hi ergodic, Would you be kind enough to try this procedure (basically simulating a power failure): Unplug your PLM (which removes power from ISY) and then plug it back in. Does this work? Also, after power failure, is it the case that you cannot communicate with ANY of your devices or just a certain few? With kind regards, Michel

helipal, at the minimum, I suggest upgrading to 2.7.7 ... if you feel brave, then upgrade to 2.7.9 and you should see the button in Configuration/IR tab. With kind regards, Michel

Hi helipal, It's quite possible that your company has blacklisted some private IPs. Can you get to ISY's homepage (not the Admin Console) from work? If not, then it's surely a firewall policy in your company (but this is extremely rare). If you can access the homepage then would you be kind enough to let me know which firmware does your ISY have? With kind regards, Michel

Hi hart2hart, Yes, there was a small batch of SWL v35s that exhibited signal sensitivity issues. The newer versions all work fine. With kind regards, Michel

Hi MarkJames, Thanks so very much for the update (and words of encouragement!). Please send an email to support@universal-devices.com and we'll have the instructions emailed to you. With kind regards, Michel

Hi MarkJames, 1. Please try 2.7.7 and above 2. Please note the following: a. IOLincs versions 31 and below return the status of their sensor for the status of the relay regardless of the status of the relay. So, if you have any programs that depend on the status of the relay, then that would explain why you have to turn it off then on b. As Rand mentioned, in momentary mode, IOLinc does NOT resend the status of the relay when it's been turned off With kind regards, Michel

Hi ergodic, I am so very sorry to hear about these problems. To be honest, I think your PLM is dead (cannot communicate with the rest of your devices). Moving to 2.7.9 is not going to help. Indications that the PLM is dead: 1. Going to Tools | Diagnostics | PLM Status/Info shows disconnected 2. The RX light remains lit on your ISY With kind regards, Michel

hart2hart, First let me ask if that specific SWL is version 35. If so, that explains the issue you are having. With group commands (activating/deactivating a scene), ISY does not hear acks back. So, it assumes that they all worked out OK unless one (or more) send a NACK. In most cases, this does not happen. With kind regards, Michel

rlebel, Yes. With kind regards, Michel

intellihome, Thanks so very much for this excellent news and workaround. With kind regards, Michel

Hello hart2hart, This means that after you add a KPL/RemoteLinc button to a scene, the status of the KPL/RL button is no longer updated in ISY if you activate/deactivate the button physically. This problem is not readily reproducible but it does happen once in a while and especially with KPL v36 and new installations. With kind regards, Michel

Hello all, Matt at SmartHome has been extremely helpful in tracking down Venstar gurus and has gotten an answer which I post down here verbose (THANK YOU MATT): It seems that the only thermostat version that is causing problems is the T1700. I talked with Mike at Venstar and he provided a quick fix to stabilize the humidity value (if you’re good at soldering). Look near the humidity sensor spot on the T1700 PCB. You can short the two contacts located next to the “C32” text. This will set the humidity value to 0% permanently. With kind regards, Michel

Hi Wayne, I am almost certain that they are not. You may want to post this question to the SmartHome section. With kind regards, Michel