sorka

5.0.14 for the ISY and UI and 6.81.0 for the zwave controller. Not sure what you mean by dongle? There's nothing plugged into my ISY. In the about it says zwave(21100). I updated my ISY last year in February with this one: https://www.amazon.com/gp/product/B07GNS1B7V

The Minoston will trigger programs because the ISY sees its locally changed status so its disappointing that it can't act as a controller in a scene.

So excluding the Minoston and then including them seems to have resulted in the 1011 going away. But from the folks that tried that in the previous threads the 1011 icon always came back eventually. So far it's gone. None of the plugs act as controllers when included in scenes of controllers and the Decora even when excluded and re-added still doesn't update its status even though it is not the one that had the 1011 icon problem in the first place.

More broken stuff. Neither on/off plug brand mentioned above responds to scenes with only zwave devices. If I add an insteon device as a controller, both these plugs respond. When I create test scenes with either of these two plugs as controllers, nothing happens. For the Minoston plug, controlling it locally shows it's on off status changing in the scene in the admin console but it does not control the other plug. When the Decora is added as a controller, it's on/off status does not update when controlled locally. ZWave appears to be not well supported on the ISY.

Another module just arrived: https://www.amazon.com/gp/product/B01NAO4B9Z It does NOT have the same issue but it also doesn't function properly. The decora module doesn't report its change in status when controlled locally unlike the Minoston which instantly reflects its locally controlled change in status in the ISY but also continually displays the 1011 update icon. If I query the decora, it does report its status but the fact that it doesn't do so without being queried is a deal killer so it is going back. Switches need to report their status so they can trigger programs or their scenes.

Interesting. As I add more, I'll note if any don't have this issue. It doesn't seem to effect anything. The first two devices I installed were a pair of these z-wave plus on/off modules. https://www.amazon.com/gp/product/B08LN2NPZ3/ I got them because I wanted repeaters and figured these costs as much as dedicated repeaters but with additional capabilities. I have more z-wave devices arriving over the next week and will report if any of them don't have this issue. The on/off modules have fantastic range. With one as a repeater outside the metal server cabinet where the ISY is, the other one responds plugged in as far as 100 feet away through 5 to 6 walls. I'm in the process of replacing Insteon wall switches that aren't part of intricate insteon scenes with multiple ramp rates. Nothing in the zwave offerings can match Insteon when it comes customized ramp rates with every device having it's own ramp rate depending on the scene it's responding to. But many of my devices are either standalone or simple scenes like just on or off with no ramp rates. For those devices, I'm replacing the Insteon switches with zwave and then will stash the Insteon switches remove as replacements for core Insteon scenes that I want to keep Insteon only. I don't believe in the long term viability of Insteon any more so I'm reducing my reliance on it. I've already replaced the motion sensors, i/o lincs, and door sensors with alternatives.

I suspect this just hasn't gotten any attention since it doesn't effect the operation of the device. At the very least, if there was a detected problem, you'd think manually clicking write updates to device wouldn't just do nothing. No feedback of any sort. The button literally does nothing.

One year.

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?