-
-
Notifications
You must be signed in to change notification settings - Fork 429
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
"value too high" cron expression not accepted although expression is correct in OH2 #1813
Comments
mstormi
changed the title
Cron expression not accepted
"value too high" cron expression not accepted
Nov 13, 2020
mstormi
changed the title
"value too high" cron expression not accepted
"value too high" cron expression not accepted although expression is correct in OH2
Nov 28, 2020
Hilbrand
added a commit
to Hilbrand/openhab-core
that referenced
this issue
Dec 22, 2020
Closes openhab#1813 Signed-off-by: Hilbrand Bouwkamp <[email protected]>
kaikreuzer
pushed a commit
that referenced
this issue
Dec 22, 2020
Closes #1813 Signed-off-by: Hilbrand Bouwkamp <[email protected]>
Hello, |
@Besenreiter you could try and change "SAT-SUN" to "SAT,SUN" as a workaround. |
Thanks, I used the shnapshot, it's working |
cweitkamp
pushed a commit
that referenced
this issue
Jan 10, 2021
Closes #1813 Signed-off-by: Hilbrand Bouwkamp <[email protected]>
splatch
pushed a commit
to ConnectorIO/copybara-hab-core
that referenced
this issue
Jul 11, 2023
Closes openhab#1813 Signed-off-by: Hilbrand Bouwkamp <[email protected]> GitOrigin-RevId: df20138
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
using 3.0M3
I deployed a rule that was working fine under 2.5.10
Replacing "MON-SUN" with "*" fixes this so it's not critical but nonetheless this should be fixed in the cron code not in users' rules.
Related: #1516
The text was updated successfully, but these errors were encountered: