Version 1.0.23 adds import/export dialogs:
3 Likes
I was one behind but 1.0.23 is up on github now.
Question: I added as Action a bash Script Execution - can i grep or See the Script execution Status or the Log-Output of the Script and create New Steps based on the Output?
Usecase: I created a bash Script which syncs some Folders from Phone — seafilecloud and back with help of rclone — as trigger I want to set something like @home or time based or wifi-Network related to Sync only, when at Home to Save battery and mobile Data
Prior to version 1.0.24, as a workaround, you could only write the output to a file and then parse it in a get step, because actions do not currently return any output to the flow.
In the current version, you should be able to use shell execution in a get step instead of an action step, which can return the standard output to the flow. You can also split stdout by delimiter, regular expression, and so on.
2 Likes
Just in case you may need it, you can read the current wifi network name via dbus:
{
"address": "system",
"destination": "net.connman",
"enabled": true,
"id": "source_wifi_name",
"interface": "net.connman.Technology",
"method": "GetProperties",
"name": "Get Wifi Name",
"path": "/net/connman/technology/wifi",
"transformations": [
{
"in": "arg0/TetheringIdentifier",
"out": "wifi_ssid",
"type": "copy"
}
],
"trigger": false,
"type": "dbus"
}
I’ve added this to the online library.
1 Like
Version 1.0.28 replaces the Examples Library with a Community Library, allowing users to share examples with the community:
3 Likes
Are there any other protocols worth adding, or any missing functionality?
maybe something related to flow testing / debugging of flows:
- If you run a flow, show last runs of it and if it failed or completed successfully
- and maybe show / allow to see states and values of item which run within the flow
that’s what i’m personally miss - right now debugging of flows is a little bit tricky to me or do you have any recommendations or best practices how to debug and test new flows?
Currently I just run journalctl -u automagic.service -f inside a terminal but you’re right and I probably should look into more convenient ways to debug flows.
1 Like