Ok, please try again with the packages here.
For a long press you need to hit the play button. But it should take only about 1 sec and timer screen should open up. “Works at least for me ;)”
Anyway, I was hasty so put the current version to Harbour review (which however might take months) just moments ago.
So any further fixes will come there later…
1 Like
No change. I still get error. 
I first tapped play button to activate situation and after that hold stop button to set timer, but no matter how long I hold, I don’t get timer.
Ok, thanks! In Harbour there is actually this sort of field:
Detected OS versions compatibility
5.1.0.*
So it might play a role…
1 Like
I noticed using both the Jolla store and release 325 versiona an issue when using ‘bluetooth devices’ as a when condition.
I used the search button but it always says ‘turn on bluetooth’ (‘activer bluetooth’ in French) while bluetooth is already on.
A workaround was to enter device name amd address manually. Then it works as expected.
(this is for JP2 on latest 5.2)
Thanks
Thanks. That happens likely because you have AppSupport Bluetooth installed(?). I haven’t yet checked if or what is possible to do about it. But will.
In my case that is correct.
No I did not activate the bluetooth in Android app support
By “activating” you mean what? Installing it is enough to break it.
I think it is available by default in SFOS 5.2 as I never installed it
Ahh, ok. That explains. But yeah, unfortunately that currently breaks the “old” dbus interface somehow. I will have a look at it at some point.
1 Like
Would it be possible to get function “Location” not only as “When”, but also as “What”, to be able to enable or disable location service? Or is this function somewhere?
Sorry, I don’t currently know how to do it. There is officially some MDM-api, but using it is probably out of question as it requires the app to be installed as MDM app.
Brilliant app. I might miss the previous discussion but I wonder if it is possible to 1. terminate the app when the the situation is activated/deactivated and 2. a situation is triggered when any wifi connection is lost instead of connected to certain wifi ?
1 Like
Currently that is possible only with a custom command - i.e. add a Command action, add a command to stop the application there, and select “At situation end” if you want that to happen at situation end. I suppose there’s no “reliable” way to do this on Sailfish UI similar to launching an app.
I wonder if this works as intended: As a condition select WiFi Networks (pro version), as a method select “Any connection” and accept it. So the condition is active on any connection. Then on the situation page tap the WiFI Networks icon to invert the condition, i,e, make it active when there’s no any connection.
1 Like
I use this app for scheduled ambiances for different work scenarios and silencing during night. I’m curious is gyroscope data accessible? For building automatic silencing, then on a flat desk. (Perhaps this would need the proximity sensor input too for a second oppinion)
I’ve been thinking about the idea of using device orientation as a condition - but haven’t yet come to any conclusion. Would a simple “face up/down” be ok for most of the cases - or does it need to be more controllable? Otherwise I suppose it should be doable. Will think about it again…
2 Likes
Hey,
Updated app available at Release Alpha release 326 · pastillilabs/packages · GitHub .
The main thing is added support for startup actions. They can happen either on any start of the background process. Or once after any boot.
Also fixed some actions when run with non-root background process. And increased plugin instance maximum amounts to 20 (from 10). Along with other small(ish) improvements…
Edit: Of course found some issues, so updated the packages already once.
4 Likes
Thanks for your tip. Unfortunately “any connection” rule does not work well. It doesn’t trigger any actions when the phone connected to wifi networks.
It was actually triggering if any wifi network is found at all - not just connected. I changed that now, so perhaps it works better now? Please test with the latest package.
Not sure if there should also still be an option to also trigger if any network is found. Anyone here using that?