Modbus configuration broken after update to 2024.4.1

Zapnologica · April 8, 2024, 5:24am

Good day,

My HA was working perfectly fine and using all my modbus sensors daily. I then updated to 2024.4.1 and then all my modbus sensors stopped working.

If I check the debug menu, I get this:

Here is my modbus.yaml file (I haven not edited this in months):

# cat modbus.yaml
# configuration entry for a TCP connection
# com.victronenergy.grid    slave: 30
# com.victronenergy.system  slave: 100
# com.victronenergy.battery slave: 225

# system :
- name: victron
  retry_on_empty: true
  retries: 5
  type: tcp
  host: 192.168.1.9
  port: 502
  # REMARK: scan_interval: <5 can cause troubles
  sensors:
    # Upstream AC Consumption
    # - name: "AC Consumption L1"
    #   unit_of_measurement: "W"
    #   slave: 100
    #   address: 817
    #   data_type: uint16
    #   scan_interval: 3
    #   device_class: power

    # L1 Grid power
    - name: "Multiplus Grid power"
      unit_of_measurement: "W"
      slave: 100
      address: 820
      data_type: int16
      scan_interval: 5
      device_class: power

any ideas what could be causing these issues?

makai · April 8, 2024, 6:22am

Hi,

What was the last working HA release?
Anything in the log?
Did you check the documentation?

Retry_on_empty is not a valid configuration. Remove it and retry.

dj-bauer · April 12, 2024, 1:43pm

I have the same issue with type: tcp as an invalid value.
Especially line 4 and line 9 is weird and seems very broken.

Invalid config for 'modbus' at modbus.yaml, line 3: required key 'bytesize' not provided, please check the docs at https://www.home-assistant.io/integrations/modbus
Invalid config for 'modbus' at modbus.yaml, line 3: required key 'method' not provided, please check the docs at https://www.home-assistant.io/integrations/modbus
Invalid config for 'modbus' at modbus.yaml, line 3: required key 'parity' not provided, please check the docs at https://www.home-assistant.io/integrations/modbus
Invalid config for 'modbus' at modbus.yaml, line 3: required key 'stopbits' not provided, please check the docs at https://www.home-assistant.io/integrations/modbus
Invalid config for 'modbus' at modbus.yaml, line 4: not a valid value for dictionary value 'modbus->0->type', got 'tcp', please check the docs at https://www.home-assistant.io/integrations/modbus
Invalid config for 'modbus' at modbus.yaml, line 5: 'close_comm_on_error' is an invalid option for 'modbus', check: modbus->0->close_comm_on_error, please check the docs at https://www.home-assistant.io/integrations/modbus
Invalid config for 'modbus' at modbus.yaml, line 9: 'host' is an invalid option for 'modbus', check: modbus->0->host, please check the docs at https://www.home-assistant.io/integrations/modbus
2024-04-12 15:15:58.725 ERROR (MainThread) [homeassistant.setup] Setup failed for 'modbus': Invalid config.

Mattie · April 16, 2024, 5:15pm

Has anyone upgraded to 2024.4.3 and can confirm if it was fixed?

TadasB · April 16, 2024, 8:29pm

Not fixed. I saw that it should be fixed in 2024.4.5 at best, so hold off for now.

Mattie · April 16, 2024, 8:47pm

Okay thanks for the info

Msperl · May 2, 2024, 4:23pm

I just tied 2024.5.0 just now and the problem still persists!

Is there any reference to git that would indicate that it gets fixed in a future release?

Msperl · May 5, 2024, 12:41pm

There has been a new issue opened in git related to this:

github.com/home-assistant/core

Modbus issue - SMA inverter

opened 09:25AM - 03 May 24 UTC

SonnyBBQ

