Device failed to configure

[Cor]

Hello,

I was playing with the fibaro universal sensor, I had some issues with it . I reset the device , included it again.
All was fine, but than I clicked the "configure node right now"on the child devices ..... they stay red and say "device failed to configure"  , the "parent" is still fine , and both childs are working as they should , they just show this error message.

Resetting the vera lite didn't help , pressing the configure now on the parent doesn't help either.

How can I get this error message away?

Thanks,
Cor

[Da_JoJo]

do z-wave heal and dont configure child nodes lol

[Cor]

Did that last night, but still the same :-s

Cor

[chixxi]

do z-wave heal and dont configure child nodes lol

I don't think that is something to lol about. It is just stupid from mcv to allow to try to configure child devices, something like this should be prevented by the UI.

However, is there a general solution if you once tried to configure a child device which is now marked read? Cause a heal didn't help...

I have a child device (Motion Sensor from EZMotion 3in1) which works jsut fine, but it is also marked in red "Device failed to configure".

[Cor]

@ Chixxi,   for how long is that status now on your vera?  I guess it doesn't go away by it's own 

[chixxi]

I guess about 6 month or so, a very very long time. Not going away by itself.

[Cor]

Crap 

So , what are the options , remove-reset them and include them again, open a ticket with MCV? something else?


The vera lite and universal sensor is completely build in, outside nera my gate ..... it is lots of work to get to the devices 

Cor

[chixxi]

Well you know, it isn't really a big problem since the my sensor is working just fine. And since I only use the vera webinterface to configure and not to control I don't really care about it. Was just wondering if there is a straight forward solution.

Excluding and including the device sounds simple, but it is used in a hole lot of scenes, and all of these would have to be reconfigured too then. For this reason I don't like this approach.

EDIT:
I just changed the child devices variable "Configured" from -3 to one, looks better now, error is gone. But I have to check if it still works when I get home.

[RichardTSchaefer]

Did you try to restore a backup from the before you tried to heal ?

[Da_JoJo]

chixxi ur right its not that lol if you have a dozen devices connected to it and you experience problems with it
i had this error in config before and i deleted the childdevice and press configure on the main device if i remember well.
after setting the Configured parameter in main device to 0 . seems to make the child-device do its job again ok.
probably setting Configured to 0 will do. no need for deleting the child-devices.
think ur right about that one should not be able to reconfigure child-devices . its useless to do that but its nice to have the possibility to set parameters in child-devices. i used this many times on my 2 6-port powernodes.

[chixxi]

Did you try to restore a backup from the before you tried to heal ?

I'd never accept such a huge risk for such a small error which basically doesn't matter. Whenever I do things like restoring from backups or updating firmwares and stuff like that I am close to a nervous breakdown, that is how much I trust mcv and their software. 

[Cor]

EDIT:
I just changed the child devices variable "Configured" from -3 to one, looks better now, error is gone. But I have to check if it still works when I get home.

Did this work?

@ RichardTSchaefer : I am a little bit afraid of restoring a back up as well ..... especially for such a small issue.

probably setting Configured to 0 will do. no need for deleting the child-devices.

I might try this.

Cor

[mikesus]

I have seen this on battery devices... The seem to work fine tho?

[Cor]

@ mikesus:

.......... , the "parent" is still fine , and both childs are working as they should , they just show this error message.

[chixxi]

I just changed the child devices variable "Configured" from -3 to one, looks better now, error is gone. But I have to check if it still works when I get home.

It has been a while ago since I tried this, the error has never reoccured and all child an parent devices work just fine. So for me this is fixed.