The mystery of devices turning on (or off) by themselves

New burst today, see logs here. All Osram:

11:04:47:947 DeviceAnnce of LightNode: 0x7cb03eaa0a018193 Permit Join: 0
11:04:46:773 DeviceAnnce of LightNode: 0x7cb03eaa0a018193 Permit Join: 0
11:04:45:768 DeviceAnnce of LightNode: 0x7cb03eaa0a018193 Permit Join: 0
11:04:45:409 DeviceAnnce of LightNode: 0x7cb03eaa00ab9f0b Permit Join: 0
11:04:45:396 DeviceAnnce of LightNode: 0x7cb03eaa00abab48 Permit Join: 0
11:04:45:361 DeviceAnnce of LightNode: 0x7cb03eaa00af6a19 Permit Join: 0
11:04:45:317 DeviceAnnce of LightNode: 0x7cb03eaa00ab82b1 Permit Join: 0
11:04:45:054 DeviceAnnce of LightNode: 0x7cb03eaa00abab48 Permit Join: 0
11:04:45:027 DeviceAnnce of LightNode: 0x7cb03eaa00abb36e Permit Join: 0
11:04:45:006 DeviceAnnce of LightNode: 0x7cb03eaa00abab48 Permit Join: 0
11:04:44:151 DeviceAnnce of LightNode: 0x7cb03eaa00af6a19 Permit Join: 0
11:04:43:766 DeviceAnnce of LightNode: 0x7cb03eaa0a09aa49 Permit Join: 0
11:04:43:282 DeviceAnnce of LightNode: 0x7cb03eaa00ab82b1 Permit Join: 0
11:04:43:229 DeviceAnnce of LightNode: 0x7cb03eaa00abc0fa Permit Join: 0
11:04:43:128 DeviceAnnce of LightNode: 0x7cb03eaa00abb36e Permit Join: 0
11:04:43:066 DeviceAnnce of LightNode: 0x7cb03eaa0a018143 Permit Join: 0

But not deCONZ rebooting?

Just want to mention, and then we can close this ancient thread, that the issue described has been resolved with #7605, #7608, #7609, #7613..

I also percieve that deconz core developers are now much more willing to look into issues instead of trying to deflect. This gives me confidence to stay with deconz, because it is a great piece of software with some quite unique and valuable features like source routing, GUI.