This might have to do with the move to OZW 1.6 (which is still in beta phase in domoticz, but this will be the default)
First:
You do not have to exclude/include, you do not have to reset the controller or the node, all information is stored inside the controller/node, and this is hardware... and OZW 1.6 is software...
I see a lot of people freaking out and doing excludes/includes/resets... you will loose your logs, your timers, scripts etc... do not do this...
There have been many changes in the OZW library, and most (almost all) for the better.
There have been many changes as well in Domoticz related to OZW, and also all for the better, all is looking much clearer now, and also the working should be better, there could still be some issues, but hopefully not to much.
You're not the first one using the beta with OZW...
The configuration/cache file has been renamed, but it needs to be build from scratch anyway because a lot of index/instances has been changed.
This is easier said then done.... Sure OZW will ask kindly to all (powered) nodes to send it's configuration again, but some nodes (battery powered nodes), are probably in 'sleep' mode...
They will respond when they wake-up most times, but that could take up to some hours.
For those nodes, what has been working for me, was to have to node next to my computer, open, so i could (triple) click the wake-up button.
Select the node from the list, and press '
Refresh Node Info', now within a second, wake up the node
What works best for me is to open two browsers, on the left browser open the log, on the right browser open the OZW hardware setup
This way you could directly see if something is happening
Be patient, try waiting a few hours
Also search for (closed) issues on the github repository, like
https://github.com/domoticz/domoticz/is ... -514125507