Michel Kohanim

Hello alphamale78, Need a little more clarification. a. What goes to 100%? b. What's controlling #a? Is it when you click on the switch itself? through ISY? through another controller in the scene? This is a little confusing: 1. What's NOT controlling the loads? Same questions as above. With kind regards, Michel

Hello CodeMonkey, Are you specifically referring to the HTTPS port? In all cases, no, you should be able to install using any of the ports (http/https) ports you have configured for your ISY. With kind regards, Michel

Hello all, I am happy to announce the availability of our 3.3.3 (Beta) release! For a list of changes, please take a look at this post. This is a minor release. Know Issues - None Things to test: - UDP and especially UDP network resources - FanLinc options - KeypadLinc sub button anomalies - 2477SA1 linking problems - 2441TH/2441ZTH (requires restore device or remove/add device) - IOLinc sensor status - Irrigation Module 994 - SSL/HTTPS Important Information 1. Important Brultech module is no longer supported on ISY99 Series. Please contact sales@universal-devices.com for options 2. Important NetBios removed from ISY99 Series. You can no longer access ISY by going to http://isy on Windows 3. Important If you have a 994, you will need to re-install a certificate. Please review ISY994 Series Advanced Network Security Configuration for more information. 4. Important We have removed SSLv2 support (very insecure) from ISY99/ISY994. Unfortunately, the only protocol supported by MAC with Java 1.6 is SSLv2. As such, you MUST upgrade your MAC to Java 1.7 (Software Update) 4. Please note that Safari does not support SSL session reuse and thus might take an exorbitant amount of time to communicate with ISY. As such, when using 2048 bit SSL, it's best not to use Safari. 5. If you are using the Irrigation Module and are upgrading from releases prior to 3.1.5, you must edit the programs using Irrigation variables and save the programs again. Irrigation module is no longer on promotion 6. Upgrading from 3.1.3 and below: If you are using WeatherBug Module's Rain Today in your programs, please note that the precision has changed from 1/10 to 1/100 and thus your programs might not run properly 7. For a discussion of variables, please look at our Program Variables forum. Instructions: 1. Please backup your ISY (File | Backup ISY). If you are backing up a 3.1.6 system, please note that the backups are corrupted. If you have a backup from prior releases, you should be OK 2. Please download the firmware for your platform - please do not unzip ISY 99i Series ISY 994i Series 3. Login to the Admin Console and choose Help | Manually Upgrade [the name of your system] 4. Choose the file saved in step 2 5. After the upgrade, ISY reboots. Please do ensure to clear your Java Cache 6. IMPORTANT Once upgrade is completed and ISY reboots, use any of the following methods to access your ISY's Admin Console: a. http://your.isy.ip.address/admin - applet --- Security Warning: Due to recent Java security problems, it's best to always use method #d b. http://your.isy.ip.address/admin.jnlp - Java application c. http://www.universal-devices.com/99i/3.3.3 - applet --- Security Warning: Due to recent Java security problems, it's best to always use method #d d. http://www.universal-devices.com/99i/3.3.3/admin.jnlp - Java application Best method to access Admin Console Dashboard - not fully supported - http://www.universal-devices.com/99i/3. ... board.jnlp 8. Please backup your system again Thanks and with kind regards, Michel

Hi pounce, I didn't realize Iris is using Zigbee ... as far as I remember, they only supported ZWave and WiFi devices. So, are you specifically looking for Zigbee devices? Does the protocol really matter to you? If so, in what aspects? With kind regards, Michel

Hi db2ace2, Unfortunately we do keep putting limit notifications to a lower priority. As of right now, you can either use the Topology and count the nodes. Or, when you try to add a device, although successful, the device does not get added to the device tree. With kind regards, Michel

Hi Xathros, Thanks for the update. Subscription is as easy as sending a Subscribe request to ISY have it point to a server/URL. I can certainly help you with that when you decide to go forward. With kind regards, Michel

Hi John, Yes. Also, if you use http://www.universal-devices.com//admin.jnlp then you will get an ISY Finder dialog which lists all your ISYs on the same network + you can add others to the list (click on the Add button). With kind regards, Michel

