Resolved: Oh Vera... you don't have to put on the red light ...

Community Playground General Discussions
1

Checked in on my remote Vera setup 2 days ago.

  • Had red cogs next to light and motion sensor. All had been peachy green prior.
  • was able to control light, view camera fine
  • No “Neighbors” or “configured at” info on the devices

Went to Z-Wave options and clicked Heal Network.

  • waited overnight
  • still red cogs today
  • can still control light

Went to device (light) and clicked Configure Node Right Now.

  • Red cogs, Job failed. Yippee.

I left it in this state. Submitted report #381. Firmware: 1.0.523

.//A.

2

Welcome to the club!

My Vera lost states of pretty much all of my devices after couple weeks of running - i.e. it can still directly control lights, when the button is pressed on the Dashboard, but their states are not correct. Some devices don’t even show any states (None of the buttons are highlighted), but some devices show the wrong state. It seems at some point Vera just stopped polling the devices…

“Poll all nodes” shows lots of failed polls due to either “Failed with TXStatus: 1” or “Node never responded”…

3

This has also been happening with my Vera setup Firmware: 1.0.523.

4

Clicked Heal Network.
Waited another 24 hours.
Still Red cogs.

.//A.

[quote=“anthonyris, post:1, topic:164350”]Checked in on my remote Vera setup 2 days ago.

  • Had red cogs next to light and motion sensor. All had been peachy green prior.
  • was able to control light, view camera fine
  • No “Neighbors” or “configured at” info on the devices

Went to Z-Wave options and clicked Heal Network.

  • waited overnight
  • still red cogs today
  • can still control light

Went to device (light) and clicked Configure Node Right Now.

  • Red cogs, Job failed. Yippee.

I left it in this state. Submitted report #381. Firmware: 1.0.523

.//A.[/quote]

5

Constantly we’re upgrading and improving our firmware, it’s always a good idea to upgrade your firmware as soon a new version appears. Choosing keep settings preserve all your previous settings.

In our last firmware we’ve add and option for Vera to automatically configure devices / manage associations which is needed for some devices to work: http://wiki.micasaverde.com/index.php/ZWave_Configuration_Options#Automatically_configure
Also if your Vera isn’t the Master COntroller all the events won’t get directly to it, this causing Vera for not showing accurate device status.

I’ve looked at your ticket 381 and I’ve noticed that your nodes aren’t configured (this is caused by not having Vera Master or the Automatically configure devices box checked) you should try pressing “Configure Node right now” on every device that doesn’t say it’s configured already.
More info about Zwave Debugging you can find here: http://wiki.micasaverde.com/index.php/ZWave_Debugging

PS: Before submitting a trouble report it’s always better to first enable Verbose logging ( from Advanced->Logs) then reproduce the problem, then submit the ticket, then disable Verbose logging.

6

What I found interesting and strange, is that sometimes my devices (mostly Leviton ViziaRF/RF+) stop responding to queries. I always thought the problem was in Vera, when polling would start showing red pencil icon. Commands would still work - i.e. switching the device On/Off. Then after some experimentation I found out that my Leviton Master controller would also fail to acquire any data from the device - like manufacturer info or capabilities. I ended up “rebooting” the device - i.e. unplug it and plug in back in w/o erasing the network data. That would make the device function properly and Vera would start polling it just fine.

So, the question is why after some time of working fine most of my Leviton devices went into that weird unresponsive state? Was it because Vera’s constant polling or periodic reconfiguration? Is it “abusive” to devices?

BTW, to “reboot” the plug-in type of device it is sufficient to unplug in from the socket outlet, wait couple seconds and plug it back in. To “reboot” an in-wall Leviton device, the “air gap” needs to be engaged - pull the bottom part of the toggle pad, so all LEDs go off, wait couple seconds and push it back in place.

7

OK, another swing at trying to solve this. Pls note that i can control the light switch, however light and motion detector remains red cogged.

Today’s effort:

  • Upgraded to new firmware (.565)
  • Configure Node Now failed (red cogs).
  • Heal Network failed. (red cogs)

