Thanks Marco!
Please note that the Test version is still in development and there might be (small) changes before i push for live.
Im sorry, but i am not sure which scripts you mean?
The Simple Log “Auto Add Cards” i just wrote?
If so: This script, as far as i know, cannot be executed in HomeyScript. It must be executed in the API Playground.
How or where i am gonna place this script, i am not sure yet.
I though about the Device Capabilities app, because it has allready the homey-api included.
However, it might be that this script wouldn’t need the homey-api, because i can generate the full code for the playground.
And i do have an alternative in mind, but i must test that first…
Thanks!
It works for the 1st flow in the flownames array.
(And the flowname is in the log card, great! )
let flowNames = ['Transition Example Copy1','Transition Example Copy2'];
When I run it with only
let flowNames = ['Transition Example Copy2'];
that flow is getting log cards as well.
(Oh and I’m not trying the script with the ‘all flows’ selector
let flowNames;
yet ).
Additional question:
Is it possible to add logcards to ‘normal’ action cards as well, but just with the flowname in it, and ‘severity’ “informational”?
@Arie_J_Godschalk A quick question: Is this new version of Simple LOG depending on any other app to be installed (Better Logic?) to be functional, or is it (still) a standalone app?
I am using the current version of Simple LOG, and it looks like you have made some real improvements now. I haven’t yet tested the new version, but I plan to. Thanks for all your good work, both on this and other apps!
RIght now the test version is yeah, you need BLL for it’s datetime function and config and the File Server.
Also, the Settingsscreen now uses BLL components.
But, i have already made a Memory backlog.
This backlog is used as long as BLL is not running.
It’s format is based on the flowcard definitions, meaning, the exact same format/datamodel as the Old Simple (Sys) Log datamodel.
When BLL starts, the new parts of SL is activated, the BackLog is writen into the new/FileBased Log and if Syslog clients are connected, the updates get executed.
Now, in my current develop version, you can already request the BackLog as JSON through it’s default (new) GetLog flowcard.
So, “all” thats left todo is find a (nice) way of still showing the (old?) settingscreen when BLL is not installed (doesn’t even need to be running for the settings tho, just needs to be installed.
If that works correctly, i need to make sure the BackLog is saved in Homey’s Settings and reloaded on app start (right now it’s still more a temporary memory before BLL can start up).
But currently (my dev version and most of test also) will work without BLL, SL will startup, all logging flowcards will work (clear log doesn’t do anything in that situation yet i guess ) and i can retrieve it’s json.
But for all the cool stuff, like Excel files on your phone, and logs with nicely formatted dates etc, and Syslog clients (altho i am looking into how to not need the BL.datetime.toString for Syslog clients), with the current test version, you will need/want BLL
Great, thanks! I have had BL installed for a long time, but I haven’t actually used it. I just updated to the latest (and renamed version), and I might update to the test version of Simple LOG in the near future, since it sounds like it is fairly close to being done and stable.
When I am switching from Papertrails to Simple LOG, I need a way to remove the flowcards that were automatically added by Papertrails (or do it by hand which would mean an awfull lot of work… )
Is there a way to do that as well by a (modified?) script you’re working on for Simple LOG??
Alternatively; If I uninstall the Papertrails app these flowcards (THEN add to papertrailslog” become broken. So a script that would remove all broken flowcards would be fine as well, to keep it more general perhaps…
Well, when i am done, i actually want users the option to use the script for Papertrails or SimpleLog.
It’s a big script to make and perfect for AFs and the difference in which card to use is small (i guess once small method would be enough).
That being said, i suppose you could then also use that script to remove the Papertrails cards, altho i don’t know yet which are added automaticly.
That would be great, @Arie_J_Godschalk. Thx!
Only thing is that the Papertrails app is not yet ready for Homey Pro / SDK 3.
I know this might not be a question for you and this topic perhaps, but wouldn’t it be possible to have a script that deletes broken flow cards from all flows?
To keep it more general and useful in more situations…