I had referenced this in issue #116289 as well, but since that was closed, openi…ng as a new issue. The Modbus connection to SMA no longer works since upgrading to 2024.4. I'm currently on 2024.5 and the issue persists. What version of Home Assistant Core has the issue? 2024.4 onwards What was the last working version of Home Assistant Core? 2024.3.3 What type of installation are you running? Home Assistant OS Integration causing the issue Modbus Link to integration documentation on our website https://www.home-assistant.io/integrations/modbus/ Diagnostics information No response Example YAML snippet ``` modbus: - name: SMA type: tcp host: 192.168.1.223 #fixed ip in SMA 192.168.1.223 port: 502 sensors: - name: SMA_Power_AC unit_of_measurement: W slave: 3 address: 30775 data_type: int32 - name: PV Daily Yield unit_of_measurement: kWh slave: 3 address: 30517 scale: 0.001 precision: 3 data_type: uint64 - name: PV Total Production unit_of_measurement: MWh slave: 3 address: 30513 scale: 0.000001 precision: 3 data_type: uint64 - name: Grid Voltage unit_of_measurement: V slave: 3 address: 30783 scale: 0.01 precision: 2 data_type: uint32 - name: Grid frequency unit_of_measurement: Hz slave: 3 address: 30803 scale: 0.01 precision: 2 data_type: uint32 - name: SMA_temp unit_of_measurement: °C slave: 3 address: 30953 scale: 0.1 precision: 1 data_type: int32 - name: SMA_status slave: 3 address: 30201 data_type: uint32 - name: SMA_grid slave: 3 address: 30217 data_type: uint32 - name: Insulation slave: 3 address: 30225 scale: 0.001 unit_of_measurement: kOhms data_type: uint32 - name: SMA_Residual_current slave: 3 address: 31247 scale: 1 unit_of_measurement: mA data_type: int32 - name: Apparent Power unit_of_measurement: VA slave: 3 address: 30813 scale: 1 precision: 0 data_type: int32 - name: Reactive Power unit_of_measurement: VAr slave: 3 address: 30805 scale: 1 precision: 0 data_type: int32 ``` Anything in the logs that might be useful for us? ``` 2024-04-30 09:02:26.711 WARNING (MainThread) [pymodbus.logging] Failed to connect 2024-04-30 09:02:26.711 INFO (MainThread) [homeassistant.components.modbus.modbus] modbus SMA communication open 2024-04-30 09:02:27.372 ERROR (MainThread) [homeassistant.components.modbus.modbus] Pymodbus: SMA: Error: device: 3 address: 30775 -> Modbus Error: [Connection] Not connected[AsyncModbusTcpClient 192.168.1.223:502] 2024-04-30 09:02:27.372 DEBUG (MainThread) [homeassistant.components.modbus.modbus] Pymodbus: SMA: Error: device: 3 address: 30517 -> Modbus Error: [Connection] Not connected[AsyncModbusTcpClient 192.168.1.223:502] 2024-04-30 09:02:27.373 DEBUG (MainThread) [homeassistant.components.modbus.modbus] Pymodbus: SMA: Error: device: 3 address: 30513 -> Modbus Error: [Connection] Not connected[AsyncModbusTcpClient 192.168.1.223:502] 2024-04-30 09:02:27.373 DEBUG (MainThread) [homeassistant.components.modbus.modbus] Pymodbus: SMA: Error: device: 3 address: 30783 -> Modbus Error: [Connection] Not connected[AsyncModbusTcpClient 192.168.1.223:502] 2024-04-30 09:02:27.381 DEBUG (MainThread) [homeassistant.components.modbus.modbus] Pymodbus: SMA: Error: device: 3 address: 30803 -> Modbus Error: [Connection] Not connected[AsyncModbusTcpClient 192.168.1.223:502] 2024-04-30 09:02:27.381 DEBUG (MainThread) [homeassistant.components.modbus.modbus] Pymodbus: SMA: Error: device: 3 address: 30953 -> Modbus Error: [Connection] Not connected[AsyncModbusTcpClient 192.168.1.223:502] 2024-04-30 09:02:27.381 DEBUG (MainThread) [homeassistant.components.modbus.modbus] Pymodbus: SMA: Error: device: 3 address: 30201 -> Modbus Error: [Connection] Not connected[AsyncModbusTcpClient 192.168.1.223:502] 2024-04-30 09:02:27.381 DEBUG (MainThread) [homeassistant.components.modbus.modbus] Pymodbus: SMA: Error: device: 3 address: 30217 -> Modbus Error: [Connection] Not connected[AsyncModbusTcpClient 192.168.1.223:502] 2024-04-30 09:02:27.381 DEBUG (MainThread) [homeassistant.components.modbus.modbus] Pymodbus: SMA: Error: device: 3 address: 30225 -> Modbus Error: [Connection] Not connected[AsyncModbusTcpClient 192.168.1.223:502] 2024-04-30 09:02:27.382 DEBUG (MainThread) [homeassistant.components.modbus.modbus] Pymodbus: SMA: Error: device: 3 address: 31247 -> Modbus Error: [Connection] Not connected[AsyncModbusTcpClient 192.168.1.223:502] 2024-04-30 09:02:27.382 DEBUG (MainThread) [homeassistant.components.modbus.modbus] Pymodbus: SMA: Error: device: 3 address: 30813 -> Modbus Error: [Connection] Not connected[AsyncModbusTcpClient 192.168.1.223:502] 2024-04-30 09:02:27.382 DEBUG (MainThread) [homeassistant.components.modbus.modbus] Pymodbus: SMA: Error: device: 3 address: 30805 -> Modbus Error: [Connection] Not connected[AsyncModbusTcpClient 192.168.1.223:502] ValueError: Sensor sensor.modbus_sma_pv_power has device class 'None', state class 'None' unit 'W' and suggested precision 'None' thus indicating it has a numeric value; however, it has the non-numeric value: 'unavailable' (<class 'str'>) 2024-04-30 09:02:53.982 ERROR (MainThread) [homeassistant] Error doing job: Exception in callback <_OneTimeListener homeassistant.helpers.start:<function _async_at_core_state.<locals>._matched_event at 0x7f9b85aac720>>(<Event homeassistant_start[L]>) Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/components/sensor/__init__.py", line 668, in state numerical_value = float(value) # type:ignore[arg-type] ^^^^^^^^^^^^ ValueError: could not convert string to float: 'unavailable' The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run self._context.run(self._callback, *self._args) File "/usr/src/homeassistant/homeassistant/core.py", line 1322, in __call__ self.hass.async_run_hass_job(self.listener_job, event) File "/usr/src/homeassistant/homeassistant/core.py", line 837, in async_run_hass_job hassjob.target(*args) File "/usr/src/homeassistant/homeassistant/helpers/start.py", line 41, in _matched_event hass.async_run_hass_job(at_start_job, hass) File "/usr/src/homeassistant/homeassistant/core.py", line 837, in async_run_hass_job hassjob.target(*args) File "/usr/src/homeassistant/homeassistant/components/template/template_entity.py", line 491, in _async_template_startup result_info.async_refresh() File "/usr/src/homeassistant/homeassistant/helpers/event.py", line 1075, in async_refresh self._refresh(None) File "/usr/src/homeassistant/homeassistant/helpers/event.py", line 1261, in _refresh self.hass.async_run_hass_job(self._job, event, updates) File "/usr/src/homeassistant/homeassistant/core.py", line 837, in async_run_hass_job hassjob.target(*args) File "/usr/src/homeassistant/homeassistant/components/template/template_entity.py", line 439, in _handle_results self.async_write_ha_state() File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 998, in async_write_ha_state self._async_write_ha_state() File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1119, in _async_write_ha_state state, attr, capabilities, shadowed_attr = self.__async_calculate_state() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1056, in __async_calculate_state state = self._stringify_state(available) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1004, in _stringify_state if (state := self.state) is None: ^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/components/sensor/__init__.py", line 670, in state raise ValueError( ValueError: Sensor sensor.modbus_sma_pv_apparent_power has device class 'None', state class 'None' unit 'VA' and suggested precision 'None' thus indicating it has a numeric value; however, it has the non-numeric value: 'unavailable' (<class 'str'>) 2024-04-30 09:02:53.990 ERROR (MainThread) [homeassistant] Error doing job: Exception in callback <_OneTimeListener homeassistant.helpers.start:<function _async_at_core_state.<locals>._matched_event at 0x7f9b85aac9a0>>(<Event homeassistant_start[L]>) Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/components/sensor/__init__.py", line 668, in state numerical_value = float(value) # type:ignore[arg-type] ^^^^^^^^^^^^ ValueError: could not convert string to float: 'unavailable' The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run self._context.run(self._callback, *self._args) File "/usr/src/homeassistant/homeassistant/core.py", line 1322, in __call__ self.hass.async_run_hass_job(self.listener_job, event) File "/usr/src/homeassistant/homeassistant/core.py", line 837, in async_run_hass_job hassjob.target(*args) File "/usr/src/homeassistant/homeassistant/helpers/start.py", line 41, in _matched_event hass.async_run_hass_job(at_start_job, hass) File "/usr/src/homeassistant/homeassistant/core.py", line 837, in async_run_hass_job hassjob.target(*args) File "/usr/src/homeassistant/homeassistant/components/template/template_entity.py", line 491, in _async_template_startup result_info.async_refresh() File "/usr/src/homeassistant/homeassistant/helpers/event.py", line 1075, in async_refresh self._refresh(None) File "/usr/src/homeassistant/homeassistant/helpers/event.py", line 1261, in _refresh self.hass.async_run_hass_job(self._job, event, updates) File "/usr/src/homeassistant/homeassistant/core.py", line 837, in async_run_hass_job hassjob.target(*args) File "/usr/src/homeassistant/homeassistant/components/template/template_entity.py", line 439, in _handle_results self.async_write_ha_state() File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 998, in async_write_ha_state self._async_write_ha_state() File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1119, in _async_write_ha_state state, attr, capabilities, shadowed_attr = self.__async_calculate_state() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1056, in __async_calculate_state state = self._stringify_state(available) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1004, in _stringify_state if (state := self.state) is None: ^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/components/sensor/__init__.py", line 670, in state raise ValueError( ValueError: Sensor sensor.modbus_sma_pv_reactive_power has device class 'None', state class 'None' unit 'VAr' and suggested precision 'None' thus indicating it has a numeric value; however, it has the non-numeric value: 'unavailable' (<class 'str'>) 2024-04-30 09:02:53.996 ERROR (MainThread) [homeassistant] Error doing job: Exception in callback <_OneTimeListener homeassistant.helpers.start:<function _async_at_core_state.<locals>._matched_event at 0x7f9b85aacc20>>(<Event homeassistant_start[L]>) Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/components/sensor/__init__.py", line 668, in state numerical_value = float(value) # type:ignore[arg-type] ^^^^^^^^^^^^ ValueError: could not convert string to float: 'unavailable' The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run self._context.run(self._callback, *self._args) File "/usr/src/homeassistant/homeassistant/core.py", line 1322, in __call__ self.hass.async_run_hass_job(self.listener_job, event) File "/usr/src/homeassistant/homeassistant/core.py", line 837, in async_run_hass_job hassjob.target(*args) File "/usr/src/homeassistant/homeassistant/helpers/start.py", line 41, in _matched_event hass.async_run_hass_job(at_start_job, hass) File "/usr/src/homeassistant/homeassistant/core.py", line 837, in async_run_hass_job hassjob.target(*args) File "/usr/src/homeassistant/homeassistant/components/template/template_entity.py", line 491, in _async_template_startup result_info.async_refresh() File "/usr/src/homeassistant/homeassistant/helpers/event.py", line 1075, in async_refresh self._refresh(None) File "/usr/src/homeassistant/homeassistant/helpers/event.py", line 1261, in _refresh self.hass.async_run_hass_job(self._job, event, updates) File "/usr/src/homeassistant/homeassistant/core.py", line 837, in async_run_hass_job hassjob.target(*args) File "/usr/src/homeassistant/homeassistant/components/template/template_entity.py", line 439, in _handle_results self.async_write_ha_state() File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 998, in async_write_ha_state self._async_write_ha_state() File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1119, in _async_write_ha_state state, attr, capabilities, shadowed_attr = self.__async_calculate_state() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1056, in __async_calculate_state state = self._stringify_state(available) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1004, in _stringify_state if (state := self.state) is None: ^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/components/sensor/__init__.py", line 670, in state raise ValueError( ValueError: Sensor sensor.modbus_sma_pv_residual has device class 'None', state class 'None' unit 'mA' and suggested precision 'None' thus indicating it has a numeric value; however, it has the non-numeric value: 'unavailable' (<class 'str'>) 2024-04-30 09:02:54.003 ERROR (MainThread) [homeassistant] Error doing job: Exception in callback <_OneTimeListener homeassistant.helpers.start:<function _async_at_core_state.<locals>._matched_event at 0x7f9b85aacea0>>(<Event homeassistant_start[L]>) Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/components/sensor/__init__.py", line 668, in state numerical_value = float(value) # type:ignore[arg-type] ^^^^^^^^^^^^ ValueError: could not convert string to float: 'unavailable' The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run self._context.run(self._callback, *self._args) File "/usr/src/homeassistant/homeassistant/core.py", line 1322, in __call__ self.hass.async_run_hass_job(self.listener_job, event) File "/usr/src/homeassistant/homeassistant/core.py", line 837, in async_run_hass_job hassjob.target(*args) File "/usr/src/homeassistant/homeassistant/helpers/start.py", line 41, in _matched_event hass.async_run_hass_job(at_start_job, hass) File "/usr/src/homeassistant/homeassistant/core.py", line 837, in async_run_hass_job hassjob.target(*args) File "/usr/src/homeassistant/homeassistant/components/template/template_entity.py", line 491, in _async_template_startup result_info.async_refresh() File "/usr/src/homeassistant/homeassistant/helpers/event.py", line 1075, in async_refresh self._refresh(None) File "/usr/src/homeassistant/homeassistant/helpers/event.py", line 1261, in _refresh self.hass.async_run_hass_job(self._job, event, updates) File "/usr/src/homeassistant/homeassistant/core.py", line 837, in async_run_hass_job hassjob.target(*args) File "/usr/src/homeassistant/homeassistant/components/template/template_entity.py", line 439, in _handle_results self.async_write_ha_state() File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 998, in async_write_ha_state self._async_write_ha_state() File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1119, in _async_write_ha_state state, attr, capabilities, shadowed_attr = self.__async_calculate_state() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1056, in __async_calculate_state state = self._stringify_state(available) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1004, in _stringify_state if (state := self.state) is None: ^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/components/sensor/__init__.py", line 670, in state raise ValueError( ValueError: Sensor sensor.modbus_sma_temperature has device class 'None', state class 'None' unit '°C' and suggested precision 'None' thus indicating it has a numeric value; however, it has the non-numeric value: 'unavailable' (<class 'str'>) 2024-04-30 09:02:54.008 ERROR (MainThread) [homeassistant] Error doing job: Exception in callback <_OneTimeListener homeassistant.helpers.start:<function _async_at_core_state.<locals>._matched_event at 0x7f9b85aad120>>(<Event homeassistant_start[L]>) Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/components/sensor/__init__.py", line 668, in state numerical_value = float(value) # type:ignore[arg-type] ^^^^^^^^^^^^ ValueError: could not convert string to float: 'Not Measured' The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run self._context.run(self._callback, *self._args) File "/usr/src/homeassistant/homeassistant/core.py", line 1322, in __call__ self.hass.async_run_hass_job(self.listener_job, event) File "/usr/src/homeassistant/homeassistant/core.py", line 837, in async_run_hass_job hassjob.target(*args) File "/usr/src/homeassistant/homeassistant/helpers/start.py", line 41, in _matched_event hass.async_run_hass_job(at_start_job, hass) File "/usr/src/homeassistant/homeassistant/core.py", line 837, in async_run_hass_job hassjob.target(*args) File "/usr/src/homeassistant/homeassistant/components/template/template_entity.py", line 491, in _async_template_startup result_info.async_refresh() File "/usr/src/homeassistant/homeassistant/helpers/event.py", line 1075, in async_refresh self._refresh(None) File "/usr/src/homeassistant/homeassistant/helpers/event.py", line 1261, in _refresh self.hass.async_run_hass_job(self._job, event, updates) File "/usr/src/homeassistant/homeassistant/core.py", line 837, in async_run_hass_job hassjob.target(*args) File "/usr/src/homeassistant/homeassistant/components/template/template_entity.py", line 439, in _handle_results self.async_write_ha_state() File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 998, in async_write_ha_state self._async_write_ha_state() File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1119, in _async_write_ha_state state, attr, capabilities, shadowed_attr = self.__async_calculate_state() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1056, in __async_calculate_state state = self._stringify_state(available) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1004, in _stringify_state if (state := self.state) is None: ^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/components/sensor/__init__.py", line 670, in state raise ValueError( ValueError: Sensor sensor.modbus_grid_frequency has device class 'None', state class 'None' unit 'Hz' and suggested precision 'None' thus indicating it has a numeric value; however, it has the non-numeric value: 'Not Measured' (<class 'str'>) 2024-04-30 09:02:54.013 ERROR (MainThread) [homeassistant] Error doing job: Exception in callback <_OneTimeListener homeassistant.helpers.start:<function _async_at_core_state.<locals>._matched_event at 0x7f9b85aad440>>(<Event homeassistant_start[L]>) Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/components/sensor/__init__.py", line 668, in state numerical_value = float(value) # type:ignore[arg-type] ^^^^^^^^^^^^ ValueError: could not convert string to float: 'Not Measured' The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run self._context.run(self._callback, *self._args) File "/usr/src/homeassistant/homeassistant/core.py", line 1322, in __call__ self.hass.async_run_hass_job(self.listener_job, event) File "/usr/src/homeassistant/homeassistant/core.py", line 837, in async_run_hass_job hassjob.target(*args) File "/usr/src/homeassistant/homeassistant/helpers/start.py", line 41, in _matched_event hass.async_run_hass_job(at_start_job, hass) File "/usr/src/homeassistant/homeassistant/core.py", line 837, in async_run_hass_job hassjob.target(*args) File "/usr/src/homeassistant/homeassistant/components/template/template_entity.py", line 491, in _async_template_startup result_info.async_refresh() File "/usr/src/homeassistant/homeassistant/helpers/event.py", line 1075, in async_refresh self._refresh(None) File "/usr/src/homeassistant/homeassistant/helpers/event.py", line 1261, in _refresh self.hass.async_run_hass_job(self._job, event, updates) File "/usr/src/homeassistant/homeassistant/core.py", line 837, in async_run_hass_job hassjob.target(*args) File "/usr/src/homeassistant/homeassistant/components/template/template_entity.py", line 439, in _handle_results self.async_write_ha_state() File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 998, in async_write_ha_state self._async_write_ha_state() File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1119, in _async_write_ha_state state, attr, capabilities, shadowed_attr = self.__async_calculate_state() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1056, in __async_calculate_state state = self._stringify_state(available) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1004, in _stringify_state if (state := self.state) is None: ^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/components/sensor/__init__.py", line 670, in state raise ValueError( ValueError: Sensor sensor.modbus_grid_voltage has device class 'None', state class 'None' unit 'V' and suggested precision 'None' thus indicating it has a numeric value; however, it has the non-numeric value: 'Not Measured' (<class 'str'>) ``` Additional information Resetting the inverter will make the connection work for a limited time only. Couple hours at most. _Originally posted by @SonnyBBQ in https://github.com/home-assistant/core/issues/116289#issuecomment-2084569884_