Hi Xathros, ISY uses utf-8. I am not sure what's going on with Thunderbird. Email is, well, for email = text. If you want unit-less values for a data logger, may I humbly recommend subscribing to ISY instead? This way, you will get all parameters in the form: You can parse, ignore, and do whatever else you want with the units. Last, I do not know. With kind regards, Michel

Hi pounce, Thanks so very much for your thoughts. Now, it's time to generate some demand so that we can measure ROI for this solution! Do you know of any others who might be interested? With kind regards, Michel

Hi Xathros, Yes, but it has a very low priority. With kind regards, Michel

Hi pounce, Thank you. We already support SEP (Smart Energy Profile) in our 99r4i ZS series. Currently, we have no plans for supporting HA profile mostly because there's no demand, a dearth of interopertable devices, and the fact that HA has some constraints (such as polling intervals) which does not work well for commercial venues. This said, it all depends on what we are trying to achieve. If the goal is to support generic sensor/actuators, then HA is not a good fit and having an application layer with well defined events/commands is much cleaner. On the other hand, if the goal is to use existing HA devices, then we should pursue standard Zigbee profiles. I have heard of both companies but, just like you, I do not like us to be tied to the cloud of any sorts. ISY must remain autonomous. With kind regards, Michel

Hello mvprj84, That's the correct behavior ... high temp is updated whenever the temp goes above the last high temp. So, at nights you will have high temp for the day till 12:00 AM in which case it's reset and the cycle continues. With kind regards, Michel

Hi Guys, this was a bug and it should be fixed in 3.3.3. Thanks Xathros for finding it. With kind regards, Michel

Hi mvprj84, Can you please post the contents of your email configuration? Also, is this also the case with the information in the Admin Console (I know your primary source is the email)? With kind regards, Michel

Hi pounce, I am all for it. Having a generic messaging system to discover Zigbee devices, their capabilities, and types is quite powerful. The only nagging problem will be that we will be implementing things that are already in HA or BA profile. i.e. we'll be competing with those profiles. What are the advantages of having our own communications protocol vs. using those already offered through Zigbee Profiles? With kind regards, Michel

Hi Xathros, This was a bug in 3.2.6. What's your firmware version? With kind regards, Michel

Hello pounce, It's not really APIs. ISY has to know what type of device it's communicating with and its capabilities. For instance, is it a sensor, what are the ranges, how many sensors, what type of a sensor, can it be configured? What can we do to it? Can we turn it on/off/dim? Without this information, it would be very difficult to have programs respond to events from these sensors. Things that are important are Profile/Cluster IDs and commands. As such, it would be impossible to reuse existing code without forcing ISY to consider those devices as thermostats or energy monitors. With kind regards, Michel

Hi pounce, ISY is extremely strongly typed device and framework. Although 994i Z supports Zigbee PRO, however, it has to know what it's communicating with. So, for instance, ISY994iZ supports RCS thermostats as well as Brultech energy monitors both of which are based on XBee. 994iZ Pro can support up to 64 Zigbee nodes. So, in short, we would need the APIs/Specs for your sensors. We'll then do a sizing and based on ROI assign development priority. With kind regards, Michel

Hi someguy, I cannot be certain. The bottom line is that you cannot communicate with your ISY remotely so, the cause may be one of the following: 1. Your computer firewall 2. Hardware firewall between your remote site and ISY 3. Dynamic DNS 4. No connectivity at ISY location or router issues 5. ISY is too busy doing something ... check Error Log and look for any errors during the times that you had connectivity issues With kind regards, Michel

Thank you Andrew. Based on the event log, I think our next release will help (3.3.3). We were going to release it on Friday but had to postpone to fix a bug for DirecTV crashing the system. With kind regards, Michel

Hi Andrew, thanks so very much. Can you tell me which firmware version is running in your ISY? With kind regards, Michel

Hi someguy, Yes, very much so especially since you were accessing it remotely. With kind regards, Michel

Hi Mike, I have only seen this feature on IE and nothing else. With kind regards, Michel

Hi someguy, In all likelihood, your dynamic dns is no longer pointing to ISY your router. Can you get to your ISY locally? With kind regards, Michel

Hi Mike, Unfortunately not that I know of on iphone. With kind regards, Michel