sorka

I've already gone through those "factors" as everyone else did in the previous threads. This is a known bug that hasn't been fixed yet. Yes I'm ranting. And no there isn't a fix.

I'm not asking for help. I'm asking when this bug: ...is going to be fixed. The cause was already determined and the thread closed without there ever being a resolution.

Just added my first zwave devices today and every one of them has the green 1011 icon even without adding them to scenes. Looks like everyone has had this problem and it has been a bug for years. I would have responded in one of the other threads but they've all but CLOSED. I should think have a bug this glaringly obvious go on for years without being fixed would be a big embarrassment. Is this ever going to be fixed?

That repeater costs as much as other zwave plug in outlets that also advertise as being a repeater. Any reason to get a dedicated repeater if I can get one that has additional capabilities?

Discontinued and even removed from the menu so no way to switch to external antenna. Just starting to add zwave devices but my ISY is in a metal server cabinet so I'll definitely need to get an external antenna.

I didn't know that it had gone off line and missed some important notifications that left a very expensive package on my front porch for far longer than I would have liked. Maybe you could send a "Test" email to everyone using the service to let them know it's offline and to please find another alternative.

Yup. No longer working for me. Time to switch to gmail.

It's really unfortunate that they just didn't provide a new state. So in addition to WET, DRY, HEARTBEAT, they could have added WET-LATCHED or something like that.

There's a sealed Rev 2.1 on ebay.

Trying to figure out exactly what version so I know what to buy. There's a 2.2 on ebay right now. Also found some sealed ver 1.05 sensors which are older than any I have. Does anyone know if these are equivalent to the 2.0 sensors?

Does anyone know if this change happened every version greater than 2.0 which is what Insteon told me? I have a version 2.6 that has the same issue that was out in the garage that was also left in the on state for probably several years. I need to get rid of the existing 3 sensors I already had that have this issue as they cannot be relied upon since they only send their signal once and if that signal misses due to interference or an ISY reboot, then they will miss the leak unlike the 2.0 sensors that keep sending the signal while wet.

I have one for a similar use where I've extended contacts several feet below keeping the unit well above any danger of getting wet.

I like how the 2.0 sensors work. I like the battery life so it seems for me the best option is to put a persistent search on ebay and just watch for the version I need. But I'm also open to other options out there. What are these tag sensors and how long do the batteries last, how much are they, and how do they integrate with the ISY?

I strongly suspect that some customers just blindly linked some i/o lincs as responders to the rev 2.0 sensors and so that when a real leak happened and a valve was shut off that when it dried out, the valve turned back on continuing the water damage. In their attempt to avoid liability for this situation, they made a change that created yet more situations where water damage can now happen. 1) Either because a user familiar with 2.0 sensors bought 2.1 or greater rev sensors and didn't know they have to make sure the state is OFF when installed, or 2) if the signal fails due to interference or whatever, the one time leak signal is missed and never resent.

Here's another issue. With Rev 2.0, it keeps sending on events WHILE water is detected. The 3.0 ones don't so if you bring the 3.0 sensor out of wireless range, and then trigger it on, and then bring it back into range, the leak is never detected. So in the normal case should the the message fail due to interference or because your ISY is down or you're rebooting it, then the detected leak is lost.

I left 1 star review on Amazon along with others that had the exact same complaint.

So does anyone know if the state can be set back to off remotely?

Like I said, I've read the manual for the product. I just didn't re-read it every time I ordered an extra sensor.

What is a QSG? And re-read my post. I don't RE-READ manuals for products that I already own, have lots of, and have used for years.

The point is that the program is triggered on the sensor sends an ON. If it's already on, the program doesn't doesn't trigger.

So apparently I already own one of these and didn't realize it. Last year I bought one and put it behind my built in refrigerator after the ice supply line sprung a leak. Well it's in the ON position now and it probably has been like that since I installed it since I pressed the button to trigger the program and left it in the ON state. Had there been a leak, it would have never been detected. Now with the skirt removed, I can see it all the way back there and I can tell it's bone dry. Does anyone know a way to reset this remotely? Otherwise I'll have to pull it out which is about 90 minute process.

It's NOT in the manual. I don't make a habit of reading the manual for extra copies of devices that I already own. Now had they called this a different kind of sensor or changed the model number, then I would have looked at the manual.

Right. I'm just pointing out had I not known this was a change, I would not have known I needed to reset the sensor and would have been in a state that had a serous damage causing leak started, the sensor would NOT have detected it. There's no way way to justify that this is a good change.

What's even more messed up, is that if the sensor is in the ON state and you reset your ISY, there's no status. The sensor IS in the on state but you have no clue what it is so now you have to go toggle it a few times to get the status and make SURE it's in the off state. It's TOTALLY screwed up!

Had I NOT discovered this and just blindly added these and a leak occurred, then I would never have known I needed to hit the reset button as my program is triggered to activate when the leak is detected but these now work as if they continually detect a leak when they're not really. This completely removes functionality that previously existed with no way around it.