Foldersync doesn't run

[AnotherTraumaticEvent]

I am using the Folderysnc plugin as an action to try and get any or all of my folderpairs to sync but it isn't working. Trying test action does nothing where I am expecting it to sync the chosen folderpairs.

I have had Foldersync installed for many years and it works fine, both manually as well as on a schedule that I run through Automate every night.

I have Automation enabled in Foldersync settings and I also tried to copy the deeplink into Macrodroid instead of using the plugin from Macrodroid menu. Doesn't make a difference.

What am I missing?

 

[Josué García]

I am using the Folderysnc plugin as an action to try and get any or all of my folderpairs to sync but it isn't working. Trying test action does nothing where I am expecting it to sync the chosen folderpairs.

I have had Foldersync installed for many years and it works fine, both manually as well as on a schedule that I run through Automate every night.

I have Automation enabled in Foldersync settings and I also tried to copy the deeplink into Macrodroid instead of using the plugin from Macrodroid menu. Doesn't make a difference.

What am I missing?

I tried the free and pro version and as a plugin it worked well for me.

Have you checked to see if your sync folders have not been misconfigured or you lost access?

Deep links don't seem to work, they always give a 404 error...

 

[AnotherTraumaticEvent]

My sync folders work fine. If I sync them from Foldersync itself they sync like they should. What do you mean by 404 error? I get no response at all. Nothing happens as far as I can see.

 

[AnotherTraumaticEvent]

Okay, well, I may have figured it out. Apparently something weird was going on where Foldersync somehow didn't accept my wifi connection as being established, even though it was. Turning wifi off and on fixed it. So the problem is not with Macrodroid. I honestly have no idea what happened.

Only thing I can think of is this: the macro I made triggers when I am in my home location, then waits when I connect to my wifi network and then starts the sync. Maybe the sync being launched immediately after my network was found resulted in the error? I don't know, i've added 1 minute of waiting time now.

 

[Josué García]

Okay, well, I may have figured it out. Apparently something weird was going on where Foldersync somehow didn't accept my wifi connection as being established, even though it was. Turning wifi off and on fixed it. So the problem is not with Macrodroid. I honestly have no idea what happened.

You probably have location permission set to "Allow only when the app is in use"
If you have the permission that way, change it so that it is allowed all the time

 

[AnotherTraumaticEvent]

That's not it. Macrodroid has permission to access location all the time and Foldersync doesn't need to have access to location.

 

[Endercraft]

That's not it. Macrodroid has permission to access location all the time and Foldersync doesn't need to have access to location.

Location and Wi-Fi are linked. For apps to check Wi-Fi state location services must be on and permission granted for the apps. Why can you check the state yourself when location is disabled though? Because location isn't actually needed. It's just yet another Google meaningless restriction.

 

[AnotherTraumaticEvent]

Location and Wi-Fi are linked. For apps to check Wi-Fi state location services must be on and permission granted for the apps. Why can you check the state yourself when location is disabled though? Because location isn't actually needed. It's just yet another Google meaningless restriction.

I'm afraid I don't follow this.

Folderysnc works fine with location off even though I have set it to only sync when wifi is present. My setup until now was to have it sync everything every night a 4am run from an Automate flow.

 

[Endercraft]

Apparently something weird was going on where Foldersync somehow didn't accept my wifi connection as being established, even though it was

That could be the reason.

 

[dhj49er]

I'm afraid I don't follow this.

Folderysnc works fine with location off even though I have set it to only sync when wifi is present. My setup until now was to have it sync everything every night a 4am run from an Automate flow.

I use Foldersync to backup folders to my NAS using macros.

I only do this at home connected to my WiFi.

I use all those conditions as constraints in the macro.

The macro is scheduled to run once overnight.

In Foldersync I turn off the WiFi checking (as the macro does it) and auto sync (use scheduled macro instead).

I've attached a screenshot of my macro, so you can see how I do it.

 

[AnotherTraumaticEvent]

Thank you, I will take a look at that next. Going to check first if my original macro works now with the extra minute but I haven't left my home in the last 2 days. Having Macrodroid do the wifi check and Foldersync not makes sense.

Although that begs the question: what if the wifi dies a second after Macrodroid told Foldersync to sync?

 

[dhj49er]

Thank you, I will take a look at that next. Going to check first if my original macro works now with the extra minute but I haven't left my home in the last 2 days. Having Macrodroid do the wifi check and Foldersync not makes sense.

Although that begs the question: what if the wifi dies a second after Macrodroid told Foldersync to sync?

Foldersync will fail to sync reporting error.
I find Foldersync to be quite robust & it generally does what you expect when it encounters errors.

 

[AnotherTraumaticEvent]

Then I don't understand. If you have Foldersync set to not check for wifi doesn't that mean that it will sync over any kind of connection available once it is told to sync?

 

[dhj49er]

Yes, you are right but I use the following setup to allow the macro control running the folderpairs.

In Foldersync I use connection type WiFi for the folderpairs in the macro.

I disable get location in the background - this is only required if you want to specify a SSID in the folderpairs.

I turn off auto sync, as I want the macro to control when the folderpairs are run.

I hope that's clear!

 

[AnotherTraumaticEvent]

That is basically what I already do. I also have my folderpairs set to wifi sync only. But doesn't that make your Macrodroid constraint that checks for wifi redundant then?

 

[dhj49er]

Not redundant.

This macro backups folders to my NAS.

So being at Home connected to my WiFi and the NAS is on are all the conditions required to access the NAS.

You could suggest it could be redundant for that, but I prefer that all the conditions are met and not just 1 or 2 for accessing my NAS.

 

[AnotherTraumaticEvent]

So, Macrodroid checks for wifi and then after that Foldersync checks for wifi. So, unless the wifi fails directly after Macrodroid has checked for it while Foldersunc hasn't finished syncing it would be redundant, right? Or am I missing something? That's the failcase situation I was talking about earlier. What I don't understand really is this statement by you:

In Foldersync I turn off the WiFi checking

Because that seems contrary to the fact that you have Folderysnc pairs set up to sync only on wifi. Doesn't that make Foldersync do exactly what you say turned off; checking the wifi?

 

[dhj49er]

I think you are confusing checking WiFi with using WiFi as a connection type.

When Foldersync permission location in the background, it does not check for WiFi.

In folderpairs a connection type or types need to be specified. Here is where I select WiFi.

When a folderpairs runs with just WiFi connection type selected, it will terminate with an error if there is no WiFi connection and run with a WiFi connection. No checking.

 

[AnotherTraumaticEvent]

I am not trying to be obtuse! Just to be sure, I just don't honestly understand. When you say:

it will terminate with an error if there is no WiFi connection and run with a WiFi connection

and

No checking

Then how does Foldersync know which of the two things to do? If it does not check for wifi how does it know it needs to either run or terminate?

 

[dhj49er]

Then how does Foldersync know which of the two things to do? If it does not check for wifi how does it know it needs to either run or terminate?

It knows by running the folderpairs.

Let's say the connection times out because WiFi is not connected. This is an error and will terminate running the folderpairs.

Let's say the connection doesn't time out as WiFi is connected. This will allow the folderpairs to run to completion.

I don't think I can explain it any better.

If it's still not clear, I can't help you any further.