Global Moderators group | Smart Home

CatmanV2

@toggledbits this is precisely what it is, yes

C

CatmanV2

Sorry I tried to make it clear. For the avoidance of doubt the original post should (and shortly will) read
'Currently I am using the owntracks_sensor for tracking phones being in region in MSR and it works great.'

C

toggledbits

@CatmanV2 said in Expose MSR entities:

Currently I am using the owntracks_sensor for tracking phones being in region in HA and it works great.

I'm reading this as "it's coming from HA."

Is it actually an MQTT entity created using the owntracks_in_region template of MQTTController? Because there's nothing natively called owntracks_sensor in Reactor.

toggledbits

I am still completely confused. Yes, Reactor will publish the sensor from HA. I use that myself. But since the Reactor sensor entity comes from HA, why would want to publish Reactor's entity back to HA then?

toggledbits

I'll say again, local variables are not processed/evaluated in the same way as global variables. Local variables are only evaluated when the Rule to which they belong is being evaluated (i.e. its triggers are being checked). They are not evaluated when a dependent local variable is changed. When the Rule is evaluated, its local variables, if any, are evaluated before the triggers, and yes, they are evaluated in the order in which they are defined. That is known.

Combine this with using a Set Variable action... if you don't check the "Force re-evaluation" checkbox, any other local variables that use the variable being set will not be updated until the Rule is next evaluated. If you check the box, it forces a Rule evaluation, and it is the second evaluation that will update the dependent variables.

The Script Action is absolutely relevant in your case, at least from what you've posted, because you apparently still had local variables that are dependent on the local variable that the script was changing, and that was not consistent with my recommendation. The script will not cause the dependent variables to be updated, because there is no "Force re-evaluation" option for the script, and local variables are not dependency-scanned/triggered, as I said above. That means your script action will change the local variable ok_to_reset, but that won't make peak_power change immediately after. That is why I recommended that you make all local variables expressionless when using the Script Action, and do all of the work in the script, none of the work in the local variables' expressions.

None of this is new. And again, no changes have been made to how variables (global or local) in any of these recent builds. The earlier changes you mentioned to make isRuleSet() and isRuleEnabled() trigger with the rules they reference (build 25082 -- a long time ago) was a change to the implementation of those functions themselves , but was not in any way a change to the mechanism that handles changes in global expressions.

CatmanV2

Yes that was stupid of me! Sorry!

said in Expose MSR entities:

Currently I am using the owntracks_sensor for tracking phones being in region in

MSR! Not HA!

So the owntracks_sensor exists in MSR and works great. I'm wondering if there's an easy way to expose to HA

What a buffoon

C

toggledbits

@CatmanV2 said in Expose MSR entities:

Apologies if the ask is not clear/

Yeah, sorry. It's not at all clear to me what you're asking here. I'm reading "I have an owntracks_sensor in Home Assistant... is there any way to expose that sensor (which comes from Home Assistant) to Home Assistant trivially?" Uh... what?

CatmanV2

Probably a really dumb question.

Currently I am using the owntracks_sensor for tracking phones being in region in MSR and it works great.

Digging around with Home Assistant and toying with some dashboards, is there any way of exposing that sensor to HA trivially? I could set MSR to trip a virtual switch in OpenLuup which can then be exposed to HA (with all my other Vera devices) but that feels a bit in-elegant if I can do it directly.

Any thoughts?

Apologies if the ask is not clear/

TIA

C

toggledbits

Post your script. Based on the instructions given, your local variables should be expressionless, so that seems wrong and I want to see what your script is trying to do.

I can tell you right now, if ok_to_reset is expressionless and you are resetting it in the Script Action script, and expecting peak_power to see the updated value, it won't work.

therealdb

Yep, I confirm I had to update a couple of rules where I had similar variables as @tunnus
I used script action because it’s multi line and definitely better in terms of readability.

Global Moderators

Posts

Member List