OverflowError: date value out of range

[bpennypacker]

I just tried setting this up but it didn't seem to be doing anything. I found the debug log option and tried that. The logs are showing the below exception. Any thoughts on how to resolve this?

2026-03-11 14:09:19.507 ERROR (MainThread) [homeassistant.components.datetime] Error adding entity datetime.solarcharger_mqtt_tesla_ble_5yjygdee7mf190560_next_charge_time for domain datetime with platform solarcharger
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 680, in _async_add_entities
    await self._async_add_entity(
        entity, False, entity_registry, config_subentry_id
    )
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 998, in _async_add_entity
    await entity.add_to_platform_finish()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1393, in add_to_platform_finish
    await self.async_added_to_hass()
  File "/config/custom_components/solarcharger/datetime.py", line 62, in async_added_to_hass
    datetime.fromisoformat(last_state.state).astimezone(
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^
        ZoneInfo(self.hass.config.time_zone)
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    )
    ^
OverflowError: date value out of range
2026-03-11 14:09:22.533 WARNING (MainThread) [custom_components.solarcharger.utils] mqtt_tesla_ble_5yjygdee7mf190560: Saved callback: callback_ha_stop
2026-03-11 14:09:22.534 WARNING (MainThread) [custom_components.solarcharger.utils] mqtt_tesla_ble_5yjygdee7mf190560: Saved callback: callback_next_charge_time_update
2026-03-11 14:09:22.535 WARNING (MainThread) [custom_components.solarcharger.utils] mqtt_tesla_ble_5yjygdee7mf190560: Saved callback: callback_sun_elevation_update
2026-03-11 14:09:22.535 ERROR (MainThread) [custom_components.solarcharger.chargers.controller] mqtt_tesla_ble_5yjygdee7mf190560: Charger already stopped
2026-03-11 14:11:23.540 DEBUG (MainThread) [custom_components.solarcharger.coordinator] SolarChargerCoordinator _async_execute_update_cycle is running in event loop thread: True
2026-03-11 14:11:23.540 DEBUG (MainThread) [custom_components.solarcharger.sc_state] SolarChargerCoordinator: 'sensor.net_power' = '6'
2026-03-11 14:11:23.541 DEBUG (MainThread) [custom_components.solarcharger.coordinator] No running charger for net power allocation. Try again next cycle.

[flashg1]

Please check if your timezone is set up in HA?

Settings > System > General > Time zone

[bpennypacker]

Please check if your timezone is set up in HA?

Sorry, that was the first thing I checked. It's set to (GMT-05:00) Eastern Time

[bpennypacker]

And not sure if this is related or not, but I'm spotting some other exceptions as well:

2026-03-11 16:26:48.363 WARNING (MainThread) [custom_components.solarcharger.sc_state] mqtt_tesla_ble_5yjygdee7mf190560: Cannot get number: entity='number.tesla_ble_5yjygdee7mf190560_charging_limit', value='None'
2026-03-11 16:26:48.363 ERROR (MainThread) [custom_components.solarcharger.chargers.solar_charge] mqtt_tesla_ble_5yjygdee7mf190560: Error charging device: Cannot get charge limit
Traceback (most recent call last):
  File "/config/custom_components/solarcharger/chargers/solar_charge.py", line 851, in _async_charge_device
    self._running_goal = await self._scheduler.async_get_schedule_data(
                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    ...<4 lines>...
    )
    ^
  File "/config/custom_components/solarcharger/chargers/scheduler.py", line 329, in async_get_schedule_data
    goal.old_charge_limit = self._get_charge_limit_or_abort(chargeable)
                            ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^
  File "/config/custom_components/solarcharger/chargers/scheduler.py", line 132, in _get_charge_limit_or_abort
    raise EntityExceptionError("Cannot get charge limit")
custom_components.solarcharger.exceptions.entity_exception.EntityExceptionError: Cannot get charge limit
2026-03-11 16:26:48.367 WARNING (MainThread) [homeassistant.helpers.service] Referenced entities button.tesla_ble_5yjygdee7mf190560_force_update_charge are missing or not currently available
2026-03-11 16:27:18.708 INFO (MainThread) [backoff] Backing off async_request(...) for 0.9s (tesla_wall_connector.exceptions.WallConnectorConnectionTimeoutError: Timeout while connecting to Wall Connector at 172.16.1.183)
2026-03-11 16:27:48.368 WARNING (MainThread) [custom_components.solarcharger.sc_state] mqtt_tesla_ble_5yjygdee7mf190560: Cannot get number: entity='number.tesla_ble_5yjygdee7mf190560_charging_limit', value='None'
2026-03-11 16:27:48.369 ERROR (MainThread) [custom_components.solarcharger.chargers.solar_charge] mqtt_tesla_ble_5yjygdee7mf190560: Error charging device: Cannot get charge limit
Traceback (most recent call last):
  File "/config/custom_components/solarcharger/chargers/solar_charge.py", line 851, in _async_charge_device
    self._running_goal = await self._scheduler.async_get_schedule_data(
                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    ...<4 lines>...
    )
    ^
  File "/config/custom_components/solarcharger/chargers/scheduler.py", line 329, in async_get_schedule_data
    goal.old_charge_limit = self._get_charge_limit_or_abort(chargeable)
                            ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^
  File "/config/custom_components/solarcharger/chargers/scheduler.py", line 132, in _get_charge_limit_or_abort
    raise EntityExceptionError("Cannot get charge limit")
