Inovelli appears to be following the Hubitat custom of disabling debug logging 30 minutes after it is enabled (and again, by custom, it is also enabled by default on a new device installation). This is to limit the amount of information that gets logged, both to marginally cut down on the load to the system and also make the “Past Logs” more usable so they won’t be so cluttered or hit their limit so quickly. Debug logging is normally only necessary to turn on when investigating a specific problem.
Where they appear to be going an extra step is disabling info logging (description text logging) after this timeout as well. That is not Hubitat custom. Again by custom, this will normally log things like attribute changes: on/off state of the switch, level of the dimmer, power consumption, etc. I would suggest to the driver author that they not automatically disable info logging. If you don’t want this to happen, you can manually edit the driver by removing this line, which is at 184 in the current version:
device.updateSetting("infoEnable",[value:"false",type:"bool"])
The message you’re seeing in your logs is not bad–it’s just telling you that this is happening. (Again, the wording is a bit different from Hubitat’s customary message in this case, but the idea is the same.)
In related news, Hubitat is supposed to be releasing a built-in driver for these in their next hub firmware release. No word on when or what features it will include. They will undoubtedly write it in a way that matches the Hubitat customs they’ve created, but since of those is also “double-tap max” I suspect we’ll have to use Inovelli’s custom drivers to get full use of the switch anyway. But who knows!