Michel Kohanim

gfridland, The issues are KPL related: 1. Mutual exclusive buttons 2. Buttons from the same KPL in the same scene If you do not have any of these conditions, then everything should be migrated automatically. rlebel, No, because once 2.7.10 migrates 2.7.9 files, it's going to ignore certain bytes and thus restore will not work. With kind regards, Michel

Hi richardl007, Apologies for the inconvenience. Would you be kind enough to let me know: 1. Which firmware version does your ISY have? 2. Do you access your ISY remotely using HTTPS? 3. When the web server stops, can you access ISY locally at home? With kind regards, Michel

Hello wacvmd, If you have communication issues, I do recommend replacing them. In some cases, they would cause communication problems impacting communications with other devices as well. With kind regards, Michel

greg, Yes, this must be quite frustrating ... First of all, let's make sure that we are coming to the right conclusions: I am not sure I understand how we arrived at IOLinc working properly and ISY being the culprit. In short, you linked a dimmer as a controller to your IOLinc and it worked properly. Whereas, in your previous posts, it seems as if you are controlling the IOLinc relay from the Admin Console and not from a controller (or a scene). One more test: What happens if you create a scene, put your dimmer as a controller and the IOLinc RELAY as the responder? Does IOLinc respond properly? Please note that IOLinc will never ever send a status update when it turns off (or on) in momentary mode. With kind regards, Michel

Hello all, Apologies for causing a panic! We put that notice up there to discourage new installations. Please note the following: 1. 2.7.10 will automatically migrate your system from 2.7.8/9 2. The only things you might lose (are not going to be in synch with ISY) are KPL related settings: -- Mutually exclusive button for the same KPL -- Buttons from the same KPL controlling one another 2. If you really want to go back to 2.7.7, you will have to RESTORE the backup from 2.7.7 ... 2.7.7 cannot backward migrate file system With kind regards, Michel

Hi robandcathy, Apologies for a tardy reply (I was sleeping!). Is is possible that this device is a SwitchLinc v35? Hi Nick, There was an issue with the file system which could have contributed to what you are experiencing. This has been fixed ... With kind regards, Michel

Hi greg, This seems to be an issue with the IOLinc itself: if you turn it on and it turns off by itself even though you are not in momentary mode, then there's something really wrong. Can you try: 1. Remove the IOLinc from your ISY 2. Do a factory reset on it 3. Add it back to ISY and check again With kind regards, Michel

Hello robandcathy, I suspect you have some signal/noise issues. Can you query this device? If not, try doing a factory reset on it and then a Restore (right mouse click | Restore Device). If that still fails, then we would have to figure out what's preventing the signal to get to your device. With kind regards, Michel

Hi Nick, We'll have to check into it ... was this the last entry in your log? Please note that log entries are flushed to the file at some intervals so, if possible, check your log again and see if you have another entry for that device now. With kind regards, Michel

Hi evarsanyi, that would be PERFECT! Thanks and with kind regards, Michel

Hi Mark, This error happens when the motion sensor sends a NACK to the PLM. In most cases, when motion in sensed, the motion sensor should send a group command to the PLM + all associated responses. NACK is sent when the MS has problems processing something. Do you get these errors on ALL your motion sensors or only one? If only one, I would do a factory reset on it and retry. If on all, then I would check the location of your Access Points. With kind regards, Michel

Hi Nick, Apologies for the inconvenience. Are you saying that the logs show that the program actually ran but the devices do not respond nor do you get any errors in the log? Please note that you are not going to see comm errors on the Admin Console if a) there was a comm error and the subsequent command was successful. What we need to find out are -2s in the log right after the execution of the programs. With kind regards, Michel

Hi AnthemAVM, The best and least intrusive method is this: 1. If your KPL button is already a controller in a scene, then add the "something" in that scene as a responder and then remove it 2. If your KPL button is NOT already a controller in a scene, make scene, but the KPL button as a controller in the scene, add the "something" as the responder in the scene and then remove both as well as the scene With kind regards, Michel

Hi Carl, I personally do not recommend disabling SSL because your credentials will be in cleartext and thus anyone, by the virtue of knowing your IP address, can turn on/off your devices and change all your programs. Now, if you so choose to use HTTP, all you have to do is to change the port forwarding port from 443 to 80. And, from then on, you can use http://your.external.ip.address . With kind regards, Michel

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