Think I had the same issue.
However I did not send a diag before restarting and after a restart it is working.
Thanks for letting me know.
It happends sometimes after a reinstall/update that the api doesnt boot correctly.
I have added many logging lines to see why that happends, because i never can reproduce the issue myself, so i need to solve this from the diagnostics.
Since after any random restart solves the issue, its a bit difficult to find the exact reason (even debugging someone else homey wouldnt work, because as soon as its installed through the CLI the problem will also be solved).
I plan on taking out my old homey 2016 model or 2019 and see if i csn reproduce it on those slower system next week.
If anyone has this issue: please send a diagnostic before restarting the app. Thanks!
I just completly rewrote the way BLL startsup.
Reason was that it uses its own library through the API to startup and load its modules.
This, completly randomly, sometimes made the app not start-up. And this creates issues for other Apps like Device Capabilities.
I rewrote this whole part, so BLL loads its module directly from the disk instead of going through its own API for those files.
This seems to work, because i now load everything directly on the app.init, instead of a part in a async method.
This also increases the loading time from about 5-7 seconds to less then 1 second (on my HP at least). Plus, drivers/devices are now only loaded after the app itself is completly loaded and running.
The BLL Update is live.
perfect. thanks a lot…
@Patric_Hedin
You can now again with 4.2.1.
Thanks a lot @Arie_J_Godschalk 
And fixed on a saturday morning within an hour 
Amazing, thanks!
Can you make this trigger work?
It isn’t working?
Can you send me a PM?
