You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Logger: custom_components.solax_modbus
Source: custom_components/solax_modbus/init.py:707
integration: SolaX Inverter Modbus (documentation, issues)
First occurred: 11:56:11 AM (6 occurrences)
Last logged: 4:38:34 PM
Something went wrong reading from modbus
Traceback (most recent call last):
File "/config/custom_components/solax_modbus/init.py", line 707, in async_read_modbus_data
res = await self.async_read_modbus_registers_all(group)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/solax_modbus/init.py", line 895, in async_read_modbus_registers_all
data[descr.key] = descr.value_function(0, descr, data)
~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^
File "/config/custom_components/solax_modbus/plugin_solax.py", line 232, in value_function_battery_voltage_cell_difference
return datadict.get('cell_voltage_high', 0) - datadict.get('cell_voltage_low',0)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
TypeError: unsupported operand type(s) for -: 'NoneType' and 'NoneType'
Integration Version
2024.11.2
Homeassistant core version
core-2024.12.2
Inverter brand
Solax Power
Plugin used
plugin_solax.py
Serial prefix
H34A10
Inverter firmware versions
ARM1.44 DSP1.47
Connection Method
Packet Wifi + LAN 3.0
Dongle firmware
1.002.11
Detailed Error Log
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
I am getting the same error - means the readings are non sensical.
Logger: custom_components.solax_modbus
Source: custom_components/solax_modbus/init.py:707
integration: SolaX Inverter Modbus (documentation, issues)
First occurred: 16 December 2024 at 19:59:40 (38 occurrences)
Last logged: 07:06:33
Something went wrong reading from modbus
Traceback (most recent call last):
File "/config/custom_components/solax_modbus/init.py", line 707, in async_read_modbus_data
res = await self.async_read_modbus_registers_all(group)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/solax_modbus/init.py", line 895, in async_read_modbus_registers_all
data[descr.key] = descr.value_function(0, descr, data)
~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^
File "/config/custom_components/solax_modbus/plugin_solax.py", line 232, in value_function_battery_voltage_cell_difference
return datadict.get('cell_voltage_high', 0) - datadict.get('cell_voltage_low',0)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
TypeError: unsupported operand type(s) for -: 'NoneType' and 'NoneType'
Describe the bug
Logger: custom_components.solax_modbus
Source: custom_components/solax_modbus/init.py:707
integration: SolaX Inverter Modbus (documentation, issues)
First occurred: 11:56:11 AM (6 occurrences)
Last logged: 4:38:34 PM
Something went wrong reading from modbus
Traceback (most recent call last):
File "/config/custom_components/solax_modbus/init.py", line 707, in async_read_modbus_data
res = await self.async_read_modbus_registers_all(group)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/solax_modbus/init.py", line 895, in async_read_modbus_registers_all
data[descr.key] = descr.value_function(0, descr, data)
~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^
File "/config/custom_components/solax_modbus/plugin_solax.py", line 232, in value_function_battery_voltage_cell_difference
return datadict.get('cell_voltage_high', 0) - datadict.get('cell_voltage_low',0)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
TypeError: unsupported operand type(s) for -: 'NoneType' and 'NoneType'
Integration Version
2024.11.2
Homeassistant core version
core-2024.12.2
Inverter brand
Solax Power
Plugin used
plugin_solax.py
Serial prefix
H34A10
Inverter firmware versions
ARM1.44 DSP1.47
Connection Method
Packet Wifi + LAN 3.0
Dongle firmware
1.002.11
Detailed Error Log
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: