I’ve added some additional checks into the database - some of these result in “errors” which need to be removed before the database entries can be exported. If you are a Z-Wave binding user, please read on and spend a few minutes to check that your devices are properly defined…
There are two main new checks - firstly, there’s a check to ensure that device IDs are not duplicated which would result in an ambiguous selection of the device - I thought that this was in the database checker already, but it seems not…
The second check is to ensure that configuration parameters max/min settings are set consistently - or more specifically, that the default value is consistent with the min max. Sometimes people aren’t putting in the min/max and this is causing problems in the UI which ultimately results in not being able to save the configuration. This is especially notable in PaperUI as it checks, and sends, all parameters to the server - the error display in PaperUI is not very clear so it’s often confusing to people why PaperUI doesn’t allow updates. Since HABmin only updates parameters that have been changed it’s less of an issue there, but it does still apply.
Below is an example error output from the Aeon ZW116 -:
I will likely try and resolve some of the Type:Id duplication errors by removing the offending duplication on one device - this might be wrong, but if the duplication remains, then there is no way to know how the device is detected anyway. In many cases it is obvious which is correct as there’s often some sort of pattern used by manufacturers (and this is the case with the Aeon device above).
I’ve found that there are simply some duplicated devices, and in this case I’ll likely remove the one that looks to be the least complete.
If you spot issues with these checks, and you think they are wrongly detecting issues, then please let me know. If you are unsure what do do, then please discuss…
There are now around 660 devices in the database, so it would be great if people could take a quick search of the database for their devices to make sure there are no errors showing up, and if there are, correct them. Alternatively, you can also check the summary page, but note this takes a while to process the data…
On other news, I’ve also written an import function to read the configuration parameters from the ZWave Alliance XML files, so if these are available, we can now use them as a starting point for the database. There are often errors in these files (strangely!) so they normally need editing, but it should reduce the amount of work significantly for new devices.
.
.
and it is not alway obvious which thing id could be deleted or moved to another device.