How to set up correctly?

Paltoos

Member
Hello. I am trying to use this application to set up switching of sound profiles by events. Created several macros. Two are triggered when the charger is turned on / off, two when connected / disconnected to Wi Fi, and one should fire at the time and days of the week. Basically, there are problems with him. How to do it right? Thanks in advance.Screenshot_20211103-102516[1].pngScreenshot_20211103-102552[1].pngScreenshot_20211103-102607[1].pngScreenshot_20211103-102631[1].pngScreenshot_20211103-102653[1].pngScreenshot_20211103-102716[1].pngScreenshot_20211103-102735[1].png
 

tanutanu

Well-known member
You misunderstood what cancel action means. The cancel means just stopping the macro itself, not means suspending another macro execution. Use enable/disable macro action instead.
These two macros are still called as macro run action. Once macros are called, they would be running until next wait action. All your macros are simple, have no wait action, so finished everything.
 

tanutanu

Well-known member
And this is also not natural. First, if you want to limit something when your 2 apps are foreground, put the statements into the if/endif block like a sandwich.
Second, after volume changed on the 1st statement, you set vibration enable or disable next. I'm not sure your conditions because I can't read Greek? Russian? words, but it might cause your volume changed to zero once(but the level value is holding internally at this moment). Next, the value should be set to zero and the internal value cleared.
These volume controls very depend on your settings on OS settings app and OS customization by the device manufacturer, so check them on step by step test first before running through.
 

Paltoos

Member
You misunderstood what cancel action means. The cancel means just stopping the macro itself, not means suspending another macro execution. Use enable/disable macro action instead.
These two macros are still called as macro run action. Once macros are called, they would be running until next wait action. All your macros are simple, have no wait action, so finished everything.
That is, in the Weekend mode, you need to do it like this, right?
 

Attachments

  • Screenshot_20211103-182002[1].png
    Screenshot_20211103-182002[1].png
    176.5 KB · Views: 9

Paltoos

Member
And this is also not natural. First, if you want to limit something when your 2 apps are foreground, put the statements into the if/endif block like a sandwich.
Second, after volume changed on the 1st statement, you set vibration enable or disable next. I'm not sure your conditions because I can't read Greek? Russian? words, but it might cause your volume changed to zero once(but the level value is holding internally at this moment). Next, the value should be set to zero and the internal value cleared.
These volume controls very depend on your settings on OS settings app and OS customization by the device manufacturer, so check them on step by step test first before running through.
Well, in this macro, Vibration is not so important to me. Set up for trial. The rest is not quite understood :) And if you write down the necessary steps for me step by step, I will be very grateful. Since translating action names is easier than our Google dialogue ...
 

tanutanu

Well-known member
That is, in the Weekend mode, you need to do it like this, right?
I talked about these 2 cancel actions. You seems to be stopping 2 other macros, but they should be run if not running at the moment it called.
The macro A is running whenever it detect Wifi AP and macro B is running whenever the device is disconnected in business days. When the initiator macro is called 10am in holidays, it should cancel both A and B executions if both are running eventually.
However, I guess these Wifi range in/out events does NOT occur on just 10am when it runs while you are at your home or office. so it is meaningless.
If you want to make sure A and B macros does NOT run whole the day, you have to use disable action instead. And also you need to use enable action when you want to restart.
 

Attachments

  • Screenshot_20211103-102552[1]~2.png
    Screenshot_20211103-102552[1]~2.png
    200.6 KB · Views: 5
Last edited:

tanutanu

Well-known member
Well, in this macro, Vibration is not so important to me. Set up for trial. The rest is not quite understood :) And if you write down the necessary steps for me step by step, I will be very grateful. Since translating action names is easier than our Google dialogue ...
Sorry, it is impossible because these complexed macros didn't crystal clearly figure out what you really want to do, each macro action behavior is not difficult, very simple though.
Before cleaning up the macros, would you write down all thing how you want to do as below example:

when: 10am at business day
what: set device volume 50

