Errors after updating to MQTTController build 25139

[cw-kid]

It appeared to evaluate as it flashed green, Value is null however.

This is what is in the "RouterMemoryResponse"

Last value: (string) " total used free shared buffers cached\nMem: 426020 330068 95952 3488 0 37716\n-/+ buffers/cache: 292352 133668\nSwap: 0 0 0\n"

[toggledbits]

OK. Try changing all of the spaces to \\s* like this:

match( RouterMemoryResponse, "Mem:\\s*(\\d+)\\s*(\\d+)\\s*(\\d+)", 3 )

[cw-kid]

@toggledbits That seems to work.

[toggledbits]

OK. So your router must be returning some space-looking character that isn't space in the string somewhere. That's fine... the \\s means match anything that looks like a space. That's your path forward.

[cw-kid]

Great thanks. I just need to know how to use a Global Expression in my rule now?

As using a value like ${{ RouterMemoryFree }} only seems to work if the expression is a local expression within the rule.

[cw-kid]

The Global Expressions look like this now. I have the used and free memory values OK.

[cw-kid]

Seems I can just do them as Local Expressions after all instead of Global ones.

[toggledbits]

If you are only going to push them out in the same Reaction to other places, that's fine. You don't be able to use them in conditions, though.

[cw-kid]

Yes that's right, info only

The routers CPU temp and WIFI chip temps however I am using those in another rules trigger to warn me if its getting hot. so those had to be Global Expressions.

[toggledbits]

Oh... wait though... rule-based expressions evaluate a bit differently from global.

As global expressions, when "Response" changes, it triggers an immediate update/re-evaluation of Free and Used, as was happening in our troubleshooting.

When you move them to rule-based however, expressions in rules are only evaluated when the rule's trigger conditions are checked. That means the interval will cause Response to get fetched and updated, but Free and Used as local variables will not be updated immediately after... they will not update until the next time the interval triggers an evaluation of the rule, so each response will not have its new values posted until the interval period lapses. Do you understand what I'm on about here? I think you should be able to observe this behavior in the rule status.

[cw-kid]

Yes I understand what you just said.

But back to my other question then, is it possible to use a Global Expression value in a rules action with a value like ${{ RouterMemoryFree }} but for the Global Expression rather than any local one.

[toggledbits]

Sure, use it just like you've shown. As long as there is not a local variable with the same name, it will find/choose the global variable.

[cw-kid]

OK cool I didn't know you could do that and it was that simple !

[toggledbits]

Also FYI, I fixed the initialization so a function like match() returning a null initial result won't leave the "not yet evaluated" message stuck in the display, even though it has actually been evaluated. Next build.

[cw-kid]

I am confused now. I deleted the local expressions in the rule. I then created the global ones again. When I run the actions of the rule e.g. run the shell command and populate the "RouterMemoryResponse" Global expression that works OK.

However the other two global expressions were not automatically evaluated.

I pressed the play button on one and that is why that one has a value now. but the other one does not have a value.

Running the rules actions again and its the same.

Looking in a test trigger in a rule the value is null for "RouterMemoryUsed".

So I am still not convinced these global expressions are auto evaluating.

EDIT: Ignore this I forgot to restart MSR, seems I have to do that first ?

Now when I run the rules actions all three Global Expressions flash green.

[toggledbits]

@cw-kid said in Is this possible? Store data from Asus Router ajax .asp page for Temperature data.:

EDIT: Ignore this I forgot to restart MSR, seems I have to do that first ?

Yes, this is a current limitation. I'm trying to invent a way to fix this elegantly. The expression parser is a separate module that doesn't have quite enough smarts for the way MSR needs to use it, so MSR needs one pass over the variables to figure out what the dependencies are (the expression parser can't tell it up front). It's on my list.

[cw-kid]

@toggledbits OK great. I think I have everything setup and working now. I also made all the Router Temperature expressions just Global ones, I was using a mixture of global and also local as I didn't realise I could use global expression values in the action with the $ wild card thing.

I will monitor my setup but I think its all working now.

Thank you.

[cw-kid]

@toggledbits

Hi Patrick.

I'm still not sure these Global Expressions are auto evaluating?

It's pretty hot here in the UK at the moment, been 27 degrees C today, still pretty hot now at midnight.

I just added additional fan cooling behind my router and its just dropped the CPU temp by another 4 degrees from 67 to 63.

However the Expression that makes the value pretty like 63.x degrees or whatever, for display on the Home Remote dashboard tile, did not auto evaluate as you can see in this screenshot.

I waited a while and it didn't update or change.

I then pressed the Play button on it and then it did update OK.

These should auto evaluate quite immediately right on any changes ?

Thanks.

EDIT: Looks like the CPU temp has just dropped again to 60 degrees but the other Global Expression hasn't evaluated or updated as you can see.

EDIT2:

And dropped again.

[cw-kid]

I've just updated to this version latest-23218-479da148 I will see how I get on with that.

UPDATE - I think this version is working I can see the Global Expressions auto evaluating.