Michel Kohanim

Hello Illusion, This is quite odd as 3.1.13 has gone through rigorous testing and seems to be quite stable. Can you tell me: 1. Whether or not you have the ELK module? 2. Do you use any mobile apps and, if so, which one? 3. What is your PLM's version? Hello Wayne, The fact that you have a Wait in there is a suspect. As you may know, Wait is interrupt-able. This means that while Waiting, if the condition turns to false then the program stops. The best way to test this program would be to temporarily add notifications before and after the Wait. With kind regards, Michel

Hi munch, Thank you. This is a combination of issues relating to the way NetGear (or similar) routers manage DHCP reservation and how 2.8.16 responds to those anomalies. If you don't mind, please upgrade to 3.1.13 which includes workarounds for these types of situations. With kind regards, Michel

Hello mdcastle, If your ISY's firmware version is at 2.7.15, then please try the following URL: http://www.universal-devices.com/99i/admin.jnlp Once loaded, click on the Add button on ISY Finder and then enter the HTTPS IP address for your isy (i.e https://your.isy.ip.address) and retry. Also, what do you see when you to go Tools | Diagnostics | PLM Status/Info? With kind regards, Michel

Hi munch, What is your ISY's firmware version? Also, please do look at the Tools | Erorr Log and let me know if you see any connection/network errors. And, finally, when this happens, do your programs continue to run? With kind regards, Michel

Hello Jeff, I understand and again I do apologize for the wasted time. Hopefully the new unit will work right out of the box. With kind regards, Michel

Hi Mike, Yes, you can have as many as 32 simultaneous connections and 10 subscriptions. When the Admin Console locks up, does your ISY programs still function? With kind regards, Michel

Hi cul8rv8, Sincere apologies for tardy reply and the inconvenience. It does look like that your device is not functioning properly. The initial boot up sequence should be: 1. Power 2. RX/TX 3. Short MEM 4. Power only Is this the sequence you see? With kind regards, Michel

Hi johnnyt, this is great. Thanks so very much for sharing. andyf0, yes, the batteries are going to drain if we have to query them every few minutes. Personally, I really do not think this is a good solution for temperature reading as it has ill-effect on the overall performance of your system. With kind regards, Michel

Hi Brian, sincere apologies for tardy reply. 1st, please do upgrade to 3.1.13. 2nd, please take a look at your Error Log and check for network connection issues and let me know. With kind regards, Michel

Hello johnnyt, Can you tell me which one wire temp sensor you are currently using? With kind regards, Michel

Hi tim2u, Yes, indeed. With kind regards, Michel

Hello rtp130, It all depends on what the camera can do based on the motion. If it can call a URL, then you can do anything you want. On the other hand, if the motion triggers something on a web server/mail server, then we need to figure out how to extract that information in ISY. With kind regards, Michel

Hello w1cked, Can you tell me where you purchased this unit from and what was the date of purchase. Also, it would be great if you could let me know the serial number (tech@universal-devices.com). With kind regards, Michel

Hi Teken, Thanks so very much for the vote of confidence. We'll do our best to beef up the documentation and perhaps add some training videos and material. With kind regards, Michel

Hello Teken, Yes, you can achieve all of those. The major blocking issues for us are: 1. The device has to be polled frequently ... this means that now all your programs might have a delay of (number of energy displays * polling execution delay) at every (number of energy displays * polling intervals). To me, this does not make a good system especially since all other programs are now blocked till the query is done. 2. The display can only be linked to iMeter Solo ... while, at the same time, we cannot read anything from the display that we cannot read from the iMeter Solo ... so, the query problem is now multiplied by the number of iMeter Solos We could potentially add simple temp reading query for the display and leave out everything else. Would that work for everyone? With kind regards, Michel

Hello cmccartney, Comments below. I do not see any reference as to how we can poll the averages from the Display. And, even if we did, all these queries (which are probably every second) do cause major network performance issues. I think it would be best for ISY to include these functions using the readings from iMeter directly rather than getting them from the display. We'll look into it. With kind regards, Michel

Hi Teken, You can send Beep commands to devices that support Beep. In the Action section, choose Beep (in the same list as on/off/1% ... ). Above and beyond that, we do not know how to configure the KPL to be a Chime! With kind regards, Michel

Hello Elecrick, In addition to Lee's questions, my questions is: what firewall software do you use? Is it possible that you had put exclusion rules for your ISY26 but now ISY99 has a new IP and thus not excluded from your firewall rules? With kind regards, Michel

Hi Guys, We spent a couple of days on Energy Display and realized that there's really not much we can do with it: 1. To get temperature, it has to be polled 2. You can only link it to an iMeter but the problem is that the linking in this case does not follow regular INSTEON linking 3. ISY supports iMeter Solo so readings from iMeter Solo can be done directly to iMeter Solo So, our main question to every one is: above and beyond temperature reading, what else did you have in mind as far as ISY support for this device? With kind regards, Michel

Hello williammanda, Unfortunately there are no videos. To answer your questions: 1. You can add/configure devices/scenes 2. You can add/modify programs 3. Programs are point/click (you do not have to write anything except perhaps comments for your programs) Our Wiki has extensive tutorials with pictures: http://www.universal-devices.com/mwiki/ ... w-To_Guide With kind regards, Michel

Hello srogala, Unrelated: it's best to restore your backup from 3.1.9 as there was a migration bug from 3.1.9 to 3.1.10 where some devices lost their scene settings. With kind regards, Michel

Hello keribi, Thanks for the update! The gray arrows should not cause any missed timer events. With kind regards, Michel

Hi LeeG, Thanks so very much. The main issue is that we are getting increasing number of reports with RL/RL2 (and some KPLs) not reporting their status using dual band PLM. We did send a detailed report to SmartHome describing the situation which seems to be corrupted PLM database (addresses are filled with 00s). With kind regards, Michel

polexian, Comments in variables we'll take into consideration. elk-arm-state variable changes based on area/zone status. What are you trying to accomplish? Elvis, Thank you. Most of the errors are documentation errors which have been fixed. If you wish, you can send an email to me to tech@universal-devices.com and I can send you the latest doc (which will be including in 3.1.14). All events and objects are defined in /web/elkobjs.xsd (Schema file). With kind regards, Michel

RickL66, Sorry to disappoint but no. With kind regards, Michel