You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the hour or minute Item is unitialized, getClockRule() generates a cron expression like 0 NaN NaN ? * MON *, which leads to openHAB errors.
To avoid that, hour and minute must be checked for NaN. getClockRule() may initialize hour/minute with a default value as the user cannot set those values in the openHAB iOS app or MainUI and needs either an Android device or the REST API in that case.
The text was updated successfully, but these errors were encountered:
* Fixes#9 where uninitialised hour/minute Items were parsed as NaN in the cron expression and led to errors in openhab-core.
* Initialises hour/minute in case their are NaN with default value.
* Additional refactorings were made.
When the hour or minute Item is unitialized,
getClockRule()
generates a cron expression like0 NaN NaN ? * MON *
, which leads to openHAB errors.To avoid that, hour and minute must be checked for NaN.
getClockRule()
may initialize hour/minute with a default value as the user cannot set those values in the openHAB iOS app or MainUI and needs either an Android device or the REST API in that case.The text was updated successfully, but these errors were encountered: