Michel Kohanim

Hi aawitek, I recommend moving your PLM to a different outlet. With kind regards, Michel

tandar, Have you ever done a File/Remove PLM? It does sound like it. If you have, please restore your ISY with a good backup and then repeat restore PLM. With kind regards, Michel

Hi msplain, Sometimes is trying to hack into your ISY. Please go to event viewer, change the level to 3, wait for 5 minutes then review your error log to see the source IP of the hacker. With kind regards, Michel

Hi shannong, LeeG is correct: 800 was for 2412. 2413 has a larger memory but the same processor so I do not recommend higher link counts than max of 900. With kind regards, Michel

Hi larryllix, Thanks so very much. Is it possible to put all other programs that do not depend on this one in a folder and give it a false condition so that none of them are run. Then open the Event viewer on level 3 and a) monitor the traffic and see whether or not you still see system busy. In and of itself system busy is ok. The question is what is actually happening. With kind regards, Michel

Hi shannong, No. But perhaps some of your devices no longer send their status. With kind regards, Michel

Hi larryllix, What do those heartbeat checkers do? With kind regards, Michel

Hi Walt, You will need to reprovision your ISY with PGE. With kind regards, Michel

Hi onever, Compares are links in the device and not the plm. I suspect either of the following : 1. Your plm had lost all its links 2. You have too many links in your plm and now it's been defraged. Please go to tools/Diagnostics/Show PLM Links click on the Start button, wait for it to complete and then click on the Count button... Make sure the count is not more than about 800 or so With kind regards, Michel

Hi larryllix, Thanks so very much for sharing. With kind regards, Michel

Hi larryllix, Do you have any programs that do things based on the variable's state change? With kind regards, Michel

Hi blueman2, Unfortunately not. If you have 344 plm links and your scenes have an average of 10 nodes, I would say you are in low 100s. With kind regards, Michel

Hi smokegrub, Please try again. With kind regards, Michel

Hi matapan, First, it only works on certain firmware level of certain thermostats. So if you get errors then perhaps your thermostat firmware does not support this feature. This button allows you to configure thermostat schedules inside the thermostat. With kind regards, Michel

50-50, Unfortunately Mike gave you the wrong firmware which requires a different UI: https://isy.universal-devices.com/994/4.2.18/admin.jnlp. Note there is no i after 994. With kind regards, Michel

Waketech, We are working on it. I just can't give you a firm date. With kind regards, Michel

Hi Charles, Stusviews is correct. As you mentioned In think what may have happened is that the device for unplugged before you disabled it add within that span of time something tried to communicate with it an this the error. Now the only way you can get rid of that error is to plug the device back in, enable it in ISY, disable it, and then unplug it. Or you can reboot ISY. With kind regards, Michel

Hi all, No unfortunately it does not. As Michael mentioned to be eligible as a nest partner we have to abandon everything we have done in the field of demand response. With kind regards, Michel

Thank you, Now they should send out heartbeat events. With kind regards, Michel

Hi MustangChris04, This is a very hard question to answer. As I mentioned different levels of firmware for the same device support different options most of which are not documented. We have been burnt before by doing reverse engineering and thus causing mass confusion when certain things work for some people but not others. Examples are setting time and schedules on thermostats, heartbeat on TriggerLincs, KPL sub buttons controlling the on level for the main, etc. At the end of the day everything boils down to how much resources should we expend on supporting a feature request and how many users would it impact. Perhaps you might want start a poll for a SPECIFIC feature on a SPECIFIC device and let's see the demand. Teken, I do not follow. Again, my issue is with your usage of "bug" to refer to a feature request. That's it. With kind regards, Michel

Teken, Please do not change the topic. All I said was that I take issue with calling a feature request a bug. Period. With kind regards, Michel

All, Few changes that we just recently became privy to: 1. The original open close sensor is discontinued. This device supported both heartbeat as well as low bat 2. Original TriggerLinc with firmware version 40 and above was renamed to Open Close Sensor 3. The new Open Close sensor does NOT support low bat This said, if you recently purchased an Open Close sensor or if the firmware version shows more than 39 it is probably identified as a TriggerLinc in ISY. You need to remove it from ISY , install 4.2.21 and then link it back. With kind regards , Michel

LeeG, as always thank you. Teken, please post a screenshot of options you used to have. As far as I know KPLs don't have the options button. Further it seems that you are under the impression that we have to implement everything including things that don't exist anymore. Of course you are entitled to your opinions and wishes but I do take issue with labeling those as bugs. With kind regards, Michel

Hi bfish, You might want to contact SmartHome tech support and if that fails, please don't hesitate to contact us. With kind regards, Michel Hi bfish, You might want to contact SmartHome tech support and if that fails, please don't hesitate to contact us. With kind regards, Michel

Sajata, If you have problems getting into the admin console please contact our tech support team. With kind regards, Michel