oskrypuch

Cleared the cache, clicked on the link on the site (same as above), and then ran from the desktop icon. Hasn't hung again, had the console up for 30 min or so. Fingers crossed that clearing the cache from time to time may help. * Orest

I already did that after the install. Will try it again, and then run the console from a browser. * Orest

Which optional modules are you referring to? And is this in the ISY admin console, or the system Java console? * Orest

I have not been on the admin console for a while, but needed to replace and add some modules. THIS IS A REAL problem. The admin console will work for a short bit, and then just hang. I then usually have to resort to rebooting the computer to try to restart/flush java. Incidientally I sometimes see Java Reboot as a process running in the Task Manager. Worse, when I do get control again, some actions may have been properly applied, and others not. This is making it virtually impossible to do any serious work. Any hints? Would an old XP laptop work better, with an old version of Java? * Orest

How about that, the hard reset fixed it. The second (new) leak sensor is properly detecting water too, now. Thanks, saved me some postage. * Orest

Sure, that (factory reset) sounds like a good idea. * Orest

I played around with the settings, and seemed to get it working again with my own domain SMTP. Interestingly, it works with text message alerts as well. Will monitor it. * Orest

Yep, that is my intention. Should be no issue. * Orest

I always did before, using my own domain SMTP, and then ISY stopped sending with no parameters changes. I played around a bit with it, and couldn't get it reconfigured. Will give it another shot. * Orest

OK, thanks. * Orest

The current release firmware, UI matches. (v.4.5.1) Win7Pro * Orest

I am finding that lately after a few minutes (yet sometimes not at all), I lose connectivity with the ISY from the console. A credential dialog comes up, like it does for the initial startup, although logging in doesn't seem to work. I have to close out the console, and restart it. Tried rebooting the ISY, problem still an issue. 994 with latest firmware. Latest Java. * Orest

Placed it in a plate, with at least 1/4" of water. Worked with its mate, can try dunking a bit more. * Orest

994, and running the latest firmware.

A little while ago I noticed that the alerts I have configured to go as text (Bell Canada xxx@txt.bell.ca) no longer got to my phone. The emails alerts work fine. I double checked that Bell hadn't changed the domain, it hadn't. I can email/text to my phone direclty from my laptop. I thought that perhaps Bell didn't like the domain the text was coming from, I'm using the USE DEFAULT SMTP method. I used to use my own SMTP, but a year or so ISY could no longer send with it, the config just stopped working, so I switched to default. In any case, I set up a forwarder email on my own domain. Again, emailing to it directly from my laptop will send a text message to my cell phone, but the ISY alert message, after forwarding, will not reach my cell phone. So I am wondering if Bell for some reason doesn't like the format of the text being sent. Any thoughts on this? * Orest

New Leak Sensors arrived. Both set up correctly in ISY with the v.43 firmware for the correct device. One of them senses correctly, but looks like the other one is NOT sensing water. There is no flash on a water dip, nor a state change in ISY, unlike with the other unit. Guess that one may have to go back! * Orest

Yes, bought them all at the same time. Six of them, one was a spare, the one I'm trying to hook up now. The other units are identified as firmware v.41, but they are also identified (correctly) as 2852-222 units, so the apparent v.40 firmware identification on this unit could be incorrect, or it may in fact be the issue. I am thinking that either this unit is defective, or there is a bug in the earlier firmware. I have ordered a couple more 2852-222's, will see what happens with them, and will report back. * Orest

OK, upgraded to 4.5.1 for firmware & UI. Deleted the unit. Tried autodiscover, ended up with Triggerlinc like before. Deleted the unit. Tried again specifying 2852-222, ended up with Triggerlinc. So still, no joy, * Orest

Yes, always deleted the errant entry. Otherwise, nothing happens. Will try updating to the latest firmware, and repeat. * Orest

OK, did the factory reset, battery is good. I do have to hold the button down about 3.5s or so, else there is no blink, and no device seen. Used Auto discover, same results, two pics below. * Orest

Will do, and report back. * Orest

Yes, they are. * Orest

This was in the same bunch, purchased with my other ones, and the others reset to OFF by themselves. Believe that is an older behavior? In any case, ON or OFF, the nodes are still listed as Opened, Closed and Heartbeat node as for a triggerlinc, the unit is identified as a Triggerlinc and not a Leak Sensor, so this one unit is still dead in the water. (no pun intended) * Orest

Thanks. Did a factory reset. Still same behavior, either with auto discover or specifying the type, I end up with a Triggerlinc v.40. Dipping in water turns all the modes ON, and they stay ON. Perhaps I have a bad unit. * Orest

OK, how do I get it to slow blink? Holding the button for five seconds or so will get into a 0.75 sec blink mode. If I hold it longer, the light will go ON, and then momentarily blink OFF, kind of in reverse. I think that is forced a "wet" condition. Not sure how to factory reset it. The unit is 0114 revision 2.1 * Orest