-
-
Notifications
You must be signed in to change notification settings - Fork 33
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Adding more preprocessing to rule line evaluation
- Loading branch information
Showing
2 changed files
with
36 additions
and
3 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
2ec5b36
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure, if it's my installation, but since this commit no task is automatically executed anymore (at
interval
).I see a lot of:
Plugin SendData Exception: can't start new thread ['1', 0, 0, 0]
and
!Parsed line: sendToHTTP,10.0.0.1,8072,/fhem?cmd=setreading%20rpieasy_02_ch05%20speed%20%eventvalue% can't start new thread
in the logfile.
2ec5b36
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
interesting. looks like you find a way to create an endless loop.
please attach full rules.
did you tried to comment out line 1273 in commands.py?
2ec5b36
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Commenting out line 1273 seems to solve the issue.
Rules did not change and are more or less identical to what I use on ESPEasy (FIY: currently I have a ESPEasy node running productively which does exact the same as this RPIEasy unit, just that the GPIO's are physically connected to the ESPEasy and, at some point in time, I plan to move them to the RPI, that's why I test quite thouroughly, as I use this node to run my complete pool control/management, and I don't want to get flooded or similar π ....)
Full Ruleset:
2ec5b36
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanx, i will test it!
2ec5b36
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
PS: probably a small explanation why I use these
ch<nr>r
events: as in ESPeasy a change of a physical PCFGPIO (input) switches the assiciated task with that value and generates an event. Now when changing the same PCFGPIO with a command from somewhere else (eg. a rule or form the server) it would generate an endless loop. This is because you can use PCFGPIO's as input and output in parallel.2ec5b36
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Recursion fixed in commit 6586a67
2ec5b36
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Did a quick check, seems to be ok again. Thanks for the quick fix!!
2ec5b36
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanx for testing!