Why do you say "corrupted"? Was this rule working and then stopped? I reproduced it and it seems to work as expected.
Sorry, I should have included more info.
The rule appears to be functioning correctly but when I click on Actions to make modifications I get:
and an error in the Logs:
Ive had this ... I needed to go into the gear icon and REMOVE it from there. Mine happened when I editted or deleted something and something got out of whack with the parser. There might be a way to fix it, but nuking it seemed the quicker path .. curious as to the actual method
Actually, in my case, just clicking into the rule would toss up the blank screen if I remember correctly
I've been tracking these down and finding ways to prevent or catch the cause. The cause is usually not obvious, so need something reproducible. This most likely is the consequence of some db corruption, assuming that none of the variables or device were removed. Sorry for the hassle.
My scenario is reproducible. Every time I click on the Actions I get the blank screen and error in the Logs.
Clicking on Triggers works as expected.
Please let me know if there is anything I can do to help debug.
No, it's how you got into this state in the first place that needs to be reproduced.
@bravenel is the state its in helpful at all? Still dont know how it got there, but what went wonk might help?
Not really. I need reproducible steps that lead to a broken rule. Something internal in Rule-5.1 gets off the rails, but after the fact it's pretty much too obscure to spend time on.
2 Likes
The weirded out rule was created by cloning another rule and replacing one temp sensor for another, tweaking values, rule name…