You don't need to split what you want to do in the same manner of your macros, simply write them one by one.
These too many exceptions seem to present the complex in your brain, not in the macro codes.

Please mind that reading macro in Greek? Russian? is painful for me, so please make it in English next time. You can change it in MD settings section. Some guys tend to shere it as .macro exported file, but it is annoying as well. A screenshots like you is better:) but use long screenshot next time. It is easy to take a picture with "share as image" in the upper right corner ... menu.
 
Last edited:

Paltoos

Member
Sorry, it is impossible because these complexed macros didn't crystal clearly figure out what you really want to do, each macro action behavior is not difficult, very simple though.
Before cleaning up the macros, would you write down all thing how you want to do as below example:

when: 10am at business day
what: set device volume 50

You don't need to split what you want to do in the same manner of your macros, simply write them one by one.
These too many exceptions seem to present the complex in your brain, not in the macro codes.

Please mind that reading macro in Greek? Russian? is painful for me, so please make it in English next time. You can change it in MD settings section. Some guys tend to shere it as .macro exported file, but it is annoying as well. A screenshots like you is better:) but use long screenshot next time. It is easy to take a picture with "share as image" in the upper right corner ... menu.
Good afternoon. That's better?
Now I will try to paint:
1. Macro Turn on charging
The USB charger is connected
Possibly low sound signals are set (with the addition of volume exceptions for certain phone numbers, ideally vibration signals)
2. Macro Turn off charting
The charger is disconnected
Sounds are set to medium volume, similar to the Houses macro (with the addition of volume exceptions for specific application alarms, with maximum volume and vibration).
3. Macro Outside
Fires when a particular router is disconnected from the signal. Signals of maximum volume with vibro are set. There are no exceptions.
4. Houses macro
Fires when connected to a signal from a specific router. Medium volume beeps are set with the addition of volume exceptions for specific application alarms, with maximum volume and vibration. Do not disturb mode is activated.
5. Macro Weekend
It works at the appointed time and on the designated days of the week. Turns off when it finishes Displays medium volume tones similar to the Houses macro, with the addition of volume exceptions for specific alarms, with maximum volume and vibrations. Do not disturb mode is activated.
While trying to test the free version. If I can handle it, I'll go full.
 

Attachments

  • Screenshot_20211103-182002.png
    Screenshot_20211103-182002.png
    176.5 KB · Views: 3
  • Screenshot_20211104-165441.png
    Screenshot_20211104-165441.png
    125.6 KB · Views: 3
  • Screenshot_20211104-165454.png
    Screenshot_20211104-165454.png
    117.3 KB · Views: 4
  • Screenshot_20211104-165530.png
    Screenshot_20211104-165530.png
    185.4 KB · Views: 5
  • Screenshot_20211104-165545.png
    Screenshot_20211104-165545.png
    141.4 KB · Views: 4
  • Screenshot_20211104-165609.png
    Screenshot_20211104-165609.png
    177.9 KB · Views: 3
  • Screenshot_20211104-165622.png
    Screenshot_20211104-165622.png
    197.2 KB · Views: 4

tanutanu

Well-known member
Good afternoon. That's better?
Now I will try to paint:
1. Macro Turn on charging
The USB charger is connected
Possibly low sound signals are set (with the addition of volume exceptions for certain phone numbers, ideally vibration signals)
2. Macro Turn off charting
The charger is disconnected
Sounds are set to medium volume, similar to the Houses macro (with the addition of volume exceptions for specific application alarms, with maximum volume and vibration).
3. Macro Outside
Fires when a particular router is disconnected from the signal. Signals of maximum volume with vibro are set. There are no exceptions.
4. Houses macro
Fires when connected to a signal from a specific router. Medium volume beeps are set with the addition of volume exceptions for specific application alarms, with maximum volume and vibration. Do not disturb mode is activated.
5. Macro Weekend
It works at the appointed time and on the designated days of the week. Turns off when it finishes Displays medium volume tones similar to the Houses macro, with the addition of volume exceptions for specific alarms, with maximum volume and vibrations. Do not disturb mode is activated.
While trying to test the free version. If I can handle it, I'll go full.
They seem to be clean them up more:)

