Jump to content

Recommended Posts

Posted

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?

 

 

 

 

Posted (edited)
1 hour ago, lilyoyo1 said:

Since you've provided zero information about your setup we can't be off much help. We could assist you if you stated how many devices, what they were, Firmware, and UI, etc. 

https://forum.universal-devices.com/topic/29371-zwave-tips-and-tricks/

 

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.

Edited by sorka
Posted
6 minutes ago, sorka said:

 

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.

Since you already feel a 3 year old post is a bug (especially considering no recent posts on the matter from anyone), I'll step back. Good luck

Posted
1 hour ago, sorka said:

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?

 

 

 

 

The 1011 in green indicates the device is online but there is binary data waiting to be written to the device. In Insteon devices this is typically because the device is a battery operated one and the data cannot be written until the device is manually place in Linking mode.

I don't know about Zwave but,  this is not a bug, but rather a feature of the admin console indicating several factors the user needs to correct or be aware of.

Posted
14 minutes ago, larryllix said:

The 1011 in green indicates the device is online but there is binary data waiting to be written to the device. In Insteon devices this is typically because the device is a battery operated one and the data cannot be written until the device is manually place in Linking mode.

I don't know about Zwave but,  this is not a bug, but rather a feature of the admin console indicating several factors the user needs to correct or be aware of.

 

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.

Posted (edited)
26 minutes ago, lilyoyo1 said:

Since you already feel a 3 year old post is a bug (especially considering no recent posts on the matter from anyone), I'll step back. Good luck

One year.

Edited by sorka
Posted (edited)

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.

Edited by sorka
Posted

I had a single switch that exhibited this behavior for a few years. I have several of these same brand and model switches yet only one exhibited this behavior but I never did figure out how to make that annoying (switch otherwise worked) green icon go away.  Recently, I replaced the switch for unrelated reasons.  No more green icon.  Was this a bug in the ISY?  A bug in the switch?  A faulty or marginal device?  Not sure there is enough data to reach any conclusions.

 

  • Like 1
Posted
9 hours ago, lilyoyo1 said:

Well, i have done at least 30 homes with zwave devices  including 2 of my own and none have that issue. Your don't want help so it's a moot point. Good luck

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. 

Posted

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.

Posted

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.

Posted
30 minutes ago, sorka said:

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.

What version of the Zwave dongle do you have, the 300 or 500 series?

What are the firmware versions of your ISY and UI?

Posted

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.

 

Posted

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. 

Posted (edited)
40 minutes ago, Techman said:

What version of the Zwave dongle do you have, the 300 or 500 series?

What are the firmware versions of your ISY and UI?

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

 

Edited by sorka
Posted
3 minutes ago, sorka said:

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).

No dongle but an internal Zwave card. As I have read here, if you have a green LED sticking out of the case (on back?) you have the 300 version.

Posted
9 minutes ago, sorka said:

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).

 

What is the current version of your UI (the ISY launcher)?

UD refers to the Zwave card as a dongle

You have the 500 series Zwave dongle. You should update your ISY firmware and UI to the latest version 5.3.4. This version of the firmware fully supports your current zwave dongle and you may see improved  Zwave functions

  • Like 1
Posted
2 hours ago, Techman said:

Did you read my last post?  Doing what I suggested could most likely resolve you problems

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.

Posted
2 hours ago, sorka said:

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

 

So you’re using firmware that was released October 2018… 3years ago.. but complaining about a bug that hasn’t been fixed? Really?

  • Like 1
  • Haha 1
Posted
1 hour ago, MrBill said:

So you’re using firmware that was released October 2018… 3years ago.. but complaining about a bug that hasn’t been fixed? Really?

Isn't 4.9 the current official release?

Guest
This topic is now closed to further replies.

×
×
  • Create New...