This is a script written for Openhab2. It is written in Jython and depends on the new jsr223 scripting feature. See jsr223 for more information. You need at least openhab 2.4 or newer.

• calendar: specifies the daily schedule that is to be run on a particular day.
• daily schedule: e.g. "workday" "weekend" "vacation". It defines the rules that are to be run a particular type of day.
• rule: defines the time/trigger and action to be run on which rollershutter.
• shading logic: create a shading model for each rollershutter and then have the script calculate if it is currently sunlit or not. (using the astro binding). Autoclose the rollershutter when window is sunlit.
• weather / sun sensor awareness: include info from weather binding and / or a sun sensor
• master automation ON/OFF switch
• entirely configured through yaml

• The script depends on: org.eclipse.smarthome.core.scheduler.CronExpression which still has bugs. E.g. 30.07.2017 does not match * * * ? * SAT,SUN *.
• Since the problems with o.e.s.c.scheduler do not seem to get fixed, I decided to replace it at least for the time being with quartz. It happened to be available in my environment. I think it was downloaded to the cache by the astro binding, but I'm not really sure. So, if it is not available in your environment, you may have to add the jar file to your boot directory.

The examples are not from an actual running config. There may very well be errors or inconsistencies. If you replace your config file with this repo you should get a working demo site.

The calendar specifies the daily schedule that is to be run on a particular day. E.g. you may define daily schedules like workday, weekend and vacation:

calendar:
  - desc: "Summer Vacation"
    timerange: {from: "12.06.2017", to: "25.06.2017" }
    daily_schedule: vacation
  - desc: "Weekends"
    cron: "? * 7,1 *"
    daily_schedule: weekend
  - desc: "Workdays"
    cron: "? * 2-6 *"
    daily_schedule: workday

It is possible to use time ranges or cron expressions ( without seconds, minutes, hours ). The cron expressions use the syntax from org.eclipse.smarthome.core.scheduler.CronExpression. (compatible with Quarz, see CronExpression )

The first match wins.

Daily schedules define lists of rules that are to be run on a specific type of day.

daily_schedules:
  weekend:
    - open_weekend
    - kids_evening
    - close_dusk
  workday:
    - open_workday
    - kids_open
    - kids_evening
    - close_dusk
  vacation:
    - open_workday
    - kids_open
    - close_dusk

Rules define triggers after which a set of rollershutters should be put into a specific state (action)

rules:
  open_weekend:
    desc: "Open all on weekends"
    triggers:
      - cron: '0 0 9'
    action: SUN
    items:
      - shutter_kitchen
      - shutter_office
      - shutter_living
      - shutter_kids
      - shutter_bedroom
  open_workday:
    desc: "Open all on workdays"
    triggers:
      - cron: '0 0 7'
    action: SUN
    items:
      - shutter_kitchen
      - shutter_office
      - shutter_living
      - shutter_bedroom
  kids_evening:
    desc: "Kids: close manually when kids are ready and don't open after sunset when kids already asleep"
    triggers:
      - cron: '0 30 19'
    action: MANUAL
    items:
      - shutter_kids
  kids_open:
    desc: "Kids: open in the morning"
    triggers:
      - cron: '0 0 8'
    conditions:
      - item_state: {item_name: 'condition_item', operator: '=', state: 'ON'}
    action: SUN
    items:
      - shutter_kids
  close_dusk:
    desc: "dusk: shut shutters after nightfall or at 22:00"
    triggers:
      - channel_event: {channel: 'astro:sun:local:nauticDusk#event', event: 'START'}
      - cron: '0 0 22'
    action: DOWN
    items:
      - shutter_kitchen
      - shutter_office
      - shutter_living
      - shutter_kids
      - shutter_bedroom

A set of Openhab2-items that have to exist and are used by the rollershutter script (they are defined in your <config_dir>/items/*.items files.)

items:
  azimuth: astro_sun_azimuth
  elevation: astro_sun_elevation
  weather_sunny: weather_sunny
  shutter_automation: shutter_automation

• azimuth & elevation: Items linked to the Astro binding e.g. defined as:

Number astro_sun_elevation  "Elevation [%.0f]" { channel="astro:sun:local:position#elevation" }
Number astro_sun_azimuth    "Azimuth [%.0f]"   { channel="astro:sun:local:position#azimuth" }

• weather_sunny: Switch item which is ON when the sun is shining. Could be from a weather binding or a sensor.

• shutter_automation: Switch item which allows for turning on/off the rollershutter automation.

This allows for modeling the window shading.

sun_exposure:
  shutter_living:
    orientation: 240
    sun_openings:
      - azimuth: 160
        below:
          - { azimuth: 240, elevation: 60}
        above:
          - { elevation: 5}
      - azimuth: 240
        below:
          - { azimuth: 240, elevation: 60}
          - { azimuth: 280, elevation: 10}
        above:
          - { azimuth: 240, elevation: 3}
      - azimuth: 280
        below:
          - { azimuth: 280, elevation: 60, angle: 35}
        above:
          - { azimuth: 240, elevation: 3}
      - azimuth: 330
  shutter_office:
    orientation: 150
    sun_openings:
      - azimuth: 160
      - azimuth: 330

• orientation: in which direction faces the window (perpendicular to the window's surface) E.g. 180 would mean a window facing south.
• sun_openings: series of sections (between two azimuths) where the sun is limited by two uniform obstacles from above and below.
• above & below: top and bottom limitation for the elevation of the sun beyond which the sun does not shine into the window.

• Obstacle following the horizon. E.g tree line far away.

  • { elevation: 5}

• Obstacle describing strait horizontal line. E.g a balcony above the window parallel to the window's surface. Azimuth & elevation can be any point on that line

  • { azimuth: 240, elevation: 60}

• Obstacle describing arbitrary strait line between two points. E.g. the roof partly shading the window.

  • { azimuth: 240, elevation: 60}
  • { azimuth: 280, elevation: 30}

• Alternatively, a line may also be described by a point and an angle:

  • { azimuth: 280, elevation: 60, angle: 35}

• The last azimuth defines the end of the last section:

  • azimuth: 330

• You need openhab 2.2.0 dated 20170729 or newer.

• Make sure you have the new rules support enabled.

• Install the jython library: Download jython-standalone-2.7.0.jar and install it in the boot folder: /usr/share/openhab2/runtime/lib/boot/

• Download snakeyaml-1.18.jar and install it in the addonsboot folder: /usr/share/openhab2/addons/usr/share/openhab2/runtime/lib/boot/.

• Install the contents of the automation folder in this repo in your automation folder: /etc/openhab2/automation. Note: You don't need 000_log.py if you already have some jython to openhab log bridge installed.

• You may want to add the following lines to your logging config.

log4j2.logger.jython.name = jython
log4j2.logger.jython.level = INFO

• Edit shutter_schedule.yml and shutters.yml according to your needs.

• In case your installation paths differ, change the paths in shutter.py variable: automationDir

• Create state items. You need two for each shutter. e.g. if you hava a shutter called shutter_kitchen define two additional Strings with the prefixes state_auto_ and state_sunlit_. Make them persistent.

Rollershutter shutter_kitchen         "RTS Kitchen"         (mysql)  { channel="rfxcom:rfy:0001:thing_rts_kitchen:shutter" }
String state_auto_shutter_kitchen     "RTS Kitchen AUTO"    (mysql)
String state_sunlit_shutter_kitchen   "RTS Kitchen SUNLIT"  (mysql)