Creating timeslot in Dashboard results in timeslot with wrong timezone in Steering

When I create a timeslot via Dashboard, it is recorded 2 hours earlier in Steering.

Steps to Reproduce

1. Create timeslot using Calendar View in Dashboard with start time 15:30.
2. Check the timeslot rendered by the Playout endpoint /steering/api/v1/playout

Expected Result

Actual Result

The Playout endpoint /steering/api/v1/playout returns a timeslot with start time at 13:30 this:

[
   {
      "id":25,
      "start":"2022-07-19T13:30:00",
      "end":"2022-07-19T13:50:00",
      "title":"Musikprogramm",
      "schedule_id":25,
      "is_repetition":false,
      "playlist_id":null,
      "schedule_default_playlist_id":null,
      "show_default_playlist_id":null,
      "show_id":1,
      "show_name":"Musikprogramm",
      "show_hosts":"Musikredaktion",
      "show_type":"Unmoderiertes Musikprogramm",
      "show_categories":"",
      "show_topics":"",
      "show_musicfocus":"",
      "show_languages":"",
      "show_fundingcategory":"Standard",
      "memo":"",
      "className":"danger"
   }
]

Environment

• Docker Compose aura-web
• Noticed the same behavior before with the Docker Compose provided in Steering too

changed milestone to %1.0-alpha2 — Precise Pheasant

added bug label

assigned to @nnrcschmdt

From the logs:

steering           | /usr/local/lib/python3.9/site-packages/django/db/models/fields/__init__.py:1358: RuntimeWarning: DateTimeField TimeSlot.start received a naive datetime (2022-07-19 00:00:00) while time zone support is active.
steering           |   warnings.warn("DateTimeField %s.%s received a naive datetime "

marked this issue as related to #69 (closed)

marked this issue as related to dashboard#88 (closed)

added P1 label

added discuss label

added To Do label

mentioned in issue aura#135 (closed)

added 1 deleted label

mentioned in issue aura#165 (closed)

removed discuss label

closed with commit 82eee15d

mentioned in commit aura@339bf978

removed To Do label