Timezones when scheduling firmware activation

We are trying to schedule a firmware activation in Star meters.
The system running our code currently runs in UTC+2 (Swedish summer time)
The meters runs in UTC+1 (Swedish normal time)
So we adjust the time to match the meters timezone like:
Ex.
var normalTime = firmwareInformation.ScheduleTime.Value.ToUniversalTime().AddSeconds(utcDiffSec);
var activateTime = new DateTimeOffset(normalTime.Year, normalTime.Month, normalTime.Day, normalTime.Hour, normalTime.Minute, normalTime.Second, normalTime.Millisecond, TimeSpan.FromSeconds(utcDiffSec));

var activationSchedule = new GXDLMSActionSchedule(scheduleLogicalName) { ExecutionTime = new[] { new GXDateTime( activateTime ) } };

utcDiffSec in this case is meters UTC offset in seconds (+3600).

When examining the GXDateTime object you can see that Value (that is a DateTimeOffset object) contains three DateTime properties:
- UtcDateTime which is the UTC time of what we entered, that is normalTime - utcDiffSec
- DateTime that contains the time we entered (normalTime)
- LocalDateTime which is a calculated value matching the systems timezone, DateTimeKind.Local

When this is sent to meter it seems that it is the LocalDateTime that is sent, and consequently meter schedules one hour to late in this example.

Shouldn't it be the DateTime object that should be sent? Or what are we doing wrong? As it is now we have to do a lot of manipulation to adjust for this, since there are no requirements in what timezone system should run, all we know is the timezone of the meter.