KWGT forgets variables

[420]

After some time (it was 6 days this time) the variables that i passed to KWGT become empty, and it really messes up my widgets big time!

All i could find about this were these 2 questions from 2017;

KWGT "forgets" tasker variables.

I love how KWGT looks, but I'm having a problem where my widget forgets tasker variables really fast. I wonder if there is something I'm doing wrong, or if it is a bug? The whole widget doesn't go blank, just the tasker variables. More specifically, the KWGT widget seems to forget values from...

help.kustom.rocks

Reseted automate variables

I use 2 KWGT widgets, which display 2 different variables from automate (similar to tasker). But when one widget receives a broadcast from automate, it works fine, then they are both reseted to a null value after a few seconds. How does KWGT refreshes variables coming from broadcast?

help.kustom.rocks

I would like to ask if anyone else is having this problem, and if there is anything i can do to prevent this from happening?

I could go and edit my macro's in a way where they periodically re-send the variables, but i'd rather not have to do all that..

 

[Dm114]

After some time (it was 6 days this time) the variables that i passed to KWGT become empty, and it really messes up my widgets big time!

All i could find about this were these 2 questions from 2017;

KWGT "forgets" tasker variables.

I love how KWGT looks, but I'm having a problem where my widget forgets tasker variables really fast. I wonder if there is something I'm doing wrong, or if it is a bug? The whole widget doesn't go blank, just the tasker variables. More specifically, the KWGT widget seems to forget values from...

help.kustom.rocks

Reseted automate variables

I use 2 KWGT widgets, which display 2 different variables from automate (similar to tasker). But when one widget receives a broadcast from automate, it works fine, then they are both reseted to a null value after a few seconds. How does KWGT refreshes variables coming from broadcast?

help.kustom.rocks

I would like to ask if anyone else is having this problem, and if there is anything i can do to prevent this from happening?

I could go and edit my macro's in a way where they periodically re-send the variables, but i'd rather not have to do all that..

I also use KWGT and have no problem passing variables from MD. But I switch off my device every night and boot every morning. So, maybe it's the reason why I don't have any issue...

 

[420]

I also use KWGT and have no problem passing variables from MD. But I switch off my device every night and boot every morning. So, maybe it's the reason why I don't have any issue...

Hmm... thank you for sharing, i tried rebooting and it actually forgot another variable even though that one had been updated only hours before!

My phone has been giving me warnings lately that the memory is getting full, only 1,5GB left, maybe this has something to do with it...?


I've taken a screenshot to show the problem (sorry for my poor drawing skills )

On the second light it should show the % of brightness and the current mode, and on the fan it should also show the current mode under it, and those 2 arrows should be green. (indicating that the swing is on)

 

[Dm114]

Hmm... thank you for sharing, i tried rebooting and it actually forgot another variable even though that one had been updated only hours before!

My phone has been giving me warnings lately that the memory is getting full, only 1,5GB left, maybe this has something to do with it...?


I've taken a screenshot to show the problem (sorry for my poor drawing skills )

On the second light it should show the % of brightness and the current mode, and on the fan it should also show the current mode under it, and those 2 arrows should be green. (indicating that the swing is on)


View attachment 958

For the brightness, I guess you send the value from MD to KWGT via a MD variable.
But for the fan mode, how do you collect the info in MD?

What you could do would be to check (with a pop-up message, for instance) what are the values of these variables when you notice they are not up-to-date in KWGT.

 

[420]

For the brightness, I guess you send the value from MD to KWGT via a MD variable.
But for the fan mode, how do you collect the info in MD?

What you could do would be to check (with a pop-up message, for instance) what are the values of these variables when you notice they are not up-to-date in KWGT.

How i get the fan mode is simply by only controlling it through macrodroid, everytime the macro runs it goes to the next mode. (see the screenshot below)

Yeah one of the posts in those links mentioned that tasker might be sending blank values to KWGT (I think your suggesting that macrodroid might be doing that aswell), but i already opened macrodroid to check the macrodroid variables and they were all correct, so I really don't think this can be macrodroid's fault.. Maybe i should see if i can post on that KWGT forum aswell..

One thing i came up with is changing the formula's for the lights/fan mode in KWGT, so they check if the KWGT variables are empty and can then say "ERROR" or something... Then i can atleast click on it and run the macro to change/update the KWGT variables..

 

[Dm114]

How i get the fan mode is simply by only controlling it through macrodroid, everytime the macro runs it goes to the next mode. (see the screenshot below)

Yeah one of the posts in those links mentioned that tasker might be sending blank values to KWGT (I think your suggesting that macrodroid might be doing that aswell), but i already opened macrodroid to check the macrodroid variables and they were all correct, so I really don't think this can be macrodroid's fault.. Maybe i should see if i can post on that KWGT forum aswell..

One thing i came up with is changing the formula's for the lights/fan mode in KWGT, so they check if the KWGT variables are empty and can then say "ERROR" or something... Then i can atleast click on it and run the macro to change/update the KWGT variables..

I agree with you, I don't think it's MD's fault...

Good luck for investigating!