sorka

Since this thread is now completely off topic, I've asked the mod to either retitle and move it or split it.

False. Had the the old thread been up still I simply would have ask "was this ever solved for anyone"? . If no answers, I would have started a new thread posted all the details as if it had never been asked. But that's NOT what would have happened. Every member in this forum who posted this issue has already had it solved and one of them would have replied.

You mean like what I did in the first post? How's that working out? Had they not been closed I wouldn't have done what you claimed closing the topics fixes.

This is an awful practice. It eliminates context and previous lessons learned. It also keeps those who have awareness of the issues being informed when something new related to it is posted since they are not following the new threads already. I totally agree that closing out threads that get off track is an occasional ok practice when it doesn't lock out awareness of valuable trouble shooting. By closing these threads, folks who've had their problem solved can't post in the existing threads so it looks like the problem was never solved...as in this case. I did post links to the previous threads, but I was already so irritated by them being closed and preventing awareness of this issue already being solved, that it basically turned into a rant from me. Also, I didn't upgrade to a weird version. I updated to the version every said I should 3 years ago and haven't gotten a prompt in the UI since to upgrade that version to something newer. Prior to 5.0.14, I'd occasionally get prompted to update the firmware which I would do. Did upgrading to 5.0.14 eliminate that because I was on some funky version?

It's not a signal strength or mesh size issue. Maybe if it was far enough that exceeding 4 hops on the way back might cause the issue. There are several technical reviews in the Amazon review section for this switch that mention that status reporting is not supported and the hail work around. I've already initiated the return and will not be buying any Leviton products until this is confirmed fixed for any future models.

I get where you're coming from. I did make an attempt to see if this issue had been resolved before making a single post. The two threads on it were closed resulting in: Those who'd previously posted about the issue not being able to report to the existing threads that a newer update fixed the problem. They would be unlikely to start a new thread just to report something had been fixed. Those who go searching for the problem previously reported can't post in the existing threads asking if the issue was ever resolved which would result in those who are already following the thread and had the issue fixed being able to reply as such if they hadn't already.

That was the first thing I tried.

Just installed a GE Enbrighten. Works ok. The only downside so far is it's slow to report its status. Takes about 2 seconds vs the Minoston which shows up instantly. Of course even with the speed of the Minoston, scenes would never be as slick as Insteon since those don't require a hub and all devices in the scene listen and react at the same time to the controller. With zwave scenes, the hub has to listen to the controller and then send out commands to the other devices listening.

Just the amazon reviews that claim the product page is wrong about 2-way status being supported.

Just like the folks in this thread: No status reported with this device: https://www.amazon.com/gp/product/B01NAO4B9Z/ If I query the status, that works fine but no status broadcast with local control. Running 5.3.4 firmware and UI. 500 series dongle running 6.81.0 Works fine with these: https://www.amazon.com/gp/product/B08LN2NPZ3 Assuming at this point that this is a Leviton bug?

Isn't 4.9 the current official release?

Updating to 5.3.4 has fixed the scene controller issue for Minoston plugs. The Decora switch is still not reporting it's status when changed locally. I'll check its documentation to see if there are any params that need to be set.

This is the dongle I have:

There is no led at all sticking out the back. It was purchased last in in February from Amazon: https://www.amazon.com/gp/product/B07GNS1B7V

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?