Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add more logging to RuleEngineImpl for debugging the cause of startup rule execution #1293

Closed
dominicdesu opened this issue Dec 23, 2019 · 0 comments · Fixed by #1812
Closed

Comments

@dominicdesu
Copy link

There are certain situation where startup rules are triggered but it is unclear why they have been triggered (see for example this thread).
For this case it would be very useful if the RuleEngineImpl had more logging output, especially in the allItemsChanged(), added() and modelChanged() methods (basically all methods which call scheduleStartupRules()), describing why the startup rules are executed.

lolodomo added a commit to lolodomo/openhab-core that referenced this issue Nov 12, 2020
Fix openhab#1293

Signed-off-by: Laurent Garnier <lg.hc@free.fr>
kaikreuzer pushed a commit that referenced this issue Nov 13, 2020
* Log reason for rules/scripts refresh

Fixes #1293

Signed-off-by: Laurent Garnier <lg.hc@free.fr>
Rosi2143 pushed a commit to Rosi2143/openhab-core that referenced this issue Dec 26, 2020
Signed-off-by: Kai Kreuzer <kai@openhab.org>
splatch pushed a commit to ConnectorIO/copybara-hab-core that referenced this issue Jul 11, 2023
* Log reason for rules/scripts refresh

Fixes openhab#1293

Signed-off-by: Laurent Garnier <lg.hc@free.fr>
GitOrigin-RevId: 8102cff
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant