error on line 1
phone automation

since kebabapps pulled my beloved automation-app llama from the play store i had to find an alternative.
llamalab (coincidence or my bias?) automate provides a decent functionality and a community with a lot prebuilt algorithms. going pro is well spent.
it is another kind of programming with careful planning of data structures and algorithms.

warning: debugging is messy, editing and rearranging on mobile for bigger flows is cumbersome. but in the end you'll always wonder what you could automate next.




automate at the play store
a daily routine bluetooth handler

no pro required
switches bluetooth state depending on power supply.
turns bluetooth on in the morning and afternoon on workdays for a limited time frame to establish connection e.g. to car. customize to your needs.
checks every 15 minutes if to keep bluetooth enabled.
saves battery life by limiting bluetooth to certain situations only.
consists of 15, hopefully clearly arranged blocks




to flow
a simple car connectivity handler

no pro required
autoplay music on bluetooth connection to car device. saves and reapplies volume before and after connection while using default volume on connection.
if connected to car and being charged car mode will be activated. (manual deactivation though)
sends message to beloved one on returing home in the afternoon. this if connected to bt, within certain time frame and not being near home. accoustic confirmation for sent sms.
music app set to sony currently. set these up, as well as bluetooth device and number of message recipient. consider automatizing bt enabling as well e.g. with 'a daily routine bluetooth handler'.
consists of 13, hopefully clearly arranged blocks




to flow
a simple cell based wifi handler

no pro required
saves battery life by enabling wifi on special occasions.
checks every 15 minutes whether to switch wifi on or off depending on cell tower based location; if not already connected.
displays connection to known locations in status bar.
add/customize more locations/display variables within the flows location block to the right of the main procedure
  • customize home,
  • add work and/or
  • friends to the preceding no-wire

add the display variable and connect the outcome just to true and false.
goto blocks for easier scalability.
consists of 18+, hopefully clearly arranged blocks




to flow
a universal car connectivity handler

pro required. can recommend.
no customization within flow necessary. so best to use if you have to set up electronica for your family during the holidays.
autoplay music on bluetooth connection to car device. saves and reapplies volume before and after connection while using a default volume on connection.
if connected to car and being charged car mode will be activated. (manual deactivation though)
option to send message to beloved one if connecting to bt.
define home, applicable weekdays and timeframe to having the sms sent on returning home only. accoustic confirmation for sent sms. carrier fees may apply.
you will be guided through the setup process. settings will be saved in atomic storage and lost if the flow is changed. on every start of the flow you can decide whether to proceed with, or change the stored settings. on the end of the setup there is a chance of copying the data as json.
there is also an expert setup where a json-object can be inserted directly.
consider automatizing bt enabling as well e.g. with 'a daily routine bluetooth handler'.
consists of 56, hopefully clearly arranged blocks of
  • setup
  • processing values for display
  • connection handling

mildly interesting fact: 77% of the blocks are for the setup. 23% of the blocks perform the task with provided values that could as well be set hard.




to flow
a trainable cell based wifi handler

pro required. can recommend.
no customization within flow necessary. so best to use if you have to set up electronica for your family during the holidays.
saves battery life by automatically enabling wifi at trained locations.
checks in a customizable interval whether to switch wifi on or off depending on cell tower based location; if not already connected.
displays in status bar if a known location is recognized.
if no connection is established albeit being at a known location, wifi turns off and tries again after the interval.
with connection to a wifi network the user can decide to add the location. while being connected all found cell towers will be constantly added to refine precision.
a prior version had a selection for cell towers which was unreliable due to cell towers switching signatures occasionally.
the concept of using cell tower approximation may lead to fuzzy results and depends on signal strength, but is considered more energy efficient than enabling gps. it detects rather villages or districts than streets, let alone addresses. this might lead to unexpected results in rural areas but the flow will still save energy by disabling wifi for the interval without connection.
input timeout might not take effect properly while device is inactive, but responded reasonable on activation during tests. otherwise a decline of request simply restarts loop.
settings are saved in atomic storage as long as the flow is unchanged. interval is 15 minutes by default. be aware that on change of the flow all known locations are gone and have to be reentered on the next visit.
to reset the monitoring interval restart the flow. saved locations will not be affected.
this flow does not have the necessity for editing, providing a guided user input. if you want to edit defaults though, you find dedicated variables declared on the beginning.
consists of 37, hopefully clearly arranged blocks grouped by
  • start with default variables
  • interval reentry and wifi methods
  • storage processin
  • notification display and deletion
  • learning module




to flow