Motion sensor hsm100 fail to initialise

According to the developer of the HSM100

HSM100 was developed long before the current rules on endpoints were in place.
The endpoints are only to differentiate between the sensors in the device.
Everything else should be sent without multichannel encapsulation.
Wakeup CC must be sent without multichannel encapsulation.
Wakeup applies to the device as a whole, not to the individual sensors.

According to @chris

this is exactly what the database modification would do - effectively to remove
the wakeup class that the device currently advertises from the 2 endpoints.

@chris Is the database modification something that I can do, or it needs to be done on your side?
If the latter, do you know when it would be done? Do I then have to download an updated version of the database? Where from?

Also, do you know if the Zway binding can potentially resolve this issue, without changes to the database?
Does it rely on the database of zwave devices that you are maintaining?

Thanks