Michel Kohanim

Hello Elvis, Do you have any baby monitors around? Also, what's your thermostat's firmware version? And, finally, what's your PLM's firmware version? With kind regards, Michel

Hello mrxmas, In most cases, it's best to run the Admin Console version equaling to the firmware version. This can be done in two ways: 1. Use the network shortcut which downloads the Admin Console directly from ISY --> it will have the same version as ISY version; OR 2. Go to Help | About, find your version (Insteon_UD99 v.nn.uu.mm where nn.uu.mm is the firmware version) and then go to http://www.universal-devices.com/99i/nn.uu.mm Please clear your Java cache before you doing either. With kind regards, Michel

Hi matapan, Unfortunately not yet. With kind regards, Michel

Hi Tom, I totally understand and YES, you can use a different ISY for production, restore your backup from the development as long as the PLM remains the same. This said, I do not feel right that you would have to purchase another ISY just to test our current release. Please do send me an email (tech@universal-devices.com) and let's see what we can do ... perhaps a short time loaner of some sorts? With kind regards, Michel

Hello GreyFox, I do apologize for the inconvenience. Please do be kind enough to submit a ticket (link below) and we'll schedule a remote session to see what's going on. With kind regards, Michel

Hello rodtoll, Is your questions whether or not ISY can trigger a program in case of change in status of "any" switch or one switch. If one switch then the following should work: If Status device_a is not off Then .... If you want to add more devices, then you can Or them together If Status device_a is not off Or Status device_b is not off Or ... Then .... If you want to sense actual button presses, then what you need to do is to use Control instead of status. With kind regards, Michel

Hello GreyFox, My pleasure. So, the remaining question is whether or not M1XEP does actually have the IP address that you have set in the Admin Console. Please go to https://elk.m1xep.address and see if you can communicate with it. With kind regards, Michel

LeeG, thanks so very much! You are 100% correct. johnnyt, there's a bug in 3.1.x where the time in the Admin Console does not get updated properly. The issue is in the Admin Console and not ISY. With kind regards, Michel

Hello AutomationNut, Please upgrade to 3.1.16 and then follow the instructions below to link it to ISY: http://www.universal-devices.com/mwiki/ ... rmostat_V2 with kind regards, Michel

Hi Tom C., My pleasure. We are hoping to have 3.1.x official release by the end of this month. So far things look good. Since you are using a lot of network resources - and if you don't mind and if you can ensure you have a good backup - I would appreciate it if you could upgrade to 3.1.16 and make sure your system still behaves the same. The reason is that we decoupled Network Resource activation from program execution so, now, program only requests for the resource to be activated and then continues. The resource activation requests are queued and run in a separate thread. This has boosted program execution performance dramatically with the caveat that you cannot be certain that the resource is activated prior to the end of the program. Your input will be quite appreciated. With kind regards, Michel

Hello Tom C., Unfortunately not in the current releases but, based on your input, it shall be implemented in 3.1.17. With kind regards, Michel

Hello GreyFox, Your assumption is correct. When ISY connects to ELK, you will see ELK status messages at the top of the Admin Console. As per your screenshot, ISY is not currently communicating with ELK. This could be caused by three things: 1. You do not have the correct firmware version for ELK and ELK's Boot loader 2. When you changed ELK RP settings to support the non-secure port (2101), you didn't press the Send button to activate M1XEP with non-secure port 3. You have ELK RP connected ... ELK RP has to be disconnected for ISY to be able to communicate with ELK For 1, please review: http://www.universal-devices.com/mwiki/ ... quirements For 2, please review: http://www.universal-devices.com/mwiki/ ... guring_Elk With kind regards, Michel

Hi dss, Thanks so very much for the feedback. I do not think ZWave would work if the door lock is the only ZWave device in your network since: 1. Max range of ZWave radio is around 300ft 2. You need between 6 to 12 devices to have a good mesh (depending on the size of the location) We shall investigate Zigbee. With kind regards, Michel

Hello kaisersoze, You can currently do this by having a program that is only run at Start up. With kind regards, Michel

GreyFox, You absolutely do NOT need the ELK module. The most basic reason for buying the ELK module is "where do you want your rules to run"? If you are comfortable with the rules running in ELK (those that deal with alarm state and communicating with ISY), then you are all set. All you have to do is to export your lighting to ELK and then program rules. If you want your rules to reside in ISY, then you would need the ELK module. I hope this answers your question. With kind regards, Michel

Hello dss, Unfortunately not ... or at least not simply because there has not been much demand for it. Obviously, we are very eager to add more capabilities to 994iZ series ... just have to figure out support for devices with a little ROI. With kind regards, Michel

Hello gfridland, I have not seen those causing any issues but it might be that there are not very many installed. The best test would be to make sure you have good scene communications with all your devices. If you have failed communications with a few, please see if one is a ToggleLinc. With kind regards, Michel

Hello gfridland, Sorry, for the lack of update. This is fixed in 3.1.17. With kind regards, Michel

Hello ahwman, Excellent question and the answer is that we had complaints about the green not being bright enough. So, presupposing that ISY would be where the router is (and probably hidden) we went for the brightest blue LED on the market! With kind regards, Michel

Hi LeeG, Thanks so very much! I had completely forgotten. We should change that mostly because we use XML and, in some cases (not always) and some clients have a hard time with a / and differentiating it from /> especially when the / is at the end of the string. Admin Console work regardless but we had to put this constraint for some clients. Perhaps we can remove this limitation. With kind regards, Michel

Hello everyone, Thank so very much for the feedback. Even though there's currently no way for dimming the LEDs, we'll surely take this into consideration in our future HW designs. With kind regards, Michel

Hi Brett, I think you have one of those PLMs that have issues with RF devices. Please send an email to tech@universal-devices.com and we'll try to sort it out for you. With kind regards, Michel

Hi dsdee, Apologies I didn't see your post before. Which default names are we talking about? I am not aware of any default names with / in them. With kind regards, Michel

Hi Guys, Sincere apologies. All of these relate to intermittent program behavior when state variables were being used. In some cases, the old value of the state variable was still being used for evaluation even though a new event had updated the status. With kind regards, Michel

andyf0, what's the precise error please? dgm0522, please go to Event Viewer on Device Communications events and turn on/off a few of your switches locally. Do you see any events in the Event Viewer? Slalom, still investigating ... as you may note, a fix for this issue is not listed in our release notes. With kind regards, Michel