- Platform information:
- Hardware: Synology DS918+
- OS: DSM 7.0.1-42218 Update 3
- Java Runtime Environment: Contained in OH 3.2 docker image, no idea what that is
- openHAB version:3.2
- Issue of the topic:
I am trying to switch on the coffee machine each weekday at 06:00 am.
What I already achieved:
I can switch on the coffee machine using the OH web interface
What does not work?
None of my time based rules get executed. But the rules engine seems to be up and running because the following script does work. It switches the subwoofer to ON when the receiver powers on.
Example of rule which works:
configuration: {}
triggers:
- id: "1"
configuration:
itemName: DenonAVRX2200WAVRX2200W_Power
state: ON
type: core.ItemStateChangeTrigger
conditions: []
actions:
- inputs: {}
id: "2"
configuration:
command: ON
itemName: Subwoofer_Betrieb
type: core.ItemCommandAction
Now the script which does not work:
configuration: {}
triggers:
- id: "1"
configuration:
cronExpression: 0 0 6 * * ? *
type: timer.GenericCronTrigger
conditions: []
actions:
- inputs: {}
id: "2"
configuration:
command: ON
itemName: Kaffeemaschine_Betrieb
type: core.ItemCommandAction
Please note that I didn’t write the script but clicked it with the help of the “Design” tab.
My assumption is that for some reason no time events are sent to OH. the reason for that could be that my OH3.2 must run inside of a docker container (as Java 11 is not supported on DSM>7). I followed the instructions here: Synology DiskStation | openHAB. Now I am not an expert but could it be that the cron job is part of the OS. When OH runs inside the docker container perhaps the events of the surrounding OS with its cron service does not “reach” into the container?
Do you have any idea how to check whether any cron events reach OH? Some kind of hello world example to test whether timer events reach OH.
Or do you have any idea of how to resolve this issue?
- If logs where generated please post these here using code fences:
Here are the logs from the docker container where OH resides
|022-05-12 06:05:21|stdout|e[?1he=e[90m~e[0m e[?2004he[36mopenhab>e[0m |
|—|—|—|
|2022-05-11 20:49:34|stdout||
|2022-05-11 20:49:34|stdout|To exit, use ‘e[1me[0m’ or ‘e[1mlogoute[0m’.|
|2022-05-11 20:49:34|stdout|and ‘e[1m[cmd] --helpe[0m’ for help on a specific command.|
|2022-05-11 20:49:34|stdout|Use ‘e[1me[0m’ for a list of available commands|
|2022-05-11 20:49:34|stdout||
|2022-05-11 20:49:34|stdout|e[91m || e[0m 3.2.0 - Release Builde[0m|
|2022-05-11 20:49:34|stdout|e[91m ___/| / _/|| ||e[97m|| ||// _|/ e[0m|
|2022-05-11 20:49:34|stdout|e[91m | () | () | __/| | | |e[97m| _ | / ___ \ | |) )e[0m|
|2022-05-11 20:49:34|stdout|e[91m / _ \ / _ \ / _ \ / _ \ e[97m| || | / _ \ | _ \ e[0m|
|2022-05-11 20:49:34|stdout|e[91m ___ ___ ___ ___ e[97m| | | | / \ | __ ) e[0m|
|2022-05-11 20:49:34|stdout|e[91m e[97m _ _ _ ____ e[0m|
|2022-05-11 20:49:34|stdout||
|2022-05-11 20:49:15|stdout|Launching the openHAB runtime…|
|2022-05-11 20:49:15|stdout|+ exec gosu openhab tini -s ./start.sh|
|2022-05-11 20:49:15|stdout|+ ‘[’ true == false ‘]’|
|2022-05-11 20:49:14|stdout|+ sync|
|2022-05-11 20:49:14|stdout|+ ‘[’ -d /etc/cont-init.d ‘]’|
|2022-05-11 20:49:13|stdout|+ sync|
|2022-05-11 20:49:12|stdout|+ chown -R openhab:openhab /openhab|
|2022-05-11 20:49:12|stdout|+ ‘[’ ‘!’ -z ‘]’|
|2022-05-11 20:49:12|stdout|++ cmp /openhab/userdata/etc/version.properties /openhab/dist/userdata/etc/version.properties|
|2022-05-11 20:49:12|stdout|tmp’ ‘]’|
|2022-05-11 20:49:12|stdout|secrets|
|2022-05-11 20:49:12|stdout|persistence|
|2022-05-11 20:49:12|stdout|logs|
|2022-05-11 20:49:12|stdout|kar|
|2022-05-11 20:49:12|stdout|jsondb|
|2022-05-11 20:49:12|stdout|etc|
|2022-05-11 20:49:12|stdout|config|
|2022-05-11 20:49:12|stdout|+ ‘[’ -z ‘cache|
|2022-05-11 20:49:12|stdout|++ ls -A /openhab/userdata|
|2022-05-11 20:49:12|stdout|+ source=/openhab/dist/userdata|
|2022-05-11 20:49:12|stdout|+ volume=/openhab/userdata|
|2022-05-11 20:49:12|stdout|+ initialize_volume /openhab/userdata /openhab/dist/userdata|
|2022-05-11 20:49:12|stdout|transform’ ‘]’|
|2022-05-11 20:49:12|stdout|things|
|2022-05-11 20:49:12|stdout|sounds|
|2022-05-11 20:49:12|stdout|sitemaps|
|2022-05-11 20:49:12|stdout|services|
|2022-05-11 20:49:12|stdout|scripts|
|2022-05-11 20:49:12|stdout|rules|
|2022-05-11 20:49:12|stdout|persistence|
|2022-05-11 20:49:12|stdout|items|
|2022-05-11 20:49:12|stdout|icons|
|2022-05-11 20:49:12|stdout|html|
|2022-05-11 20:49:12|stdout|+ ‘[’ -z ‘automation|
|2022-05-11 20:49:12|stdout|++ ls -A /openhab/conf|
|2022-05-11 20:49:12|stdout|+ source=/openhab/dist/conf|
|2022-05-11 20:49:12|stdout|+ volume=/openhab/conf|
|2022-05-11 20:49:12|stdout|+ initialize_volume /openhab/conf /openhab/dist/conf|
|2022-05-11 20:49:12|stdout|+ id -u openhab|
|2022-05-11 20:49:12|stdout|Starting with openhab user id: 1028 and group id: 65536|
|2022-05-11 20:49:12|stdout|+ echo ‘Starting with openhab user id: 1028 and group id: 65536’|
|2022-05-11 20:49:12|stdout|+ NEW_GROUP_ID=65536|
|2022-05-11 20:49:12|stdout|+ NEW_USER_ID=1028|
|2022-05-11 20:49:12|stdout|+ rm -f /openhab/userdata/tmp/instances/instance.properties|
|2022-05-11 20:49:12|stdout|+ rm -f /openhab/runtime/instances/instance.properties|
|2022-05-11 20:49:12|stdout|+ ‘[’ limited = unlimited ‘]’|
|2022-05-11 20:49:12|stdout|’|
|2022-05-11 20:49:12|stdout|+ IFS=’|
|2022-05-11 20:45:22|stdout|e[?1le>e[?1000le[?2004l|
|2022-05-11 20:45:20|stdout|e[?1he=e[90m~e[0m e[?2004he[36mopenhab>e[0m |