In weekend, the "Weekends" macro fire only when it's 10am on Saturday and Sunday. So the constraint for 5 business day is meaningless and conflit against the trigger. It never fire, so you have to delete the constraint.
Constraints mean the allowance of macro execution, NOT denial conditions.

The if/else statements are still meaningless on the bottom of the "Houses." Delete it if you don't need.
If you want to add something another, it's ok. If you want to change the device volume only when the 2 apps on foreground, you have to put them into the if code block like a sandwich or hamburger.
Screenshot_20211104-234410~2.png

You should stop unlimited jumping like Run macro actions once until you understand well. The "turn off charging" macro calls "Houses" and "Weekends." However, the "Weekends" macro calls "Houses" as well. Changing the volume level twice doesn't cause bad result but meaningless.
One important thing is that you mixed everything like "Spaghetti." It's just a wild guess. Therefore you have many exceptions what you surely need or not.
 

tanutanu

Well-known member
Good afternoon. That's better?
Now I will try to paint:
1. Macro Turn on charging
The USB charger is connected
Possibly low sound signals are set (with the addition of volume exceptions for certain phone numbers, ideally vibration signals)
2. Macro Turn off charting
The charger is disconnected
Sounds are set to medium volume, similar to the Houses macro (with the addition of volume exceptions for specific application alarms, with maximum volume and vibration).
3. Macro Outside
Fires when a particular router is disconnected from the signal. Signals of maximum volume with vibro are set. There are no exceptions.
4. Houses macro
Fires when connected to a signal from a specific router. Medium volume beeps are set with the addition of volume exceptions for specific application alarms, with maximum volume and vibration. Do not disturb mode is activated.
5. Macro Weekend
It works at the appointed time and on the designated days of the week. Turns off when it finishes Displays medium volume tones similar to the Houses macro, with the addition of volume exceptions for specific alarms, with maximum volume and vibrations. Do not disturb mode is activated.
While trying to test the free version. If I can handle it, I'll go full.
First, let's split 2 different conditions before talking about exceptions.

1. Connecti to outlet/Disconnect from outlet
2. You are out/in the range of the Wifi.

And reduce your macros to manage them simply like this.
 

Attachments

  • Screenshot_20211105-004424~2.png
    Screenshot_20211105-004424~2.png
    102.4 KB · Views: 5
  • Screenshot_20211105-004206~2.png
    Screenshot_20211105-004206~2.png
    126.7 KB · Views: 5

Paltoos

Member
First, let's split 2 different conditions before talking about exceptions.

1. Connecti to outlet/Disconnect from outlet
2. You are out/in the range of the Wifi.

And reduce your macros to manage them simply like this.
That is, these two actions (enable / disable) can be combined into one macro? I understand correctly?
And then, what does this expression mean - "you have to put them into the if code block like a sandwich or hamburger"?)))
 

tanutanu

Well-known member
That is, these two actions (enable / disable) can be combined into one macro? I understand correctly?
And then, what does this expression mean - "you have to put them into the if code block like a sandwich or hamburger"?)))
Yep, you can.
I explained on the comments #9 and #10. Please refer the attached images and compare them to your macros.
After you got them, continue to talk about exceptions:)
 

Paltoos

Member
Yep, you can.
I explained on the comments #9 and #10. Please refer the attached images and compare them to your macros.
After you got them, continue to talk about exceptions:)
Ok, thanks a lot!
Today I will try to "digest" the information received. And tomorrow, if you have any questions, I will contact you again. OK? :)
 

tanutanu

Well-known member
Ok, thanks a lot!
Today I will try to "digest" the information received. And tomorrow, if you have any questions, I will contact you again. OK? :)
Sure:)
I don't think you are fun if I did everything. You are interested in building your own macros though. And English is not first language for bith, you and me. I afraid not only your mislead but also my misunderstanding due to language and/or difference of cultures.
So, it's better to do step by step:)
 

