I get these all the time. Somewhere in the forum or GH @chris explained it to me. Z-Wave does not do much error checking and it is RF, so bits get flipped. If you want a surprise, look into your XML files and chances are you will find a bunch of inaccuracies, like command classes that do not belong to that device. These show up from legitimate communications that have gone awry and added to the wrong XML. I don’t think this causes much of an issue, but I periodically wipe them out to start fresh.
Thanks for the info…I anticipated it could be something like that.
So you are saying the XML files get recreated if you wipe them out? I have one mains powered node that has become unidentified after an upgrade and can’t get it to be recognized…maybe killing the xml file will help it get reidentified? I’ve removed it from OH with the hope it would get recognized…but it always comes back unidentified and stays that way.
Absolutely, just do it with OH not running. Everything in $OPENHAB_HOME/userdata/zwave/ can be deleted and it will be rebuilt. as the devices initialize.
That sounds like a ghost node. Search the forum. You can try getting rid of it through Habmin, but may need to use PC Controller (replacement for Zensys Tools) from SiLabs. But if your nodes end at 42, then this wouldn’t be possible. I never noticed XMLs created for the nodes reported in these warnings.
I’m confused . When I start OH, I get warnings like you posted. You also posted…
This sounds exactly like my experience.
So, this is a separate issue? Deleting the XML will not help. Deleting the Thing (not excluding) and rediscovering may help, if the binding was updated. If not, post the xml, as it may not be in the database or it may have a newer firmware than what is in the database. What is the make/model of the device… or screenshot the Attributes section from Habmin.
The Attributes section provides the type:id (useful to look it up in the db) and firmware version. But if you have another, then you know that is not the problem! Unrecognized mains powered device… hmmm… my advice is to power cycle it. If that doesn’t work, reinitialize it. If that doesn’t work, exclude and reinclude.