But there is also this older issue:

github.com/home-assistant/core

Modbus configuration error

opened 01:21PM - 11 Apr 24 UTC

closed 02:02PM - 11 Apr 24 UTC

Fraserhardy

integration: modbus

### The problem Since upgrading to 2024.4.x I'm getting a configuration error f…or my modbus setup. It seems to be incorrectly complaining that I have missing 'required' keys. However these keys are not required for the type of connection I am using. I am using TCP connection type so baudrate, parity shouldn't be needed in the configuration. `Invalid config for 'modbus' at configuration.yaml, line 22: required key 'baudrate' not provided, please check the docs at https://www.home-assistant.io/integrations/modbus Invalid config for 'modbus' at configuration.yaml, line 22: required key 'bytesize' not provided, please check the docs at https://www.home-assistant.io/integrations/modbus Invalid config for 'modbus' at configuration.yaml, line 22: required key 'method' not provided, please check the docs at https://www.home-assistant.io/integrations/modbus Invalid config for 'modbus' at configuration.yaml, line 22: required key 'parity' not provided, please check the docs at https://www.home-assistant.io/integrations/modbus Invalid config for 'modbus' at configuration.yaml, line 22: required key 'stopbits' not provided, please check the docs at https://www.home-assistant.io/integrations/modbus Invalid config for 'modbus' at configuration.yaml, line 23: not a valid value for dictionary value 'modbus->0->type', got 'tcp', please check the docs at https://www.home-assistant.io/integrations/modbus Invalid config for 'modbus' at configuration.yaml, line 24: 'host' is an invalid option for 'modbus', check: modbus->0->host, please check the docs at https://www.home-assistant.io/integrations/modbus Invalid config for 'modbus' at configuration.yaml, line 29: 'retry_on_empty' is an invalid option for 'modbus', check: modbus->0->retry_on_empty, please check the docs at https://www.home-assistant.io/integrations/modbus Invalid config for 'modbus' at configuration.yaml, line 71: 'write_registers' is an invalid option for 'modbus', check: modbus->0->switches->0->write_registers, please check the docs at https://www.home-assistant.io/integrations/modbus` ### What version of Home Assistant Core has the issue? 2024.4.2 ### 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 modbus ### Link to integration documentation on our website https://www.home-assistant.io/integrations/modbus ### Diagnostics information _No response_ ### Example YAML snippet ```yaml modbus: - name: MC6-ModBus type: tcp host: 192.168.1.100 port: 502 delay: 1 timeout: 10 retries: 5 retry_on_empty: true message_wait_milliseconds: 200 climates: - name: "MC6" slave: 1 address: 0 target_temp_register: 64 target_temp_write_registers: true min_temp: 5 max_temp: 35 scan_interval: 30 temperature_unit: C data_type: int16 scale: 0.1 offset: 0 precision: 1 write_registers: true hvac_mode_register: address: 62 values: state_heat: 0 state_off: 5 write_registers: true hvac_onoff_register: 61 sensors: - name: "MC6-test-Humi" unit_of_measurement: "%" slave: 1 address: 2 scale: 1 offset: 0 precision: 0 - name: "MC6-Floor" unit_of_measurement: "c" slave: 1 address: 1 scale: 0.1 offset: 0 precision: 1 switches: - name: "Boost" address: 16 write_registers: true ``` ### Anything in the logs that might be useful for us? ```txt Invalid config for 'modbus' at configuration.yaml, line 22: required key 'baudrate' not provided, please check the docs at https://www.home-assistant.io/integrations/modbus Invalid config for 'modbus' at configuration.yaml, line 22: required key 'bytesize' not provided, please check the docs at https://www.home-assistant.io/integrations/modbus Invalid config for 'modbus' at configuration.yaml, line 22: required key 'method' not provided, please check the docs at https://www.home-assistant.io/integrations/modbus Invalid config for 'modbus' at configuration.yaml, line 22: required key 'parity' not provided, please check the docs at https://www.home-assistant.io/integrations/modbus Invalid config for 'modbus' at configuration.yaml, line 22: required key 'stopbits' not provided, please check the docs at https://www.home-assistant.io/integrations/modbus Invalid config for 'modbus' at configuration.yaml, line 23: not a valid value for dictionary value 'modbus->0->type', got 'tcp', please check the docs at https://www.home-assistant.io/integrations/modbus Invalid config for 'modbus' at configuration.yaml, line 24: 'host' is an invalid option for 'modbus', check: modbus->0->host, please check the docs at https://www.home-assistant.io/integrations/modbus Invalid config for 'modbus' at configuration.yaml, line 29: 'retry_on_empty' is an invalid option for 'modbus', check: modbus->0->retry_on_empty, please check the docs at https://www.home-assistant.io/integrations/modbus Invalid config for 'modbus' at configuration.yaml, line 71: 'write_registers' is an invalid option for 'modbus', check: modbus->0->switches->0->write_registers, please check the docs at https://www.home-assistant.io/integrations/modbus ``` ### Additional information _No response_

SonnyBBQ · May 16, 2024, 7:11am

Yep. And still not solved on my end. Sometimes it works for a few days, sometimes a few hours. But the connection will always break.
I have been repeating this at length on GitHub, my connection via Modbus had been working rock solid for years. With upgrade to 2024.4 things broke. No Hardware change, no firmware change on the SMA, no network change. The only thing was the upgrade to 2024.4, hence why I’m looking for the issue there.

Was thinking to bring this to SMA as well, but it seems there are issues with other devices too.