Michel Kohanim

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

Hello Techman, Thanks so very much for the suggestion. Unfortunately after much deliberation it seems that it may cause confusion. With kind regards, Michel

Hi saidmacias, In this case I suspect your API key is invalid because 401 simply means unauthorized. So, the server does not like your API key OR you are using an invalid path. As far as notifications, it's quite possible that the notification you are sending has blank subject/body in which case it shall not be sent. To test, right mouse click on the program and then choose Run Then from the menu. With kind regards, Michel

Hi saidmacias, 401 is authorization issues. Somehow somewhere you are missing userid/password information. Do you know if it expects them in the header? If so, in your network resource click on Add Header, choose Authorization, enter your userid/password and then click Update and Save. If not, do you know how userid/passwords are communicated to this service? With kind regards, Michel

Hi Mike, yes, there is but we have to first make sure the calculations are accurate. With kind regards, Michel

binaryman, It should already be supported in 3.3.2. With kind regards, Michel

Hi Orest, I do not think it had anything to do with UAC since, otherwise, a lot of other things would stop behaving as well. I think it had to do with one of the UI versions that had a problem with program load. What version of ISY are you on? With kind regards, Michel

Hi, I am so very sorry. I didn't realize it was a PRO in which case the limit is 1024. With kind regards, Michel

Hi Mike, If you depend on your Irrigation module, I do not recommend it since it's in alpha and being tested by a couple of our customers who agreed to use their system for real-life testing. Furthermore, with V2, you are going to have even less Irrigation Requirement. With kind regards, Michel

Hi paauto, If your 60 devices are all KPLs, then you have already surpassed it (though, I assume that you have not since you have not gotten any errors yet). So, for your calculations: 1. Each button on a device is a node 2. For thermostats, you have 4 nodes 3. Each scene is a node With kind regards, Michel

Hi Mike, If you have not explicitly requested to be part of the V2 release, then you have the original one. There was a bug in V1 in which case we didn't use Julian days. That might explain the fact that the readings are lower now. With kind regards, Michel

Hi Mike, Are you using the irr_v2 build? With kind regards, Michel

Hi ski2020, I am not sure which ACK you are referring to. There's nothing in your logs that says the thermostat was ACKing anything from the PLM. The only ACK is when you reset the thermostat yourself. With kind regards, Michel

Hi Teken, 1. Click on the Admin Console icon now on your desktop 2. When Admin Console comes up, minimize it 3. Click on the Add button 4. Use the IP address for your ISY in https://your.isy.ip.address 5. Close Admin Console 6. Click on the icon again and then choose the HTTPS entry With kind regards, Michel

Hi Teken, I think we are talking passed each other. Let me try again: 1. The problem is the Admin Console/Java using SSLv2. This has NOTHING to do with your browser and its configuration 2. The link I sent in my email (http://www.universal-devices.com/99i/3.3.2/admin.jnlp) is the one that you said you had no problem using. Is this still the case? If so, I am not sure I understand why you keep using the link from TouchSwitch (which may be pointing to a different UI) With kind regards, Michel

Hi Rich! Yes, I have been in contact with George ... he's quite impressive himself! Still haven't heard back. It seems that they our discontinuing fypower.org ... I have already sent 3 emails in the past week. Just hope someone is there. With kind regards, Michel