Hi @philh30 @Mariano_Colmenarejo, right now this is expected. On several platforms including V2/V3 we do not have any timezeone/locale information directly available on target or cannot really be trusted. Our best bet for a consistent local time provider would be to use information from the location in which the hub belongs which adds a bit of complexity.
For prioritizing any feature, do you have some specific examples of cases where local time is required for the correct operation of a driver? Many concerns that would normally require local time (e.g. turn on the lights at 7AM) are properly handled via automations rather than directly in drivers.