Standalone v8.40+ / Inverter type 'OTHER': WebSocket crash loop due to invalid service call input_datetime/set_value

[brunnwart]

Describe the bug

When running Predbat as a HA addon (v8.40+) with inverter_type: 'OTHER' and set_read_only: False, the system gets stuck in an infinite 10-second WebSocket error loop.

Predbat tries to write the charge window times to Home Assistant using the service input_datetime/set_value. However, this service does not exist in Home Assistant Core (the correct service name is input_datetime/set_datetime). As a result, Home Assistant rejects the call with a service_not_found error, causing Predbat to drop and reconnect the WebSocket continuously.

To Reproduce

1. Set inverter_type: 'OTHER'
2. Set set_read_only: False
3. Define charge_start_time, charge_end_time, etc. as input_datetime entities.
4. Watch the log during a calculation cycle.

Logs

Warn: Web Socket result failed {'id': 27, 'type': 'result', 'success': False, 'error': {'code': 'not_found', 'message': 'Service input_datetime.set_value not found.', 'translation_key': 'service_not_found', 'translation_placeholders': {'domain': 'input_datetime', 'service': 'set_value'}, 'translation_domain': 'homeassistant'}}
Warn: Service call input_datetime/set_value data {'value': '12:30:00', 'entity_id': 'input_datetime.charge_start_time'} failed

Expected behavior

Predbat should use the official Home Assistant Core service input_datetime.set_datetime instead of input_datetime.set_value when modifying input_datetime helpers in the OTHER inverter profile.

Environment

• Predbat Version: v8.40.6 (Standalone Add-on)
• Home Assistant Core: 2026.x
• Inverter Type: OTHER (MQTT / Victron Custom)

[springfall2008]

Fixed and will be in the .8 release