Update to 3.0.4 please (its live now) and let me know if it solves the issue?
no…same problem…
Update to 3.0.4 and a reboot of Homey helped for me
Yeah i already know this is a solution.
However, as developer, i would love to find out why a reboot fixes the issue, while an app update itself does not.
An app update (obviously) means the app restarts.
There should be zero difference between an app restart or an homey restart, it should not affect if you can edit an AVD, certainly not an existing AVD.
(Their was a bug in 3.0.1 which didn’t allow to edit fields with a fresh/new AVD, but that already has been resolved).
@Davide_Zamo
Thanks!!!
Could i ask that you dont reboot the homey so we can solve this together?
for sure-
i don’t reboot…
Thanks, i have just updated the version to 3.0.5.
COuld you install it and send me another screenshot of the console AND send me a diagnostic (after you have opend repair)?
this is the diagnostic…
0006818b-2e13-4585-aa7d-0eb674e040c7
Thanks, the diag is showing me something. Working on it right now!
@Davide_Zamo and @scwl and @JayR
The issue was with the BLL app and has now been resolved (in the test version).
(This was the reason a homey restart was the solution: BLL needed a restart because it hang on startup after the update.)
I just released a minor bug fix for DC:
When starting up the app, flowcards could be triggered (When Field has been set) falsely. This is resolved in the latest version.
Today I tried to install Device Capabilities on my Homey SHS (on macOS, MacMini Pro). But it doesn’t run, it crashed immediately after installing. The error it reports is: Error: EMFILE: too many open files followed by a long list of files. When I started using Homey a while ago I also had it installed to test it, then it worked fine, but I uninstalled it after trying. But now that I want to actually start using it, it crashes. Some help or insight is appreciated.
Could you PM me that long list of filenames?
It looks like the timers are no longer being displayed correctly since the latest update. The timers are running, even though this isn’t visible in the last screenshot.
Could you please check whether this might be related to the update?
Yes, ill check it right now.
Resolved in 3.0.7.
@Arie_J_Godschalk , The timers are displaying correctly again! Thanks for the quick fix and all your hard work on the app. Much appreciated! ![]()





