Michel Kohanim

Thanks so very much oktane. Got the email and we are investigating. With kind regards, Michel

Hi rlebel, Known issue with our cryptography library and JRE 1.6 on MAC. Still trying to figure out how to fix it without having to rewrite the whole engine. On the Excel sheet, are you given the option of disabling security for Macros. In Windows, you are given the option of disabling security otherwise you will get a blank sheet. With kind regards, Michel

Hi tahoe, If you do not mind giving them access to the unsecure port (80), then all you have to do is to open port forwarding to port 80 instead of 443. Certificates are very important since, otherwise, anyone being able to hack into one ISY can get to others as well (knowing the private key). With kind regards, Michel

Hi ryarber, It means that there are pending write operations for that device. If it does not go away, it means that ISY could not complete the operation fully. So, it memorizes where it left off (persistent) till the comm. errors are fixed and everything has been written to the device. With kind regards, Michel

Hi 87boosted, Thanks so very much for your detailed response. Our Orchestrator Series currently supports reading meters equipped with Zigbee SEP 1.0/2.0. Orchestrator is only sold to the utilities directly. The main question I have is: with the push for SEP and standardized Energy Service Interface, don't you think Modbus for meter reading will become legacy within the next couple of years? I am very open to using ModBus Ethernet since it does not require hardware modifications (such as additional ports). Is there a minimum level of support/requirements that can provide the maximum amount of functionality? With kind regards, Michel

nachthorn, This is fixed in the next drop. hart2hart, We have to investigate the IRLinc issue. Currently, the best thing to do would be to send us your backup files (tech@universal-devices.com) and please let us know the address of your IRLinc. Thanks SO very much. The KPL issue should be fixed in the next drop. With kind regards, Michel

Hi ryarber, Indeed removing one will remove all. You need all these nodes for everything to work properly. I am not sure why you cannot group them ... Please note that in order to link these devices, you have to make sure that they are in the OFF position (clicking the mode button till you see off on the display). Please remove them all, factory reset, make sure the thermostat is in the off position, and then try Link Management | Start Linking. With kind regards, Michel

Hi Dave, Unfortunately not that I have been able to configure. Button A is the load on an 8 button KPL and although it works in grouping (i.e. turning a sub button can turn it on) but mutually exclusive buttons cannot turn it off. The best solution is to use a scene and change the on level to 2% (0 does not work) for each one of the buttons for which you wish mutual exclusivity. With kind regards, Michel

Hello oktane, When you are trying to remove the SWL from the scene, does the Admin Console ask you to put the RL in programming mode? Also, would you be kind enough to go to Event Viewer (level 3), retry, capture the log and post it here? With kind regards, Michel

Hi AnthemAVM, It's very important to figure out the version number. We have two choices: 1. Remove the IOLinc from ISY and this time add it using Link Management | Start Linking 2. Check the back of the unit to see if it has a label with the firmware version In versions 31 and below, IOLinc always returned the status of the relay for the status of the sensor. This is the root cause of all issues. With kind regards, Michel Michael, I am not sure I checked correctly but in the header it says v.00

Hi, Thanks so very much. We will look into this. With kind regards, Michel

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