Recent content by dhj49er

I'm not able to provide answers to your questions, as I don't know how MD has implemented this feature. However, i can provide an insight to how I use Geofences and I have very good battery life. Like you I have many Geofences including a few abroad (I live in the UK) but only have 1 or 2 active...

Unfortunately I won't be able to edit your macro. It can only be done on your phone. I suggest doing it steps. Add the read screen contents action to the loop. Doing this will create a dictionay variable. Run the macro - with an initial login failure the endless loop will run, populating the...

To break the endless loop try using read screen content in the loop. Find the key that holds login text. When this key value changes use as constraint for the break loop action.

Have you tried including break loop action in your endless loop with a trigger as a constraint? Do you have a suitable trigger? Needs to be when the login text disappears. Hence my original question how do you detect the disappearing text?

When a trigger fires the macro runs from the start. So if the actions at the start of the macro are not constrained they will run every time any of the triggers fire. Is it possible to provide a screenshot or your macro?

How are you determining when the specific screen content disappears?

On the latest versions of Android you can select a trusted device to unlock the phone. I thought I would share how I use this feature to automate unlocking the phone, as it might be of interest to other users. Google has named this feature Extend Unlock. You will need to go to Settings...

Yes...the merged macro has 2 triggers, but there is only 1 event. MD will run the macro on the first match of the event to the triggers. There is no 2nd event to trigger the macro again. That's my understanding on how MD works.

I wouldn't expect your merged macro to run twice, as that would require 2 triggers and there is only 1. However, the 2 macros, albeit with slightly different triggers, will each run on when the headset connects. The event is the trigger for each macro.

Are your other macros working on the Xiaomi? Is the TAPO app generating the notification on the Xiaomi?

Wow ....i wasnt expecting to see the date added to system log entries. Unfortunately, it takes up a lot of the line and to me is of no benefit. I couldnt find a way to disable showing the date. Would it be possible to add the show date as an option in the same way and place of show...

I use autonotifications for this type of action. It's a paid app but worth it, as once set you won't see that notification again.

I've updated my macro and attached a screenshot. By adding the screen on constraint means the macro will only run once providing it turns off the screen (which it does). Manually turning off the screen will prevent the macro running. Whilst this macro doesn't do the hourly check it will switch...

It's 12am not 12pm. The screenshot is a macro that should turn off the screen when the battery drop to below 30%.

Just to make sure I have the correct understanding. At 12pm the screen is on and stays on until the sleep macro turns it off when the battery level is <30. Is that correct? If so, the screen could be on for hours, consuming lots of battery. I'm sorry, but it doesn't seem to make sense.