Almost everything about the homey-api is heavy on cpu/memory. There are some situationeel that the Watch card is the only available option, but if not, beter use alternative if possible.
BLL coding is done in a Javascript Sandbox (stand-alone engine running the code). So using 6 flowcards to calculate will indeed use more resources than using one flowcard (be it a BLL or HomeyScript flowcard).
BLL coding/expressions uses the same methods as HomeyScript, so singular use would use about the same resources. BLL does add some functions and replaces some possible values (like the checkmark we get instead of true since hp23), so it might use a little bit more cpu when starting the script, but thats real small/low.
@Arie_J_Godschalk, I also thought that BLL used JavaScript quite efficiently. But the difference between the old en new flow is quite large, is this only because of the reduction from 6 to 3 cards (and maybe use of global variable vs BLL variable). I tried 1 single scriptcard, but that became less clean with merging and splitting values. Moreover, no less CPU load (or even more load when getting capabilities inside the script, in stead of as argument from the flow)
Could you please have a look at the diagnostic report and let me know whether there is something wrong with the generated download route or the BLL file server?
Thanks. I tested this with a newly generated file: MDalarm_20260823_192229.avi.
I’m sure the filename is correct. Using the URL generated by BLL internally returns HTTP 200, and the response starts with RIFF, so the AVI file exists and can actually be read.
I also tested your suggestion and removed /getfile/ from exactly the same URL. In Safari that request just keeps loading and returns nothing.
So with /getfile/ the BLL-generated URL works internally (HTTP 200 + RIFF), but opening it externally results in “Cannot GET”. Without /getfile/, the request hangs.
Okay, an have you tried looking up your Cloud ID in More->Settings->System and using this URL: https://cloudid.connect.athom.com/app/net.i-dev.betterlogic/userdata/getfile/83ad6434c8227defb26d0580a8b379f3f952e69186ff7114/MDalarm_20260823_192229.avi, where you replace cloudid with your actual Cloud ID? So the exact same URL. If that doesn’t work, you should contact Athom as app developers have no control over how the cloud relay handles userdata.
The Athom relay does work with userdata, at least in my own apps (I’m using a Pro 2019). Maybe Athom blocked specific filetypes to prevent abuse (e.g. to prevent people abusing their cloud relay for watching hours-long movies remotely which it’s obviously not intended for). Have you tried another file extension?
i have removed your app and switched all the vars to homey vars unfortunately
It messes up to much depending flows for weeks now and had no response on my earlier question…. So i can not test anymore. Also it seams i am the onlyone somehow