Missing devices from Aeotec stick

I am new to HA, just installed a version 0.99.2 system on Raspberry PI 4.

I am using Aeotec Z-Wave stick as a secondary controller. Before installing HA, I used the Zensys tools on Windows to include the Aeotec into my Vera Plus , after including it into the z-wave network, I can see all devices on the stick.

I than took the Aeotec stick and plugged it into the PI , in the OZW log, I can see almost all of the devices (I think it is missing some battery ones), but when I open the UI , I am missing many devices which are also missing in the core.device_registry.

Any idea to why devices are missing if they are on the stick ?

How can I increase the OZW debug prints?

Please, don’t use code formatting like that, it makes it really hard to read your post.

I will rewrite/explain my issue.
I have a VeraPlus controller with around 40 devices. All devices are working.
I just added a new Aeotec gen5 stick which is connected to my PI running HA 0.99.2

The Aeotec was added to the Vera controller and when I use the Zensys tools I can see all 40 devices, but when I move the stick to my PI I can see only half of the devices.
In the OZW log I sometimes see timeouts from the devices which do not appear on HA.
It seems HA either don’t wait enough or doesn’t retry .
How can I fix this?

Have you tried going around all the devices and either operating them (mains/USB powered) or waking them (battery powered)?

I have opened two browsers, the first to HA and the second to Vera, the nodes which I can’t see in HA are all connected directly to power and are working perfectly from Vera.
It tried to look on one specific node, I can see HA is getting replies from that node ( it gets errors but also good replies) but it does appear on the GUI.
I also looked for this nodes on some files under .storage directory and it’s not there.
Is there a way to clear all HA database and tell it to re-read the Aeotec stick?
( all the correct info is on the stick when I check it via Zensys tools.

There is no database in HA, it loads the config from the stick.

However, operating/waking the devices may refresh HA’s cache or knowledge of the device. That’s why I recommended that.

I got some progress with the following steps:
Stop HA , remove the files: zcfg_0x , core.devices_registry , core.entity_registry , core.restore_state , power cycle my PI.

I still have missing nodes, for example (it was easy to discover) one of my Fibaro FGRM222 cover is missing , when I look at the OZW log I can see this device:

2019-10-11 20:00:39.141 Info, Node023, Received reply to FUNC_ID_ZW_GET_NODE_PROTOCOL_INFO
2019-10-11 20:00:39.141 Info, Node023,   Protocol Info for Node 23:
2019-10-11 20:00:39.141 Info, Node023,     Listening     = true
2019-10-11 20:00:39.141 Info, Node023,     Beaming       = true
2019-10-11 20:00:39.141 Info, Node023,     Routing       = true
2019-10-11 20:00:39.141 Info, Node023,     Max Baud Rate = 40000
2019-10-11 20:00:39.141 Info, Node023,     Version       = 4
2019-10-11 20:00:39.141 Info, Node023,     Security      = false
2019-10-11 20:00:39.141 Info, Node023,   Basic device class    (0x04) - Routing Slave
2019-10-11 20:00:39.141 Info, Node023,   Generic device Class  (0x11) - Multilevel Switch
2019-10-11 20:00:39.141 Info, Node023,   Specific device class (0x06) - Motor Control Class B
2019-10-11 20:00:39.141 Info, Node023,     COMMAND_CLASS_BASIC will be mapped to COMMAND_CLASS_SWITCH_MULTILEVEL
2019-10-11 20:00:39.141 Info, Node023,   Mandatory Command Classes for Node 23:
2019-10-11 20:00:39.141 Info, Node023,     COMMAND_CLASS_BASIC
2019-10-11 20:00:39.141 Info, Node023,     COMMAND_CLASS_SWITCH_BINARY
2019-10-11 20:00:39.141 Info, Node023,     COMMAND_CLASS_SWITCH_MULTILEVEL
2019-10-11 20:00:39.141 Info, Node023,     COMMAND_CLASS_MANUFACTURER_SPECIFIC
2019-10-11 20:00:39.141 Info, Node023,     COMMAND_CLASS_VERSION
2019-10-11 20:00:39.141 Info, Node023,   Mandatory Command Classes controlled by Node 23:
2019-10-11 20:00:39.141 Info, Node023,     None
2019-10-11 20:00:39.179 Info, Node023, NoOperation::Set - Routing=true

but in the core.entity_registry I don’t see this node at all.
When I go to configuration - integration - zwave , I also don’t see this device.

any idea ?

Update -
I rebooted my PI and the missing devices (powered ones) appear. One exception is the ZXT-120 (powered) which still doesn’t appear .
Still the battery ones are showing in the OZW log , but not appearing as entities.
All Z-wave elements appear in the zcfgX…. file, so how can I add them as entities ?
Manually ? More reboots ?

Just wanted to say that nirgal previous recommendations to remove the files did fixed missing devices issue for me.

So thank you very much :slight_smile:

Huh, I’m seeing a few missing devices (interesting note, my controller Aeotec 5 is a secondary controller as well). I’m seeing interesting data in my logs, the consistant issue between the devices is that the node identity codes are all zeros.

2020-05-12 23:19:37.418 Info, contrlr,     Node 030 - Known
2020-05-12 23:19:37.418 Detail, Node030, AdvanceQueries queryPending=0 queryRetries=0 queryStage=CacheLoad live=1
2020-05-12 23:19:37.418 Detail, Node030, QueryStage_CacheLoad
2020-05-12 23:19:37.418 Info, Node030, Node Identity Codes: 0000:0000:0000
2020-05-12 23:19:37.418 Info, Node030, NoOperation::Set - Routing=true
2020-05-12 23:19:37.418 Detail, Node030, Queuing (NoOp) NoOperation_Set (Node=30): 0x01, 0x09, 0x00, 0x13, 0x1e, 0x02, 0x00, 0x00, 0x25, 0x1c, 0xc0
2020-05-12 23:19:37.418 Detail, Node030, Queuing (Query) Query Stage Complete (CacheLoad)