custom_components.solarcharger.exceptions.entity_exception.EntityExceptionError: Cannot get charge limit

[flashg1]

Just wondering was time zone set before you installed SolarCharger?

Try to reset the "Next charge time" value directly if you can access the local device config.

If not, this might or might not work because the value with incorrect time zone was saved by the system. Please try delete and re-add the integration. Instructions here.

[flashg1]

2026-03-11 16:26:48.363 ERROR (MainThread) [custom_components.solarcharger.chargers.solar_charge] mqtt_tesla_ble_5yjygdee7mf190560: Error charging device: Cannot get charge limit

Please check the value for charge limit entity in mqtt to make sure mqtt is working.

This error might be related to the timezone one. Need the whole log to determine.

[bpennypacker]

The Tesla MQTT integration is working properly. I'm able to do things like lock/unlock the car using it.

I uninstalled and reinstalled everything and that got rid of the MQTT related issues but not the time zone exception that I initially reported. So I added a logger line before the exception to log the value of last_state.state. It's showing:

2026-03-11 19:58:17.712 WARNING (MainThread) [custom_components.solarcharger.datetime] [0001-01-01T00:00:00+00:00]

That looks like a default value that could very well be the cause of the date value out of range error.

[flashg1]

Thanks. Let me investigate and get back to you.

Try to reset the "Next charge time" value directly if you can access the local device config.

Are you able to reset the value? Ie. Settings > Device and service> SolarCharger> mqtt charger> Next charge time

[flashg1]

I am not able to reproduce the problem, possibly due to hardware/OS differences. Are you using HA OS or some other hardware?

I worked around the issue by catching the exception for min datetime UTC. Not sure if this is acceptable. Not sure if you are able to set the value in Settings > Device and service> SolarCharger> mqtt charger> Next charge time?

Please test with the v0.4.1-beta2. Please see instructions on how to download.

[flashg1]

Please try this version instead

https://github.com/flashg1/SolarCharger/releases/tag/v0.4.1-beta3

• Catch possible exception converting UTC min time to local time during restore, and just set to UTC min time without conversion.

It is still a work-around, but should be a better fix.

[bpennypacker]

Thanks. I'll give it a try and let you know. We didn't get any sun today and don't expect a lot over the next few days either, so it may be a few days before I can really test it out.

[bpennypacker]

I installed v0.4.1-beta3 and also manually set what I think is Next charge time (the GUI has squashed things so I didn't recognize it at first). The initial exceptions I reported are no longer showing up, and I've done some more troubleshooting. I now started seeing this exception:

2026-03-13 05:00:58.076 WARNING (MainThread) [homeassistant.helpers.service] Referenced entities button.tesla_ble_5yjygdee7mf190560_wake_up_car are missing or not currently available
2026-03-13 05:01:38.078 WARNING (MainThread) [homeassistant.helpers.service] Referenced entities button.tesla_ble_5yjygdee7mf190560_force_update_charge are missing or not currently available
2026-03-13 05:02:03.082 WARNING (MainThread) [custom_components.solarcharger.sc_state] mqtt_tesla_ble_5yjygdee7mf190560: Cannot get number: entity='number.tesla_ble_5yjygdee7mf190560_charging_limit', value='None'
2026-03-13 05:02:03.082 ERROR (MainThread) [custom_components.solarcharger.chargers.solar_charge] mqtt_tesla_ble_5yjygdee7mf190560: Error charging device: Cannot get charge limit
Traceback (most recent call last):
  File "/config/custom_components/solarcharger/chargers/solar_charge.py", line 908, in _async_charge_device
    self._running_goal = await self._scheduler.async_get_schedule_data(
                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

I tried to manually check on the entity number.tesla_ble_5yjygdee7mf190560_charging_limit but it didn't seem to exist. If I go into Settings -> Developer Tools -> States and filter on tesla_ble_5yjygdee7mf190560_ I saw a number of entities like number.solarcharger_mqtt_tesla_ble_5yjygdee7mf190560_charger_max_current that all show valid looking values, but none with a name like charging_limit, or anything containing the word limit for that matter.

Based on the above, something occurred to me. When I set up my Tesla BLE MQTT docker device I when into my MQTT settings and renamed the device to Tesla_Local to make it clear to me that it was the local BLE device for my car. I do have a number.tesla_local_charge_limit entity available that looks like what it's trying to access. So I did some more testing. I deleted the custom name of the MQTT device, leaving it as the default Tesla_BLE_5YJYGDEE7MF190560, and had HA rename all the entity IDs. After doing all that and rescheduling the next charging time again it seems to have started working.

So it looks like there's some sort of issue where SolarCharger will work if you stick with the default name of the MQTT device, but if you rename it for any reason then SolarCharger will get confused.

Somehow the Next Charge Time also reverted to January 1, 2026 for some reason during all my troubleshooting. I'm not sure why that happened, but resetting it to a later time got it working.

[flashg1]

Glad that it is working for you.

So it looks like there's some sort of issue where SolarCharger will work if you stick with the default name of the MQTT device, but if you rename it for any reason then SolarCharger will get confused.

Please see here on how to rename in SC.

"Next charge time" is for internal use only. Please check out the user guide.

When you have a spare moment, could you please update these 2 threads?

charger API
inverter brand

Thanks