Green 10101 Icon will not go away

[jca001]

I added an Inovelli NZW30 In-Wall Switch (on/Off) with no problems. This was done near my ISY and installed in another room and did a Heal Z-wave Network and all seemed OK. I can turn the light on and off at the switch and get instant status update in the Admin Console and see the communication messages in the Event Viewer. I can also turn the light on and off from the Admin Console with no problems.

Everything was fine for several hours and then I noticed the green 10101 Icon for the node. I have selected write changes at the bottom, I have right click on the node and selected Write Updates to Device, but the icon is still there.

Watching the Event Viewer there is a message

[ZWAVE-WAKEUP  12] Force writes to ZW012_1

and no other messages. So I am not sure if the writes were successful or not, but the icon does not changed.

[IndyMike]

Bump - Have the same issue with a Aeotec DSB05 motion sensor and my Schlage door lock.

The ISY apparently wants to write something to these devices.  Same issue as reported by jca001 - writing updates/forcing writes does nothing to clear the icon.

What is the ISY trying to do here?  Is there a way to resolve the pending write?

Running V 5.0.14

Thanks for any insight

 

[oberkc]

I have the same thing with a z-wave "on/off power switch".  I have not been able to make that go away.  It is a scene controller to a micromodule and keypad secondary button.  The module responds fine, the button does not respond.  

[io_guy]

Same here with a door lock

[IndyMike]

Interesting...

The pending write on my motion sensor showed up after I tried to include the sensor as a scene controller for a number of Insteon devices.  It did not function as a controller (would not activate the scene).

I removed the sensor from the scene and have been stuck with the pending write icon ever since.

The door lock icon manifested itself on its own.  The door lock has been in place for years and has always been under program control (never part of a scene).  

Ghosts in the machine?

[oberkc]

2 hours ago, IndyMike said:

The pending write on my motion sensor showed up after I tried to include the sensor as a scene controller for a number of Insteon devices. 

I don't remember the specifics, but I recall similar experience.  Mine originally did not have this pending icon, but came only after I started incorporating it into scenes and programs.  Furthermore, removing the z-wave device, resetting it, and adding it back did NOT solve the problem.  (of course I have also tried "write updates" options without success.)

[mwester]

After trying everything else I could think of, I finally excluded and re-included my door sensor that behaved that way (followed by updating all the programs that referenced that device... painful).

[IndyMike]

7 minutes ago, mwester said:

After trying everything else I could think of, I finally excluded and re-included my door sensor that behaved that way (followed by updating all the programs that referenced that device... painful).

Thanks for confirming that the exclude/include removes the pending writes.  After seeing your post, I did this on my motion sensor and the pending write did disappear.  This only affected a couple of programs.

Unfortunately, excluding/including the lock is more involved.  It's in the garage and re-including requires me to dismount the lock and bring it to the ISY.  That's actually easier than using an extension cord/cat 5 extension to bring the ISY to the lock.

Either way, it's more pain than I'm willing to deal with right now.  Maybe i'll change the font size again...

[jca001]

I am glad to see others are having this problem, not because I wish anybody ill will, but because hopefully UDI will look into this sooner.

Even though excluding and including the device clears the problem, I don't think that is the solution. The underlying cause needs to be identified and fixed.

If adding a Z-Wave device to a scene causes the ISY to think it is an Insteon device and needs to write configuration information, but there is really nothing that needs to be written, then this needs to be fixed. If there really is some configuration information that needs to be written, associating the device with a Z-Wave Group, but can't, then this needs to be fixed.

 

UDI:

Let us know what addition information you need from us to help identify and fix this problem.

[oberkc]

45 minutes ago, jca001 said:

Even though excluding and including the device clears the problem

That solution did NOT work for me.

[Chris Jahn]

Similar to Insteon, Z=Wave uses native link information in either (or both) the Z-Wave controller and responder.  In addition to links explicitly created by the user, there are some implicit links created that are required for the ISY (e.g. to detect a button press).  Therefore, you will see the 1011 icon when there is link information that needs to be written to the device.  For example, this can happen for battery powered Z-Wave devices that are not awake.

One way to try this manually is to make sure the device is awake, and then right+click on the node and select Write Updates to Device

You may want to do this with the Admin Console Event Viewer to level 3 to see if any errors occur.

[jca001]

Chris:

In my case this is a wall on/off switch that basically should be awake all the time from what I understand because it is AC Powered and not a Motion Sensor that is battery powered. As I stated in my original post, I had the Event Viewer open and I am pretty sure at level 3. It just showed the one message and no errors. I even looked at the Error Log for the time period and there were no errors at all.

So I think there is a real problem, not just the device is no awake.