Submitted new support ticket with verbose logs (#494).

Original posting 3 weeks ago.
.//A.

[quote=“anthonyris, post:4, topic:164350”]Clicked Heal Network.
Waited another 24 hours.
Still Red cogs.

.//A.

[quote=“anthonyris, post:1, topic:164350”]Checked in on my remote Vera setup 2 days ago.

  • Had red cogs next to light and motion sensor. All had been peachy green prior.
  • was able to control light, view camera fine
  • No “Neighbors” or “configured at” info on the devices

Went to Z-Wave options and clicked Heal Network.

  • waited overnight
  • still red cogs today
  • can still control light

Went to device (light) and clicked Configure Node Right Now.

  • Red cogs, Job failed. Yippee.

I left it in this state. Submitted report #381. Firmware: 1.0.523

.//A.[/quote][/quote]

8

anthonyris it seems that you’ve had a ZWave dongle lock up. I’ve done a restart of the dongle chip from Setup->Device->Zwave Options->Restart Zwave Chip, and now it seems that your devices are working.
Since the Motion Sensor it’s an battery operated device, you’ll have to click on it’s blue configure button and then press configure now, for the red cog to disappear.

9

We just added a new improved ‘heal/diagnose’ network that creates a detailed report on the health of all the nodes and the network. It will be released in a few days.

10

I am remote from the box (summer house). Is there any way to do this remotely?

.//A.

[quote=“cj, post:8, topic:164350”]anthonyris it seems that you’ve had a ZWave dongle lock up. I’ve done a restart of the dongle chip from Setup->Device->Zwave Options->Restart Zwave Chip, and now it seems that your devices are working.
Since the Motion Sensor it’s an battery operated device, you’ll have to click on it’s blue configure button and then press configure now, for the red cog to disappear.[/quote]

11

No, but Vera will configure the sensor next time it wakes up, so in about 20-30 minutes (it can takes up hours too, depending of the sensor wakeup interval) the red cog should disappear.

12

OK, waited overnight and the motion detector has not given up its red cog and remains unconfigured.

  • tried to “Configure Node Now” on the light switch to see if this was working (switch was in green cog state).
  • Light switch would not configure - red cog.
  • Clicked Heal Network - light switch would not configure.
  • Clicked Reset Zwave chip to get the light switch to configure. green cog.

I will guess if I try to Configure Now the light switch, it will fail again.

It seems as though there is still something wrong with this. What to try next? Pls note I am remote from the box.

13

Have you tried pressing the blue button and the going to vera and pressing configure now?

Is it possible the sensor has been moved from the location it was istalled to or is it too far from comunication?

14

“Pls note I am remote from the box”

Sensor hasn’t moved in months, as no one has been there for months. All devices are within 15 feet of Vera.

[quote=“zmistro, post:13, topic:164350”]Have you tried pressing the blue button and the going to vera and pressing configure now?

Is it possible the sensor has been moved from the location it was istalled to or is it too far from comunication?[/quote]

15

Having the same issue. All devices showing red cogs. Vera is not able to get information on devices. Vera can control the devices. Heal network and reset of Z-Wave chip did not resolve the issue.

Submitted trouble ticket.

16

What brand of devices are those? Do you have another controller - can you try querying those devices from another controller?

As I explained above, in my case red cogs were because devices got into that unresponsive state (while still being controllable) - so even my Leviton controller was unable to run “Dev Properties” on them. I fixed the issue by “restarting” the devices - unplug/plug back in…

17

In my case all of the devices are from Intermatic:

Intermatic HA03C Lamp module
Intermatic HA02 Appliance module
Intermatic HA 04 Outdoor module

Unplugging the devices does not seem to help.

18

Having the same issue too. I found that the heal network option causes all my devices to stop responding to polls. However, I was able to use the reset of Z-Wave chip option to get them to respond again (except for my motion sensors).

19

Anthony, I re-read this, and I hope I did not miss this, but are you sure the battery on the sensor is still good? You mentioned it hadn’t been touched in months.

Best wishes,
D.

20

I’m also having reliability issues now.
All my devices are Intermatic as is my Primary controller. Vera is added as secondary. Also my ControlThink controller is secondary. And all has worked well for months. Just the last couple of weeks it seems to give problems…

My CT ctrl still functions reliably, thus I have no doubt that my Zwave network is unresponsive. It seems to be a Vera issue…