oskrypuch

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

OK, the title notes my problem. I have a 994i running 4.4.6 in a complex network. I have successfully added the original 2852-222 sensors before, and these are running in the system. I had one left over that I hadn't added in at that time, and decided to today. Followed the New Insteon Device dialog, typed in the address, selected 2852-222, put the device into discover mode with the fast blinks. The dialog disappears, for a moment 2852-222 is shown, and then it changes to (2421) Triggerlinc v.40, with an Opened, Closed and Heartbeat node. Also tried AutoDiscover, same thing. The other units were correctly added in (a year or two ago) with Leak Sensor v.41 shown and Dry, Wet & Heartbeat nodes. What am I doing wrong? * Orest

I would love to see this addressed as well. You can also use the windows Magnify app. Just set the admin console size appropriately, and hit magnify enough to make it about full screen. The magnifier does munge the fonts a bit, but it does make it a little more readable. * Orest

Well, replacement modem arrived, installed as per proper routine, all FIXED. NIce to have things back to normal. * Orest

I noticed that thread, I may well do that on the old one (actually have the previous one too), at my leisure once I get the new one installed. * Orest

Thanks everyone for your help, modem is ordered, should be here Tuesday/Wednesday. Will report back, expect that will fix it all up. * Orest

2413S is ordered. Should I order two, just in case (discussions re availability of chips) ? * Orest

LED is about normal. Hmm, but, there are only 28 links, that surely can't be right. So, 2413U or 2413S? * Orest

2413S v1.3 1329 -- is that the 29th wk of 2013? I'm thinking that might be beyond the usual witching time then. My previous one is sitting on the stud above it, that one was from 2009. Is the 2413U just the dual mode equivalent, and compatible with the ISY? EVen if compatible, is the 2413S preferred? Both are available at the same price, locally. * Orest

Haven't been here in a while, guess things have been running smoothly. I have a 994i, running 4.3.26, and maybe 60 different devices incl. keypads, switches, relays, motions and thermostats, and a rich and complex programming structure. I posted some parts of it as samples and examples here. I have a number of keypads some are used strictly for ISY generated scenes to control lights, but most are used as mini-control centers to trigger programs, like opening the curtains, or telling the furnace to up the temp for a hour, that sort of thing. They also display information, like the garage door is open. Overnight all of my keypads have lost several aspects of their functioning, although the rest of the functions still work ... ISY generated device scenes still work ISY can address and change the status of each key (ON/off) However, ISY can no longer dim/brighten the keypads ISY can no longer beep the keypads And what is the biggest issue ... Pressing the keys on the keypad no longer generates an event that the ISY can see and act on, knocking out a good portion of house control. From the ISY java panel, you can otherwise trigger the respective programs that the keys would start up, and they work fine, in fact this is what I'm having to do now to get certain things to happen. Viewing the devices from the ISY panel, pushing the keys manually results in no changes to the status of the device, or to the scene that the key is linked to (if any). Not surprising, as the respective programs are not triggered either. In addition, all four motions will no longer generate an event on motion. They flash, but not once or twice, but many sequencial flashes. Batteries all checked. I have four wireless water sensors. They also stopped communicating with the ISY. I have a monitor program (as described here) that looks for the once daily heartbeat on these devices, and it disappeared for several days. I have tried factory reseting and ISY refreshing the keypads and motions. Some of the keypads are the newer dual mode type, so I tried pulling some of the wireless nodes thinking there might be a bad one somehow causing an issue. I tried rebooting the ISY. I tried pulling the power on all the keypads, to see if the motions would start working, they didn't. I even tried jiggling the cords. I have one sick system. Is a multiple unit hardware failure really possible? Seems much more likely that there is some sort of software scrambling. I did a lot of x10 work years ago, and was experienced at tracking down troubles with line monitors, but I'm not really up on the more complex structure of insteon comm ... So, where do I start to fix this. Thanks for anyone's help. * Orest