Paltoos

Member
Sure:)
I don't think you are fun if I did everything. You are interested in building your own macros though. And English is not first language for bith, you and me. I afraid not only your mislead but also my misunderstanding due to language and/or difference of cultures.
So, it's better to do step by step:)
I completely agree with your words! But, even with all the difficulties, it became much easier for me to use the application. And for this, thank you very much!
Although, of course, there is still a lot of incomprehensible ... :(
 

Paltoos

Member
Sure:)
I don't think you are fun if I did everything. You are interested in building your own macros though. And English is not first language for bith, you and me. I afraid not only your mislead but also my misunderstanding due to language and/or difference of cultures.
So, it's better to do step by step:)
During this time, I made the settings that you recommended. In general, everything works, but several questions arose:
1. Since the sound settings of the Off charging and Houses macros are almost the same, can it be configured so that the Houses macro is turned on immediately after charging is complete?
2. I did not find how to add phone numbers and applications to the exceptions of the macro settings in order to set sound and vibration modes for them ...
3. Since I have a free macro, I decided to add the Missed call macro (I attach a screenshot). How to make it possible to repeat the signal, for example, after 1 minute within 1 hour?
I don't touch on the Weekends macro yet, I hope the time will come to it ... :)
P / S I apologize in advance, but the application for some reason does not fully translate all the settings, even when switching languages ...
 

Attachments

  • Screenshot_20211105-111145.png
    Screenshot_20211105-111145.png
    147.5 KB · Views: 8

tanutanu

Well-known member
During this time, I made the settings that you recommended. In general, everything works, but several questions arose:
1. Since the sound settings of the Off charging and Houses macros are almost the same, can it be configured so that the Houses macro is turned on immediately after charging is complete?
If almost same, the moment when the Trigger fire is different. So, set the volume on each timing once. Probably you feel same actions should be unified. That's right, but not prior than jumping. It tend to cause unexpected errors. Once everything is working correctly, you can do refactoring later days.
One important thing is that all macros fire just when the trigger condition is satisfied. So, "power disconnected" means just getting it off from a outlet, doesn't mean when your device is 100% charged. MD has another trigger named "battery level." It contains option to check the current battery left while increasing.

2. I did not find how to add phone numbers and applications to the exceptions of the macro settings in order to set sound and vibration modes for them ...
OK, let's talk about the exception.
You want to change the ringger volume when you get a call from your family members. It also means you need to turn the macro back to normal condition on weekends. It doesn't be back by itself.
MD has two options for you. One is checking notifications, the other is checking call itself. "call incoming" trigger can set one or more specific caller id in the options of it. make sure you assigned the access permission of your contacts to MD.

3. Since I have a free macro, I decided to add the Missed call macro (I attach a screenshot). How to make it possible to repeat the signal, for example, after 1 minute within 1 hour?

