Difference between Run Actions Rule and Pressing Run Actions Button?

[habitat]

Is there/ should there be a difference between having a Rule that is to Run Action in a Rule and actually pressing the Run Action button in the Rule.

I ask this because I am trying to debug something weird.

This Rule ran just fine for over three months and recently fails 90% of the time.

It fails because the TRVs do not open to 99% they remain stuck at 0%

So much so I restored to 2.2.6. But the problem remains.

So I put in this rule because at 6am the house goes from Night to Morning Mode and the Thermostat Controller changes target temp from 17c to 20.5c in the Lounge (amongst other zones )

So this runs every 15 mins to ensure that TRV Valves are either Open or Closed (should be by Trigger)
but the Trigger doesn't appear to work.

So when I checked at 8:30am in the morning the Lounge temp is 17c, the Trigger should have tripped at 6am, and the Kick Heating Zones has successfully run 10 times each times it should have opened the vales of the two radiators in the Lounge.

So suspecting issues with Rules here because why BOTH radiator valves not Open they should have opened on the first Trigger at 6am when the HeatDemandLounge=TRUE, or actually when the Kick rule plays.

Nope nothing, it looks like the Valve is showing that it has been set to 99% but the radiator is not changing temp at all.

But when I hit the Run Actions button - BANG the valves actually open.

The Radiator Temp goes up immediately - see Yellow line on the graph, this is a temp sensor sat on the radiator, the TRV Temp takes longer to react (Blue line)

So it appears when the Rule pushes the valves to open they don't but if you manually press the Rule button they do.

Anyway I can automate making the Rule run and actually get the valves to open?

Any diagnostic tests - anything else I can do?

[marktheknife]

Looks like you have logging enabled for your rules. Have you reviewed that? Log entries from the TRV at the times the rule is supposed to execute could be relevant too. Hard to say where the fault lies without more investigation.

[habitat]

Interesting,

Lounge TRV
Something is setting Valve back to 0

Starting at he bottom of the TRV Event log

Yellow box - The 15 minute Rule forcing the TRV controllers to set Valve settings runs and sets the valve to 0 CORRECT.

Blue Box - The Trigger - HeatDemandlounge=TRUE triggers set valve to 99% AND every 15 min rule runs and set Valve to 99% CORRECT

RED Box at 06:02:27 VALVE SET TO 0 - INCORRECT - need to find out what is setting this...

Then the next TWO GREENS where valve set to 99% and then 2 minutes 27 (28) seconds later valve gets set back to 0 INCORRECT

So now need to dumpster dive and work out what is setting the valves back to 0 2:27 after they get turned on

Investigating

[habitat]

The TRV is not used by much

The Dashboard or Battery monitor are unlikely to be resetting the Valve Levels

So next is the Trigger based upon HeatDemandLounge - which is behaving as expected.

[habitat]

I think the timing here is indicative of an automated process.

ie 2:27 min after the valve opens it receives instruction to close again.

147 seconds seems very specific..

Still investigating

[habitat]

The Lounge Front TRV is experiencing the same issue of keep getting reset back to 0

But not the Kitchen ( which is the other room still getting heat during spring in UK )

[habitat]

It looks like the Rule is running properly, in fact shouldn't need the check every 15 mins if the auto shut off was not occurring.

Any suggestions on how I find out what is telling the valve to shutdown?

I would say a rogue TRV except both Front and Back radiator TRVs have gone the same way at the same time and not others.

Still investigating - but any ideas on how to track down what is doing this would be much appreciated

[habitat]

OK gone through everything and NOTHING is resetting the Valves to 0.

So it appears the Radiator valves went rogue at the same time as 2.2.7.

So have remedied by sending valve instructions every 2 minutes to the rogue valves - see if that improves response.

Because right now, after several months of consistent reliable behaviour these TRVs are misbehaving and every time they get set to open the valve they auto reset the valve to 0% after 2:27 minutes has elapsed.

Will see how brute force works.

[habitat]

The Lounge radiator TRVs received and responded to the every two minute reminder of the valve setting and worked fine.

The kitchen TRV did not receive any instructions from the rule at all, several hundred Rule runs failed to send the command to the TRV.

This rule is failing to send instructions to the TRV anyone any idea why it is failing?

So throughout the night it should been sending valve level 0% every two minutes, none were recorded in the Rule log or device log.

Despite a two minute trigger it was not running.

Looking at the Lounge version, which was working, the log is packed with events.

The final kicker, and relates to the thread label.

If I push the button Run Actions, the rule sent the correct instructions to the TRV immediately.

So it looks like the Rule is broken and is not auctioning on the Triggers.

This is deeply troubling.

I’ll re-create the rule and see if it has the same issues.

But it does appear a Rule that looks all good, was working for several months can stop functioning without any indication of failure, which means frequently having to check that Rules are working as configured.

Which somewhat defeats the Automation in Home Automation.

I would love to be wrong here, and will work with anyone to disprove this, but it appears to be a fundamental flaw in HE.

[habitat]

Found this in the Application state for the Lounge

and this in the Kitchen Rule Application State

Where is bathroom referred to in the RULE?

Is it possible that this is why the Rules are failing?

[habitat]

I have created another Rule Identical to the first

Which is IDENTICAL to the manual copy I made

BUT when you look at the Settings the underlying config is different.

Original (Bad Suspended) Rule

And the manual duplicate Rule Settings

It looks like that even though the Rule appears good it is actually corrupted and that explains why the rule is inconsistent with the Rule/App is displayed ?

I assume there is some logic that explains why this Rule was failing,(silently) but operating as expected when manually executed.

Now going through ALL rules to see if they have become corrupted

[habitat]

@marktheknife I think I bottomed this issue out

Looks like the Rules retain previous config that have been removed and don't show unless you get into the Rules details.

I have created two completely new and identical to the Rules that were failing and the new rules are working where the old IDENTICAL rules were failing.

Not sure how to bring this to HE developers attention - they need to investigate this.

I am now going through re-creating ALL my Rules from scratch and will ensure that I do not edit a Rule in the future - get it right or delete it and start again.

Appears to be the work around until resolved.