Situations application feedback

I seem to remember that the location of the systemctl binary was changed some time ago from /bin to /usr/bin. I had to modify sudoers then.

1 Like

It has indeed changed to /usr/bin. That was it.
Thanks, appreciated!

I’ve just started using this application and really like what it can do, so thanks for that! :blush:

Though I do have a question as well: Is (already?) possible to trigger a When event at startup? I’d like to automatically start certain applications on boot, and haven’t yet found a way to do that completely automatically!
At the moment I have a “When” → DND to launch applications, which is a nice workaround, but fully automated would be neater of course.

Thanks for the feedback!

I Wonder If this works for you: do not have any condition in the situation that is supposed to run in startup. Instead, make it manual and activated by hand. I.e. swipe left and swipe right on the main list. You should see a red stop-sign on the right (manual) and yellow play-sign on left (activated).

Of course it will run the actions first time. But should activate also in the future in startup if Situations is autostarted.

“Downside” is that the situation is then always active…

3 Likes

You can fully automize, make a situation with when based on time for 24h full hours. Then use that situation for when and for what just start your apps. This is what I do and it works, it will only start apps on boot.

1 Like

That works and solves my issue, so easy I just didn’t think it would work as a trigger! :sweat_smile:
Thanks a lot! :hugs:

Is there any way to enable hotspot when the phone is connected via Bluetooth to a specific device ? I want to be able to open hotspot when connected with my car Bluetooth device

Hi, and apologies for the slow reply.

With BT scanning condition (pro-version), it should be possible to set scanning method to “active connection” and select your car bluetooth. And then add hotspot action to that situation.

But I haven’t tested it for a long time and apparently Situations is not really working with the latest SF OS (I hear). I’ve focused on getting Android version running on top of latest Qt and recent enough Android SDK. Will jump back to Sailfish also at some point, but not yet…

7 Likes

It work like a charm ! Amazing job on the app . I ve also setup Nightish to start during night hours and terminate in the morning via the command feature. Its a tasker alternative in sailfishos but friendlier abd simplier. Sailfishos 5 works. I will be donating

1 Like

Situations indeed seems to work with SFOS 5. The only thing I could not set up so far is commands to stop and start Android AppSupport (such as ‘systemctl start apkd.service’). It is likely related to missing privilege inside situations. I thought that the daemon that we install upon the installation of Situations would be enough to get the right to launch commands as root?

1 Like

Ok, thanks. So perhaps it was some other issue with SFOS 5 then.

Sorry, I have no help to starting/stopping that Android AppSupport. The separately installed background service should indeed have enough privileges to do that though. The best that I can remember now is closing individual applications with command something like “sudo appsupport-attach am force-stop [androidapllication]”.

3 Likes