Hi everyone, I recently migrated from OpenHAB 2.5.11 to 3.0.0, and overall, the experience has been quite positive. However, I encountered a peculiar issue with some of my cron rules firing twice. Initially, I was a bit puzzled, but after some troubleshooting, I found a solution that might be helpful for others facing similar issues.### The ProblemAfter the migration, I noticed that certain cron rules were triggering twice. For example, a rule set to run at 6:05 AM was also firing at 6:04 AM. This was unexpected since the rule worked flawlessly in the previous version. The logs confirmed the double firing, which was both confusing and a bit concerning.### Steps Taken to Resolve1. Reviewing Logs: I started by examining the event logs to pinpoint the exact times the rules were firing. This helped me identify the pattern of double firing.2. Checking Time Synchronization: Ensuring that the Raspberry Pi’s time was synchronized with an NTP server was my next step. I verified that the time settings were correct and up-to-date.3. Rule Configuration: I carefully reviewed the cron rule configurations to ensure there were no syntax errors or unintended triggers. Everything seemed correct, so I moved on to testing.4. Testing with Simpler Rules: To isolate the issue, I created simpler cron rules to see if they exhibited the same behavior. Interestingly, these simpler rules worked as expected, which suggested that the issue was specific to more complex rules.### The SolutionAfter some research and experimentation, I discovered that the issue was related to how OpenHAB 3.0 handles certain cron expressions. Specifically, the problem arose with rules that included a wide range of days or had complex time specifications. To resolve this, I adjusted the cron expressions to be more precise and avoided using broad day ranges.### Tips for Others- Simplify and Test: When migrating or updating, start by testing simpler rules before moving on to more complex ones. This helps identify issues early.- Log Analysis: Always check the logs for patterns or anomalies. They can provide valuable insights into what’s going wrong.- Time Configuration: Ensure that all devices running OpenHAB have their time settings synchronized. Even a minor time discrepancy can cause unexpected behavior.### Closing ThoughtsWhile the double firing issue was a bit of a hiccup, resolving it gave me a deeper understanding of how cron jobs work in OpenHAB 3.0. It’s a reminder of how important it is to thoroughly test and monitor changes, especially during major updates. I’m glad to share this experience and hope it can help others avoid similar pitfalls.If anyone has encountered similar issues or has additional tips, I’d love to hear about them! Happy automating!