Michel Kohanim

Hello llovering, If you do not see any of your programs, please go to Tools | Diagnostics | PLM Status/Info and let me know what you get. If you are still having problems, it's best to schedule a remote session with our tech support team (links below). With kind regards, Michel

Hello IM, Thanks so very much for this thorough analysis. The problems we are finding are that: 1. Link count is much larger than what it should be (>800) 2. Devices do not send status updates The only commonality in this case is duplicate link records. Sometimes, a PLM restore removes some of the duplicate records but, in most cases, the duplicates are the same (i.e. same devices). Was this the case with your 2412S as well? With kind regards, Michel

Hi Gary, Thanks for reporting. We'll take a look. With kind regards, Michel

Hi someguy, in addition to LeeG's comments right above, would you please do a quick browse through of your PLM links table and see if you have many IDENTICAL records. By identical I mean truly identical: everything is identical! Lately, we have had many reports of PLMs with identical records (which should be an impossibility) and thus contributing to large number for link count. With kind regards, Michel

Hello davidology, Yes, there are definitely plans to expand our Zigbee product support. This said, it all depends on demand for specific products. Specifically for Zigbee, unfortunately interoperability is only at a Profile layer. So, for instance, Home Automation Profile is NOT interoperable with RC Profile. SEP is not interoperable with anything else. So, we will basically have to figure out where most of the demand comes from and implement those. With kind regards, Michel

Hi Guys, We have had this request many times and we have decided against it for the following reasons: 1. ISY does not need to be backed up unless you are explicitly making changes to its configuration. In those case, it's always best to backup at success points. So, in short, once you are done with any configuration, take a backup and you are done 2. The problem of automatic backup gets into many intricate details of delta vs. full, at what times, during what events, blocked by what other events, and many different permutations thereof With kind regards, Michel

Hi Stephan, Please send to support@universal-devices.com. I am only interested in the negotiation packets. With kind regards, Michel

Hi johncrab, You cannot query a folder in programs. You can query scenes. Are we talking about the same thing? With kind regards, Michel

Stephan, I am not worried about traffic between ISY and the server. I am more interested in the traffic between your computer and the server. With kind regards, Michel

Hi jmed999, 3.3.3. With kind regards, Michel

Hi guys, Based on their documentation, the mode MUST be URL Encoded. I really do not know what else to try. Perhaps their server (HTTPS) requires client certificates. Or, perhaps they require higher level of security. If you have a 994, perhaps changing the strength to high might help: http://www.universal-devices.com/docs/I ... 0Guide.pdf Apart from the above, I really do not know what else could be contributing to this issue. Wireshark (not LiveHeader) traffic log would be quite useful. With kind regards, Michel

Hi Stephan, In your test (outside of ISY), please remove the cookie and let me know if it still works. I suspect that the server is maintaining a session. With kind regards, Michel

Hi Stephan, the problem is that I do not know what curl does. Can you send me a wireshark traffic of a system that works. I cannot fathom why you would get request failed for content-encoding header. With kind regards, Michel

Hi Stephan, viewtopic.php?f=27&t=9770 With kind regards, Michel

Stephan, Yes, it's on the agenda with a very low priority and thus no ETA. With kind regards, Michel

Hi stephan, I think Xathros is correct. From what I gather above: Protocol: https Host= api.notifio.com Port=443 Path=/v1/send_notification Body=to=shesmer&msg=Test With kind regards, Michel

Hi Stephan, Unfortunately not yet. With kind regards, Michel

Hi Stephan, Unfortunately not yet. With kind regards, Michel

Hi Guys, Currently, our Zigbee solution supports only the following devices: RCS Thermostats RCS Load Controllers Brultech ECM1240 UDI 3 Phase Heavy Duty Energy Monitor With kind regards, Michel

Hi Sïmon, I do not think 3.3.3 was installed properly (or fully) and perhaps there lies all the problems. Did you get any green 1011 icons next to any nodes? If so, it's possible that ISY is updating your devices. With kind regards, Michel

Hi Simon, I am so very sorry to hear. Unfortunately I do not think you are out of the woods: 3.3.3 migrates configuration files in a way that 3.2.6 would not be able to understand and process them correctly. So, if you have gone back to 3.2.6, please make sure you also restore your 3.2.6 backup. As far as not being able to use https with 3.3.3, as may note in the important notes section, 3.3.3 no longer supports SSLv2 (for security reasons). Unfortunately Java 1.6's default mode is SSLv2 and thus all the problems. You might want to go to Java 1.7 and retry (if you wish that is). With kind regards, Michel

Hello mrobles, Are you saying that a new notification program does not work? If so, what happens if you right mouse click on the program and then choose Run Then? If that does not work either, then in all likelihood either the subject or the body are evaluating to empty. With kind regards, Michel

Hi Simon, I am so very sorry. Is there any chance you can give me remote access to your ISY so that I can test and see where we are crashing? If so, you can change the userid/password to something else and PM me access details. I would sincerely appreciate it. With kind regards, Michel

Hi RLIKWARTZ, Unfortunately this is not something we have been privy to. With kind regards, Michel

Hi jeffl012 and alx9r, Please do ensure that you try our latest firmware (viewtopic.php?f=25&t=9612 ) and then let us know if you are still having problems. Please do ensure to remove the thermostat from ISY and then register it back after installing the firmware. With kind regards, Michel