I will shortly perform a complete “resynchronisation” of the ZWave database and this will flow into the SNAPSHOT binding in the next day or so… What this means is I delete all the XML files that are created when the database is exported, and re-export everything. This ensures that any changes get fl…

Most of the channels that are deprecated are not recommended (hence why they are being removed) - eg switch channels when there is a dimmer channel, or some older alarm channels where we have an improved option. In the longer term (probably for 2.6) we will probably look to remove some of these (th…

@chris Does that mean a “pause” of database changes for a day or so?

No - it’s fine. I actually did the export a few days back, but just havent have the time to write this “warning” message before merging :slight_smile:

I just updated to S1698. I had to restart several times because I kept getting the Queue Full message. I removed zwave from the addons.cfg, restarted again, waited for the load on the server to return to normal, and then added zwave back to the addons.cfg. However, all four of my DZS15 devices came…

I suspect the information was always missing and the device has just become unpublished and missed with the export. I’ve just re-exported and will do an update tomorrow.

@5iver If you could provide the inclusion & exclusion information ir would help complete that database entry. :wink:

I have no prob completing the db entry… just wanted to confirm this was related to the resync and not an issue with the recent device db cleanup.

I just updated to S1705 with zwave 2.5.0.201909300431 and the Thing xml for the DZS15 is still missing from the binding. Everything looks right in the device db , but the changes I made were done after the last export, so that would explain why it is still missing.

@chris , did this slip past you?

Indeed, it looks missing here .

openHAB Community

ZWave database re-synchronisation

Add-ons Bindings

chris (Chris Jackson) October 3, 2019, 6:25pm 24

[zwave] openHAB 2.5.0 Build #1723 exception during startup