Michel Kohanim

With pleasure! With kind regards, Michel

Hello dss, Unfortunately not since a) the Zigbee doorlocks are from Control4 they don't provide any APIs and c) there are not very many interoperable Zigbee devices out there and thus, for consumer use, ZWave is a better choice. We should have a mailing list for Alpha ZWave solution shortly. With kind regards, Michel

Hello gwpetersburg, Please do make sure your network settings (Configuration | System | Network Settings) are correct. Specifically, please make sure your DNS/Gateway are correct. If you are using DHCP, then please make sure your router’s firewall is not blocking ISY. With kind regards, Michel

Hi Jim/dss, We are currently alpha testing the INSTEON/ZWave solution. This said, I really cannot give an ETA mostly because of all the certification requirements. With kind regards, Michel

Hello Teken/blueman2, We are trying to get to the bottom of the SWL relay issue ... we shall keep you both updated. With kind regards, Michel

Hi Ken, Welcome to our forum! Yes, most providers have email addresses for their services. So, for instance, SMS to Verizon used to be: your_phone_number@vztext.com .... Who's your service provider? With kind regards, Michel

Hi LeeG/blueman2, I tend to agree with LeeG: there's certainly a firmware issue with this device. This said, I am not sure why only releases 3.2.x cause it to misbehave. We have to take yet another look. With kind regards, Michel

Hi Niccolo, As you may have noticed, we have changed our basic HTML page with a little nicer UI which uses Javascript. As long as your mobile phone supports Javascript, then yes ... this should be fixed after the upgrade. With kind regards, Michel

Hi Niccolo, Yes, we added ELK back in for our next drop (3.2.5) hopefully by the end of next week. With kind regards, Michel

Hi Jeff, Please click on 0B.4C.89.A within the All Indoor Lights scene and then check the on level/ramp rate for the other two devices. Please do keep us posted. If you're still having problems (and 4/5 days must be quite frustrating) please do not hesitate to contact our tech support team (contact info below) and we'll walk you through it. With kind regards, Michel

Hi Nuttycomputer, I have been thinking about your comments and I think you might be onto something here. It seems that the absorption factor should be 1-(soil type absorption factor). But, I am still not convinced that this is a rate. With kind regards, Michel

Hi blueman2, Thank you. Mine shows 15 but it's not constant. This is definitely a bug. With kind regards, Michel

Hello hart2hart, The first thing I recommend is upgrading to 3.2.4 so that we have the same point of reference. Looking at the logs, it seems that there are major network connectivity issues. Invalid socket means that the ISY is acting on a socket that has already been closed. This means two things: 1. Something is bombarding ISY with traffic 2. Port forwarding issues where by traffic destined for another devices is directed at ISY After upgrading to 3.2.4, I suggest the following: 1. If you have any port forwarding rules, please do make sure they point to ISY 2. Telnet to ISY, and then issue DON ... this turns debugging on. Let it run for a couple of days and then send your Error log to support@universal-devices.com With kind regards, Michel

Hello Nuttycomputer, Apologies for tardy reply ... it's been quite hectic here lately. Things that you have to note: Irrigation Requirement is calculated in two cases and two cases only: - At midnight (which may increase in case of summer/decrease in case of rain) - Every time cycle complete is called (decreased) Absorption factor is the amount of water that's absorbed by the the soil (NOT the plant); i.e. the amount of water that's wasted. Unless I am not seeing things correctly, then, allowable depletion is the fraction of water that's ultimately applied to the plant. And, thus, this is the amount that can be depleted to get to empty. As far as I know, this value is a constant and not a rate as you suggest it would be. Again, I must emphasize that my knowledge in this realm is not extensive and what I have posted above is based on the gist of our discussions with the forum members. As such, I do think that it would be best to post your question on the same forum. I am hoping that we can get this issue cleared up as soon as possible. With kind regards, Michel

Hello Nuttycomputer, Allowable Depletion is the amount of water that's depleted from your soil based on the absorption factor and amount water applied: Allowable Depletion = Absorption Factor ( So, are you referring to Allowable Depletion OR Irrigation Requirement? Allowable Depletion is constant while Irrigation Requirement is calculated based on Evapotranspiration which does take into account Allowable Depletion. With kind regards, Michel

Hello blueman2, Thanks so very much for the update. I still haven't heard back from SmartHome but I tend to agree with you. I do not think this value can be changed. This said, the fact that it returns random values, to me, is a bug. With kind regards, Michel

Hello strahan001, Please copy/paste your program here ... With kind regards, Michel

Hello rmlinnovator, My suggestion is that you create a folder for evenings and add a condition (say from sunset till 11:00 PM every day). Then, within the folder, create two programs: 1. One for status of the thermostat being greater than 70 (If Status Thermostat >=70) and 2. one for status of the thermostat being less than 70 (If Status Thermostat With kind regards, Michel

Hi Nuttycomputer, I am not sure if you have time (or the desire) to read the history behind our Irrigation Module. If you do, it may shed some light on why we did what we did: viewtopic.php?f=7&t=6452&hilit=absorption+factor Absorption factor is a heuristic number which Evapotranspiration algorithm takes into consideration based on other variables such as temperature, humidity, pressure, etc. Here's some high level background on Evapotranspiration: http://www.universal-devices.com/mwiki/ ... Irrigation With kind regards,

Hi Xathros, Thanks so very much for the detailed answers. Hi Nuttycomputer, Your suggestions and feedback are invaluable and, as I mentioned before, we do have precisely what you're suggesting in our requirements. The main problem is that they are the victims of "this is desirable" rather than "this is mandatory" (such as support for FanLinc or I2CS or ELK). Based on our history, I do very much think that MobiLinc (with MobiLinc Connnect solution) can address your requirements sooner than we can! With kind regards, Michel

Hello Nuttycomputer, Support for multiple userid/password support has been on our list for a long time now but it keeps getting pushed down the priority list. If I understand you correctly, above and beyond multiple userid/password, you would like to have granular control over authorization (what can each user do). Although this can be accomplished on the Admin Console but we have to make sure other clients, such as MobiLinc, can retrieve authorization information in a secure manner. Otherwise, above and beyond Admin Console, this feature becomes much less useful. I know MobiLinc has a favorites section wherein you can add specific programs, scenes, devices. Would this not address your requirement? With kind regards, Michel

Thank you! With kind regards, Michel

Hi Matt, Unfortunately, currently only Brultech and our own EM3 (which is still being tested). At one point we had support for Current Cost but because of high inaccuracies (up to 20%), we had to abandon it. With kind regards, Michel

Hello ralbright, You mentioned that you have ELK ... do you have any common areas setup in your ELK? If so, please note that there's a bug in ELK M1 firmware which inundates ISY with events from common areas. Sometimes, this will bring the unit to very slow response times. Also, please do make sure you are on 3.2.4 so that we have the same baseline for testing. With kind regards, Michel

Thanks Illusion, We'll look into it. Just to clarify, you used Link Management | Add a button to IRLinc Receiver. Correct? With kind regards, Michel