Indicates interference issues when displayed very often. It is issued when a message couldn’t be send due the medium (air) is too busy, the radio uses a listen-before-talk mechanism before sending out any message.
Using a ConBee II without an USB extension cable.
USB 3.0 interference, using a USB 3.0 disk near to a ConBee II. This has a dramatic effect to 2.4 GHz radios when in close proximity. See Intel’s white paper.
From that I m reading (but I don’t know how deconz manage the SQL part) it just mean deconz can’t save information on the database. Can come from deconz (it don’t need to happen, if it s from deconz , it s probably a bug) or direclty your OS.
Your configuration is persistant ? You don’t loose device when restarting ?
I don’t think it s database corruption, because the lock is from an application that use the database (and lock it for itslef)
Thank you for your answer. I am not loosing devices at restart. Maybe only some of the save attempts are failing. The behaviour is consistent. I just checked the log and in the meantime I have a newer error:
16:39:19:167 DB sqlite3_exec failed: COMMIT, error: database is locked (5)
16:39:19:168 void DeRestPluginPrivate::saveDatabaseTimerFired(),6035: assertion ‘saveDatabaseItems == 0’ failed
Could you advice what to do to further investigate and fix? I have programming knowledge but I have 0 knowledge on deconz.
I can’t answer, idk if it s something normal.
I have enabled logs on my side to see if I have same message (with error and error_l2 ?)
What is your deconz version ? You are sure not having 2 instances running ?