I don't touch on the Weekends macro yet, I hope the time will come to it ... :)
You can do it with stopwatch feature. On the bottom of the macro, set a stopwatch to work every minutes until an hour later and add a trigger like this.
IMG_20211105_224157.jpg
I added 1 trigger, 2 action statements and 1 variable. The top one memorizes the timestamp when you missed a call in the variable as numeric. The integer value presents a date time as another format. The bottom one starts the stopwatch. It needs to pre-define with your preferred unique name in advance.
When 1 minute passed, the stopwatch trigger should be called and ring again. After 1 hour passed the last statement matches the constraint condition, so is no longer executed. The constraint compares the time when you missed and the time when the macro called by the stopwatch trigger. when the current time - 60 x 60 (it's seconds, so means 3600 seconds equal to 1 hour) is greater than the time you missed, the difference testing returns false value.
You might need another trigger to stop the reminder ringing when you noticed like tapping a notification.

P / S I apologize in advance, but the application for some reason does not fully translate all the settings, even when switching languages ...
Don't worry:) It sometimes happens, is well known bug. You set your language setting back once and change it again to fix it briefly.
 
Last edited:

Paltoos

Member
If almost same, the moment when the Trigger fire is different. So, set the volume on each timing once. Probably you feel same actions should be unified. That's right, but not prior than jumping. It tend to cause unexpected errors. Once everything is working correctly, you can do refactoring later days.
One important thing is that all macros fire just when the trigger condition is satisfied. So, "power disconnected" means just getting it off from a outlet, doesn't mean when your device is 100% charged. MD has another trigger named "battery level." It contains option to check the current battery left while increasing.


OK, let's talk about the exception.
You want to change the ringger volume when you get a call from your family members. It also means you need to turn the macro back to normal condition on weekends. It doesn't be back by itself.
MD has two options for you. One is checking notifications, the other is checking call itself. "call incoming" trigger can set one or more specific caller id in the options of it. make sure you assigned the access permission of your contacts to MD.


You can do it with stopwatch feature. On the bottom of the macro, set a stopwatch to work every minutes until an hour later and add a trigger like this.
View attachment 1443
I added 1 trigger, 2 action statements and 1 variable. The top one memorizes the timestamp when you missed a call in the variable as numeric. The integer value presents a date time as another format. The bottom one starts the stopwatch. It needs to pre-define with your preferred unique name in advance.
When 1 minute passed, the stopwatch trigger should be called and ring again. After 1 hour passed the last statement matches the constraint condition, so is no longer executed. The constraint compares the time when you missed and the time when the macro called by the stopwatch trigger. when the current time - 60 x 60 (it's seconds, so means 3600 seconds equal to 1 hour) is greater than the time you missed, the difference testing returns false value.
You might need another trigger to stop the reminder ringing when you noticed like tapping a notification.


Don't worry:) It sometimes happens, is well known bug. You set your language setting back once and change it again to fix it briefly.
Thank you, I will deal with the information.
Regarding point 2 - I understand that you need to set a call trigger to exclude calls, and a notification trigger to exclude application signals? Or are there triggers specifically for applications?
 

tanutanu

Well-known member
Thank you, I will deal with the information.
Regarding point 2 - I understand that you need to set a call trigger to exclude calls, and a notification trigger to exclude application signals? Or are there triggers specifically for applications?
This is my post on another thread for a guy who want to reject most of calls including specific area codes but accept some of them.
Post in thread 'Blocking whole area codes of numbers except one or two'

It is similar to you, showcasing how to branch the macro process. Basically the macro accepts any call on the trigger condition. Next, going to actions, the macro gets the caller id at first.
Then checking the caller id on the if statement, quits the macro to accept the calls from white listed people. And on elseif clause, it tests matching a specific condition, i.e. area codes.
In your case, for the white listed your family members, you increase the device ringger volume, otherwise keep muted. You have to set the volume muted again even when the volume is still muted for the case the volume increased previously. The difference is only what should be done, the macro flow control logic is the same thing.

EDITED: Please remember that all MD behaviors are event basis, not mean keep on doing something. It means each macro instance has NO relation with what happened previously. You have to check current states in most cases. The reliability of the state value you memorized in a variable depends on how and when you put it on.

correctd few typos
 
Last edited:

Paltoos

Member
This is my post on another thread for a guy who want to reject most of calls including specific area codes but accept some of them.
Post in thread 'Blocking whole area codes of numbers except one or two'

It is similar to you, showcasing how to branch the macro process. Basically the macro accepts any call on the trigger condition. Next, going to actions, the macro gets the caller id at first.
Then checking the caller id on the if statement, quits the macro to accept the calls from while listed people. And on elseif clause, it tests matching a specific condition, i.e. area codes.
In your case, for the while listed your family members, you increase the device ringger volume, otherwise keep muted. You have to set the volume muted when the volume is still muted for the case the volume increased previously. The difference is only what should be done, the macro flow control logic is the same thing.

Please remember that all MD behaviors are event basis, not mean keep on doing something.
Thanks. This is a lot of information for me. It takes time to digest it. :)
 
Top