Let me know if you would like more information, Event Viewer, Error Log, etc.

[oberkc]

I hold the same view as jca001.  Mine also is a wall switch constantly powered and, I assume, constantly awake.  Still, I toggle the switch (only thing I can think to do to make sure it is awake) and, within 10 seconds, tried to write updates to the device.  I see no errors in the event viewer (set to level 3), as shown in the attached image.  In fact, it appears to me that the messages are telling me that there is nothing left to write ("awake with no pending work, putting back to sleep ZW022_1" see edit comment below).  Still, the little green icon persists.

edit: After I posted, I notice that the log includes references to two z-wave devices.  The device in question for me is ZW026.  The message about "no pending work" was in relationship to a different zwave device (a motion sensor) and I assume is purely coincidental that the message came within 10 seconds of the write attempt to the wall switch.

[Chris Jahn]

Thanks Guys,

Now I see the problem, its the same as another we are working on.

For some devices it is difficult for the ISY to determine the Z-Wave group being used to represent the switch, and in this case the group ID has not yet been determined (hence the "group 0" in the messages).  Therefore, the association cannot be written to the device until the group number is determined, which due to the bug, may be never.

[jca001]

Chris:

Is this other bug the one I reported about not being able to set parameters?

I watched a demo of another Z-Wave Controller setup and it had options/setting to associate the different Z-Wave groups with the controller so it could receive the events the Z-Wave device sent for groups other than the main one which I think is 1.

Any chance this can be added to ISY?

Hopefully I have used the correct terminology, if not please correct me and explain things.

 

[Chris Jahn]

This is different from setting parameters, but it is the direction we are going.  Unfortunately, we can infer and query information from the device but in seemingly far to many cases, this information is incorrect and/or insufficient and thus needs to be provided explicitly.

[jca001]

Chris:

I am sorry, but I do not completely understand you reply.

Can you explain what you mean by "it is the direction we are going"?

Everything I have read about Z-Wave group 1 is defined and the lifeline, if I am remembering the terminology correctly. So to me that seems like it is the default group and seems like that is the group that should be used unless something indicate differently. So if information comes from the device and does not specify a group, then it seems like group 1 should be assumed.

If some information needs to be provided explicitly, then how can we can we do that?

Like query or set information for a specific group for the device.

 

[Chris Jahn]

Yes, group 1 is lifeline, but some devices use groups 2+ for things like button presses or reporting motion, etc.

Currently you do not have the ability to specify the group, the ISY determines it, but we plan on having a way to specify extra information like this explicitly.

[jca001]

Chris:

Thanks for the clarification.

Hopefully the plan is to implement the changes soon so we can use more Z-Wave devices.

 

[pwmcmaho]

Just to add to this, I recently replace my PLM and since the replacement I have noticed a number of varying Insteon Devices showing the green icon.  Neither Write Updates to Device or Restore Device seem to work....

[paulbates]

Just now, pwmcmaho said:

Just to add to this, I recently replace my PLM and since the replacement I have noticed a number of varying Insteon Devices showing the green icon.  Neither Write Updates to Device or Restore Device seem to work....

Are the devices in question wireless? Wireless devices like sensors need to be individually put in linking mode prior to restore device.

Paul

[pwmcmaho]

5 minutes ago, paulbates said:

Are the devices in question wireless? Wireless devices like sensors need to be individually put in linking mode prior to restore device.

Paul

Nope, I don't have any wireless devices, these are all hard wired light switches.

[paulbates]

Just now, pwmcmaho said:

Nope, I don't have any wireless devices, these are all hard wired light switches.

Ok. Assuming you followed the modem replacement procedure, the only other thing I can think of is to factory reset those devices and then do a restore device to each of them.

Paul

[pwmcmaho]

21 minutes ago, paulbates said:

Ok. Assuming you followed the modem replacement procedure, the only other thing I can think of is to factory reset those devices and then do a restore device to each of them.

Paul

I tried that to a couple of devices, did the factory reset and restore.  Still shows the green icon.  (BTW, I did follow the PLM replacement, actually did the restore mode several times, as suggested in other posts that I saw)...

[paulbates]

1 hour ago, pwmcmaho said:

I tried that to a couple of devices, did the factory reset and restore.  Still shows the green icon.  (BTW, I did follow the PLM replacement, actually did the restore mode several times, as suggested in other posts that I saw)...

I'm stuck at this point.

• Submit a ticket to UDI here
• Paste a link to this discussion in it so that they can see what's been tried
  • https://forum.universal-devices.com/topic/25197-green-10101-icon-will-not-go-away/?do=findComment&comment=253298

Not sure about the holidays and it is a Friday.. but someone will get back to you and resolve

Paul