Michel Kohanim

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

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