victron_ble: Sensor state value 'no_input_power|engine_shutdown' not in allowed options

[hhgerhard-google]

The problem

After restarting Home Assistant, the Victron BLE integration fails to initialize a sensor correctly. The integration tries to set a sensor value ( 'no_input_power|engine_shutdown' ) that is not in the list of expected options.

Steps to Reproduce:

• Start or restart Home Assistant.
• Ensure the victron_ble integration is active.
• The error occurs for the sensor Victron Orion TS Smart DC-DC charger (sensor.orion_smart_hq2228pvtdn_aus_ursache).

Expected behaviour:

• The sensor should accept the state correctly, even if the value no_input_power|engine_shutdown is reported by the device, without raising an error.

Actual behavior:

• Home Assistant log shows:
  ValueError: Sensor sensor.orion_smart_hq2228pvtdn_aus_ursache provides state value 'no_input_power|engine_shutdown', which is not in the list of options provided

Log Snippet:

• Logger: homeassistant.components.sensor
• Source: helpers/entity_platform.py:684
• Error adding entity sensor.orion_smart_hq2228pvtdn_aus_ursache for domain sensor with platform victron_ble
  ...
  ValueError: Sensor sensor.orion_smart_hq2228pvtdn_aus_ursache provides state value 'no_input_power|engine_shutdown', which is not in the list of options provided

What version of Home Assistant Core has the issue?

core-2026.1.3

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

victron_ble

Link to integration documentation on our website

https://www.home-assistant.io/integrations/victron_ble

Diagnostics information

Logger: homeassistant.components.bluetooth.manager
Quelle: components/bluetooth/manager.py:238
Integration: Bluetooth (Dokumentation, Probleme)
Erstmals aufgetreten: 21:20:43 (1 Vorkommnis)
Zuletzt protokolliert: 21:20:43

Error in bluetooth callback
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/bluetooth/manager.py", line 238, in async_register_callback
callback(service_info, BluetoothChange.ADVERTISEMENT)
~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/bluetooth/passive_update_processor.py", line 383, in _async_handle_bluetooth_event
self._process_update(update, was_available)
~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/bluetooth/passive_update_processor.py", line 409, in _process_update
processor.async_handle_update(update, was_available)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/bluetooth/passive_update_processor.py", line 624, in async_handle_update
self.async_update_listeners(new_data, was_available, changed_entity_keys)
~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/bluetooth/passive_update_processor.py", line 594, in async_update_listeners
update_callback(data)
~~~~~~~~~~~~~~~^^^^^^
File "/usr/src/homeassistant/homeassistant/components/bluetooth/passive_update_processor.py", line 693, in _handle_processor_update
self.async_write_ha_state()
~~~~~~~~~~~~~~~~~~~~~~~~~^^
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1024, in async_write_ha_state
self._async_write_ha_state()
~~~~~~~~~~~~~~~~~~~~~~~~~~^^
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1149, in _async_write_ha_state
self.__async_calculate_state()
~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1086, in __async_calculate_state
state = self._stringify_state(available)
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1030, in _stringify_state
if (state := self.state) is None:
^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/sensor/init.py", line 663, in state
raise ValueError(
...<2 lines>...
)
ValueError: Sensor sensor.orion_smart_hq2228pvtdn_aus_ursache provides state value 'no_input_power|engine_shutdown', which is not in the list of options provided

Logger: homeassistant.components.sensor
Quelle: helpers/entity_platform.py:684
Integration: Sensor (Dokumentation, Probleme)
Erstmals aufgetreten: 21:20:43 (1 Vorkommnis)
Zuletzt protokolliert: 21:20:43

Error adding entity sensor.orion_smart_hq2228pvtdn_aus_ursache for domain sensor with platform victron_ble
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 684, 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 1010, in _async_add_entity
await entity.add_to_platform_finish()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1380, in add_to_platform_finish
self.async_write_ha_state()
~~~~~~~~~~~~~~~~~~~~~~~~~^^
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1024, in async_write_ha_state
self._async_write_ha_state()
~~~~~~~~~~~~~~~~~~~~~~~~~~^^
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1149, in _async_write_ha_state
self.__async_calculate_state()
~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1086, in __async_calculate_state
state = self._stringify_state(available)
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1030, in _stringify_state
if (state := self.state) is None:
^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/sensor/init.py", line 663, in state
raise ValueError(
...<2 lines>...
)
ValueError: Sensor sensor.orion_smart_hq2228pvtdn_aus_ursache provides state value 'no_input_power|engine_shutdown', which is not in the list of options provided

Example YAML snippet

From ESP32 S3 ESPhome file, which is working as a bluetooth proxy:


substitutions:
  name: esp32-bluetooth-proxy-a38318
  friendly_name: Bluetooth Proxy a38318

packages:
  esphome.bluetooth-proxy: github://esphome/bluetooth-proxies/esp32-generic/esp32-generic-s3.yaml@main

esphome:
  name: ${name}
  name_add_mac_suffix: false
  friendly_name: ${friendly_name}

Anything in the logs that might be useful for us?

Additional information

The issue only occurs with certain status values (no_input_power|engine_shutdown).
All other sensors from the Victron BLE integration work correctly.
The problem occurs even when the Bluetooth Proxy (ESP32) is stable.
Likely a mapping/validation issue of sensor values within the integration.

[home-assistant]

Hey there @rajlaud, mind taking a look at this issue as it has been labeled with an integration (victron_ble) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of victron_ble can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign victron_ble Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component, problem in config, problem in device, feature-request) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component, problem in config, problem in device, feature-request) on the issue.

_{^{(message by CodeOwnersMention)}}

---

@hhgerhard-google Thanks for reporting this issue!

Before we dive in, please make sure this isn't a duplicate by searching through existing issues. Also check recently closed issues, as your problem might already be fixed but not yet released.

https://github.com/home-assistant/core/issues?q=%20label%3A%22integration%3A%20victron_ble%22%20
_{^{(message by IssueContext)}}

---

victron_ble documentation
victron_ble source
_{^{(message by IssueLinks)}}

[rajlaud]

Thank you for the detailed report. The issue is that off_reason is actually a bitmask that can have multiple options set on at once, but Home Assistant sensors need to to have a list of possible options so that we can provide translations.

I'm thinking through the right way to implement this. Having one binary sensor per off reason is an option, but seems a bit cumbersome.

[rajlaud]

Actually, in the most recent upstream library, the maintainer switched from FLAG to ENUM. This means that each combination needs to have its own state. There is a pending pull request to include a state for this exact combination: keshavdv/victron-ble#85

I'll bump to the latest version of the upstream library.

I'm also going to propose an update to victron_ble so that it handles unknown combinations of these bitmasks. Right now it creates a value error that kills the whole sensor update.